Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 9 · Migration strategy and reconciliation
Mapping legacy values to Fusion
Lesson 92 of 177 · 2 min
A cross-reference table maps old codes to new ones, and it is the most under-valued artefact in any migration. Legacy cost centre 0450 becomes Fusion cost centre C-0450. Legacy supplier SUP1234 becomes a Fusion supplier with a system-generated id. Every one of those pairs is a decision somebody made, and the table is where they live. WHERE THEY LIVE MATTERS: not in a consultant's spreadsheet. The mapping is client property and belongs in the project record, with a version and a date. Two mappings that disagree — one used for balances and one for open items — produce a migration that reconciles in each half and not overall, and that is a genuinely hard failure to diagnose. AND THEY MUST OUTLIVE THE MIGRATION. Three reasons, all of which arrive after go-live. A corrective load needs to find the record it is correcting, which means the same mapping. A reconciliation question…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Fusion Technical: Reports, Data, Integrations and Extensions, with a certificate on completion and a fourteen-day refund window.
In this module: Module 9 · Migration strategy and reconciliation
- 1What to migrate, and what to leave behind
- 2Balances versus transactions
- 3The cutover sequence
- 4Reconciliation: proving a migration landedFree preview
- 5Data cleansing, and who owns it
- 6Mapping legacy values to Fusion
- 7Trial loads and the rehearsal nobody schedules
- 8Sub-ledger and general ledger agreement
- 9Signing off: what "done" means
- 10What breaks: the migration that reconciled and was wrong
- 11Lab briefing · Plan and reconcile a migration