RPM Bulk Cc Pe Thread
In ScopeTechnical: RPM_BULK_CC_PE_THREAD | ID: OR-RPCS-RPM_BULK_CC_PE_THREAD
Stores the price events that need to be bulk conflict checked that is requested by a bulk cc request from the client. the price events are grouped by the sequence (parent_thread_number) and thread number.
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_BULK_CC_PE_THREAD
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_BULK_CC_PE_THREAD 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 (39)
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_BULK_CC_PE_THREAD 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.)
