Alc Plan
In ScopeTechnical: ALC_PLAN | ID: OR-RACS-ALC_PLAN
Stores all plan information used by the allocation system for gathering need. a record can exist at any of the following levels by week/location/quantity: department, department-class, department-class-subclass, item-diff and sku.
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_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_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_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.)