Ordloc

In Scope

Technical: ORDLOC | ID: OR-MFCS-ORDLOC

Stores one row for each order/SKU/store or warehouse combination that has been placed by the company. When an order header is purged all associated rows in this table are also purged.

See how this object fits into Purchasing

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
ORDLOC

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 after Purchase Order Header, Purchase Order Detail, Store, and Warehouse so purchase order location records in ORDLOC can resolve required parent references. Sequence this object with its purchasing peers so MFCS processing can consume it without synthetic defaults. (Inferred from vendor object description, current scope dependencies, and Oracle Retail MFCS documentation.)

Cutover

Load during Stage 2 / .

Data Governance

Requires business ownership and source-to-target crosswalk governance.

Field Definitions (27)

Typical Source Systems

ERPLegacy

Notes

Load during Open Transactions to stage transactional records only after prerequisite master data and opening positions are stable. Load after Purchase Order Header, Purchase Order Detail, Store, and Warehouse so purchase order location records in ORDLOC can resolve required parent references. Sequence this object with its purchasing peers so MFCS processing can consume it without synthetic defaults. (Inferred from vendor object description, current scope dependencies, and Oracle Retail MFCS documentation.)