Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 9 · Migration strategy and reconciliation
Balances versus transactions
Lesson 88 of 177 · 2 min
Bringing an opening balance is cheap and loses detail. Bringing transactions is expensive and brings problems with it. Both sentences are true and the second half of each is what decides. A BALANCE is one journal per account per period. It is fast to build, easy to reconcile — it either agrees with the legacy trial balance or it does not — and it carries no supporting detail. The ledger is right and nothing can be drilled into. TRANSACTIONS carry their own problems across. A legacy invoice references a supplier, a cost centre, a tax code, a currency rate and a period, and every one of those has to map to something that exists in Fusion. Anything unmapped becomes a decision, and a hundred thousand transactions contain more unmapped values than anybody estimated. Where each is right. Balances for closed periods, always — nobody transacts on a closed period and…
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