Obligation Comp
In ScopeTechnical: OBLIGATION_COMP | ID: OR-MFCS-OBLIGATION_COMP
Stores the detail level information found on an obligation (i.e. bill or invoice) sent to the client for expenses or assessments incurred while bringing goods from point A to point B.
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_COMP
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 Import Obligation Header so import obligation components records in OBLIGATION_COMP can resolve required parent references. Sequence this object with its trade management 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 (9)
Typical Source Systems
Notes
Load during Open Transactions to stage transactional records only after prerequisite master data and opening positions are stable. Load after Import Obligation Header so import obligation components records in OBLIGATION_COMP can resolve required parent references. Sequence this object with its trade management peers so MFCS processing can consume it without synthetic defaults. (Inferred from vendor object description, current scope dependencies, and Oracle Retail MFCS documentation.)