Loading the interface tables

The upload puts your rows into INTERFACE TABLES — a staging area inside Fusion that belongs to the loader, not to the application. Nothing in the business has changed yet. No invoice exists, no supplier exists, no journal is posted. THAT INTERMEDIATE STATE IS YOUR BEST CHANCE TO CATCH A MISTAKE, and most people run straight past it because the import is one click away. What to do in the window. Count the rows that arrived and compare against the file — a mismatch means the CSV was truncated, misnamed inside the zip, or partly rejected at upload. Look at three rows in full, including the columns you left empty, because this is where a defaulted value is still a blank rather than a decision already taken. Sum one numeric column and compare against the source total. Three checks, five minutes, and they are the difference between a mistake you…

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