Wo Activity
In ScopeTechnical: WO_ACTIVITY | ID: OR-MFCS-WO_ACTIVITY
Stores information for the work orders that can be attached to a transfer for carrying out finishing activities on items while at a finisher location. Finishing activities are small value additions to the goods, for example adding a monogram to the shirts or reticketing merchandise.
See how this object fits into Inventory 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
- WO_ACTIVITY
Implementation Considerations
Use Cases
Initial load, rehearsal loads, cutover
Sequencing
Load during Open Transactions to stage transactional records only after prerequisite master data and opening positions are stable. Load once prerequisite cross-domain reference data is available so WO_ACTIVITY can be established cleanly. Sequence this object with its inventory 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 (5)
Typical Source Systems
Notes
Load during Open Transactions to stage transactional records only after prerequisite master data and opening positions are stable. Load once prerequisite cross-domain reference data is available so WO_ACTIVITY can be established cleanly. Sequence this object with its inventory management peers so MFCS processing can consume it without synthetic defaults. (Inferred from vendor object description, current scope dependencies, and Oracle Retail MFCS documentation.)