Fixed Deal Dates
In ScopeTechnical: FIXED_DEAL_DATES | ID: OR-MFCS-FIXED_DEAL_DATES
This table will hold a column for each date of the fixed deal that the amount should be collected from the supplier/partner.
See how this object fits into Cost
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
- FIXED_DEAL_DATES
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 FIXED_DEAL_DATES can be established cleanly. Sequence this object with its finance & cost 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 (5)
Typical Source Systems
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 FIXED_DEAL_DATES can be established cleanly. Sequence this object with its finance & cost peers so MFCS processing can consume it without synthetic defaults. (Inferred from vendor object description, current scope dependencies, and Oracle Retail MFCS documentation.)