GL-06: Consolidation Diagnostic

Oracle EBS GL consolidation is the process of combining balances from multiple subsidiary ledgers into a parent consolidation ledger. It is the final step in the financial close cycle — everything else must be complete and correct before consolidation can run accurately. When consolidation fails, or produces incorrect results, the root cause is almost always in one of three places: the source ledger period close is incomplete, the consolidation set mapping between the subsidiary chart of accounts and the parent chart of accounts has gaps, or the elimination entries required to remove intercompany transactions between consolidated entities have not been generated.

The consolidation mapping problem is the most technically complex. In Oracle EBS, the consolidation process uses GL_CONSOLIDATION_SETS and account range mappings to translate subsidiary account balances into parent account codes. If a new account is added to a subsidiary ledger mid-year without a corresponding mapping entry in the consolidation set, the balance for that account will not be transferred to the parent ledger. The resulting consolidation shortfall is not reported as an error — the consolidation simply runs to completion with a balance that is understated by the amount of the unmapped account. The discrepancy surfaces only when the consolidated trial balance is reviewed against the sum of subsidiary trial balances.

Elimination entries are required for any intercompany transaction that appears in both a subsidiary ledger (as a receivable) and the parent ledger (as a payable). If the elimination set is not configured, or if the intercompany accounts in the subsidiaries are not mapped to the elimination accounts in the parent, the consolidated balance sheet will overstate both assets and liabilities by the intercompany amount. In organizations with significant intercompany activity, this can represent a material error.

GL-06 runs a complete consolidation diagnostic — consolidation set configuration and mapping completeness, source ledger close status per subsidiary, intercompany elimination set configuration and balance, unmapped account identification, consolidation journal existence and amount for the current period, and balance comparison between the sum of subsidiary ledgers and the consolidated parent ledger.

Source Ledger Status

Period close status for all subsidiary ledgers in the consolidation set. Consolidation cannot run until all source ledgers have closed the period.

Account Mapping Completeness

GL_CONS_FLEX_HIERARCHIES mapping validation — identifies subsidiary accounts with non-zero balances that have no corresponding mapping to a parent account.

Elimination Entries

Intercompany elimination set configuration and balance. Confirms elimination journals have been generated and posted before consolidation runs.

Consolidation Journals

Existence and posting status of consolidation transfer journals in the parent ledger for the current period. Balance comparison against the expected consolidated amount.

Subsidiary Reconciliation

Consolidated parent ledger balance compared to the sum of subsidiary ledger balances by account. Identifies any mapping gaps or consolidation errors by account type.

════════════════════════════════════════════════════════════
  ORACLE EBS R12 — GL CONSOLIDATION DIAGNOSTIC
════════════════════════════════════════════════════════════
  Consolidation Set  : US-CONSOLIDATED-FEB2026
  Parent Ledger      : Worldwide Consolidation Ledger
  Subsidiaries       : US Primary, US Secondary, CA Subsidiary
  Case Number        : GL-538490
  Report Date        : 25-FEB-2026 17:50:40
════════════════════════════════════════════════════════════

[ SECTION 1 — SOURCE LEDGER STATUS ]
────────────────────────────────────────────────────────────
  US Primary         : FEB-2026 CLOSED ✓
  US Secondary       : FEB-2026 CLOSED ✓
  CA Subsidiary      : FEB-2026 OPEN ✗ — not yet closed
  ✗ FAIL: CA Subsidiary period not closed — consolidation cannot run

[ SECTION 2 — ACCOUNT MAPPING ]               STATUS: ✗ FAIL
────────────────────────────────────────────────────────────
  Total Accounts     : 842 mapped
  Unmapped Accounts  : 3 accounts with balances NOT in mapping ✗
  Unmapped 1         : CA: 01-620-8110-0000 — CAD 84,200 unmapped
  Unmapped 2         : CA: 01-620-8120-0000 — CAD 12,100 unmapped
  Unmapped 3         : US-SEC: 01-500-9410-0000 — USD 4,800 unmapped

[ SECTION 3 — ELIMINATION ENTRIES ]           STATUS: ✓ PASS
────────────────────────────────────────────────────────────
  IC elimination entries generated and posted ✓

[ SECTION 4 — CONSOLIDATION JOURNALS ]        STATUS: ⚠ BLOCKED
────────────────────────────────────────────────────────────
  ⚠ Consolidation not yet run — blocked by CA Subsidiary close

════════════════════════════════════════════════════════════
  DIAGNOSTIC SUMMARY
════════════════════════════════════════════════════════════
  2 blocking conditions: CA Subsidiary not closed, 3 unmapped accounts
  FIX: Close CA period, add 3 mapping entries, rerun consolidation
════════════════════════════════════════════════════════════

Diagnostic Engine

Runs 28+ checks covering consolidation set configuration and mapping completeness, source ledger close status per subsidiary, intercompany elimination set configuration and balance, unmapped account identification with balance amounts, consolidation journal existence, and consolidated vs subsidiary balance reconciliation.

Backup Created

Before any consolidation mapping or journal data is modified, CONS_BACKUP.GL_CONSOLIDATION_SETS_<case#> and GL_CONS_FLEX_HIERARCHIES_<case#> are created and row counts verified.

Guided Data Fix

Account mapping additions and consolidation journal corrections are the primary fix actions. GL-06 generates the mapping INSERT for each unmapped account and provides the Consolidate Balances resubmission parameters after source ledgers are closed.

KB Article Generated

Complete KB article generated — consolidation set, unmapped accounts with balances, source ledger status, resolution sequence, consolidation completion confirmation. Upload directly to your knowledge base.

KB-GL-538490-001 · Script: GL-06

Consolidation Blocked — CA Subsidiary Period Open and 3 Unmapped Accounts

Module: General Ledger
Platform: EBS R12.2.10
Status: RESOLVED

Symptom

GL consolidation for FEB-2026 cannot run. CA Subsidiary period FEB-2026 not yet closed. 3 accounts with balances (CAD 96,300 + USD 4,800) have no mapping in the consolidation set. Consolidated parent ledger will understate the balance if run without the mapping.

Root Cause

CA Subsidiary close delayed — 2 unposted journal batches identified by GL-02. Accounts 01-620-8110 and 01-620-8120 were added to the CA Subsidiary COA in JAN-2026 for a new cost center — the consolidation mapping was not updated when the accounts were added.

Tables Affected

GL_CONS_FLEX_HIERARCHIES — no mapping rows for CA accounts 8110, 8120, and US-SEC account 9410
GL_PERIOD_STATUSES — STATUS = OPEN for CA Subsidiary, FEB-2026

Fix Applied

CA Subsidiary: 2 unposted batches posted, period closed. 3 consolidation mapping entries added to GL_CONS_FLEX_HIERARCHIES with full backup. Consolidate Balances rerun — parent ledger updated. Consolidated trial balance reconciled to subsidiary sum.

Prevention

COA change process updated: new account requests must include a consolidation mapping update before the account is activated. GL-06 mapping completeness check should run at period day-minus-3 for all subsidiaries.

Subsidiary Period Not Closed

Consolidation cannot run if any source ledger period is still open. GL-06 identifies which subsidiary is blocking and runs GL-02 checks for that ledger to surface the specific close blocker.

Mapping

Unmapped Account with Balance

New account added to subsidiary COA without corresponding consolidation mapping entry. Balance silently omitted from consolidated parent ledger. GL-06 identifies unmapped accounts and generates the mapping insert.

Elimination

IC Elimination Not Generated

Intercompany transactions between subsidiaries not eliminated in the consolidated ledger — overstating both assets and liabilities. GL-06 identifies the IC accounts and the elimination set configuration gap.

Variance

Consolidated Balance ≠ Subsidiary Sum

Post-consolidation variance between the parent ledger balance and the sum of subsidiaries. Indicates a mapping gap or an incomplete consolidation run. GL-06 calculates the exact variance by account.

Table	Module	Purpose
GL_CONSOLIDATION_SETS	GL	Consolidation set definitions — source and target ledgers
GL_CONS_FLEX_HIERARCHIES	GL	Account mapping — subsidiary account to parent account
GL_JE_HEADERS	GL	Consolidation and elimination journal headers
GL_BALANCES	GL	Period-end balances — subsidiary and parent
GL_PERIOD_STATUSES	GL	Period close status per subsidiary ledger
GL_LEDGERS	GL	Ledger configuration — parent and subsidiary
GL_TRANSLATION_STATUSES	GL	Translation completion status before consolidation
GL_INTERCOMPANY_ACCOUNTS	GL	IC elimination account configuration

Decision Framework

How Every Fix Decision Is Made

Before any data is modified in a production Oracle database, AP-01 walks through a four-stage decision process. Every condition identified by the diagnostic maps to exactly one resolution path.

First Option — Always

Can the front end fix this?

Oracle's own forms and concurrent programs are always the first option. If the condition can be corrected through Oracle's standard UI — a form, a concurrent program, a setup screen — that path is taken first. No consultant SQL required, no database risk, and the fix is fully supported by Oracle. The diagnostic identifies these conditions explicitly and states the exact front-end navigation path.

✓ Functional Fix

When Front End Is Not Available

Is a direct data fix safe to apply?

When the front-end path is unavailable or would require an unacceptable volume of manual steps, a direct fix is evaluated against explicit criteria. All of the following must be true before proceeding:

→The fix mirrors exactly what Oracle's own code would have done if the underlying condition were corrected

→All dependent tables have been identified and will be updated in the same transaction

→The fix is fully reversible — a single INSERT from the backup table restores the original state

→The environment patch level has been confirmed against the fix logic version

⚡ Direct Fix

Hard Stops — No Exceptions

Does this require Oracle Support?

Certain table areas are never touched directly, regardless of how well the underlying structure is understood. The diagnostic flags these conditions and generates the Service Request documentation:

✗XLA subledger tables — XLA_EVENTS, XLA_AE_HEADERS — incorrect changes corrupt the subledger audit trail in ways undetectable until period close fails or an auditor requests a reconciliation

✗Workflow engine tables — WF_ITEMS, WF_ITEM_ACTIVITY_STATUSES — ad-hoc DML can corrupt the workflow engine state instance-wide

✗Recurring conditions after a fix — indicates a code defect, not a data error. Documented and submitted as a Service Request with a reproducible test case

⚠ Oracle Support

For All Approved Direct Fixes

Backup → Execute → Verify → Document

A timestamped backup table is created and row-count verified before the first UPDATE fires. Explicit parameter confirmation is required — the script will not self-execute. After execution, a verification query confirms the expected state. A complete change record — rows affected, before and after values, database username, timestamp — is written to the FIX_BACKUP_REGISTRY and becomes the primary artifact in the knowledge base entry for this incident.

📋 Documented

Condition Identified	Resolution Path	Notes
Source ledger period not closed — consolidation blocked	Functional First	Close the subsidiary period using GL-02 period close readiness diagnostic for that ledger. Consolidation can only run after all source ledger periods are in CLOSED status.
Unmapped accounts with balances in subsidiary	Direct Fix	GL-06 generates the INSERT for each missing mapping row in GL_CONS_FLEX_HIERARCHIES with full backup. Parent account is identified from the subsidiary account type and the existing mapping pattern.
Elimination entries not generated	Functional First	Submit the Consolidate Balances program with elimination sets enabled. GL-06 identifies which intercompany account pairs are missing elimination entries and the elimination set configuration.
Consolidation journal out of balance	Direct Fix	GL-06 calculates the exact variance, identifies the unbalanced mapping, and generates the correcting consolidation journal entry with full backup and Controller authorization.
Translation not run before consolidation	Functional First	Submit the Translate Balances concurrent program for the subsidiary ledger. Consolidation of a foreign currency subsidiary requires translation to the parent functional currency first.
Consolidation set missing subsidiary	Functional First	Add the subsidiary ledger to the consolidation set via GL > Setup > Consolidation Sets. GL-06 identifies which subsidiary ledgers have balances but are not included in the active consolidation set.
Prior consolidation run not reversed	Direct Fix	GL-06 identifies the prior-period consolidation journals that should have been reversed and generates the reversal entry with full backup before the current period consolidation runs.
Balance mismatch after consolidation — subsidiary sum ≠ parent	Functional First	Run Consolidate Balances again after confirming all mappings are complete. GL-06 calculates the exact variance between subsidiary sum and consolidated parent balance for each account.

Safeguards

Nothing Executes Without a Safety Net

Before any data fix runs, the script verifies pre-flight conditions and creates a complete verified backup. If any check fails, the script aborts. There is no partial execution path.

Pre-Flight Checks — All Must Pass

✓

POSTED_FLAG = 'N'

Will not modify a posted transaction under any circumstances

✓

ACCOUNTING_EVENT_ID IS NULL

Will not modify rows with an active or pending XLA accounting event

✓

No active database lock

Checks V$LOCK — will not proceed if another session holds a lock on target rows

✓

CONS_BACKUP schema writable

Backup schema must be accessible before any DML is permitted

✓

Explicit confirmation required

Script outputs a confirmation prompt — DML does not execute until consultant enters the case number as the execution parameter

Backup Methodology

Before the first UPDATE fires, the script creates a complete copy of every row to be modified. Tables are named CONS_BACKUP.<TABLE>_<CASE#> and persist permanently after execution.

GL_CONSOLIDATION_SETS

GL_CONS_FLEX_HIERARCHIES

GL_JE_HEADERS

GL_BALANCES

Row count verified after backup creation. If backup fails for any reason the script aborts without executing any DML. Rollback is a single INSERT from the backup table. No reconstruction required.

GL-06 — Pre-Flight & Backup Verification

════════════════════════════════════════════════════════════
  PRE-FLIGHT SAFETY CHECK
════════════════════════════════════════════════════════════
  Consolidation Set  : US-CONSOLIDATED-FEB2026
  Unmapped Accounts  : 3 — mapping to be added
  CONS_BACKUP Schema : Accessible ✓
  Session Lock Check : No locks ✓
────────────────────────────────────────────────────────────
  ALL PRE-FLIGHT CHECKS PASSED
════════════════════════════════════════════════════════════
  Creating : CONS_BACKUP.GL_CONS_FLEX_HIERARCHIES_538490
  Rows     : 842 existing mapping rows backed up ✓
  Registry : FIX_BACKUP_REGISTRY — ID 4152 created ✓
────────────────────────────────────────────────────────────
  BACKUP COMPLETE
════════════════════════════════════════════════════════════
  Enter case number to confirm 3 mapping inserts : 538490
  Confirmed.
════════════════════════════════════════════════════════════

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-GL-538490-001

Consolidation Blocked — CA Subsidiary Period Open and 3 Unmapped Accounts

EBS R12.2.10 · General Ledger

● RESOLVED

Symptom

Root Cause

Tables

GL_CONS_FLEX_HIERARCHIES — no mapping rows for CA accounts 8110, 8120, and US-SEC account 9410
GL_PERIOD_STATUSES — STATUS = OPEN for CA Subsidiary, FEB-2026

Fix Applied

Prevention

R12 Guide (PDF)	Title & Chapter	Detail
120glug.pdf	Oracle General Ledger User's Guide — Consolidation	Consolidation sets, consolidation programs, and elimination journal entry generation
120glug.pdf	Oracle General Ledger User's Guide — Reporting	Financial Statements Generator (FSG) and consolidation reporting in EBS R12
120funmo.pdf	Oracle Applications Multiple Organizations Implementation Guide	Ledger hierarchy and legal entity structure for consolidation entity setup

Consolidation Diagnostic

Why This Fails — and What It Costs

What This Script Diagnoses

What the Report Looks Like

The Four-Layer Architecture in GL-06

Backup & Rollback for GL-06

Tables Backed Up — GL-06

Pre-Flight Safety Guards

FIX_BACKUP_REGISTRY Entry

Auto-Generated Knowledge Base Article

What This Script Finds

Subsidiary Period Not Closed

Unmapped Account with Balance

IC Elimination Not Generated

Consolidated Balance ≠ Subsidiary Sum

Tables Examined

How Every Fix Decision Is Made

Nothing Executes Without a Safety Net

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

What the Report Looks Like

The Four-Layer Architecture in GL-06

Backup & Rollback for GL-06

Tables Backed Up — GL-06

Pre-Flight Safety Guards

FIX_BACKUP_REGISTRY Entry

Auto-Generated Knowledge Base Article

What This Script Finds

Subsidiary Period Not Closed

Unmapped Account with Balance

IC Elimination Not Generated

Consolidated Balance ≠ Subsidiary Sum

Tables Examined

How Every Fix Decision Is Made

Nothing Executes Without a Safety Net

Every Execution Produces a Record

Oracle Documentation References

Related Diagnostic Scripts

GL Period Close Readiness

Revaluation Diagnostic

Intercompany Balancing Diagnostic

Ready to Resolve This in Your Environment?