Search Results gl_interface_history




Overview
Explore in AI Chat

Overview

The GL_INTERFACE_HISTORY table is a critical data object within the Oracle E-Business Suite (EBS) General Ledger (GL) module, specifically for versions 12.1.1 and 12.2.2. As indicated by its description, it serves as a historical repository for imported journal entry batches. Its primary role is to store a persistent record of data that has successfully passed through the GL Interface (GL_INTERFACE table) and been processed into the core GL tables. This provides an audit trail and facilitates troubleshooting by preserving the exact state of the imported data before it was posted, allowing for reconciliation between the source data and the final journal entries created in the system.

Key Information Stored

The table's structure is designed to mirror key attributes of a journal entry batch and its constituent lines at the point of import. Based on the documented foreign key relationships, the table stores identifiers that link the historical data to the final posted transactions and related master data. Important columns include JE_BATCH_ID, JE_HEADER_ID, and JE_LINE_NUM, which connect the history to the created GL_JE_BATCHES, GL_JE_HEADERS, and GL_JE_LINES. The SET_OF_BOOKS_ID (Ledger ID), CODE_COMBINATION_ID (Accounting Flexfield), CURRENCY_CODE, and REQUEST_ID (for the concurrent import process) are also stored. Additional columns like BUDGET_VERSION_ID and ENCUMBRANCE_TYPE_ID indicate the table supports the historical tracking of budget journal and encumbrance imports.

Common Use Cases and Queries

The primary use case for GL_INTERFACE_HISTORY is audit and reconciliation reporting. It is essential for verifying what data was submitted to the interface and how it was ultimately created in the General Ledger. A common query pattern involves joining this table to the final journal entry tables to compare imported and posted values. For example, to trace a specific journal batch back to its source data:

  • SELECT gih.*, gjb.name batch_name FROM gl_interface_history gih, gl_je_batches gjb WHERE gih.je_batch_id = gjb.je_batch_id AND gih.request_id = :req_id;

It is also frequently used in diagnostic queries when the Journal Import process completes with warnings or errors, allowing analysts to examine the specific rows that were processed in a given run by filtering on REQUEST_ID.

Related Objects

The GL_INTERFACE_HISTORY table maintains documented foreign key relationships with several core EBS tables, as per the provided metadata. These relationships define its integration within the GL schema:

These relationships confirm that GL_INTERFACE_HISTORY is a central point linking the interface process to master data, transactional data, and the execution context of the concurrent manager.