Alc Receipt Plan
In ScopeTechnical: ALC_RECEIPT_PLAN | ID: OR-RACS-ALC_RECEIPT_PLAN
Receipt and Plan table. Table is used to generate Need at different hiearchy level when Receipt and Plan is used in Allocation as rule.
See how this object fits into Allocations
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
- ALC_RECEIPT_PLAN
Implementation Considerations
Use Cases
Initial load, rehearsal loads, cutover
Sequencing
Load during Open Transactions to stage transactional records only after prerequisite master data and opening positions are stable. Load once prerequisite cross-domain reference data is available so ALC_RECEIPT_PLAN can be established cleanly. Sequence this object with its allocations peers so RACS processing can consume it without synthetic defaults. (Inferred from vendor object description, current scope dependencies, and Oracle Retail RACS documentation.)
Cutover
Load during Stage 2 / .
Data Governance
Requires business ownership and source-to-target crosswalk governance.
Field Definitions (12)
Typical Source Systems
Notes
Load during Open Transactions to stage transactional records only after prerequisite master data and opening positions are stable. Load once prerequisite cross-domain reference data is available so ALC_RECEIPT_PLAN can be established cleanly. Sequence this object with its allocations peers so RACS processing can consume it without synthetic defaults. (Inferred from vendor object description, current scope dependencies, and Oracle Retail RACS documentation.)