Oracle Fusion Data Migration Object Library

How Oracle Fusion accepts data

Load order and mechanism apply across every object on this platform.

1. 1Pick the load mechanism per objectFBDI for Financials, Procurement and SCM; HDL for HCM and Payroll; ADFdi spreadsheets for small corrective loads; REST and SOAP for integration rather than bulk migration. The choice fixes the file format, so it is made before transformation is built.
2. 2Build to the Oracle template exactlyFBDI templates are column-position-sensitive CSV. A shifted column does not raise a useful error — it writes a valid-looking wrong value, so generated output is validated against the template rather than inspected by eye.
3. 3Load the enterprise structure firstChart of accounts, ledgers, legal entities, business units, cost centres and their value sets. Transactional data referencing a structure that does not exist yet fails at import.
4. 4Load master dataSuppliers, customers and items become the reference points transactional records resolve against, carrying a cross-reference to the legacy key where it retains audit value.
5. 5Upload and invoke the importFiles are zipped and uploaded to UCM; the Load Interface File for Import job stages them into interface tables; the object's import process promotes them into base tables.
6. 6Work the interface-table rejectionsA row can pass the file load and still fail the import on a referential or business-rule check. Rejections are categorised, fixed in the transformation rules and reprocessed.
7. 7Load transactional and historical dataBalances, open items and history, in the order the target's own validations require.

Two stages, two failure modes. Source-to-file reconciliation proves the transformation was right; file-to-target reconciliation proves Oracle accepted it. Check only the first and a migration reports success while rows sit rejected in an interface table.