Results for “gl_archive_headers”

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

Overview

GL_ARCHIVE_HEADERS is a General Ledger archive table that stores archived journal header records within Oracle EBS 12.1.1 and 12.2.2. The table captures journal entry header information that has been moved out of the active transaction tables, typically during an archiving or purge operation. The ETRM metadata describes the object as "Archive journal headers," indicating that it functions as a historical repository for journal header data that is no longer required in the operational GL_JE_HEADERS and GL_JE_BATCHES structures. Because its column layout mirrors the live journal header structures, GL_ARCHIVE_HEADERS supports retention of audit trail information without impacting the performance of active journal processing.

Based on the foreign key structure mined from the metadata, a Data Vault modeling classification of link is suggested. This classification reflects the table's role as a connector between the journal header/batch entities and reference dimension tables such as GL_SETS_OF_BOOKS, FND_CURRENCIES, GL_BUDGET_VERSIONS, GL_ENCUMBRANCE_TYPES, GL_RECURRING_HEADERS, GL_DAILY_CONVERSION_TYPES, and GL_JE_HEADERS. In practice, however, the table behaves more like a satellite snapshot of the GL_JE_HEADERS hub, since it retains descriptive journal attributes alongside the foreign key references.

Notably, the ETRM implementation data states that GL_ARCHIVE_HEADERS is "Not implemented in this database." This does not mean the table is absent from the underlying Oracle EBS schema; it indicates that the archive table was not populated or configured in the documented instance at the time of cataloguing.

Key Information Stored

The table's primary surrogate key is defined by the GL_ARCHIVE_HEADERS_PK unique index on JE_HEADER_ID. This surrogate identifier uniquely identifies each archived journal header record. In addition to the primary key, a second unique index, GL_ARCHIVE_HEADERS_UK1, is defined on the combination of JE_BATCH_ID and NAME, establishing these as a business-key candidate for the archived header within its batch context.

• JE_HEADER_ID — Surrogate primary key uniquely identifying the archived journal header; also a foreign key to GL_JE_HEADERS.
• JE_BATCH_ID — Foreign key to GL_JE_BATCHES identifying the journal batch to which the archived header belonged; part of the unique business key UK1.
• NAME — The journal header name; combined with JE_BATCH_ID in UK1.
• SET_OF_BOOKS_ID — Foreign key to GL_SETS_OF_BOOKS identifying the ledger/set of books for the archived entry.
• CURRENCY_CODE — Foreign key to FND_CURRENCIES giving the transaction currency.
• CURRENCY_CONVERSION_TYPE — Foreign key to GL_DAILY_CONVERSION_TYPES indicating the rate type used.
• ENCUMBRANCE_TYPE_ID — Foreign key to GL_ENCUMBRANCE_TYPES when the journal is encumbrance-related.
• BUDGET_VERSION_ID — Foreign key to GL_BUDGET_VERSIONS for budget journal entries.
• FROM_RECURRING_HEADER_ID — Foreign key to GL_RECURRING_HEADERS for entries generated from recurring journals.
• ACCRUAL_REV_JE_HEADER_ID — Foreign key to GL_JE_HEADERS referencing the related accrual reversal header.

These columns preserve the core descriptive and referential context of the original journal header, enabling accurate historical reconstruction of archived accounting entries.

Common Use Cases and Queries

Typical usage of GL_ARCHIVE_HEADERS centers on audit, retention, and reporting of historical journal data. A common query pattern joins the archive headers back to the reference tables to reconstruct the original journal context:

• Audit retrieval: SELECT h.JE_HEADER_ID, h.NAME, b.NAME batch_name FROM GL_ARCHIVE_HEADERS h, GL_JE_BATCHES b WHERE h.JE_BATCH_ID = b.JE_BATCH_ID;
• Currency reconciliation by set of books: joining to GL_SETS_OF_BOOKS and FND_CURRENCIES on SET_OF_BOOKS_ID and CURRENCY_CODE.
• Encumbrance analysis: filtering on ENCUMBRANCE_TYPE_ID and joining GL_ENCUMBRANCE_TYPES.
• Recurring journal tracing: joining FROM_RECURRING_HEADER_ID to GL_RECURRING_HEADERS.
• Accrual reversal matching: joining ACCRUAL_REV_JE_HEADER_ID to GL_JE_HEADERS.

Because the table is an archive, these queries are usually read-only and target historical periods that have been purged from the live tables.

Related Objects

The most significant related objects are derived from the documented foreign key relationships:

• GL_JE_HEADERS — Referenced by JE_HEADER_ID and ACCRUAL_REV_JE_HEADER_ID; source of the archived headers.
• GL_JE_BATCHES — Referenced by JE_BATCH_ID; defines the batch grouping.
• GL_SETS_OF_BOOKS — Referenced by SET_OF_BOOKS_ID; the ledger context.
• FND_CURRENCIES — Referenced by CURRENCY_CODE.
• GL_DAILY_CONVERSION_TYPES — Referenced by CURRENCY_CONVERSION_TYPE.
• GL_ENCUMBRANCE_TYPES — Referenced by ENCUMBRANCE_TYPE_ID.
• GL_BUDGET_VERSIONS — Referenced by BUDGET_VERSION_ID.
• GL_RECURRING_HEADERS — Referenced by FROM_RECURRING_HEADER_ID.

Together these objects form the referential backbone around which archived journal header data is organized and subsequently reported.