RPM Clearance
In ScopeTechnical: RPM_CLEARANCE | ID: OR-RPCS-RPM_CLEARANCE
Stores one row for each clearance event stored within Pricing. It stores item information, location information, and the retail change information.
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_CLEARANCE
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 after Item Master and Store so clearance records in RPM_CLEARANCE can resolve required parent references. 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 (38)
Typical Source Systems
Notes
Load during Master Data to establish foundational reference data before dependent setup or transactional loads. Load after Item Master and Store so clearance records in RPM_CLEARANCE can resolve required parent references. 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.)
