Search Results gl_interface




Overview
Explore in AI Chat

Overview

The GL_INTERFACE table is a critical staging table within the Oracle E-Business Suite General Ledger (GL) module, specifically designed for the import of journal entry batches. It serves as the primary data interface between external subledger systems, legacy applications, or manual data entry processes and the core GL journal tables. Data is inserted into GL_INTERFACE, typically via custom programs or standard APIs, and is subsequently validated and transferred into the permanent GL journal tables (GL_JE_BATCHES, GL_JE_HEADERS, GL_JE_LINES) by running the Journal Import concurrent program. This process ensures data integrity and enforces GL business rules before journal entries are posted to the ledger.

Key Information Stored

The table stores a comprehensive set of attributes required to create a complete journal entry. Key columns include identifiers for the target ledger (LEDGER_ID), currency (CURRENCY_CODE), and accounting flexfield (CODE_COMBINATION_ID). It holds the core journal data: the accounting date (ACCOUNTING_DATE), entered debit (ENTERED_DR) and credit (ENTERED_CR) amounts, and the journal line description (DESCRIPTION). The table also contains control columns that manage the import process, such as STATUS (indicating NEW, ERROR, or POSTED), GROUP_ID for grouping lines into batches, and REQUEST_ID linking to the Journal Import run. Foreign key columns like JE_BATCH_ID, JE_HEADER_ID, and JE_LINE_NUM are populated after successful import to link the interface record to the created permanent journal entry.

Common Use Cases and Queries

The primary use case is the automated population of GL journals from external sources. A common operational task is monitoring and troubleshooting the Journal Import process. The following query pattern is frequently used to identify records that failed import validation:

  • SELECT STATUS, GROUP_ID, ACCOUNTING_DATE, CODE_COMBINATION_ID, ENTERED_DR, ENTERED_CR, REJECTION_REASON FROM GL.GL_INTERFACE WHERE STATUS = 'ERROR' AND REQUEST_ID = :req_id ORDER BY GROUP_ID, ROWID;

For reporting on pending, unposted data, analysts may query records with a status of 'NEW'. Furthermore, the table is central to custom journal upload programs, where data is first loaded into GL_INTERFACE before invoking the standard Journal Import program via a concurrent request.

Related Objects

As indicated by its foreign keys, GL_INTERFACE has direct dependencies on several foundational GL and application tables. It references GL_LEDGERS to define the target ledger, GL_CODE_COMBINATIONS for the accounting flexfield, and FND_CURRENCIES. For successful journal creation, it links to GL_JE_BATCHES, GL_JE_HEADERS, and GL_JE_LINES. Its relationship with FND_CONCURRENT_REQUESTS tracks the import process. The primary API for populating this table is the Journal Import public API (GL_JOURNAL_IMPORT_PKG). The standard transfer to permanent tables is executed by the Journal Import program, which reads from and ultimately purges processed records from GL_INTERFACE.