Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 7 · FBDI: the file-based loader end to end
Mandatory columns, and the ones that only look optional
Lesson 65 of 177 · 2 min
The loader demands some columns and accepts others empty — and the second group is where the damage is. Mandatory columns are the easy half. Leave one blank and the row is rejected with a message naming it; you fix it and move on. Annoying, visible, cheap. THE COLUMNS THAT ONLY LOOK OPTIONAL ARE THE ONES TO STUDY. Left empty, they are DEFAULTED — from a profile option, from a setup, from the first value in a list — and the row loads successfully carrying a value you did not choose. Nothing is rejected, nothing is logged as unusual, and the mistake is inside a correct-looking record. The ones that hurt most are the ones with business meaning: a business unit, a ledger, a payment term, a tax classification, a currency conversion type. An invoice loaded into the wrong business unit is a real transaction in the wrong place, 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 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