The Oracle Fusion GL journal FBDI — GL_INTERFACE — the key columns (ledger, period, segments, DR/CR), balancing rules, and how to load with Import Journals.
Journals load through a single interface table, GL_INTERFACE, then the Import Journals process creates journal batches in the ledger.
| Column group | Examples |
|---|---|
| Ledger & period | LEDGER_ID, ACCOUNTING_DATE, PERIOD_NAME |
| Source & category | USER_JE_SOURCE_NAME, USER_JE_CATEGORY_NAME |
| Account | SEGMENT1..n (chart-of-accounts segment values) |
| Amounts | ENTERED_DR, ENTERED_CR, CURRENCY_CODE |
GROUP_ID / REFERENCE columns to control how lines batch into journalsGet the object’s FBDI spreadsheet (.xlsm) from Oracle’s File-Based Data Import guide for your Fusion release.
Populate the required and conditionally-required columns; leave system-derived columns blank.
Use the template’s “Generate CSV File” macro, then ZIP the resulting .csv file(s).
Run the Load Interface File for Import scheduled process, selecting the import job and your ZIP — data lands in the interface tables.
Run the object’s import process to move data from interface tables to base tables.
Check the import output/error report, fix rejected rows, reload, and reconcile record counts source-to-target.
Balances walkthrough: Migrate GL balances to Oracle Fusion →
The Journal Import FBDI, which populates GL_INTERFACE and is processed by the Import Journals scheduled process to create journal batches in the ledger.
Common causes: invalid or disabled code-combinations, accounting dates in a closed period, an import-disabled journal source, or unbalanced debits and credits within a group.
Syntra generates and loads FBDI/HDL for every object at scale — with source extraction, mapping and reconciliation built in. Skip the hand-built templates.