Search Results gl_archive_balances




Overview
Explore in AI Chat

Overview

The GL_ARCHIVE_BALANCES table is a core data object within the Oracle E-Business Suite General Ledger (GL) module, designed to store archived historical account balances. Its primary role is to serve as a repository for summarized financial data that has been moved from the primary transactional tables, such as GL_BALANCES, for long-term retention and historical reporting. This archiving process is crucial for performance management, data lifecycle management, and maintaining a clean production environment by segregating active and historical data. The table's structure, defined by a composite primary key, is optimized for the efficient storage and retrieval of period-end balances across various accounting dimensions, including sets of books, accounts, currencies, and budget versions.

Key Information Stored

The table stores aggregated balance information keyed by a combination of accounting attributes. The primary key columns define the unique context for each archived balance record: SET_OF_BOOKS_ID identifies the ledger, CODE_COMBINATION_ID specifies the accounting flexfield combination, CURRENCY_CODE denotes the transaction currency, and PERIOD_NAME indicates the accounting period. Additional key columns further classify the balance type: ACTUAL_FLAG (e.g., 'A' for actual, 'B' for budget), BUDGET_VERSION_ID for budget-specific data, ENCUMBRANCE_TYPE_ID for encumbrance tracking, and TRANSLATED_FLAG for balances that have been currency translated. While the specific balance amount columns are not detailed in the provided excerpt, typical related tables store columns like PERIOD_NET_DR, PERIOD_NET_CR, and BEGIN_BALANCE_DR/CR.

Common Use Cases and Queries

The primary use case is generating historical financial reports that span many closed periods without querying the voluminous detail in the GL_JE_BATCHES or GL_JE_LINES tables. For instance, a trend analysis report comparing year-over-year actual balances for a specific cost center would query this archive. A common SQL pattern involves joining to dimension tables for descriptive information.

Sample Query Pattern:
SELECT gab.PERIOD_NAME,
gab.CURRENCY_CODE,
gcc.SEGMENT1 Company,
gcc.SEGMENT3 Account,
gab.PERIOD_NET_DR,
gab.PERIOD_NET_CR
FROM GL_ARCHIVE_BALANCES gab,
GL_CODE_COMBINATIONS gcc
WHERE gab.CODE_COMBINATION_ID = gcc.CODE_COMBINATION_ID
AND gab.SET_OF_BOOKS_ID = 1
AND gab.ACTUAL_FLAG = 'A'
AND gab.PERIOD_NAME LIKE '%-13';

It is critical to note the provided metadata states "Not implemented in this database," indicating this specific table might be a documented but unused artifact in standard EBS deployments. Practitioners should verify its existence and population status in their specific environment before developing dependent code.

Related Objects

GL_ARCHIVE_BALANCES maintains foreign key relationships with several fundamental GL setup and transactional tables, ensuring referential integrity for archived data. These documented relationships are:

These relationships allow archived balances to be correctly contextualized with descriptive data from master tables for comprehensive reporting. The table is conceptually related to GL_BALANCES, which likely holds the active, non-archived balance data.