Shipsku

In Scope

Technical: SHIPSKU | ID: OR-MFCS-SHIPSKU

Stores one row for each shipment/SKU combination in the system. When a shipment header is purged all associated rows in this table are also purged.

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
SHIPSKU

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 SHIPSKU 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 (38)

Typical Source Systems

ERPLegacy

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 SHIPSKU 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.)