Results for “gl_archive_batches”

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

Overview

GL_ARCHIVE_BATCHES is a General Ledger archive table in Oracle E-Business Suite (12.1.1 and 12.2.2) that stores journal batches which have been moved into archival storage. Its role is to preserve batch-level header information for journal entries that are no longer active in the operational GL_JE_BATCHES table, supporting historical reporting, audit retention, and purge-archival workflows. The table is documented as "not implemented in this database," meaning it exists as a defined dictionary object but may not be populated in every environment, particularly those where the GL archive/purge programs have never been executed.

From a Data Vault modeling perspective, the mined heuristic classification for GL_ARCHIVE_BATCHES is link. This is consistent with its structure: it carries foreign keys to GL_SETS_OF_BOOKS and GL_JE_BATCHES, making it a relationship-bearing object that associates a journal batch with a ledger (set of books). Modeling it as a link entity appropriately captures the associative nature of the record rather than treating it as an independent hub or descriptive satellite.

Key Information Stored

The documented metadata identifies the following essential columns and keys:

• JE_BATCH_ID — surrogate primary key of the table, defined by the GL_ARCHIVE_BATCHES_PK constraint. It corresponds to the source journal batch identifier in GL_JE_BATCHES and links archived rows back to their originating batch.
• NAME — the batch name. Together with DEFAULT_PERIOD_NAME and SET_OF_BOOKS_ID, this forms the unique business key captured by the GL_ARCHIVE_BATCHES_UK1 constraint.
• DEFAULT_PERIOD_NAME — the default accounting period associated with the archived batch, used to identify the accounting cycle the batch belongs to.
• SET_OF_BOOKS_ID — the ledger identifier, emphasizing that archival is performed within the context of a specific set of books.

The primary key (GL_ARCHIVE_BATCHES_PK) is a pure surrogate identifier on JE_BATCH_ID, while GL_ARCHIVE_BATCHES_UK1 (NAME, DEFAULT_PERIOD_NAME, SET_OF_BOOKS_ID) serves as the natural business-key candidate that enforces uniqueness across batch name, period, and ledger.

Common Use Cases and Queries

Typical scenarios for this table include reconciliation of archived versus active journal batches, historical audit reporting of batch activity by ledger and period, and verification that archival processes retained expected header information.

A common query pattern is to join archived batches back to their source table to identify batches that exist in both places, or to join to GL_SETS_OF_BOOKS for ledger names. For example:

• Listing archived batches for a specific ledger and period: filter on SET_OF_BOOKS_ID and DEFAULT_PERIOD_NAME using the unique key columns.
• Comparing counts between GL_JE_BATCHES and GL_ARCHIVE_BATCHES by JE_BATCH_ID to validate archival completeness.
• Reporting on ledger-level archival volume by joining SET_OF_BOOKS_ID to GL_SETS_OF_BOOKS.

Because the table may be unpopulated in a given instance, queries should first confirm row existence or check whether archival has been performed.

Related Objects

The following objects are the most significant related dependencies, based on the documented foreign keys:

• GL_JE_BATCHES — referenced via GL_ARCHIVE_BATCHES.JE_BATCH_ID; the operational source of archived journal batches.
• GL_SETS_OF_BOOKS — referenced via GL_ARCHIVE_BATCHES.SET_OF_BOOKS_ID; provides ledger context and descriptions for archived data.

In practice, GL_ARCHIVE_BATCHES is also adjacent to related GL archival and journal objects such as GL_JE_HEADERS and GL_JE_LINES, which follow similar archival logic, and to GL_ARCHIVE_BATCHES' companion archive tables that preserve journal-entry detail. GL_JE_BATCHES and GL_SETS_OF_BOOKS remain the primary join targets for meaningful reporting.