Search Results gl_xfr_tracking_pk

Overview

GL_XFR_TRACKING is a General Ledger (GL) application table owned by the GL schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to hold the tracking information that Oracle GoldenGate uses to launch Journal Import. In practice, the table acts as a control and audit ledger for high-volume, near-real-time journal transfer architectures, where external or upstream systems write journal lines into the GL interface tables and a replication or staging mechanism signals Oracle EBS when a batch is ready for import. Each row records the identity of the concurrent request that will execute (or executed) Journal Import, the ledger and journal source context, the interface table targeted, and the period information needed to run the import correctly.

The primary key is the composite GL_XFR_TRACKING_PK, defined over XFER_REQUEST_ID and SYSTEM_ID. A unique index, GL_XFR_TRACKING_U1, covers the same two columns, making that pair the business-key candidate for the table. The documented physical schema contains 13 columns. Under the heuristic Data Vault classification derived from the foreign-key structure, the table leans toward a satellite: it carries descriptive, context-bearing attributes about a transfer event rather than serving purely as a hub of unique business entities or as a link between two hubs. This classification is a modeling suggestion, not an EBS-imposed constraint.

Key Information Stored

The most operationally significant columns are:

• XFER_REQUEST_ID — The concurrent request identifier for the Journal Import submission. This is part of the primary key and the column referenced by the foreign key to FND_CONCURRENT_REQUESTS, tying the tracking row to a specific run in the concurrent manager.
• SYSTEM_ID — Identifies the originating or participating system. Part of the primary key and the GL_XFR_TRACKING_U1 unique key.
• JE_SOURCE_KEY — The journal source key, which determines the Journal Import source and, indirectly, the import validation rules and suspense handling.
• GROUP_ID — The interface group identifier used to select the batch of interface rows belonging to this transfer.
• INTERFACE_TABLE_NAME — The specific GL interface table that Journal Import should read, such as GL_INTERFACE or a related staging table.
• LEDGER_ID — The target ledger for the import, controlling chart of accounts, accounting calendar, and currency context.
• STATUS_CODE — The processing state of the tracked transfer, used to determine whether a batch is pending, in progress, completed, or in error.
• ORIGINAL_FIRST_PERIOD — The original first accounting period associated with the transfer, used for period derivation and reconciliation when imports are delayed or re-run.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns recording who created and last modified the row and when.

The primary key should be distinguished from the business key: GL_XFR_TRACKING_PK is the physical unique identifier, while GL_XFR_TRACKING_U1 expresses the same two-column combination as the enforced business-key candidate.

Common Use Cases and Queries

Typical scenarios include monitoring GoldenGate-driven Journal Import activity, troubleshooting stalled or failed imports, and reporting on interface throughput by ledger or source.

• Identifying pending or failed transfers: select rows filtered by STATUS_CODE and LEDGER_ID to determine which batches require attention.
• Joining to FND_CONCURRENT_REQUESTS on XFER_REQUEST_ID to retrieve request phase, status, completion text, and timing for each import.
• Grouping by JE_SOURCE_KEY, LEDGER_ID, or SYSTEM_ID to measure transfer volume and latency over a period.
• Using GROUP_ID and INTERFACE_TABLE_NAME to locate the exact interface rows processed by a given import run.

A representative query pattern joins the tracking table to the concurrent requests table on XFER_REQUEST_ID, filters on STATUS_CODE, and orders by CREATION_DATE to present the most recent activity.

Related Objects

• FND_CONCURRENT_REQUESTS — Referenced through the foreign key GL_XFR_TRACKING.XFER_REQUEST_ID, providing request status and run details.
• GL_INTERFACE — The primary journal interface table read by Journal Import; the value in INTERFACE_TABLE_NAME identifies the applicable object.
• GL_JE_SOURCES — Source definition corresponding to JE_SOURCE_KEY.
• GL_LEDGERS — Ledger definition corresponding to LEDGER_ID.
• GL_JE_BATCHES, GL_JE_HEADERS, GL_JE_LINES — Final journal destination tables populated after a successful import and post.
• Journal Import concurrent program — The process that consumes the tracking information to load interface data.

Together, these objects form the end-to-end path from replicated interface data through tracked import execution into posted General Ledger journals.