Merch Hier Default
In ScopeTechnical: MERCH_HIER_DEFAULT | ID: OR-MFCS-MERCH_HIER_DEFAULT
This table will hold the default structures defined for the merchandise hierarchy. This table will allow the client to use his business process to either make some kinds of attributes or options available or not available.
See how this object fits into Item 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
- MERCH_HIER_DEFAULT
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 MERCH_HIER_DEFAULT can be established cleanly. Sequence this object with its item 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 (11)
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 MERCH_HIER_DEFAULT can be established cleanly. Sequence this object with its item management peers so MFCS processing can consume it without synthetic defaults. (Inferred from vendor object description, current scope dependencies, and Oracle Retail MFCS documentation.)
