Obligation
In ScopeTechnical: OBLIGATION | ID: OR-MFCS-OBLIGATION
Stores the header level information found on an obligation (i.e. bill or invoice) sent to the client for expenses incurred while bringing goods into an origin country and to its final destination.
See how this object fits into Trade Management
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
- OBLIGATION
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, Supplier, Harmonised Tariff Schedule, and Country so import obligation header records in OBLIGATION can resolve required parent references. Load before Import Obligation Components because those downstream processes consume or reference this object. (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 (23)
Typical Source Systems
Notes
Load during Open Transactions to stage transactional records only after prerequisite master data and opening positions are stable. Load after Purchase Order Header, Supplier, Harmonised Tariff Schedule, and Country so import obligation header records in OBLIGATION can resolve required parent references. Load before Import Obligation Components because those downstream processes consume or reference this object. (Inferred from vendor object description, current scope dependencies, and Oracle Retail MFCS documentation.)