Appt Head
In ScopeTechnical: APPT_HEAD | ID: OR-MFCS-APPT_HEAD
Stores header-level information for RDM-generated appointments. It is populated during the appointments upload process, and will contain one record per appointment /location combination.
See how this object fits into Inventory 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
- APPT_HEAD
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 APPT_HEAD 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 (6)
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 APPT_HEAD 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.)