Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 9 · Migration strategy and reconciliation
Signing off: what "done" means
Lesson 95 of 177 · 2 min
The artefacts that constitute sign-off, who signs, and why a migration without a named owner is never finished, only abandoned. WHAT IS SIGNED: the reconciliation page from Lesson 4 — counts, control totals, walked sample — per data domain, dated, naming the extract it was produced from. Plus the list of known exceptions, because there always are some, and an exception acknowledged in advance is a decision while an exception found later is a defect. WHO SIGNS: the person who owns the data in the business, not the project manager and not the consultant. The finance owner signs the ledger and sub-ledger reconciliation; the HR owner signs the workforce; the procurement owner signs suppliers. A signature from somebody who cannot personally tell whether the numbers are right is a formality, and everybody involved knows it. WHY AN UNOWNED MIGRATION IS NEVER FINISHED. There is always more that could be cleansed,…
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