Results for “gl_balances”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GL_BALANCES is the core balances table in the Oracle General Ledger (GL) module of Oracle E-Business Suite, owned by the GL schema. It stores account balances for both detail and summary accounts, holding the period-end and period-activity figures that underpin financial reporting, trial balances, and consolidation across the ledger. In release 12.1.1 and 12.2.2 the table is documented with 37 columns and a composite primary key, GL_BALANCES_PK. Each row represents the balance of a single account combination, in a specified currency, for a specific accounting period, under a defined actual/budget/encumbrance context.

From a heuristic Data Vault modeling perspective, GL_BALANCES is best classified as a link object. It does not represent an independent business entity so much as the intersection of several hubs — Ledger, Code Combination, Currency, and Period — enriched with a set of measure columns (the debit, credit, and average-balance amounts). This classification is a modeling suggestion derived from its heavily referential structure rather than a documented attribute.

Key Information Stored

The composite primary key GL_BALANCES_PK comprises LEDGER_ID, CODE_COMBINATION_ID, CURRENCY_CODE, PERIOD_NAME, ACTUAL_FLAG, BUDGET_VERSION_ID, ENCUMBRANCE_TYPE_ID, and TRANSLATED_FLAG. These columns collectively define a unique balance record and serve as the de facto business key; there is no separate single-column surrogate. The most consequential columns are:

The _BEQ suffixed columns hold the equivalent balances in the ledger's reporting currency, supporting translation reporting.

Common Use Cases and Queries

The most frequent use of GL_BALANCES is financial reporting. A representative trial-balance query for a given ledger and period is:

  • SELECT code_combination_id, SUM(begin_balance_dr - begin_balance_cr), SUM(period_net_dr - period_net_cr) FROM gl_balances WHERE ledger_id = :ledger AND period_name = :period AND actual_flag = 'A' AND translated_flag = 'N' GROUP BY code_combination_id;

Other scenarios include comparing actual versus budget by filtering ACTUAL_FLAG and BUDGET_VERSION_ID, retrieving average daily balances for cash-flow analysis, and drilling from a summary template into detail via TEMPLATE_ID. Reporting tools such as FSG and the GL standard reports read this table directly. Because GL_BALANCES is volatile and large, queries should always filter on LEDGER_ID, PERIOD_NAME, and ACTUAL_FLAG to leverage the primary key and avoid full scans.

Related Objects

Referential integrity links GL_BALANCES to several master tables through documented foreign keys:

These relationships confirm GL_BALANCES as the central intersection of ledger, account, currency, and period dimensions, making it the primary source for balance enquiry and financial statement generation within Oracle General Ledger.