Calendar
In ScopeTechnical: CALENDAR | ID: OR-MFCS-CALENDAR
Stores one row for each 4_5_4 month. This table is populated by a UNIX script during installation of the system and should be modified by the database administrator to coincide with thecalendar being used at the client site.
See how this object fits into Foundation Data
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
- CALENDAR
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 CALENDAR can be established cleanly. Load before Fiscal Half and Fiscal Period because those downstream processes consume or reference this object. (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 (4)
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 CALENDAR can be established cleanly. Load before Fiscal Half and Fiscal Period because those downstream processes consume or reference this object. (Inferred from vendor object description, current scope dependencies, and Oracle Retail MFCS documentation.)