What breaks: six FBDI failures

Six failures, and only the first two announce themselves. One. A stale template. Columns shifted; either a rejection naming a column or, worse, values landing one field to the left. Lesson 2. Two. A date Excel rewrote. Rejected if the format is impossible, ACCEPTED if the day and month swap produced another valid date — and then an invoice dated four months out sits in the ledger looking ordinary. Three. A load run twice. Duplicates on anything transactional, and a supplier owed the money twice. No error at all, because both runs were valid. Four. A dependency loaded out of order. Invoices before suppliers. The message names a column and sends you to check the file, which is correct. Lesson 1. Five. A file that imported into the WRONG BUSINESS UNIT. An empty column, defaulted. Every row succeeded. This is Lesson 3 arriving as real transactions in the wrong ledger,…

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