Search Results gl_xfr_tracking_u1




Overview
Explore in AI Chat

Overview

GL.GL_XFR_TRACKING is a control and orchestration table in the Oracle E-Business Suite General Ledger module. Its documented purpose is to hold the tracking information that Oracle GoldenGate uses to launch Journal Import automatically. Each row represents one transfer run — an inbound movement of interface data into a target ledger — and carries the identifiers needed to correlate that run back to an EBS concurrent request, a journal source, a source system, and a destination ledger.

The table resides in the GL schema under FND Design Data SQLGL.GL_XFR_TRACKING, with a storage definition in tablespace APPS_TS_TX_DATA (PCT Free 10) and its unique index in APPS_TS_TX_IDX. In both 12.1.1 and 12.2.2 the object is reported VALID with a stable 13-column definition.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign key structure is satellite-leaning. The table does not act as a classic business hub; instead it records the descriptive state and status of a transfer event identified by a composite key. A Data Vault design would typically model XFER_REQUEST_ID and SYSTEM_ID as the hub or link keys, with attributes such as STATUS_CODE, JE_SOURCE_KEY, and INTERFACE_TABLE_NAME carried in an associated satellite. The primary key constraint GL_XFR_TRACKING_PK is defined over (XFER_REQUEST_ID, SYSTEM_ID).

Key Information Stored

The documented columns fall into three logical groups: run identification, payload description, and auditing.

  • XFER_REQUEST_ID — Request id in EBS of this transfer run. Part of the primary key and of the GL_XFR_TRACKING_U1 unique index; also the FK column pointing to FND_CONCURRENT_REQUESTS.
  • SYSTEM_ID — System id the data was transferred from. The other half of the primary key and unique index.
  • JE_SOURCE_KEY — Source key of the data being transferred, identifying the journal source context.
  • GROUP_ID — Group id of the data being transferred; correlates a run to a specific interface batch.
  • INTERFACE_TABLE_NAME — Name of the interface table containing the data (for example the GL interface tables Journal Import reads).
  • LEDGER_ID — Fusion ledger id the data is being transferred into, determining the target accounting context.
  • STATUS_CODE — Status code of the transfer, the principal state attribute consumed by downstream processing.
  • ORIGINAL_FIRST_PERIOD — Original first period associated with the transferred journal data.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Who columns providing insert and update audit information.

From a business-key standpoint, GL_XFR_TRACKING_U1 (XFER_REQUEST_ID, SYSTEM_ID) is unique and effectively duplicates the primary key composition. No separate system-generated surrogate column is documented; the composite of request and system id serves as the operational identifier.

Common Use Cases and Queries

The most frequent operational need is to confirm whether Journal Import was launched for a given transfer and what state it reached. A targeted lookup by the unique key is the standard pattern:

  • Retrieve a specific run: SELECT je_source_key, group_id, interface_table_name, ledger_id, status_code FROM gl.gl_xfr_tracking WHERE xfer_request_id = :req AND system_id = :sys;
  • Trace by concurrent request: join to FND_CONCURRENT_REQUESTS on XFER_REQUEST_ID to obtain request status and timing alongside the transfer status.
  • Monitor backlog: SELECT status_code, COUNT(*) FROM gl.gl_xfr_tracking GROUP BY status_code; to spot stalled or failed transfers.
  • Reconciliation and audit: list transfers by LEDGER_ID, JE_SOURCE_KEY, or ORIGINAL_FIRST_PERIOD to verify that every expected interface batch reached the intended ledger.
  • GoldenGate diagnostics: filter by INTERFACE_TABLE_NAME and SYSTEM_ID to isolate transactions originating from one source system.

Related Objects

The documented dependency information is sparse: GL_XFR_TRACKING references no database objects, while FND_CONCURRENT_REQUESTS is the target of the XFER_REQUEST_ID foreign key. GL_XFR_TRACKING# is the index-organized or secondary object listed as referencing this table within the GL schema. Beyond these, the table is consumed by the GoldenGate-driven Journal Import and GL Interface processing infrastructure.