Mod Order Item HTS
In ScopeTechnical: MOD_ORDER_ITEM_HTS | ID: OR-MFCS-MOD_ORDER_ITEM_HTS
This table is used for reporting purposes to show which items and order/items are impacted after HTS upload program has been processed. It will be purged prior to HTS upload execution.
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
- MOD_ORDER_ITEM_HTS
Implementation Considerations
Use Cases
Initial load, rehearsal loads, cutover
Sequencing
Load during Master Data to establish foundational reference data before dependent setup or transactional loads. Load once prerequisite cross-domain reference data is available so MOD_ORDER_ITEM_HTS 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 (9)
Typical Source Systems
Notes
Load during Master Data to establish foundational reference data before dependent setup or transactional loads. Load once prerequisite cross-domain reference data is available so MOD_ORDER_ITEM_HTS 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.)