# HCM Data Loader Vs FBDI: Which One Loads Your Fusion Data

> Source: https://netray.co/erp-help/fusion-hcm-data-loader-vs-fbdi
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: ERP Help

## Short answer

HCM Data Loader (HDL) is the dedicated bulk tool for HCM business objects - workers, assignments, compensation, absences - and uses a plain-text .dat file with METADATA and MERGE or DELETE action lines, not a spreadsheet template. FBDI is the general Financials and SCM bulk-load framework built on Excel macro templates that stage data into interface tables. If the object lives in HCM, use HDL; if it lives in Financials, Procurement, or SCM, use FBDI.

## Kind

how-to

## System

oracle-fusion

## Erp

Oracle Fusion Cloud ERP / HCM

## Module

HCM Data Loader (HDL) / FBDI

## Query

HCM Data Loader vs FBDI - which one for Oracle Fusion HCM data loads

## Alternate Queries

- when to use HDL instead of FBDI Oracle Fusion
- HCM Data Loader dat file format Oracle Fusion
- difference between HDL and FBDI HCM
- Oracle Fusion HCM bulk load tool comparison

## Applies To

Oracle Fusion Cloud HCM and ERP, all monthly updates; HDL via Data Exchange, FBDI via File-Based Data Import templates

## Steps

### Choose and run the right bulk load tool

**Items:**

Identify the target business object first: worker, assignment, element entry, absence, and similar HCM objects always go through HDL, never FBDI.

For HCM, get the correct HDL business object name (Worker, WorkTerms, Compensation, PayrollElementEntry) from the HCM Data Loader Business Objects guide rather than guessing the object name.

Build the .dat file with a METADATA line listing column names, then DATA lines per row, using the correct action (MERGE to insert/update, DELETE to remove).

Zip the .dat file(s) and upload through Data Exchange > Import and Load Data, or place it in the HCM_DATA_LOADER account in UCM for automated pickup.

Monitor the load under Data Exchange > Import and Load Data; review the load and process results to find rejected records and their error messages.

For Financials or SCM objects, confirm the object has an FBDI template in the File-Based Data Import guide, populate the XLSM template, generate the CSV/zip, and load via Load Interface File for Import plus the product import job.

Do not try to force an HCM object through FBDI or a Financials object through HDL - the two frameworks are not interchangeable even though both are bulk-load tools.

## Sections

### Why HCM Has Its Own Loader

**Body:**

HCM data is hierarchical and effective-dated in ways Financials and SCM data usually is not - a single worker record touches person, assignment, work relationship, and multiple effective-dated segments that all need to stay in sync. HDL was purpose-built to express those relationships and date-effective changes in one file, which a flat interface-table CSV load struggles to represent cleanly.

### File Format Differences

**Body:**

FBDI starts from an Excel macro-enabled template that generates a CSV, zips it, and loads it through Load Interface File for Import into a named interface table like AP_INVOICES_INTERFACE. HDL uses a plain-text .dat file you can generate from a flat-file extract, a HCM Extract, or a script, with METADATA rows defining columns and DATA rows for values - no macro-enabled spreadsheet involved.

**Code:**

- METADATA|Worker|PersonNumber|StartDate|ActionCode|DateOfBirth
- MERGE|Worker|10024|2026/01/15|HIRE|1990/05/02

### Where The Two Overlap

**Body:**

A handful of implementations touch both in the same project - loading new workers through HDL while loading their expense or payables setup through FBDI. Treat them as complementary tools for different data domains rather than competing options for the same object; check the relevant data loading guide (HCM Data Loader guide vs File-Based Data Import guide) to confirm which framework owns a given object before building either file.

### Diagnosing A Rejected HDL Load

**Body:**

HDL load errors show up in the process results with a business-object-specific message, often pointing to a missing effective-dated record the new row depends on, or an incorrect action code for the object's current state. Unlike FBDI's Interface Errors Report, HDL surfaces errors directly against the Data Exchange load and process history, not a separate spreadsheet.

## Pitfalls

- Trying to load HCM person or assignment data through an FBDI-style template - there is no such template; HCM data belongs in HDL.
- Getting the HDL action code wrong (MERGE vs DELETE, or the wrong DateTrack action for a correction versus a new date-effective row) and corrupting the assignment history.
- Building an HDL file without confirming column order matches the METADATA line exactly - HDL is strictly positional per the metadata definition.
- Assuming HDL and FBDI share an error-reporting UI - HDL results live under Data Exchange, not the Scheduled Processes Interface Errors Report used for FBDI.
- Loading large HCM population changes without first testing a small batch, since a bad action code can cascade across dependent effective-dated records.

## Ai Angle

ERPray grounded on your Fusion HCM and ERP setup can tell you directly which framework, HDL or FBDI, owns a given object before you build a file, and read back the actual load and process results to explain a rejected HDL row in plain language - saving the trial and error of guessing between two very differently structured bulk-load tools.

## Faq

### Can I use FBDI to load HCM worker data instead of HDL?

**Answer:** No. HCM business objects such as workers, assignments, and compensation are only supported through HCM Data Loader. FBDI templates exist for Financials, Procurement, and SCM objects; there is no supported FBDI path for core HCM person and work data.

### Do I need Excel to build an HDL file?

**Answer:** No. HDL files are plain text .dat files with METADATA and DATA lines, so they can be generated from a script, an extract, or a spreadsheet exported to a delimited text format, unlike FBDI which depends on Oracle's macro-enabled XLSM templates.

### Where do I find the correct HDL business object and attribute names?

**Answer:** The Oracle HCM Data Loader Business Objects guide lists every supported object, its required and optional attributes, and valid action codes. Using an outdated or guessed attribute name is one of the most common causes of a rejected HDL load.

### Can HDL and FBDI loads run in the same implementation project?

**Answer:** Yes, and it is common - HDL for HCM person, assignment, and payroll setup, FBDI for Financials and SCM data. Sequence them so HCM data (workers who will later be expense approvers, for example) loads before dependent Financials or SCM records that reference those people.

## Search terms

HCM Data Loader vs FBDI, HDL dat file format Oracle Fusion, Oracle Fusion HCM bulk load, HCM Data Loader business objects, FBDI vs HDL difference, Data Exchange Import and Load Data, Oracle Fusion worker load HDL, HCM Data Loader METADATA MERGE

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json