Partner Org Unit
In ScopeTechnical: PARTNER_ORG_UNIT | ID: OR-MFCS-PARTNER_ORG_UNIT
PARTNER_ORG_UNIT table will be the master table for Supplier/Supplier Site and Org Unit ID relation. This table will be populated when either Multiple Set of Books is ON And/or Financial AP is O.
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_ORG_UNIT
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_ORG_UNIT 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 (8)
Typical Source Systems
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_ORG_UNIT 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.)