Results for “xla_gl_ledgers_v”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

XLA_GL_LEDGERS_V is a Subledger Accounting (XLA) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the set of GL ledgers that are eligible for Subledger Accounting processing, together with the SLA-specific configuration attributes that govern how subledger journals are generated, balanced, and converted for each ledger. The view is not a transactional object; it is a configuration and validation view used by SLA setup, accounting program logic, and reporting layers to resolve ledger-level accounting behavior.

The view filters GL_LEDGERS to legal ledgers only, excluding ledger sets and other non-ledger entities. Because it returns one row per qualifying ledger, it is commonly used to drive lookups, LOVs, and diagnostic queries where the accounting method, balancing segment, management segment, and balancing suspension accounts must be known. The search term sla_entered_cur_bal_sus_ccid maps directly to a column in this view, indicating that the user was investigating the entered-currency balancing suspension account assigned to a ledger.

Underlying Base Objects

The view is defined over a single documented base object: GL_LEDGERS (referenced in the APPS schema through a synonym). No joins to GL_LEDGER_SETS or GL_CODE_COMBINATIONS are present in the view definition itself; the SLA columns are stored directly on GL_LEDGERS and are simply projected by the view. The WHERE clause applies three filters:

  • OBJECT_TYPE_CODE = 'L' — restricts the result to ledgers rather than ledger sets.
  • LE_LEDGER_TYPE_CODE = 'L' — restricts the result to legal ledgers.
  • LEDGER_CATEGORY_CODE IN ('PRIMARY','SECONDARY','ALC','NONE') — includes primary, secondary, and accounting-configuration ledgers, as well as ledgers with no category assigned.

Because the view is a thin projection over GL_LEDGERS, it inherits the base table's data types, security, and indexing. Responsibility-level data access to GL_LEDGERS is therefore indirectly reflected in what rows a user can retrieve through this view.

Key Columns

Common Use Cases and Queries

Typical uses include SLA setup verification, balancing-account diagnostics, and reporting on ledger accounting configuration. The view is frequently joined to GL_LEDGERS or GL_CODE_COMBINATIONS to translate the CCID columns into concatenated account strings.

To find the entered-currency balancing suspension account configured for each legal ledger:

  • SELECT l.ledger_id, l.name, l.currency_code, l.sla_accounting_method_code, l.sla_entered_cur_bal_sus_ccid FROM xla_gl_ledgers_v l ORDER BY l.name;

To resolve that CCID to its account string:

  • SELECT l.name, gcc.concatenated_segments FROM xla_gl_ledgers_v l, gl_code_combinations_kfv gcc WHERE gcc.code_combination_id = l.sla_entered_cur_bal_sus_ccid;

To list ledgers that use ledger-currency balancing:

  • SELECT ledger_id, name, sla_bal_by_ledger_curr_flag FROM xla_gl_ledgers_v WHERE sla_bal_by_ledger_curr_flag = 'Y';

Because the view is restricted to legal ledgers, it should not be used where ledger sets or non-legal ledgers must be reported; in those cases GL_LEDGERS or GL_LEDGERS_V should be queried directly.