Non Merch Code Comp
In ScopeTechnical: NON_MERCH_CODE_COMP | ID: OR-MFCS-NON_MERCH_CODE_COMP
This table will provide a cross-reference to identify which invoice non-merchandise code represents each landed cost component. When invoices are automatically created from obligations or customs entries, landed cost components will be rolled up into the specified non-merchandise cost bucket on the invoice.
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
- NON_MERCH_CODE_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 once prerequisite cross-domain reference data is available so NON_MERCH_CODE_COMP can be established cleanly. 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 (2)
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 NON_MERCH_CODE_COMP can be established cleanly. 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.)
