Purchase Order
In ScopeTechnical: PURCHASE_ORDER | ID: OR-SIOCS-PURCHASE_ORDER
Stores one row for each purchase order per location that has been placed by the company.the purchase order may have been created via a merchandise system message or when a user starts to process a shipment in sim. completed purchase orders may be purged from the table via the purgedata function.
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
- PURCHASE_ORDER
Implementation Considerations
Use Cases
Initial load, rehearsal loads, cutover
Sequencing
Load during Open Transactions to stage transactional records only after prerequisite master data and opening positions are stable. Load once prerequisite cross-domain reference data is available so PURCHASE_ORDER 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 (18)
Typical Source Systems
Notes
Load during Open Transactions to stage transactional records only after prerequisite master data and opening positions are stable. Load once prerequisite cross-domain reference data is available so PURCHASE_ORDER 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.)