Search Results gl_xfr_ledgers_u2

Overview

GL.GL_XFR_LEDGERS is a General Ledger reference table in the Oracle E-Business Suite GL schema that stores the definition and configuration of ledgers eligible for transfer (transfer ledgers). It is populated during ledger setup and upgrade routines and acts as the authoritative source of ledger attributes consumed by the Accounting Setup Manager, the General Ledger transfer and consolidation engines, and Subledger Accounting (SLA). In EBS 12.1.1 and 12.2.2 the object is registered under FND Design Data as SQLGL.GL_XFR_LEDGERS with a status of VALID, and it resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10.

Heuristically, the table is best modeled as a standalone entity rather than a hub, link, or satellite. It carries no foreign-key dependencies into other core GL entities in the documented relationship data and behaves as a self-contained configuration or reference object. Modeling guidance therefore suggests treating it as a reference or dimension-style object, keyed by its own surrogate identifier, rather than as a component of a multi-source Data Vault construct.

Key Information Stored

The primary key is GL_XFR_LEDGERS_PK on LEDGER_ID, which is also enforced through the unique index GL_XFR_LEDGERS_U2. Two business-key candidates are documented: NAME (unique index GL_XFR_LEDGERS_U1) and LEDGER_ID (unique index GL_XFR_LEDGERS_U2), confirming that both the ledger identifier and the ledger name are guaranteed unique.

• LEDGER_ID — surrogate primary key and unique business key candidate; identifies each transfer ledger.
• NAME, SHORT_NAME, DESCRIPTION — the ledger's display name, abbreviated name, and descriptive text.
• LEDGER_CATEGORY_CODE, ALC_LEDGER_TYPE_CODE, LE_LEDGER_TYPE_CODE, OBJECT_TYPE_CODE — classify the ledger (e.g., primary, secondary, consolidation) and its legal-entity association.
• CHART_OF_ACCOUNTS_ID, CURRENCY_CODE, PERIOD_SET_NAME, ACCOUNTED_PERIOD_TYPE — core accounting configuration: chart of accounts, functional currency, and accounting calendar.
• FIRST_LEDGER_PERIOD_NAME, LATEST_OPENED_PERIOD_NAME — the ledger's opening period and its most recently opened period.
• RET_EARN_CODE_COMBINATION_ID, CUM_TRANS_CODE_COMBINATION_ID, SUSPENSE_ALLOWED_FLAG — retained earnings, cumulative translation, and suspense-account behavior.
• ENABLE_AVERAGE_BALANCES_FLAG, ENABLE_BUDGETARY_CONTROL_FLAG, REQUIRE_BUDGET_JOURNALS_FLAG, ENABLE_JE_APPROVAL_FLAG, ENABLE_AUTOMATIC_TAX_FLAG — operational and control flags that govern journal processing.
• TRANSLATE_EOD_FLAG, TRANSLATE_QATD_FLAG, TRANSLATE_YATD_FLAG, TRANSACTION_CALENDAR_ID, DAILY_TRANSLATION_RATE_TYPE — translation and rate-type configuration, referencing GL_TRANSACTION_CALENDAR.
• CONSOLIDATION_LEDGER_FLAG, TRACK_ROUNDING_IMBALANCE_FLAG, BAL_SEG_VALUE_SET_ID, MGT_SEG_VALUE_SET_ID — consolidation, rounding, and balancing/management segment setup.
• AUTOMATICALLY_CREATED_FLAG, COMPLETION_STATUS_CODE, CONFIGURATION_ID — lifecycle and setup-completion tracking.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, OBJECT_VERSION_NUMBER — standard audit and optimistic-locking columns.

In total, 110 columns are documented for version 12.2.2, including many SLA-specific and attribute-flexfield columns.

Common Use Cases and Queries

The most frequent use is identifying and describing ledgers during accounting setup, transfer, and consolidation. A typical lookup resolves a ledger by name or ID:

• Retrieve ledger configuration: SELECT ledger_id, name, chart_of_accounts_id, currency_code, period_set_name FROM gl_xfr_ledgers WHERE ledger_id = :p_ledger_id;
• List primary ledgers: SELECT ledger_id, name FROM gl_xfr_ledgers WHERE ledger_category_code = 'PRIMARY';
• Find ledgers by accounting calendar using the nonunique index GL_XFR_LEDGERS_N1 on (CHART_OF_ACCOUNTS_ID, PERIOD_SET_NAME, ACCOUNTED_PERIOD_TYPE).
• Resolve balancing or management segment value sets via GL_XFR_LEDGERS_N2 (BAL_SEG_VALUE_SET_ID) and GL_XFR_LEDGERS_N3 (MGT_SEG_VALUE_SET_ID).
• Reporting on transfer-eligible ledgers for period-close and consolidation dashboards, joining to GL_TRANSACTION_CALENDAR on TRANSACTION_CALENDAR_ID.

Because it is a reference table, queries should generally be filtered on LEDGER_ID or NAME to leverage the unique indexes rather than performing full scans.

Related Objects

The documented foreign keys and reference targets include:

• GL.GL_TRANSACTION_CALENDAR — referenced via TRANSACTION_CALENDAR_ID; supplies the transaction calendar for daily translation rates.
• GL.GL_MGT_SEG_UPGRADE_H — referenced via CHART_OF_ACCOUNTS_ID in the documented dependency data, supporting management segment upgrade processing.
• GL.GL_LEDGERS — the runtime ledger definition table that shares the LEDGER_ID key and is commonly joined for full ledger context.
• GL.GL_CODE_COMBINATIONS — joined through RET_EARN_CODE_COMBINATION_ID, CUM_TRANS_CODE_COMBINATION_ID, and related CCID columns to resolve account combinations.
• GL.GL_LEDGER_CONFIG_DETAILS / Accounting Setup Manager tables — consume the transfer-ledger configuration during accounting configuration.
• GL.GL_JE_BATCHES and GL.GL_JE_HEADERS — journal entry tables whose processing is governed by the flags (approval, budgetary control) held here.
• SLA accounting APIs — reference the SLA_* columns (e.g., SLA_ACCOUNTING_METHOD_CODE, SLA_SEQUENCING_FLAG) during subledger accounting rule resolution.

These relationships make GL_XFR_LEDGERS a central configuration dependency for ledger transfer, translation, consolidation, and SLA processing across EBS 12.1.1 and 12.2.2.