HCM Data Loader Vs FBDI: Which One Loads Your Fusion Data
HCM Data Loader vs FBDI - which one for Oracle Fusion HCM data loads
Also searched as
- 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
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.
Applies to: Oracle Fusion Cloud HCM and ERP, all monthly updates; HDL via Data Exchange, FBDI via File-Based Data Import templates
Choose and run the right bulk load tool
- 1Identify the target business object first: worker, assignment, element entry, absence, and similar HCM objects always go through HDL, never FBDI.
- 2For 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.
- 3Build 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).
- 4Zip 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.
- 5Monitor the load under Data Exchange > Import and Load Data; review the load and process results to find rejected records and their error messages.
- 6For 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.
- 7Do 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.
Why HCM Has Its Own Loader
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
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.
METADATA|Worker|PersonNumber|StartDate|ActionCode|DateOfBirth
MERGE|Worker|10024|2026/01/15|HIRE|1990/05/02
Where The Two Overlap
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
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.
Common 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.
How an ERP-grounded AI assistant handles this
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.
Frequently asked questions
Can I use FBDI to load HCM worker data instead of HDL?
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?
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?
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?
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.
Related
Fix FBDI Import Failures From Interface Table Validation Errors
When a Fusion FBDI import job errors out, the cause is almost always bad data in the interface tables (an invalid value set, a wrong date format, or a missing required column), not the ESS job itself. Open the process's Interface Errors Report or the Correct Import Errors spreadsheet to see the exact rejected rows and reason codes, fix the source data, and resubmit from the interface tables instead of re-running the whole FBDI load.
How-toFix Wrong Row Counts When Joining Across OTBI Subject Areas
Most subject areas in Oracle Fusion OTBI are self-contained and only support reliable analysis within their own folders; dragging a folder from a second subject area into the same analysis without a genuine shared join key silently produces duplicated or missing rows because OTBI has no way to correctly relate the two fact grains. Fix it by staying inside one subject area where possible, or by explicitly using a subject area that Oracle designed to cross domains, rather than combining arbitrary folders yourself.
How-toOracle Fusion Period Close: A Practical Checklist
Closing a Fusion GL period cleanly means closing every feeder subledger first (Payables, Receivables, Costing, Fixed Assets), running Create Accounting to post everything to GL, reconciling subledger-to-GL balances, and only then setting the GL period status to Closed - not Close Pending, which still allows adjustments. Close Monitor gives a single dashboard of every subledger's close status instead of checking each module separately.
How-toConnect Oracle Integration Cloud (OIC) To Fusion ERP
OIC connects to Fusion ERP primarily through the prebuilt ERP Cloud Adapter, which wraps Fusion's REST and SOAP web services with OAuth-based authentication and pick-list discovery of available business objects and operations, instead of you hand-building every REST call. Use the adapter for standard integrations; drop to a generic REST or SOAP adapter only when the ERP Cloud Adapter does not yet expose the specific service you need.
Error fixClear An Oracle Fusion ESS Job Stuck In Blocked Status
A Blocked status on an Oracle Fusion Enterprise Scheduler (ESS) job almost always means an earlier instance of the exact same job is still running or stuck, and the job definition does not allow simultaneous requests. Find and finish, or cancel, the earlier request first; only then does the Blocked request move to Running.
How-toOTBI vs BI Publisher: Which One Should You Use
Use OTBI when a business user needs ad hoc, self-service, real-time analysis with no fixed layout. Use BI Publisher when you need a pixel-perfect, scheduled, high-volume, or externally distributed document such as an invoice, check, or statutory report. Most Fusion implementations end up using both, not one instead of the other.
AI for ERPFusion Cloud ERP AI: OCI Generative AI Service vs. a Private LLM
Oracle's OCI Generative AI Service is a real option for Fusion Cloud ERP, but not the only one. Compare it honestly against a private LLM for sensitive data.
AI for ERPOracle ERP AI Consulting: What a Partner Should Deliver
What to demand from an Oracle ERP AI consulting partner across EBS, JD Edwards, NetSuite, and Fusion Cloud: interface tables, APIs, and buyer questions.
Stuck on Oracle Fusion Cloud ERP / HCM?
Talk to engineers who work inside Oracle Fusion Cloud ERP / HCM every week, and who build private AI that answers these questions from your own ERP data.