Ordhead Lock
In ScopeTechnical: ORDHEAD_LOCK | ID: OR-MFCS-ORDHEAD_LOCK
This table will be used to provide a locking mechanism within the on-line purchasing dialog. There should be a one-to-one relationship with the orders stored on ordhead.
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
- ORDHEAD_LOCK
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 ORDHEAD_LOCK can be established cleanly. 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 (1)
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 ORDHEAD_LOCK can be established cleanly. 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.)