Results for “gl_interface”

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

Overview

GL_INTERFACE is the General Ledger open interface table in Oracle EBS 12.1.1 and 12.2.2. It holds journal entry lines staged for import into the General Ledger application. External feeder systems, subledger extracts, spreadsheets, and third-party applications populate GL_INTERFACE, and the Journal Import concurrent program (GLLEZL) reads the rows, validates them against ledger, currency, code combination, and period rules, and creates journal batches, headers, and lines in GL_JE_BATCHES, GL_JE_HEADERS, and GL_JE_LINES. The table is owned by the GL schema and contains 133 documented columns in 12.2.2.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign key structure is a link. GL_INTERFACE sits between business hubs such as ledgers, code combinations, currencies, and journals, and records associations that resolve into posted journal lines. It functions as a transient staging link rather than as a durable raw vault table, since rows are purged after successful import.

Key Information Stored

The most business-critical columns are as follows.

• LEDGER_ID — identifies the target ledger; foreign key to GL_LEDGERS.
• ACCOUNTING_DATE and PERIOD_NAME — determine the GL period and date used for import validation.
• CURRENCY_CODE, CURRENCY_CONVERSION_RATE, CURRENCY_CONVERSION_DATE, and USER_CURRENCY_CONVERSION_TYPE — drive foreign currency conversion; CURRENCY_CODE references FND_CURRENCIES.
• USER_JE_SOURCE_NAME and USER_JE_CATEGORY_NAME — control journal source and category assignment.
• SEGMENT1 through SEGMENT30 — the accounting flexfield segments that resolve to a CODE_COMBINATION_ID referencing GL_CODE_COMBINATIONS.
• ENTERED_DR and ENTERED_CR — entered debit and credit amounts.
• ACCOUNTED_DR and ACCOUNTED_CR — accounted amounts in the ledger currency.
• STATUS, STATUS_DESCRIPTION, and WARNING_CODE — indicate import outcome for each row.
• JE_BATCH_ID, JE_HEADER_ID, and JE_LINE_NUM — populated after a successful import and reference GL_JE_BATCHES and GL_JE_HEADERS/GL_JE_LINES.
• GROUP_ID and REQUEST_ID — tie a batch of rows to a specific import run; REQUEST_ID references FND_CONCURRENT_REQUESTS.
• ACTUAL_FLAG, ENCUMBRANCE_TYPE_ID, and BUDGET_VERSION_ID — distinguish actual, encumbrance, and budget journal types.

The table does not have a documented single-column surrogate primary key in the ETRM metadata; rows are identified by the combination of source, group, and line attributes during import processing.

Common Use Cases and Queries

Typical scenarios include loading external journals, diagnosing import failures, and reconciling staged versus posted amounts.

• Identifying failed or unprocessed rows: SELECT * FROM gl_interface WHERE status IS NULL OR status = 'E' AND group_id = :p_group_id;
• Reviewing warnings for a run: SELECT je_line_num, status, status_description, warning_code FROM gl_interface WHERE request_id = :p_request_id;
• Reconciling entered versus accounted amounts before import: SELECT SUM(entered_dr - entered_cr), SUM(accounted_dr - accounted_cr) FROM gl_interface WHERE group_id = :p_group_id;
• Confirming post-import linkage: join GL_INTERFACE to GL_JE_HEADERS on JE_HEADER_ID and to GL_JE_LINES on JE_HEADER_ID and JE_LINE_NUM.
• Auditing source and category distribution for a load set.

Rows are typically deleted after successful import, so reporting against GL_INTERFACE is best performed before purge or from archived extracts.

Related Objects

• GL_LEDGERS — joined on GL_INTERFACE.LEDGER_ID = GL_LEDGERS.LEDGER_ID.
• GL_JE_BATCHES — joined on GL_INTERFACE.JE_BATCH_ID = GL_JE_BATCHES.JE_BATCH_ID.
• GL_JE_HEADERS and GL_JE_LINES — joined on JE_HEADER_ID (and JE_LINE_NUM for lines).
• GL_CODE_COMBINATIONS — joined on CODE_COMBINATION_ID to validate the accounting flexfield.
• FND_CURRENCIES — joined on CURRENCY_CODE for currency validation.
• FND_CONCURRENT_REQUESTS — joined on REQUEST_ID to trace the Journal Import run.
• GL_BUDGET_VERSIONS and GL_ENCUMBRANCE_TYPES — joined on BUDGET_VERSION_ID and ENCUMBRANCE_TYPE_ID for budget and encumbrance journals.
• Journal Import program (GLLEZL) — the primary concurrent process that consumes GL_INTERFACE rows.