# Fix FBDI Import Failures From Interface Table Validation Errors > Source: https://netray.co/erp-help/fusion-fbdi-import-interface-table-errors > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer When a Fusion FBDI import job errors out, the cause is almost always bad data in the interface tables (an invalid value set, a wrong date format, or a missing required column), not the ESS job itself. Open the process's Interface Errors Report or the Correct Import Errors spreadsheet to see the exact rejected rows and reason codes, fix the source data, and resubmit from the interface tables instead of re-running the whole FBDI load. ## Kind error ## System oracle-fusion ## Erp Oracle Fusion Cloud ERP ## Module Financials / FBDI Data Import ## Query FBDI import failed - interface table validation errors ## Alternate Queries - Oracle Fusion FBDI import errors interface tables - Correct Import Errors spreadsheet Oracle Fusion - Load Interface File for Import failed Oracle Fusion - FBDI Loader Worker ended in error ## Applies To Oracle Fusion Cloud ERP (Financials, SCM), all monthly updates; standard FBDI templates from the Oracle File-Based Data Import guide ## Steps ### Diagnose and fix a failed FBDI import **Items:** Open Navigator > Tools > Scheduled Processes and find the import job (Import Journals, Import Payables Invoices, Import AutoInvoice, and similar). Click the process name, then View Log and View Output; look for "ended in error" or a count of rejected rows. Open the Interface Errors Report link on the process details page, or download the Correct Import Errors spreadsheet (ADFdi Excel) if the product offers one. Match each rejected row's error code to a real cause: invalid value set combination, wrong date format (FBDI expects YYYY/MM/DD as text), duplicate source document reference, or a business unit not enabled on the ledger. Fix the data either in the FBDI source spreadsheet and re-run Load Interface File for Import plus the product import job, or correct rows directly through the Correct Import Errors spreadsheet and resubmit only the corrected rows. Query the interface table directly (for example AP_INVOICES_INTERFACE, GL_INTERFACE, RA_CUSTOMERS_INTERFACE_ALL) through BI Publisher or OTBI if the UI report does not show enough detail. After a clean run, confirm the interface table is empty for your batch - leftover rows mean some records were never processed. ## Sections ### Why FBDI Errors Point At Data, Not The Job **Body:** FBDI (File-Based Data Import) loads a zipped CSV, generated from Oracle's macro-enabled XLSM templates, into standard Oracle interface tables using the same underlying validation the transactional UI applies. The file upload step itself rarely fails once the zip is well formed. The ESS jobs Load Interface File for Import (stages the file into interface tables via UCM) and the product-specific import job almost never fail structurally; they fail because a row violates a rule the transactional screen would also enforce - an invalid GL segment combination, a supplier site not associated with the business unit, or a currency code that does not match the ledger. ### Reading The Correct Import Errors Spreadsheet **Body:** Many Financials import flows - Payables invoices, Receivables AutoInvoice, GL journal import - expose a Correct Import Errors (or similarly named) ADFdi spreadsheet that lets you view, edit, and resubmit only the failed interface rows without regenerating the whole FBDI file. This is far faster than editing the original template and re-uploading everything when only a handful of rows failed. **Code:** - Navigator > Tools > Scheduled Processes > (select failed import job) > View Output > Interface Errors Report ### Common Root Causes By Module **Body:** - Payables: the supplier site is not enabled for the invoicing business unit, or the invoice source name and number combination already exists as a duplicate. - General Ledger: the journal category and source combination is not defined for the ledger, or the accounting period is not Open. - Receivables: the transaction type is not assigned to the business unit, or an AutoInvoice grouping rule does not match the incoming lines, leaving them ungrouped and rejected. ### When Interface Rows Get Stuck **Body:** Rows can be left in a New or Error status in the interface table after repeated failed attempts. Use the supported correction spreadsheet or the product's purge/delete process rather than deleting rows with ad hoc SQL, since orphaned control records and mismatched batch IDs are a common side effect of manual cleanup. ## Pitfalls - Editing interface table rows directly with SQL instead of the supported spreadsheet or UI - unsupported and can leave orphaned records. - Assuming a date typed as MM/DD/YYYY will import correctly - FBDI templates require YYYY/MM/DD as text, not an Excel date type. - Re-running Load Interface File for Import again after a partial failure, which re-stages rows and can duplicate what is already sitting in the interface table. - Ignoring a process that completed with warnings - some rows silently reject while others post successfully. - Forgetting that value sets and cross-validation rules differ per business unit and ledger, so a template that worked for one BU can fail for another. - Not checking whether the accounting period is open before troubleshooting the data - a closed period produces the same generic import-failed symptom. ## Ai Angle ERPray grounded on your Fusion instance can read the actual Interface Errors Report and interface table rows for a failed FBDI run and explain, in plain language, which specific rows failed and why - cross-referencing the value sets, business unit setup, and period status behind the rejection instead of you tracing five error codes by hand across three setup screens. ## Faq ### What is the difference between Load Interface File for Import and the product import job? **Answer:** Load Interface File for Import only takes the zipped FBDI CSV from UCM and stages the rows into the target interface table, such as GL_INTERFACE. It does not validate business rules. The second job - Import Journals, Import Payables Invoices, and so on - actually validates and posts the staged rows, and it is where most real errors surface. ### Can I fix rejected rows without regenerating the FBDI file? **Answer:** Yes for most Financials imports. Products that expose a Correct Import Errors spreadsheet let you open, edit, and resubmit only the failed interface rows in place, which is much faster than rebuilding and re-uploading the whole template for a handful of bad rows. ### Why do my dates import as the wrong day? **Answer:** FBDI templates expect dates as plain text in YYYY/MM/DD format. If Excel auto-converts the cell to a date type, or your regional settings reformat it on save, the loader can misread day and month or reject the row outright. Format date columns as text before entering values. ### The job says success but my data is missing - what happened? **Answer:** Check the process output for a rejected-row count even when the overall status shows success or warning. Partial failures are common: some rows post cleanly while others sit rejected in the interface table with a reason code visible only in the Interface Errors Report or process log. ## Search terms FBDI import error Oracle Fusion, interface table validation errors Fusion, Correct Import Errors spreadsheet, Load Interface File for Import failed, AP_INVOICES_INTERFACE errors, GL_INTERFACE import failed, Oracle Fusion FBDI troubleshooting, Import Payables Invoices error, FBDI date format YYYY/MM/DD, Import AutoInvoice interface errors --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json