GL-08: GL Journal Import Diagnostic (Oracle Fusion)

Oracle Fusion Cloud GL journal import operates through a different mechanism than EBS R12. In Fusion, journals from external sources are imported via the Journal FBDI template — the Load Interface File for Import ESS job followed by the Import Journals ESS job. Errors are reported in the Import Journals output log and via OTBI queries against the GL Journal Entries subject area. There is no GL_INTERFACE table to query directly; the diagnostic approach goes entirely through the ESS job output and OTBI.

The most common Fusion journal import error is an invalid account combination — an account string that does not exist in the Fusion Chart of Accounts, that references a segment value that is inactive, or that violates a cross-validation rule. In Fusion, cross-validation rules are enforced at import time, whereas in EBS R12 they could sometimes be bypassed during GL_INTERFACE processing. The Fusion Import Journals execution report shows the specific account combination that failed validation and the cross-validation rule or segment value that caused the failure.

The FBDI template format itself is a common source of import failures in Fusion. The Journal Import FBDI template has specific column requirements — the journal source, category, currency, and accounting date must all be populated in the correct format. A template that was built for an older Fusion release may have column positions that no longer match the current FBDI template definition, causing a structural import failure where the ESS job fails before it processes any records.

GL-08 provides a structured Fusion journal import diagnostic using ESS Import Journals job history analysis, OTBI GL Journal Entries subject area for import error population analysis, BIP Import Journals execution report interpretation, FBDI template validation guidance, and the Manage Journals screen for navigating to imported journal errors.

ESS Import Job Status

Import Journals ESS job history — Succeeded, Completed with Warnings, or Error. Record count: imported vs rejected. Full output log access for error details.

BIP Import Execution Report

BIP Import Journals Execution Report — error type breakdown per journal line. Account combination errors, balance errors, period errors, and CVR violations with the specific journal reference for each.

OTBI Error Analysis

GL Journal Entries subject area query for imported journals in Error status. Identifies error patterns across the batch — same account, same period, same source — for efficient bulk correction.

FBDI Validation

FBDI template structure validation against the current Fusion release template definition. Column mapping verification — identifies structural issues before resubmission.

════════════════════════════════════════════════════════════
  ORACLE FUSION — GL JOURNAL IMPORT DIAGNOSTIC
════════════════════════════════════════════════════════════
  Journal Source     : External Allocations
  ESS Job ID         : ESS-2026-05142
  Records Submitted  : 184 journal lines
  Case Number        : FC-GL-2026-0218
  Report Date        : 24-FEB-2026 09:15:44
════════════════════════════════════════════════════════════

[ STEP 1 — ESS JOB STATUS ]                  STATUS: ⚠ WARNINGS
────────────────────────────────────────────────────────────
  Import Journals    : Completed with Warnings
  Imported           : 166 journal lines ✓
  Rejected           : 18 journal lines ✗

[ STEP 2 — BIP IMPORT EXECUTION REPORT ]
────────────────────────────────────────────────────────────
  Error Type 1       : Invalid Account Combination — 12 lines
  Error Type 2       : Journal Not in Balance — 4 lines (2 journals)
  Error Type 3       : Closed Period Accounting Date — 2 lines

[ STEP 3 — OTBI ANALYSIS ]
────────────────────────────────────────────────────────────
  Invalid Accounts   : Account 01.500.7810.0000 (12 lines) — disabled 01-JAN-2026
  Unbalanced Journal : Journal refs EXT-2026-0441 and EXT-2026-0442
  Closed Period      : Accounting date 31-JAN-2026 — period closed

[ STEP 4 — RESOLUTION NAVIGATION ]
────────────────────────────────────────────────────────────
  Account Fix        : Manage Chart of Accounts: re-enable or remap in FBDI
  Balance Fix        : Correct source FBDI template — add offsetting lines
  Date Fix           : Update accounting date to 28-FEB-2026 in FBDI and resubmit

════════════════════════════════════════════════════════════
  FUSION DIAGNOSTIC SUMMARY
════════════════════════════════════════════════════════════
  18 lines in 3 error types — correct FBDI and resubmit
════════════════════════════════════════════════════════════

Pre-Action Documentation — GL-08

ESS: Import Journals — job output log downloaded

BIP: Import Journals Execution Report — error detail saved

OTBI: GL Journal Entries — error population export

FBDI: Journal import template exported before correction

Exported before any UI action, ESS resubmission, or FBDI reimport. Provides a point-in-time record of the error state for the KB article and SR documentation if needed.

Pre-Action Verification

Fusion tenant accessibleConfirmed ✓

ESS Import Journals job history retrievedDownloaded ✓

BIP Execution Report run and savedSaved ✓

OTBI GL Journal Entries export completedSaved ✓

No Import Journals job currently runningConfirmed ✓

Audit Trail Record

CASE_NUMBER<consultant case#>

DIAGNOSTIC_TOOL<OTBI / REST API / BIP / ESS>

ERROR_SNAPSHOT<exported before action>

ACTION_TAKEN<UI path / ESS program / FBDI>

RESULT_VERIFIEDYES ✓

No Direct DB Access — By Design

Oracle Fusion Cloud is a SaaS environment. There is no consultant-accessible Oracle schema, no SQL*Plus connection, and no CONS_BACKUP tablespace. All diagnostic and corrective activity goes through OTBI, REST APIs, BIP reports, ESS programs, and the Fusion UI — the same supported tools Oracle Support uses.

REST API Reference — Endpoints Used in This Diagnostic

All API calls use OAuth 2.0 authentication. The base URL is your Fusion Cloud instance URL. Replace {instanceName} with your tenant name. Obtain the OAuth token via the /oauth/token endpoint using client credentials.

GETJournal Lines (Import Error Review)

/fscmRestApi/resources/11.13.18.05/journalLines

Key Query Parameters

q filter — BatchId={batchId} to scope to a specific imported batch

fields JournalLineId,LineNumber,AccountedDr,AccountedCr,AccountCombination,Status,ErrorMessage

Response Fields Read

AccountCombination — the account segments as a string, e.g. 01.600.7200.0000

Status — Valid or Error

ErrorMessage — validation error text for lines that failed

AccountedDr, AccountedCr — debits and credits in ledger currency

GETJournal Batch Status

/fscmRestApi/resources/11.13.18.05/journalBatches/{BatchId}

Path Parameters

BatchId integer — Fusion internal batch ID from the import job output

Key Query Parameters

fields BatchId,BatchName,Status,PostingDate,ControlTotalDr,ControlTotalCr

Response Fields Read

Status — Unposted, Posted, Error, Selected for Posting

ControlTotalDr, ControlTotalCr — expected totals for balance verification

PostingDate — date the batch was or will be posted

KB-FC-GL-0218-001 · Script: GL-08

Fusion GL Journal Import — 18 Lines Rejected: Invalid Account, Unbalanced Journals, Closed Period

Module: General Ledger
Platform: Oracle Fusion Cloud
Status: RESOLVED

Symptom

Fusion Import Journals ESS job ESS-2026-05142 completed with warnings. 18 of 184 journal lines rejected. BIP report shows 12 invalid account combinations, 4 unbalanced journal lines (2 journals), and 2 closed-period accounting dates.

Root Cause

Invalid accounts: source system still using account 01.500.7810.0000 disabled in Fusion COA on 01-JAN-2026. Unbalanced journals: 2 journals in the External Allocations batch were each missing a balancing credit line — source system export logic error. Closed period dates: 2 lines carried the source transaction date of 31-JAN-2026 — JAN-2026 was closed.

Tables Affected

ESS Import Journals Job ID: ESS-2026-05142, status: Completed with Warnings
BIP Import Journals Execution Report — 18 rejected lines (account, balance, period errors)
OTBI GL Journal Entries — journalSource: External Allocations, importStatus: Error

Fix Applied

FBDI corrected: 12 invalid account lines remapped to 01.500.7820.0000. 2 unbalanced journals corrected with offsetting credit lines. 2 date lines updated to 28-FEB-2026. FBDI resubmitted — all 18 previously rejected lines imported.

Prevention

Source system account mapping table updated to replace 01.500.7810.0000 references. FBDI validation script added to source export process — checks journal balance before file generation. GL-08 should run after each Import Journals batch to confirm no warnings.

Invalid Account Combination

Journal lines reference an account that does not exist in Fusion COA, is inactive, or violates a cross-validation rule. GL-08 identifies the specific account from the BIP report and provides the correction path.

Error

Journal Not in Balance

Journal debits and credits do not net to zero. GL-08 calculates the exact variance and identifies whether the FBDI source file is missing an offsetting line or has an incorrect amount.

Error

Closed Period Accounting Date

Accounting date in the FBDI file falls in a closed Fusion GL period. GL-08 identifies the correct open period and the accounting date to use in the corrected file.

Template

FBDI Template Mismatch

Source FBDI file built from an outdated template version. Column positions no longer match the current Fusion release. GL-08 identifies the misaligned columns from the ESS job error output.

Data Source	Type	Purpose
ESS: Import Journals	ESS	Import job status — imported vs rejected counts
BIP: Import Journals Execution Report	BIP	Error detail per rejected journal line
OTBI: GL Journal Entries	OTBI	Error population analysis — pattern detection
ESS: Load Interface File for Import	ESS	FBDI file load status before Import Journals
Manage Journals	Fusion UI	Navigation to imported journal errors for correction

Decision Framework

How Every Resolution Decision Is Made

Every condition identified by the diagnostic maps to exactly one resolution path. In Fusion Cloud, all paths go through supported Oracle interfaces — UI, REST API, FBDI, or ESS. Direct database access does not exist in this environment.

First Option — Always

Can the Fusion UI resolve this?

Oracle's own Fusion screens, Scheduled Processes (ESS), and workflow tools are always the first resolution path. Manage Invoices, Manage Suppliers, Manage Accounting Periods, BPM Worklist, Scheduled Processes — the diagnostic identifies the exact navigation path and screen sequence for every condition that can be resolved this way. No third-party tools, no API calls, no risk beyond what Oracle's own UI carries.

✓ Functional First

When the UI Path Is Insufficient

Can a REST API PATCH or FBDI reimport resolve this?

For bulk corrections or conditions not surfaced in the standard UI, Oracle Fusion's public REST APIs and FBDI import templates are the supported programmatic path. A REST API PATCH call to correct an invoice distribution account, an FBDI resubmission with corrected records after an import failure, or a Mass Update via the REST API — these are supported, documented, and reversible through normal Oracle mechanisms. The current state is exported before any API call is made.

→The API endpoint is an Oracle-published, versioned REST resource

→The FBDI template matches the current Fusion release version

→The pre-action state is exported (OTBI report / GET response) before the PATCH or import runs

→The result is verified via a follow-up GET or OTBI query before the case is closed

⚡ API / FBDI

Hard Stops — No Exceptions

Does this require Oracle Support?

Certain conditions in Fusion Cloud cannot be resolved through any customer-accessible interface. The diagnostic flags these and generates the Service Request documentation:

✗ESS job infrastructure failures — job status Error (not Completed with Warnings) indicating an engine-level issue not caused by data

✗Subledger accounting engine errors — Create Accounting failures where the error is in the Oracle accounting engine, not in the source transaction data

✗Recurring failures after correct setup — a condition that returns after a confirmed correct resolution indicates a code defect, submitted as an SR with a reproducible test case

✗Fusion data corruption — records in an inconsistent internal state not reachable through any published API or UI action

⚠ Oracle Support

For All Actions Taken

Export → Act → Verify → Document

Before any UI action, ESS resubmission, REST API call, or FBDI reimport — the current error state is exported via OTBI report, BIP report output, or REST API GET response. After the action, a verification step confirms the expected outcome. The complete sequence — tool used, pre-action state, action taken, result verified — is written into the KB article as the primary record of what was done and why.

📋 Documented

Condition Identified	Resolution Path	Notes
Invalid account combination in Fusion journal import	Functional First	Correct the account in the FBDI source file — re-enable in Manage Chart of Accounts or remap to an active account. Resubmit via Load Interface File for Import + Import Journals ESS.
Journal not in balance — debits ≠ credits	Functional First	Correct the FBDI source file by adding the missing offsetting line or adjusting amounts. GL-08 identifies the specific journal reference and exact variance from the BIP report.
Closed period accounting date	Functional First	Update the accounting date in the FBDI source file to a date in an open period. GL-08 identifies the next open period and the correct date.
Cross-validation rule violation	Functional First	Correct the account segment combination in the FBDI file. GL-08 identifies the CVR violated and the segment values that need to change.
FBDI template structure error — wrong column layout	Functional First	Download the current FBDI template from Fusion and rebuild the source file. GL-08 identifies the misaligned columns from the ESS job error output.
Import Journals ESS job status Error — full batch failure	Functional First	Review the full ESS job output log. Common causes: profile option misconfiguration, missing journal source or category, FBDI file format corruption.
Journal source not defined in Fusion	Functional First	Define the journal source via General Accounting > Setup > Journal Sources. GL-08 identifies the source name in the FBDI and the Fusion setup navigation.
Duplicate journal import — same batch imported twice	Functional First	Identify the original import via OTBI GL Journal Entries and delete the duplicate via Manage Journals. GL-08 confirms the duplicate by matching the external reference across both import runs.

Safeguards

Nothing Acts Without a Documented State

Fusion Cloud's SaaS architecture eliminates direct database access — which means every action is a supported Oracle API call, UI operation, or ESS submission. Before any action runs, the current error state is captured. After any action, the result is verified.

Pre-Action Documentation — All Completed First

✓

ESS: Import Journals — job output log downloaded

Exported before any corrective action is taken

✓

BIP: Import Journals Execution Report — error detail saved

Exported before any corrective action is taken

✓

OTBI: GL Journal Entries — error population export

Exported before any corrective action is taken

✓

FBDI: Journal import template exported before correction

Exported before any corrective action is taken

✓

Post-action verification

Follow-up OTBI query or REST GET confirms the expected state before the case is closed

Fusion Audit Trail — What Replaces CONS_BACKUP

In EBS R12, a CONS_BACKUP table provides the rollback point. In Fusion Cloud, the equivalent audit trail is built from three sources that together give a complete before-and-after record:

BEFORE STATE

OTBI report export or REST API GET response saved as the pre-action snapshot

ACTION RECORD

Fusion audit trail (Setup and Maintenance > Audit Reports) captures every UI and API change with user, timestamp, old value, and new value

AFTER STATE

Post-action OTBI query or REST GET confirms the fix — this output becomes the KB article verification artifact

GL-08 — Fusion Diagnostic Framework

════════════════════════════════════════════════════════════
  ORACLE FUSION — GL JOURNAL IMPORT DIAGNOSTIC
════════════════════════════════════════════════════════════
  Platform           : Oracle Fusion Cloud (no direct DB access)
  Tools Available    : ESS Job History, BIP Import Report, OTBI, Manage Journals
  Pre-Action Export  : FBDI file exported before any corrections
────────────────────────────────────────────────────────────
  Step 1 — ESS       : Import Journals job history retrieved — 18 rejected ✓
  Step 2 — BIP       : Import Journals Execution Report — 3 error types ✓
  Step 3 — OTBI      : GL Journal Entries error population analyzed ✓
────────────────────────────────────────────────────────────
  DIAGNOSTIC COMPLETE — 3 error types identified, FBDI corrections ready
════════════════════════════════════════════════════════════
  Documentation      : KB article generated from ESS and BIP output
  Fusion Audit Trail : Journal import changes logged in Fusion audit trail
  SR Reference       : N/A — all errors resolved via FBDI correction
════════════════════════════════════════════════════════════

Knowledge Base

Every Execution Produces a Record

The knowledge base article is generated automatically from the script's execution output. No manual documentation required. It becomes the institutional record — for the team, for auditors, and for every future engagement in the same environment.

Zero Manual Effort

Every field — environment, tables, before/after values, backup reference, root cause, prevention — is generated from actual execution output. Nothing is written by hand.

Patterns Surface Over Time

The first engagement produces findings. The third produces patterns. Recurring conditions that are invisible as individual incidents become obvious as knowledge base trends.

Survives Staff Turnover

The knowledge base is an institutional record of the Oracle environment. A new manager, a new DBA, or an external auditor can read exactly what happened, what was done, and what prevents recurrence.

KB-FC-GL-0218-001

Fusion GL Journal Import — 18 Lines Rejected: Invalid Account, Unbalanced Journals, Closed Period

Oracle Fusion Cloud · General Ledger

● RESOLVED

Symptom

Root Cause

Tables

ESS Import Journals Job ID: ESS-2026-05142, status: Completed with Warnings
BIP Import Journals Execution Report — 18 rejected lines (account, balance, period errors)
OTBI GL Journal Entries — journalSource: External Allocations, importStatus: Error

Fix Applied

Prevention

Documentation Page	Title	Scenario
Using General Ledger.Pdf	Using General Ledger — Journal Import	Fusion GL_INTERFACE validation and journal import configuration
Oracle Fusion General Ledger	Using Analytics and Reports for Financials	Account analysis and journal reports for import error verification

GL Journal Import Diagnostic (Oracle Fusion)

Why This Fails — and What It Costs

What This Script Diagnoses

Example Completed Worksheet

The Four-Layer Architecture in GL-08

Documentation Before Every Action — GL-08

Pre-Action Documentation — GL-08

Pre-Action Verification

Audit Trail Record

No Direct DB Access — By Design

Auto-Generated Knowledge Base Article

What This Script Finds

Invalid Account Combination

Journal Not in Balance

Closed Period Accounting Date

FBDI Template Mismatch

Tables Examined

How Every Resolution Decision Is Made

Nothing Acts Without a Documented State

Every Execution Produces a Record

Oracle Documentation References

Ready to Resolve This in Your Environment?

Why This Fails — and What It Costs

What This Script Diagnoses

Example Completed Worksheet

The Four-Layer Architecture in GL-08

Documentation Before Every Action — GL-08

Pre-Action Documentation — GL-08

Pre-Action Verification

Audit Trail Record

No Direct DB Access — By Design

Auto-Generated Knowledge Base Article

What This Script Finds

Invalid Account Combination

Journal Not in Balance

Closed Period Accounting Date

FBDI Template Mismatch

Tables Examined

How Every Resolution Decision Is Made

Nothing Acts Without a Documented State

Every Execution Produces a Record

Oracle Documentation References

Related Diagnostic Scripts

GL Period Close (Fusion)

AP Invoice Validation (Fusion)

Ready to Resolve This in Your Environment?