Item Price
In ScopeTechnical: ITEM_PRICE | ID: OR-SIOCS-ITEM_PRICE
the table holds one row for each price change. these can either be created by sim, if the store is allowed to control the pricing or they are loaded in from an external system (i.e.
See how this object fits into Store Operations
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
- ITEM_PRICE
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 ITEM_PRICE can be established cleanly. Sequence this object with its store operations peers so SIOCS processing can consume it without synthetic defaults. (Inferred from vendor object description, current scope dependencies, and Oracle Retail SIOCS documentation.)
Cutover
Load during Stage 2 / .
Data Governance
Requires business ownership and source-to-target crosswalk governance.
Field Definitions (31)
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 ITEM_PRICE can be established cleanly. Sequence this object with its store operations peers so SIOCS processing can consume it without synthetic defaults. (Inferred from vendor object description, current scope dependencies, and Oracle Retail SIOCS documentation.)