Skulist Dept
In ScopeTechnical: SKULIST_DEPT | ID: OR-MFCS-SKULIST_DEPT
If using data level security in RMS, this table is used to hold all the department/class/subclass combinations that are valid for the item list. Only users with access to these department/class/subclass combinations can view or use this item list.
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
- SKULIST_DEPT
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 SKULIST_DEPT 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 (4)
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 SKULIST_DEPT 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.)