Results for “gl_interface_history”

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

Overview

GL_INTERFACE_HISTORY is a General Ledger interface table in Oracle E-Business Suite 12.1.1 and 12.2.2, owned by the GL schema. It stores imported journal entry batches, functioning as the historical counterpart to GL_INTERFACE. When journal import processes records from GL_INTERFACE into GL_JE_BATCHES, GL_JE_HEADERS, and GL_JE_LINES, the source rows are preserved in this history table for audit, reconciliation, and troubleshooting purposes. The table carries 130 documented columns in 12.2.2, closely mirroring the structure of GL_INTERFACE, including the thirty segment columns, thirty reference columns, and twenty attribute columns used for flexfield and descriptive flexfield capture.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign key structure is a link. The table does not behave as a pure hub or satellite; instead it records associations among ledgers, batches, headers, lines, concurrent requests, currencies, and code combinations, which is characteristic of a link construct. This classification should be treated as a modeling suggestion rather than a physical design statement.

Key Information Stored

The most consequential columns reflect the accounting and control context of each imported row:

• SET_OF_BOOKS_ID / LEDGER_ID — identify the ledger or set of books receiving the import; both are documented and support 11i and 12.x coexistence.
• JE_BATCH_ID, JE_HEADER_ID, JE_LINE_NUM — tie each history row back to the created journal batch, header, and line, forming the audit trail from interface to subledger posting.
• ACCOUNTING_DATE, PERIOD_NAME, TRANSACTION_DATE, DATE_CREATED_IN_GL — the accounting and transaction timing attributes of the journal entry.
• CURRENCY_CODE, CURRENCY_CONVERSION_DATE, CURRENCY_CONVERSION_RATE, USER_CURRENCY_CONVERSION_TYPE, FUNCTIONAL_CURRENCY_CODE — currency and conversion detail.
• ENTERED_DR, ENTERED_CR, ACCOUNTED_DR, ACCOUNTED_CR — entered and accounted debit/credit amounts; the core financial payload.
• STATUS, STATUS_DESCRIPTION, WARNING_CODE — import outcome indicators used for error diagnosis.
• CODE_COMBINATION_ID, CHART_OF_ACCOUNTS_ID, SEGMENT1–SEGMENT30 — the accounting flexfield interpretation of each line.
• GROUP_ID, REQUEST_ID — identify the batch run and the concurrent request that performed the import.
• ACTUAL_FLAG, USER_JE_SOURCE_NAME, USER_JE_CATEGORY_NAME — journal source and category context.
• ATTRIBUTE1–ATTRIBUTE20, CONTEXT, CONTEXT2, CONTEXT3 — descriptive flexfield storage and subledger context values.

No explicit single-column surrogate primary key is documented in the supplied metadata; the composite of JE_HEADER_ID and JE_LINE_NUM (referenced as a foreign key to GL_JE_LINES) behaves as a business-key candidate for line-level identification.

Common Use Cases and Queries

Typical uses include auditing what a journal import consumed, reconciling imported interface rows against created journal lines, and diagnosing rows that failed to post.

• Trace a batch back to its originating import run: filter on GROUP_ID or REQUEST_ID and join to FND_CONCURRENT_REQUESTS.
• Reconcile imported rows to posted journals by joining JE_HEADER_ID to GL_JE_HEADERS and GL_JE_LINES, comparing accounted amounts.
• Investigate import errors through STATUS, WARNING_CODE, and STATUS_DESCRIPTION.
• Analyze interface history by ledger, period, and source using SET_OF_BOOKS_ID/LEDGER_ID, PERIOD_NAME, and USER_JE_SOURCE_NAME.

A representative pattern:

• SELECT h.je_header_id, h.je_line_num, h.period_name, h.accounted_dr, h.accounted_cr, h.status
• FROM gl_interface_history h
• WHERE h.set_of_books_id = :ledger AND h.period_name = :period
• ORDER BY h.je_header_id, h.je_line_num;

Related Objects

The documented foreign keys connect GL_INTERFACE_HISTORY to the following principal objects:

• GL_JE_BATCHES via JE_BATCH_ID — the resulting journal batch.
• GL_JE_HEADERS via JE_HEADER_ID — the resulting journal header.
• GL_JE_LINES via JE_HEADER_ID and JE_LINE_NUM — the resulting journal lines.
• GL_SETS_OF_BOOKS_11I via SET_OF_BOOKS_ID — the ledger definition.
• FND_CONCURRENT_REQUESTS via REQUEST_ID — the import program run.
• FND_CURRENCIES via CURRENCY_CODE — currency validation.
• GL_CODE_COMBINATIONS via CODE_COMBINATION_ID — the accounting flexfield combination.
• GL_ENCUMBRANCE_TYPES via ENCUMBRANCE_TYPE_ID and GL_BUDGET_VERSIONS via BUDGET_VERSION_ID — budgetary control context.

The Journal Import concurrent program (GLLEZL) is the primary process populating this table in concert with GL_INTERFACE.