Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 7 · FBDI: the file-based loader end to end
Rollback, and why there usually is not one
Lesson 74 of 177 · 2 min
Most of what FBDI loads cannot be deleted afterwards. Not made difficult — not available. A posted journal, an accounted invoice, a receipt applied against a transaction: the correction is another transaction, and both stay. What that means for how you test is the whole point of the lesson. Test where a mistake is survivable, which means a test environment you are allowed to break, not production and not a shared instance somebody else is testing in. And test the SMALL version first — one row, then ten, then the batch — because the cost of a mistake at row one and at row ten thousand are not comparable. Where there IS a way back, know it before you load. An unposted journal can be deleted; a supplier with no transactions can be made inactive; an interface row that was never imported can be purged. Write the reversal path beside…
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 7 · FBDI: the file-based loader end to end
- 1The FBDI sequence, and why order mattersFree preview
- 2Finding and reading the right template
- 3Mandatory columns, and the ones that only look optional
- 4Preparing the file without corrupting it
- 5Loading the interface tables
- 6Running the import and reading the output
- 7Errors: finding the row that failed
- 8Correcting and reloading safely
- 9Master data versus transactional loads
- 10Volume: loading a hundred thousand rows
- 11Proving the load landed
- 12Rollback, and why there usually is not one
- 13What breaks: six FBDI failures
- 14Lab briefing · A supplier and invoice load