Deal Queue
In ScopeTechnical: DEAL_QUEUE | ID: OR-MFCS-DEAL_QUEUE
This table will hold all deals that have been approved, unapproved or closed during the day. This list will be used to drive the process rebuilding the DEAL_SKU_COST and ORDSKU_DISCOUNT tables.
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
- DEAL_QUEUE
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 DEAL_QUEUE 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 (1)
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 DEAL_QUEUE 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.)