Mrt

In Scope

Technical: MRT | ID: OR-MFCS-MRT

This table supports the concept of a Mass Return Transfer Number and other attributes to maintain multiple transfers and Rtvs. This table will hold the header information and the details to create an Rtv if an Rtv is applicable.

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
MRT

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 MRT 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 (20)

Typical Source Systems

ERPLegacy

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