MSAMM
Back to course

Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 9 · Migration strategy and reconciliation

Reconciliation: proving a migration landed

Lesson 90 of 177 · 2 min · Free preview

Counts, control totals and a sample walked end to end — DEFINED BEFORE THE LOAD rather than argued after it. The timing is the whole lesson. A reconciliation agreed in advance is a test the migration either passes or fails. A reconciliation constructed afterwards is a negotiation, conducted by people who already have a number they want to be right. COUNTS. Records in the legacy extract, records in Fusion, and the difference explained record by record. "Close enough" is not an outcome; every missing record has a name and a reason, or the migration is not reconciled. CONTROL TOTALS. A monetary sum, on a stated basis, from both sides. State the basis in advance — gross or net, which currency, as at which date — because most reconciliation disputes are two people summing different things and both being right. A SAMPLE WALKED END TO END. Three to five records, chosen…

This lesson is free

Watch the full lesson, with its written notes, without an account. It is one of the free lessons this course opens with.

Watch the full lesson

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

In this module: Module 9 · Migration strategy and reconciliation

  1. 1What to migrate, and what to leave behind
  2. 2Balances versus transactions
  3. 3The cutover sequence
  4. 4Reconciliation: proving a migration landedFree preview
  5. 5Data cleansing, and who owns it
  6. 6Mapping legacy values to Fusion
  7. 7Trial loads and the rehearsal nobody schedules
  8. 8Sub-ledger and general ledger agreement
  9. 9Signing off: what "done" means
  10. 10What breaks: the migration that reconciled and was wrong
  11. 11Lab briefing · Plan and reconcile a migration