Mon – Sat: 9:00 AM – 7:00 PM IST
Oracle

FBDI and HDL data loading in Oracle Fusion

The two bulk loaders behind every Fusion implementation, and why the tooling is never the hard part.

In short

FBDI (File-Based Data Import) loads ERP and SCM data into Oracle Fusion using prescribed spreadsheet templates converted to CSV and uploaded for processing. HDL (HCM Data Loader) does the equivalent for HCM, using a structured file format. Both are bulk, asynchronous and validated — and both will reject data that your source system has been tolerating for years.

Why It Matters

Why this matters in practice

Every Fusion implementation runs on these two loaders, and every implementation underestimates the cleansing rather than the loading. The templates are well documented and the mechanism works. What takes the time is that Fusion validates relationships your legacy system did not: a supplier without a valid address, an employee with an impossible hire date, a cost centre that was retired.

Prescribed templates, so the target structure is known up front
Validated on load, which surfaces data problems early
Asynchronous and restartable for large volumes
Reusable for ongoing interfaces, not only for the initial migration
How It Works

How it works in practice

1

Get the templates

Oracle publishes an FBDI template per object. The template defines the columns and the required fields precisely.

2

Map and extract

Map legacy fields to template columns. This is where the real design decisions surface — what to carry, what to retire.

3

Cleanse

Your team's work, and the long pole. Missing values, invalid references and duplicates all have to be resolved at source.

4

Load and review

Upload, run the import, and read the error report. Early runs are expected to fail; that is what they are for.

5

Reconcile

Record counts and control totals compared against source. A load that completed is not the same as a load that is correct.

Worked example

A worked example: a sequence that cannot work

A migration team plans to load suppliers, supplier sites, bank accounts and open invoices over one weekend. The files are prepared in parallel by different people and loaded in the order they happen to be finished.

It fails on the first attempt, and the reason is dependency rather than data quality. Supplier sites reference suppliers that must already exist. Bank accounts reference sites. Invoices reference both the supplier and the site, and also a currency, a payment term and a distribution account that must all be set up first. Loading them in the wrong order produces thousands of rejections whose messages describe missing references rather than the actual problem, which is sequencing.

The fix is to establish the dependency order first and rehearse the whole sequence in a test environment end to end — not file by file, which is how dependency errors stay hidden. A full rehearsal also produces the thing most migrations lack: a measured elapsed time, so the cutover plan is built on an observed number rather than an estimate.

Key terms

The vocabulary, briefly

Term What it means
FBDI File-Based Data Import — spreadsheet templates for loading data into Fusion applications.
HDL HCM Data Loader, the equivalent mechanism for human capital management objects.
Control file The definition telling the loader how to interpret the file's columns and records.
Business object The logical entity being loaded — a worker, an invoice, a supplier — often spanning several files.
Load sequence The order objects must be loaded in, driven by their dependencies on one another.
What Goes Wrong

Common mistakes worth avoiding

Starting cleansing in the last month

It is the single most common cause of a slipped go-live. Begin in the first month and run loads early and often.

Loading history indiscriminately

Decide deliberately how much transactional history to carry. Carrying everything is expensive and rarely used.

No reconciliation step

A successful load with wrong totals is worse than a failed one, because nobody investigates it.

Treating loaders as one-off tools

FBDI and HDL are reusable for ongoing interfaces. Building throwaway scripts instead creates work later.

What to measure

Numbers worth tracking

Metric What it tells you What distorts it
Rejection rate by object Which file is actually the problem. A high rate on one object often causes failures everywhere downstream.
Rehearsal count before cutover Two or three full rehearsals is normal. Zero is how cutovers overrun.
Elapsed load time per object The input to the cutover plan, and only knowable by rehearsing.
Reconciliation variance post-load Counts and control totals compared to source. The only real proof the load worked.
FAQ

Questions we are asked about this

FBDI for ERP and SCM objects — suppliers, customers, items, balances, invoices. HDL for HCM — workers, assignments, salaries, absences.
More than one. Most implementations run several full rehearsals, because each pass surfaces data problems the previous one masked. Plan for at least three.
You can, and for periodic bulk loads it is entirely reasonable — scheduled imports of an external payroll feed, for instance. For transactional, near-real-time integration, REST services are the better fit because file-based loading is asynchronous and errors surface late. The deciding question is latency: if someone needs to know within minutes whether a record posted, files are the wrong mechanism.
ADF desktop integration spreadsheets are interactive, validate as you work and suit small corrections by a business user. FBDI is bulk loading: prepared files, processed through the import queue, built for volume rather than for interactivity. Using the interactive tool for a migration is slow and error-prone; using FBDI for a five-row correction is overkill.
Load into a test environment first, extract the error report, categorise the failures by cause rather than fixing them one by one, and correct the source extract so the same class of error cannot recur. Fixing rejections individually in the file is the trap: it gets that load through and leaves the underlying extract logic wrong, so every subsequent load repeats the work.
Less than you might expect for the loading itself — the templates are spreadsheets. The skill is in the preceding work: understanding business object dependencies, mapping legacy structures to the target model, and designing the sequence. That is data migration expertise rather than tooling expertise, and it is the part that determines whether a migration is comfortable or not.
Related

Where to read next

What is Oracle Fusion Cloud?

Read more

Our Oracle consulting services

Read more

OTBI vs BI Publisher

Read more

Need this applied to your own systems?

We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.