Search Results gl_xfr_interface

Overview

GL_XFR_INTERFACE is a General Ledger interface table owned by the GL schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Per the ETRM documentation, it is a custom variant of the standard GL_INTERFACE table, purpose-built for the balance transfer process. Rather than journal entries entering General Ledger through the standard interface and Journal Import path, the balance transfer utility stages converted balance rows in GL_XFR_INTERFACE before they are validated and posted. The table therefore operates as a staging and transport structure rather than a repository of posted accounting.

Structurally the object is highly denormalized, carrying 140 documented columns. Thirty repeating SEGMENT columns, thirty REFERENCE columns, and twenty ATTRIBUTE columns mirror the flexible-format design of GL_INTERFACE, allowing any chart of accounts configuration to be represented without schema changes. Under a Data Vault modeling heuristic, the mined FK structure classifies GL_XFR_INTERFACE as standalone—it has no child tables depending on it, and the foreign keys it carries are descriptive lookups rather than rigid parent relationships. In practice it behaves as a transient satellite-like staging area: rows have a short lifecycle, moving from interface status to posted status to eventual purge.

Key Information Stored

The primary key is enforced by the unique index GL_XFR_INTERFACE_U1 and the constraint GL_XFR_INTERFACE_PK on the composite of SYSTEM_ID, GROUP_ID, and ROW_NUMBER. SYSTEM_ID identifies the originating source system, GROUP_ID groups the rows produced by a single transfer or loader run, and ROW_NUMBER sequences lines within that group. These three columns act as both the technical identifier and the documented business-key candidate for a staged journal row.

The most operationally significant columns include:

• LEDGER_ID / SET_OF_BOOKS_ID — the ledger receiving the transferred balances.
• ACCOUNTING_DATE, PERIOD_NAME, TRANSACTION_DATE — determine the accounting period into which the row posts.
• SEGMENT1 through SEGMENTn — the account code combination in flexible-format form.
• CODE_COMBINATION_ID — the resolved (or interim) combination identifier after validation.
• ENTERED_DR, ENTERED_CR, ACCOUNTED_DR, ACCOUNTED_CR — the debit and credit amounts in entered and ledger currency.
• CURRENCY_CODE, CURRENCY_CONVERSION_RATE, CURRENCY_CONVERSION_TYPE, CURRENCY_CONVERSION_DATE — conversion context for foreign-currency rows.
• STATUS, STATUS_DESCRIPTION, WARNING_CODE, STAT_AMOUNT — Journal Import validation outcome and error messaging.
• GROUP_ID, REQUEST_ID — the concurrent request that produced the row.
• GL_INTERFACE_ID — ties the staged row back to the GL_INTERFACE record.
• CHART_OF_ACCOUNTS_ID — identifies the chart of accounts applied to the row.

Common Use Cases and Queries

The dominant use case is diagnosing balance transfer runs. Support and functional analysts query rows by GROUP_ID or REQUEST_ID to confirm what was loaded, which rows remain in error, and what warning codes were raised:

• Error inspection: SELECT ROW_NUMBER, SEGMENT1, ENTERED_DR, ENTERED_CR, STATUS, STATUS_DESCRIPTION, WARNING_CODE FROM GL.GL_XFR_INTERFACE WHERE GROUP_ID = :group_id AND STATUS IN ('E','W');
• Group reconciliation: SELECT GROUP_ID, REQUEST_ID, COUNT(*), SUM(ENTERED_DR), SUM(ENTERED_CR) FROM GL.GL_XFR_INTERFACE GROUP BY GROUP_ID, REQUEST_ID;
• Conversion diagnostics: compare CURRENCY_CONVERSION_RATE and CUR RENCY_CONV_DATE_INTER against the interim columns CURRENCY_CONV_TYPE_INTER and CURRENCY_CONV_RATE_INTER to confirm the transfer applied the intended rate.
• Cleanup: staged rows that have posted can be purged by GROUP_ID to keep the table compact.

Related Objects

• GL_INTERFACE — the standard interface table; referenced from GL_XFR_INTERFACE via GL_INTERFACE_ID, and the source that Journal Import ultimately consumes.
• GL_ENCUMBRANCE_TYPES — referenced through ENCUMBRANCE_TYPE_ID for encumbrance-related transfer rows.
• GL_MGT_SEG_UPGRADE_H — referenced through CHART_OF_ACCOUNTS_ID in the documented FK relation.
• PQH_GL_INTERFACE — referenced through GL_INTERFACE_ID; the Public Sector / HR integration interface.
• GL_JE_BATCHES / GL_JE_HEADERS / GL_JE_LINES — populated after successful Journal Import of the staged lines.
• GL_CODE_COMBINATIONS — resolves the SEGMENT values into CODE_COMBINATION_ID.
• FND_CONCURRENT_REQUESTS — joined on REQUEST_ID to trace the balance transfer program run.