The FBDI sequence, and why order matters

Six steps: template, CSV, zip, upload, load interface, import. Each has its own failure mode, and the order is not negotiable. The TEMPLATE is a spreadsheet Oracle publishes per object per release. It defines the columns and their order, and it is version-specific. The CSV comes from that spreadsheet's own generate step, not from Save As — a hand-saved CSV is where date and leading-zero corruption enters. The ZIP is what gets uploaded, and it must contain the CSV named exactly as the interface expects. The UPLOAD puts your data in the interface tables. The IMPORT moves it from there into the application, applying validation, defaulting and business rules. UPLOAD AND IMPORT ARE SEPARATE, AND THAT SEPARATION IS THE MOST USEFUL THING IN FBDI. Between them your data is sitting in interface tables where you can look at it — before anything is committed to the application. Lesson 5 is…

In this module: Module 7 · FBDI: the file-based loader end to end

1. 1The FBDI sequence, and why order mattersFree preview
2. 2Finding and reading the right template
3. 3Mandatory columns, and the ones that only look optional
4. 4Preparing the file without corrupting it
5. 5Loading the interface tables
6. 6Running the import and reading the output
7. 7Errors: finding the row that failed
8. 8Correcting and reloading safely
9. 9Master data versus transactional loads
10. 10Volume: loading a hundred thousand rows
11. 11Proving the load landed
12. 12Rollback, and why there usually is not one
13. 13What breaks: six FBDI failures
14. 14Lab briefing · A supplier and invoice load