Partner

In Scope

Technical: PARTNER | ID: OR-MFCS-PARTNER

This table is used to store partner detail information. Partners can include any outside entity (Banks, Agents, etc.) that the company deals with except suppliers, whose detail information is stored on the sups table.

See how this object fits into Supplier 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
PARTNER

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

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