Search Results gl_xfr_source_systems
Overview
GL_XFR_SOURCE_SYSTEMS is a General Ledger configuration table in the Oracle E-Business Suite (12.1.1 and 12.2.2) that stores the registry of external source systems registered for cross-instance drill-down. Its documented purpose is to hold the list of external instances, together with their URL information, that Oracle Fusion General Ledger uses to drill down from Fusion GL balances back to the originating external instance — typically an E-Business Suite ledger. When a user reviews a balance in Fusion GL and requests drill-down, the transfer configuration defined by this table determines which external system is contacted and at which address.
The table resides in the GL schema and is one of the objects supporting the GL transfer / integration infrastructure. From a Data Vault modeling perspective, the available metadata classifies this object heuristically as a standalone structure. In practice it behaves as a hub-like reference entity: it is the parent of dependent mapping tables and is identified by a stable business key, with no foreign keys of its own pointing outward. This classification should be treated as a modeling suggestion rather than a definitive architectural statement.
Key Information Stored
The table comprises twelve documented columns. The most significant are:
- SYSTEM_MAP_ID — the surrogate primary key, enforced by the GL_XFR_SOURCE_SYSTEMS_PK constraint. It is the value propagated to child mapping tables.
- SYSTEM_ID — the business-key candidate, enforced by the unique index GL_XFR_SOURCE_SYSTEMS_U1. It provides the stable, user-meaningful identifier for the external system.
- NAME — the descriptive name of the external instance, used for identification in setup and reporting.
- DESCRIPTION — free-text explanation of the source system's purpose or scope.
- JE_SOURCE_KEY — the journal entry source key that associates transferred balances with the correct source classification.
- DRILLDOWN_URL — the URL used to navigate from a Fusion GL balance to the corresponding record in the external instance.
- OBJECT_VERSION_NUMBER — the optimistic locking column used by the OAF/ADF framework to detect concurrent updates.
- CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard WHO audit columns recording insert and update context.
The distinction between SYSTEM_MAP_ID and SYSTEM_ID is important: joins between this table and its children are performed on the surrogate SYSTEM_MAP_ID, while external references and integration payloads generally rely on SYSTEM_ID.
Common Use Cases and Queries
Typical scenarios include verifying which external instances are registered, auditing drill-down URLs after an instance migration, and reporting on the transfer configuration landscape. A basic listing query follows:
SELECT system_map_id, system_id, name, drilldown_url FROM gl.gl_xfr_source_systems ORDER BY name;- Joining to dependent mappings:
SELECT s.name, l.* FROM gl.gl_xfr_source_systems s, gl.gl_xfr_system_ledgers l WHERE s.system_map_id = l.system_map_id; - Locating a specific instance by business key:
SELECT * FROM gl.gl_xfr_source_systems WHERE system_id = :system_id; - Audit-oriented reporting on configuration changes:
SELECT name, last_update_date, last_updated_by FROM gl.gl_xfr_source_systems ORDER BY last_update_date DESC;
Because the table is configuration rather than transactional data, query volumes are low, and reporting typically centers on setup validation and post-migration verification of URL targets.
Related Objects
Two documented foreign keys establish the parent-child relationships for this table, both joining on SYSTEM_MAP_ID:
- GL_XFR_SYSTEM_LEDGERS — references GL_XFR_SOURCE_SYSTEMS.SYSTEM_MAP_ID; associates ledger information with each registered external system.
- GL_XFR_LEDGER_BSV_MAPS — references GL_XFR_SOURCE_SYSTEMS.SYSTEM_MAP_ID; maps ledger and balancing segment value combinations to the source system.
Together with the primary key constraint GL_XFR_SOURCE_SYSTEMS_PK and the unique index GL_XFR_SOURCE_SYSTEMS_U1, these objects form the core of the GL cross-instance drill-down configuration set. No additional documented dependencies are listed in the available metadata.
-
Table: GL_XFR_SOURCE_SYSTEMS
12.2.2
owner:GL, object_type:TABLE, fnd_design_data:SQLGL.GL_XFR_SOURCE_SYSTEMS, object_name:GL_XFR_SOURCE_SYSTEMS, status:VALID, product: GL - General Ledger , description: Stores the list of External Instances with URL info that will be used to drill down from Fusion GL balances to the external instance , implementation_dba_data: GL.GL_XFR_SOURCE_SYSTEMS ,
-
VIEW: GL.GL_XFR_SOURCE_SYSTEMS#
12.2.2
-
VIEW: GL.GL_XFR_SOURCE_SYSTEMS#
12.2.2
owner:GL, object_type:VIEW, object_name:GL_XFR_SOURCE_SYSTEMS#, status:VALID,
-
SYNONYM: APPS.GL_XFR_SOURCE_SYSTEMS
12.2.2
owner:APPS, object_type:SYNONYM, object_name:GL_XFR_SOURCE_SYSTEMS, status:VALID,
-
TABLE: GL.GL_XFR_SOURCE_SYSTEMS
12.2.2
owner:GL, object_type:TABLE, fnd_design_data:SQLGL.GL_XFR_SOURCE_SYSTEMS, object_name:GL_XFR_SOURCE_SYSTEMS, status:VALID,
-
TABLE: GL.GL_XFR_LEDGER_BSV_MAPS
12.2.2
owner:GL, object_type:TABLE, fnd_design_data:SQLGL.GL_XFR_LEDGER_BSV_MAPS, object_name:GL_XFR_LEDGER_BSV_MAPS, status:VALID,
-
PACKAGE BODY: APPS.GL_FUSION_TRANSFER_PKG
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:GL_FUSION_TRANSFER_PKG, status:VALID,
-
TABLE: GL.GL_XFR_SYSTEM_LEDGERS
12.2.2
owner:GL, object_type:TABLE, fnd_design_data:SQLGL.GL_XFR_SYSTEM_LEDGERS, object_name:GL_XFR_SYSTEM_LEDGERS, status:VALID,
-
12.2.2 DBA Data
12.2.2
-
12.2.2 FND Design Data
12.2.2
-
12.2.2 DBA Data
12.2.2
-
12.2.2 DBA Data
12.2.2
-
12.2.2 DBA Data
12.2.2
-
12.2.2 DBA Data
12.2.2
-
APPS.GL_FUSION_TRANSFER_PKG SQL Statements
12.2.2
-
APPS.GL_FUSION_TRANSFER_PKG dependencies on GL_XFR_SOURCE_SYSTEMS
12.2.2
-
PACKAGE BODY: APPS.GL_FUSION_TRANSFER_PKG
12.2.2
-
eTRM - SQLGL Tables and Views
12.2.2
description: This table contains the tracking information that Golden Gate will use to launch Journal Import. ,
-
eTRM - SQLGL Tables and Views
12.2.2
description: This table contains the tracking information that Golden Gate will use to launch Journal Import. ,
-
12.2.2 DBA Data
12.2.2