Errors: finding the row that failed

The error tables hold one row per rejection, and the error report renders them readably. Both name the interface row, the column, and a message — and THE MESSAGE NAMES A COLUMN RATHER THAN A CAUSE, which is the difficulty this lesson exists to solve. "Invalid supplier site" does not mean the value in that column is malformed. It means the value did not resolve, and there are four different reasons for that: the supplier does not exist yet, the site does not exist under that supplier, the site exists but not in this business unit, or the site is inactive as at the transaction date. All four produce the identical message. The method that gets from a rejection to the actual problem, in four steps. ONE: read the raw value in the interface row, not in your spreadsheet — that catches the truncation and formatting corruption from Lesson 4.…

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