RPM Zone Location
In ScopeTechnical: RPM_ZONE_LOCATION | ID: OR-RPCS-RPM_ZONE_LOCATION
table that determines which stores and/or warehouses are assigned to a given zone.
See how this object fits into Pricing & Promotions
Review the broader sequencing and dependencies for this domain
Migration Details
- Complexity
- Medium
- Stage
- Stage 2
- Cutover Wave
- —
- Dependency Level
- —
Dependencies
No dependencies
Target Structure
- Load API
- Table
- Target Objects
- RPM_ZONE_LOCATION
Implementation Considerations
Use Cases
Initial load, rehearsal loads, cutover
Sequencing
Load during Master Data to establish foundational reference data before dependent setup or transactional loads. Load once prerequisite cross-domain reference data is available so RPM_ZONE_LOCATION can be established cleanly. Sequence this object with its pricing & promotions peers so RPCS processing can consume it without synthetic defaults. (Inferred from vendor object description, current scope dependencies, and Oracle Retail RPCS documentation.)
Cutover
Load during Stage 2 / .
Data Governance
Requires business ownership and source-to-target crosswalk governance.
Field Definitions (6)
Typical Source Systems
Notes
Load during Master Data to establish foundational reference data before dependent setup or transactional loads. Load once prerequisite cross-domain reference data is available so RPM_ZONE_LOCATION can be established cleanly. Sequence this object with its pricing & promotions peers so RPCS processing can consume it without synthetic defaults. (Inferred from vendor object description, current scope dependencies, and Oracle Retail RPCS documentation.)