Search Results gl_xfr_interface_u1

Overview

GL.GL_XFR_INTERFACE is a General Ledger interface table that serves as a specialized, custom variant of the standard GL_GL_INTERFACE table, purpose-built for the balance transfer process. In Oracle EBS 12.1.1 and 12.2.2, the standard GL_INTERFACE table receives journal entries from subledgers and external sources for validation and posting via Journal Import. GL_XFR_INTERFACE fulfills an analogous but narrower role: it stages balance transfer records — movements of opening or period-end balances between accounts, ledgers, or segments — before they are validated and loaded into the ledger.

The table resides in the APPS_TS_TX_DATA tablespace in the GL schema, with application design data registered under SQLGL.GL_XFR_INTERFACE. Its status is VALID in the documented environment. Because the table is a standalone object with no dependency chain in the standard model, the heuristic Data Vault classification suggests it behaves as a standalone staging satellite rather than a conformed hub or link. Its 140 documented columns closely mirror the GL_INTERFACE structure, which is intentional — the balance transfer program populates this table using the same interface conventions, allowing it to be processed through Journal Import.

Key Information Stored

The table's physical primary key is GL_XFR_INTERFACE_PK, defined on (SYSTEM_ID, GROUP_ID, ROW_NUMBER). This composite surrogate key identifies each interface row uniquely and also underpins the unique index GL_XFR_INTERFACE_U1, which shares the same three columns in the APPS_TS_TX_IDX tablespace. Because the unique index matches the primary key exactly, these three columns are the business-key candidates for the table.

• GROUP_ID / SYSTEM_ID / ROW_NUMBER — Grouping and sequencing identifiers used to isolate a single balance-transfer batch and preserve row order during import.
• STATUS — The processing state of each interface line (e.g., NEW, IMPORTED, ERROR) and its 450-character description field STATUS_DESCRIPTION.
• LEDGER_ID and CHART_OF_ACCOUNTS_ID — The target ledger and the chart of accounts against which the balance transfer is applied.
• ACCOUNTING_DATE and TRANSACTION_DATE — The effective accounting date and the originating transaction date that drive period assignment.
• SEGMENT1 … SEGMENT30 — The key flexfield segments that resolve to the target account CODE_COMBINATION_ID.
• ENTERED_DR / ENTERED_CR and ACCOUNTED_DR / ACCOUNTED_CR — Entered and accounted debit/credit amounts, which must balance before posting.
• CURRENCY_CODE, CURRENCY_CONVERSION_RATE, CURRENCY_CONVERSION_TYPE — Currency and conversion attributes for foreign-currency balance transfers.
• ACTUAL_FLAG, PERIOD_NAME, JE_BATCH_ID, JE_HEADER_ID, JE_LINE_NUM — Balance type and the resulting journal identifiers once the row is imported.
• REQUEST_ID — Links the rows back to the concurrent request that generated them.
• GL_SL_LINK_ID / GL_SL_LINK_TABLE — Traceability to the originating subledger source.

Common Use Cases and Queries

The principal use case is troubleshooting balance transfer batches. Support analysts query GL_XFR_INTERFACE to inspect unvalidated or rejected rows before or after Journal Import runs.

• Reviewing a specific batch: SELECT ROW_NUMBER, STATUS, STATUS_DESCRIPTION, SEGMENT1, ENTERED_DR, ENTERED_CR FROM GL.GL_XFR_INTERFACE WHERE GROUP_ID = :group_id ORDER BY ROW_NUMBER;
• Identifying errors: filtering on STATUS = 'E' or non-null WARNING_CODE to surface rows that failed import validation.
• Balance verification: aggregating ENTERED_DR and ENTERED_CR by GROUP_ID to confirm the transfer batch nets to zero before posting.
• Post-import reconciliation: joining JE_BATCH_ID and JE_HEADER_ID back to GL_JE_BATCHES and GL_JE_HEADERS to confirm created journals.
• Request auditing: grouping by REQUEST_ID and CREATED_BY to trace which concurrent program submitted each batch.

These patterns support audit, period-close control, and root-cause analysis for balance transfer failures.

Related Objects

The documented foreign keys link GL_XFR_INTERFACE to the following objects, and these joins are the most significant integration points:

• GL_ENCUMBRANCE_TYPES — joined via ENCUMBRANCE_TYPE_ID to classify encumbrance balance transfers.
• PQH_GL_INTERFACE — joined via GL_INTERFACE_ID, reflecting integration with Oracle Payroll/HR interface handling.
• GL_MGT_SEG_UPGRADE_H — referenced through CHART_OF_ACCOUNTS_ID in the documented relationship data.
• GL_JE_BATCHES / GL_JE_HEADERS — the destination of posted transfer rows, keyed by JE_BATCH_ID and JE_HEADER_ID.
• GL_IMPORT_REFERENCES — links imported interface lines to their journal sources for cross-referencing.
• FND_CONCURRENT_REQUESTS — joined via REQUEST_ID to identify the submitting program run.
• GL_CODE_COMBINATIONS — resolved from the SEGMENT columns via CODE_COMBINATION_ID.

Given its structural similarity to GL_GL_INTERFACE, administrators should treat GL_XFR_INTERFACE as the transfer-specific staging counterpart when configuring Journal Import and balance transfer concurrent programs.