Search Results gl_xfr_source_systems_u1

Overview

GL.GL_XFR_SOURCE_SYSTEMS is a General Ledger configuration table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the registry of external instances — typically remote EBS or Fusion General Ledger environments — from which a user may drill down directly out of the local GL balances interface. Each row represents one external source system, together with the journal source key and the URL template required to navigate the user to the corresponding detail in that external instance. The table therefore functions as the routing directory that underpins cross-instance drilldown, an increasingly common requirement in multi-instance and coexistence deployments.

The object is owned by the GL schema, is delivered as part of the SQLGL design data, and is physically stored in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10. Its heuristic Data Vault classification is standalone, suggesting it is best modeled as a reference or hub-like entity rather than a transactional satellite. In practice it behaves as a low-volume, slowly changing configuration hub whose natural business key is the external SYSTEM_ID.

Key Information Stored

The table contains twelve documented columns. The surrogate primary key is SYSTEM_MAP_ID, a sequence-generated unique number that is the target of all downstream foreign keys. The business-key candidate is SYSTEM_ID, enforced by the unique index GL_XFR_SOURCE_SYSTEMS_U1 in the APPS_TS_TX_IDX tablespace; SYSTEM_ID corresponds to a system configured in gl_system_usages for the external instance.

NAME holds the user-facing label for the source system as presented in drilldown configuration screens. JE_SOURCE_KEY identifies the journal source that the external instance uses, which is essential when balancing or reconciling entries between the two environments. DRILLDOWN_URL stores the external instance URL, defined with a length of 3000 characters to accommodate parameterised, fully qualified addresses. DESCRIPTION provides an extended free-text explanation of up to 720 characters.

OBJECT_VERSION_NUMBER supports optimistic locking during concurrent updates. The remaining columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — are standard Who columns populated automatically by the application, providing a complete audit trail of row creation and modification.

Common Use Cases and Queries

Typical scenarios include reviewing all configured external drilldown targets, validating that each SYSTEM_ID is still active in gl_system_usages, and troubleshooting broken drilldown links caused by an outdated DRILLDOWN_URL. Administrators also audit which journal source is associated with each remote instance before reconciling inter-instance balances.

A basic listing of configured systems:

• SELECT SYSTEM_MAP_ID, SYSTEM_ID, NAME, JE_SOURCE_KEY, DRILLDOWN_URL FROM GL.GL_XFR_SOURCE_SYSTEMS;
• Locate a specific target: SELECT * FROM GL.GL_XFR_SOURCE_SYSTEMS WHERE SYSTEM_ID = :p_system_id;
• Resolve the full mapping chain for reporting: SELECT s.NAME, s.DRILLDOWN_URL, l.LEDGER_ID FROM GL.GL_XFR_SOURCE_SYSTEMS s, GL.GL_XFR_SYSTEM_LEDGERS l WHERE s.SYSTEM_MAP_ID = l.SYSTEM_MAP_ID;
• Detect stale configuration through the audit columns: SELECT NAME, LAST_UPDATE_DATE, LAST_UPDATED_BY FROM GL.GL_XFR_SOURCE_SYSTEMS ORDER BY LAST_UPDATE_DATE DESC;

Because volumes are small, these queries impose negligible performance overhead; the unique index on SYSTEM_ID supports point lookups directly.

Related Objects

Two documented foreign keys reference this table. GL_XFR_SYSTEM_LEDGERS joins on SYSTEM_MAP_ID and records which ledgers in the local instance map to a given external system, forming the core of the mapping model. GL_XFR_LEDGER_BSV_MAPS also joins on SYSTEM_MAP_ID and captures the balance sheet value mappings used when translating balances between instances. Both child tables depend on the parent row in GL_XFR_SOURCE_SYSTEMS before they can be defined.

Related configuration data resides in GL_SYSTEM_USAGES, which supplies the authoritative SYSTEM_ID values, and in the GL journal source definitions referenced by JE_SOURCE_KEY. Collectively these objects allow administrators to define, maintain, and reconcile drilldown relationships between the local ledger and any number of external source systems.