Search Results gl_archive_lines




Overview
Explore in AI Chat

Overview

GL_ARCHIVE_LINES is a General Ledger table that stores archived journal entry lines within Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented description, "Archive journal entry lines," indicates that it holds line-level detail for journal entries that have been moved out of the active transaction tables as part of the archiving and purge process. Journal archiving allows organizations to retain historical accounting detail for audit and reporting purposes while reducing the volume of data in the live GL_JE_LINES table, which directly affects query performance and maintenance windows.

The table is documented as "Not implemented in this database" in the source metadata, meaning its physical presence depends on whether archiving has been configured and executed in a given environment. The heuristic Data Vault classification supplied in the metadata is link, which suggests this object is best modeled as a relationship table connecting journal header/line context, a ledger definition, and an accounting flexfield combination rather than as a descriptive satellite. This classification is a modeling suggestion derived from the foreign key structure and should be validated against actual archival usage.

Key Information Stored

The primary key is GL_ARCHIVE_LINES_PK, defined on the composite of JE_HEADER_ID and JE_LINE_NUM. This is a natural, business-oriented composite key rather than a single surrogate identifier, and it mirrors the identifying structure of the journal line it archives.

  • JE_HEADER_ID — Identifies the journal entry header to which the archived line belonged. Part of the composite primary key and a foreign key to GL_JE_LINES.
  • JE_LINE_NUM — The line number within the journal entry. Part of the composite primary key and a foreign key to GL_JE_LINES.
  • SET_OF_BOOKS_ID — Identifies the ledger (set of books) associated with the archived line; foreign key to GL_SETS_OF_BOOKS.
  • CODE_COMBINATION_ID — Identifies the accounting flexfield combination charged by the line; foreign key to GL_CODE_COMBINATIONS.

Additional line attributes such as entered and accounted amounts, currency, and descriptive text are typically present in the archive record to preserve the full journal line image, but only the columns above are explicitly documented in the metadata. The composite key JE_HEADER_ID plus JE_LINE_NUM is the principal business-key candidate because it uniquely distinguishes each archived line and preserves the original journal line identity.

Common Use Cases and Queries

Typical scenarios include historical audit retrieval, reconciliation of archived versus live balances, and reporting on closed periods where detail has been removed from the operational tables. A standard retrieval joins the archive table to its ledger and account references to reconstruct the accounting picture:

  • Retrieve archived lines for a specific journal entry by filtering on JE_HEADER_ID.
  • Report archived activity by ledger using SET_OF_BOOKS_ID.
  • Analyze activity by accounting flexfield combination using CODE_COMBINATION_ID.

A representative query pattern is:

  • SELECT a.je_header_id, a.je_line_num, a.set_of_books_id, a.code_combination_id FROM gl_archive_lines a WHERE a.je_header_id = :header_id ORDER BY a.je_line_num;

Because the table is conditionally implemented, discovery queries against the data dictionary should confirm its existence before dependent code is deployed. Reporting solutions that span live and archived periods must union GL_JE_LINES with GL_ARCHIVE_LINES to present a complete journal history.

Related Objects

The documented foreign keys establish the principal relationships for this table:

  • GL_JE_LINES — Referenced through GL_ARCHIVE_LINES.JE_HEADER_ID and GL_ARCHIVE_LINES.JE_LINE_NUM; the source of the archived journal line detail.
  • GL_SETS_OF_BOOKS — Referenced through GL_ARCHIVE_LINES.SET_OF_BOOKS_ID; provides ledger context.
  • GL_CODE_COMBINATIONS — Referenced through GL_ARCHIVE_LINES.CODE_COMBINATION_ID; provides accounting flexfield context.
  • GL_JE_HEADERS — The parent header table for journal entries, indirectly linked through JE_HEADER_ID.

These relationships confirm the link modeling classification and define the join paths required for any reconstruction of archived journal detail in reporting or reconciliation processes.