Outloc

In Scope

Technical: OUTLOC | ID: OR-MFCS-OUTLOC

This table is used to store skeleton information about locations that fall outside of RMS Organization Hierarchy such as entry ports.

See how this object fits into Foundation Data

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
OUTLOC

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 OUTLOC can be established cleanly. Sequence this object with its foundation data 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 (21)

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 OUTLOC can be established cleanly. Sequence this object with its foundation data peers so MFCS processing can consume it without synthetic defaults. (Inferred from vendor object description, current scope dependencies, and Oracle Retail MFCS documentation.)