UDA
In ScopeTechnical: UDA | ID: OR-MFCS-UDA
Stores one row for each Used-Defined Attribute (UDA) defined within the RMS. Generally, a UDA is any attribute that does not have specific processing in the RMS.
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
- UDA
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 UDA can be established cleanly. Load before UDA Values because those downstream processes consume or reference this object. (Inferred from vendor object description, current scope dependencies, and Oracle Retail SIOCS 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 once prerequisite cross-domain reference data is available so UDA can be established cleanly. Load before UDA Values because those downstream processes consume or reference this object. (Inferred from vendor object description, current scope dependencies, and Oracle Retail SIOCS documentation.)