Oracle Fusion FBDI troubleshooting depends on finding the stage that failed. File-Based Data Import moves a prepared file through a repository and interface processing before the application creates business records. A successful upload proves that the file arrived, not that the invoices or journals were imported.
Start with the template for the exact business object and Oracle release. Oracle's Financials import guide links each supported import to its process instructions. Keep the required column order and preserve identifiers as text where leading zeroes matter. Generate the CSV and ZIP using that template's rules.
If Oracle rejects the archive before interface loading, inspect the ZIP contents and expected file names. Check delimiter and encoding assumptions against the template. Uploading an XLSM workbook where a generated ZIP is expected does not provide the import data. Keep the original archive and a checksum with the investigation so the submitted bytes remain identifiable.
If the file reached Universal Content Management, record its document identifier and account. Universal Content Management is Oracle's file repository for these transfers. Confirm that the load process references that document and the correct import type. Similar file names are insufficient evidence when several batches were uploaded.
Read the parent ESS request and its child processes separately. Load Interface File for Import loads the interface data; the application-specific process applies business validation and creates application records. A failed child can explain an apparently unhelpful parent status. Preserve the request IDs and the import batch identifiers together.
An interface load failure often points to the file structure or a value that cannot be loaded. An application import failure can involve an invalid account, missing reference data or a duplicate business key. Follow the chosen object's correction procedure. Oracle documents different correction paths for different imports, so do not assume every process retains or purges successful rows in the same way.
Use the Payables import-job guide when investigating invoice imports. Confirm the selected job's metadata and parameter order before submitting it. With Fusion Toolkit, capture the actual request ID and monitor that request rather than launching another job because a terminal session timed out.
Before retrying a corrected batch, reconcile the original source keys with records already present in Oracle. Restrict the correction to the failed population when the documented import supports it. A new successful process does not prove that an earlier ambiguous submission created nothing.
This workflow was reviewed on 8 November 2026. Resolve one failed test batch, verify its resulting business records and preserve the correction steps before adding the import to an unattended schedule.