Search Results xla_analytical_balances




Overview
Explore in AI Chat

Overview

XLA_ANALYTICAL_BALANCES is a Subledger Accounting (XLA) table owned by the XLA schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores period-end balances for each analytical criterion defined within Subledger Accounting, providing the aggregated debit and credit position of an account combination broken down by analytical detail value and accounting period. Rather than holding transactional journal entries, the table maintains summarized balances that support analytical reporting, subledger reconciliation, and drill-down from summarized positions to underlying accounting events.

Under the heuristic Data Vault classification derived from its foreign key structure, the table is satellite-leaning. Its composite primary key combines the ledger, account combination, analytical detail value, and period, indicating that the grain is a descriptive context attached to dimension-like business keys rather than a transactional hub. Modeling it as a satellite keyed on ledger, account, and analytical dimensions reflects its role as a slowly changing balance snapshot per period.

Key Information Stored

The table contains 25 documented columns. The most significant are the following:

The surrogate primary key is XLA_ANALYTICAL_BALANCES_PK, composed of APPLICATION_ID, LEDGER_ID, CODE_COMBINATION_ID, ANALYTICAL_DETAIL_VALUE_ID, and PERIOD_NAME. The unique index XLA_ANALYTICAL_BALANCES_U1 mirrors these same columns, making them the business-key candidate for uniquely identifying a balance row.

Common Use Cases and Queries

Typical uses include analytical balance reporting, period-over-period comparison, reconciliation of subledger analytical balances to General Ledger, and drill-down from summarized analytical positions to detail. A representative query retrieves current period balances for a ledger and period:

  • Filter by LEDGER_ID and PERIOD_NAME to isolate a reporting period, then aggregate PERIOD_BALANCE_DR and PERIOD_BALANCE_CR by CODE_COMBINATION_ID.
  • Join to GL_CODE_COMBINATIONS on CODE_COMBINATION_ID to resolve the account combination and produce human-readable reporting.
  • Compare BEGINNING_BALANCE_DR/CR against PERIOD_BALANCE_DR/CR to derive closing balances for analytical criteria.
  • Use DRAFT_ columns to report unposted analytical balances separately from posted balances before period close.
  • Leverage FIRST_PERIOD_FLAG and INITIAL_BALANCE_FLAG to validate opening balance setup during implementation and period roll-forward.

Related Objects

The most significant related objects, based on documented foreign key and key relationships, include:

  • GL_CODE_COMBINATIONS — joined via CODE_COMBINATION_ID, the sole documented foreign key target, supplying account combination context.
  • XLA_ANALYTICAL_BALANCES_PK / XLA_ANALYTICAL_BALANCES_U1 — the primary key and unique index enforcing the composite business key.
  • XLA analytical criteria definitions — referenced through ANALYTICAL_DETAIL_VALUE_ID to resolve the analytical criterion and its detail value.
  • Subledger accounting and GL period tables — contextualized by LEDGER_ID, APPLICATION_ID, and PERIOD_NAME for ledger and period validation.
  • XLA subledger reporting and reconciliation features — consume this table for analytical balance inquiry and drill-down.

Because the table is satellite-leaning, dependent objects primarily join to it on the composite key rather than referencing it as a parent. Any integration should preserve the ledger, account combination, analytical detail value, and period grain to avoid duplicating or splitting balance records.