Oracle Fusion FBDI Template Field Guide
File Based Data Import is how most Oracle Fusion Cloud SCM data gets loaded during implementation and cutover. This worksheet keeps the mapping decisions for each FBDI column in one place so loads stop failing for avoidable reasons.
| FBDI template | Sheet / interface table | Column | Required | Source system field | Transformation / validation rule | Data owner | Status | |
|---|---|---|---|---|---|---|---|---|
The sample rows show the shape of an item import mapping. Column names and required flags change between releases, so always copy the real list from the FBDI workbook for your update and the Oracle Help Center import guide, then use this sheet to track decisions around it.
Pre-check your legacy extract
Optional: have an expert review your mapping sheet and suggest validation rules before your next mock load.
Optional. The tool and every export work without this. No spam.
How to use the field guide
Start from the macro-enabled FBDI workbook for your release. For each sheet, list every column you will populate, whether it is required, where the value comes from, the rule that transforms it and the person who owns it. Add columns you decide to leave blank so reviewers can see that blanks were intentional. Export to Excel and share it with the business data owners so sign off is recorded against a specific column, not a general feeling.
How an FBDI load works
You fill the workbook, generate the zip of CSV files, upload it to the Universal Content Management account used by the integration, and run the Load Interface File for Import scheduled process. Then you run the import process for the business object. Errors appear in the interface tables and in the process log. Because the load is staged, you can fix the source file and rerun without touching production tables until the import step succeeds.
- Generate zip from the workbook
- Upload to the correct UCM account
- Run Load Interface File for Import
- Run the object import and review rejects
Typical mapping problems
Most rejected rows come from reference data that does not exist yet: organization codes, units of measure, item templates, catalog categories and lookup values. Load order matters, so set up and load reference data before transactional objects. Other common causes are dates in the wrong format, text with embedded commas or line breaks, and numbers with thousand separators. Put a validation rule on every column that touches a lookup.
Cutover discipline
Keep one worksheet row per column, one status per row, and review the Not started count daily in the weeks before a mock load. Re-run mock loads with the same file structure so you measure rejection rates truthfully. Freeze the mapping a few days before the final load and record any changes with who approved them.
Frequently Asked Questions
Where do I get the official FBDI template?
From the Oracle Help Center, in the File Based Data Import guide for your Fusion Cloud SCM release. Download the workbook for the object you are loading and use the version that matches your update, since columns change over time.
Why do my rows load into the interface table but fail on import?
The first step only stages the data. Import runs the business validations such as valid organization, UOM, category and lookup values. Read the error messages on the interface rows and the import process log, then fix the source data.
Should I edit the CSV files directly?
Avoid it. Regenerate from the workbook so structure stays correct, and keep your mapping in a controlled sheet. Hand edited CSV files are the usual cause of mysterious header or delimiter errors during mock loads.
Is FBDI the only way to load data?
No. REST services suit smaller or ongoing integrations, and some objects have spreadsheet loaders. FBDI is usually preferred for large initial volumes because it is staged, repeatable and supports bulk loads.
Netray can help check legacy ERP extracts against your mapping rules before they reach the FBDI workbook, on your own infrastructure if needed. The worksheet is complete without it.
Related Tools
Oracle Fusion Item Class Design Worksheet
Plan item classes, parent classes, attribute groups and templates before you configure Fusion Product Hub, then export the design to Excel.
Developer ToolsOracle Fusion REST API URL Builder
Fill in host, version and resource to generate a Fusion Cloud REST URL with query parameters and a ready curl command.
OracleOracle Fusion Supply Planning Checklist
Work through plan setup, data collection, item and sourcing attributes, plan runs and exception review for Fusion Supply Planning.
OracleOracle Fusion Role Provisioning Worksheet
Plan who gets which Fusion job role, with which data access, who approved it and whether it raises a segregation of duties concern.
More Oracle tools
See all- Oracle Fusion BI Publisher Report Specification Template
- Oracle Fusion Quarterly Update Test Checklist
- Oracle Fusion Cloud SCM Fit Gap Worksheet
- Oracle Fusion Data Migration Mapping Worksheet
- Oracle Fusion Cutover Plan Worksheet
- Oracle Fusion Inventory Organization Design Worksheet
- Oracle Fusion SCM UAT Test Script Template
- Oracle Fusion SCM Implementation Statement of Work Template
- Oracle Fusion FBDI Load Time Estimator