Subclass
In ScopeTechnical: SUBCLASS | ID: OR-MFCS-SUBCLASS
Stores one row for each department/subclass combination within the company. Whenever a subclass name is used by Oracle Retail, or a subclass is validated, it is always selected from this table.
See how this object fits into Foundation Data
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
- SUBCLASS
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 after Class so subclass records in SUBCLASS can resolve required parent references. Load before Item Master because those downstream processes consume or reference this object. (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 (15)
Typical Source Systems
Notes
Load during Master Data to establish foundational reference data before dependent setup or transactional loads. Load after Class so subclass records in SUBCLASS can resolve required parent references. Load before Item Master because those downstream processes consume or reference this object. (Inferred from vendor object description, current scope dependencies, and Oracle Retail MFCS documentation.)
