Shipment

In Scope

Technical: SHIPMENT | ID: OR-MFCS-SHIPMENT

Stores one row for each shipment within the system. Base information about each shipment for each order is held in this table for as long as its associated order header is retained.

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
SHIPMENT

Implementation Considerations

Use Cases

Initial load, rehearsal loads, cutover

Sequencing

Load during Stage 2 to load dependent business records after prerequisite master data is stable. Load once prerequisite cross-domain reference data is available so SHIPMENT can be established cleanly. Sequence this object with its merchandising system peers so merchandising reference and transaction data resolve correctly across dependent entities. (Inferred from vendor object description, dependency metadata, and Oracle Retail Merchandising System documentation.)

Cutover

Load during Stage 2 / .

Data Governance

Requires business ownership and source-to-target crosswalk governance.

Field Definitions (29)

Typical Source Systems

ERPLegacy

Notes

Load during Stage 2 to load dependent business records after prerequisite master data is stable. Load once prerequisite cross-domain reference data is available so SHIPMENT can be established cleanly. Sequence this object with its merchandising system peers so merchandising reference and transaction data resolve correctly across dependent entities. (Inferred from vendor object description, dependency metadata, and Oracle Retail Merchandising System documentation.)