Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 9 · Migration strategy and reconciliation
Lab briefing · Plan and reconcile a migration
Lesson 97 of 177 · 2 min
Given a legacy extract and a target, write the SEQUENCE and the RECONCILIATION before loading anything — then load, and see whether your own plan holds. The plan comes first and it is the graded artefact. Which objects, in which order, which go before the freeze and which during it, and how long you expect each to take. Write the expected durations down before you know them; comparing your estimate against the actual is the most useful number this lab produces. The reconciliation is defined before the load, per Lesson 4. Counts, one control total with its basis stated, and three records named IN ADVANCE that you will walk end to end. Naming them in advance is what stops the sample being chosen from the records that happen to look right. Then load, and expect the plan not to hold. Something will be missing a prerequisite, something will take four…
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