Search Results gl_consolidation_audit




Overview
Explore in AI Chat

Overview

GL_CONSOLIDATION_AUDIT is a General Ledger table in the Oracle EBS 12.1.1 and 12.2.2 schemas (owner: GL) that stores audit data generated during consolidation runs. Consolidation in Oracle General Ledger is the process by which balances from one or more source (subsidiary) ledgers are combined into a single target (parent) ledger. This table functions as the persistent audit trail for each such run, capturing the balances contributed by the source ledger, the accounts involved, and the parameters under which the transfer executed.

The table is documented with 43 columns in the ETRM 12.2.2 physical schema. Based on its foreign key structure, a heuristic Data Vault classification of link is appropriate: the table principally records associations between a consolidation definition, a source ledger, a target ledger, a source code combination, and the concurrent request that produced the output, rather than acting as a standalone descriptive hub or an attribute-only satellite.

Key Information Stored

The most operationally significant columns are:

No unique index columns are documented in the supplied metadata, so CONSOLIDATION_ID, REQUEST_ID, and the ledger/account foreign keys should be treated as the principal business-key candidates for querying and joining rather than as guaranteed unique identifiers.

Common Use Cases and Queries

Typical usage centers on auditing and reconciling consolidation output: verifying that every source account expected to transfer did transfer, tracing a consolidated balance back to its source ledger and account, and determining which concurrent request produced a given result.

A representative query pattern joins the audit table back to its parent consolidation and the concurrent request:

  • Select consolidation_id, from_ledger_id, to_ledger_id, from_period_name, to_period_name, from_code_combination_id, entered_dr, entered_cr from gl_consolidation_audit where consolidation_id = :id order by from_code_combination_id;
  • Join to fnd_concurrent_requests on request_id to identify the program run, submitter, and completion status associated with the audited balances.
  • Join to gl_code_combinations on from_code_combination_id to resolve the concatenated segment values into a readable account.

Common reporting scenarios include reconciliation of subsidiary-to-parent balances, exception analysis for accounts that failed to transfer, and historical review of consolidation activity by period and ledger pair.

Related Objects

The following objects interact with GL_CONSOLIDATION_AUDIT through documented foreign key relationships:

  • GL_CONSOLIDATION — via CONSOLIDATION_ID; the parent consolidation definition and run record.
  • GL_SETS_OF_BOOKS_11I — via FROM_LEDGER_ID; resolves the source ledger name and currency.
  • GL_CODE_COMBINATIONS — via FROM_CODE_COMBINATION_ID; resolves account segment values.
  • FND_CONCURRENT_REQUESTS — via REQUEST_ID; identifies the concurrent program execution that generated the audit rows.

The target ledger reference (TO_LEDGER_ID) is also part of the relationship structure and should be resolved against the ledger definition when reporting on the destination side of a consolidation.