Running the import and reading the output

The import process reads the interface tables, validates, and creates the real records. It is an ESS job like any other, so it has a request id, a log and a status — and the status is not the answer. THE LOG IS THE ANSWER, AND IT REPORTS COUNTS. Rows read, rows imported, rows rejected. Read all three every time: a process that completes successfully having imported nought of ten thousand rows is a completed process, and the status says so. The distinction that matters most: A ROW THAT FAILED VERSUS A ROW THAT SUCCEEDED INTO THE WRONG PLACE. A failure is visible — it is in the reject count and it names an error. A success into the wrong place is not in any count: the row imported cleanly, into the wrong business unit, the wrong period, or against the wrong supplier, because a column you left empty was…

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