Week 6 of 8

Data loads: FBDI and HDL

Most Oracle data moves through file-based data import (FBDI) for ERP and HCM Data Loader (HDL) for HR data. FBDI has two steps: Load Interface File for Import fills the interface tables, then a product import such as Import Journals moves rows into the application. Each step can fail on its own.

Two details catch testers out. Oracle purges FBDI interface data older than 30 days, so evidence disappears. And HDL loads run as an elevated user that bypasses data security, so a clean load says nothing about whether the right people can see the records.

This week: give every load object a reconciliation and a tolerance

List each load object (journals, supplier invoices, AutoInvoice lines, customers, fixed asset mass additions, workers) with its template, UCM account and import process.
For every run, record the scheduled process request IDs, source count, loaded count and rejected count. Rejected rows get a reason and an owner.
Agree tolerances with finance for amounts and counts before Mock 1 (example — set your own).
Save import reports and error output with the run. Do not rely on interface tables after 30 days.
After an HDL load, sign in as a business user and confirm the records are visible to the right roles only.

Number of the week

30 days

after which Oracle automatically purges FBDI interface table data. Capture your evidence before then.

Source: Oracle, FBDI for Financials 26D: Load Data into Tables

Use this week

Oracle FBDI & HDL Data Load Validation Tracker →
Load objects, run log with request IDs, counts, variance and tolerance checks.
Mock Cutover Rehearsal Tracker →
Time each load step in every rehearsal and flag overruns.

Next week: integrations. A quarterly update has already broken some of them. We make sure you would catch it.

Get the playbook in your inbox, one week at a time

Subscribe free and every template in the library is yours.