Store
In ScopeTechnical: STORE | ID: OR-MFCS-STORE
Stores one row for each store within the company.
See how this object fits into Foundation Data
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
- STORE
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 District so store records in STORE can resolve required parent references. Load before Clearance, Item Location, Physical Inventory Count, Price Change, Promotional Price, Purchase Order Header, Purchase Order Location, RPM Price Zone, Sales Audit Store Data, Stock Allocation Detail, Store Day, Supplier Org Unit, and Transfer Header because those downstream processes consume or reference this object. (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 (54)
Typical Source Systems
Notes
Load during Master Data to establish foundational reference data before dependent setup or transactional loads. Load after District so store records in STORE can resolve required parent references. Load before Clearance, Item Location, Physical Inventory Count, Price Change, Promotional Price, Purchase Order Header, Purchase Order Location, RPM Price Zone, Sales Audit Store Data, Stock Allocation Detail, Store Day, Supplier Org Unit, and Transfer Header because those downstream processes consume or reference this object. (Inferred from vendor object description, current scope dependencies, and Oracle Retail SIOCS documentation.)
