Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 9 · Migration strategy and reconciliation
Data cleansing, and who owns it
Lesson 91 of 177 · 2 min
Legacy data is wrong in ways only the BUSINESS can adjudicate, and that sentence is why cleansing is not a technical task. Two suppliers with almost the same name: are they duplicates, or a company and its subsidiary? A cost centre used on transactions and absent from the current structure: retired, or an error? A negative quantity on a receipt: a correction, or bad data? Every one of these is a question about the business's own history, and a technical consultant answering it is guessing with authority. WHAT HAPPENS TO YOUR TIMELINE WHEN CLEANSING IS TREATED AS TECHNICAL is the part to plan for. The task is assigned to the migration team, who cannot answer the questions, so they either escalate each one — and the queue grows faster than it is answered — or they apply a rule. A rule applied to ambiguous data produces a migration that loads…
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
