Search Results gl_xfr_system_ledgers




Overview

The GL.GL_XFR_SYSTEM_LEDGERS table is a General Ledger configuration object in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the mapping between source systems and their ledgers, along with the corresponding Balance Sheet Value (BSV) assignment type. This table is central to the Fusion Accounting Hub (FAH) integration, where EBS General Ledger acts as the source system and delivers journals to Fusion General Ledger through the accounting transformation process. Each row represents a system-to-ledger mapping that governs how transactions from a given source system are attributed to a target ledger during transfer.

From a data-modeling perspective, the metadata classifies this object heuristically as standalone. In Data Vault terms, it may be modeled as a link or a reference satellite that associates source systems with ledgers; although no Data Vault classification is explicitly assigned, the structure supports treating it as a relationship table rather than a true hub or transaction fact. The absence of dependent child tables reinforces its role as a configuration/reference object.

Key Information Stored

The table contains 10 documented columns. The most functionally significant are:

The business-key candidate is defined by the unique index GL_XFR_SYSTEM_LEDGERS_U1 on the column pair (SYSTEM_MAP_ID, LEDGER_ID), meaning a given source system can map to a specific ledger only once. The remaining columns are standard EBS audit and concurrency attributes: OBJECT_VERSION_NUMBER, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. These support optimistic locking and WHO-column auditing conventions used throughout the EBS data model.

Common Use Cases and Queries

Typical use cases include auditing the configuration of source system to ledger transfers, validating that a ledger has been properly assigned to a source system before running a transfer, and reporting on the BSV assignment type applied to each mapping. A common query lists all ledgers mapped to a given source system:

  • SELECT ledger_id, bsv_assignment_type FROM gl_xfr_system_ledgers WHERE system_map_id = :p_system_map_id;
  • Joining to the source system table to obtain readable system names: SELECT s.source_system_name, l.ledger_id, l.bsv_assignment_type FROM gl_xfr_system_ledgers l JOIN gl_xfr_source_systems s ON s.system_map_id = l.system_map_id;
  • Detecting configuration gaps by counting ledgers per system, or checking that a ledger expected to receive transfers has a row present.

Because the table is small and configuration-oriented, it is frequently queried during implementation and troubleshooting of FAH and GL transfer setup rather than as a high-volume reporting source.

Related Objects

The primary documented relationship is the foreign key from GL_XFR_SYSTEM_LEDGERS.SYSTEM_MAP_ID to GL_XFR_SOURCE_SYSTEMS, which defines the parent source-system definition. Other significant related objects in the same transfer/FAH configuration family include the ledger definition table GL_LEDGERS (via LEDGER_ID), the ledger/source-system assignment views used by the transfer programs, and the concurrent programs that perform system-to-ledger transfers. Integration to Fusion is driven by the FAH and accounting transformation APIs, which read these mappings to determine the mapping between an EBS source system and a Fusion ledger, applying the stored BSV_ASSIGNMENT_TYPE to drive Balance Sheet Value assignment. Reporting typically joins these objects to GL_LEDGERS and GL_XFR_SOURCE_SYSTEMS to produce a complete picture of the transfer configuration landscape.