Key Map GL
In ScopeTechnical: KEY_MAP_GL | ID: OR-MFCS-KEY_MAP_GL
Stores the reference key details of the GL records that are written to stg_fif_gl_data. So this new table will be used to map the records in the TRAN_DATA_HISTORY with the reference key values send by financial application system like PSFT for drill back reports.
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
- KEY_MAP_GL
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 KEY_MAP_GL 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 (16)
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 KEY_MAP_GL 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.)
