Search Results xla_lookups




Overview

XLA_LOOKUPS is a read-only database view owned by the APPS schema in Oracle E-Business Suite (EBS) releases 12.1.1 and 12.2.2. It belongs to the XLA product family, Subledger Accounting, and presents a filtered subset of the Oracle Application Object Library (FND) lookup values that pertain specifically to Subledger Accounting functionality. Rather than exposing the entire FND_LOOKUP_VALUES table, the view constrains its result set to those lookup rows that carry a VIEW_APPLICATION_ID of 602, which corresponds to the Subledger Accounting application, and a SECURITY_GROUP_ID of 0, the standard identifier used for shared, non-secured reference data.

The view serves as a convenient, self-documenting source for the enumerated values that drive Subledger Accounting configuration and processing, such as accounting method codes, journal entry statuses, line type classifications, and other seeded or user-defined lookup codes. Because it filters to the language of the current session, it returns the meaning in the runtime language of the user (English in most environments), allowing reports and concurrent programs to display translated descriptions automatically. The metadata confirms the object is VALID in the ETRM data dictionary, indicating it is compiled and available for query at runtime.

Underlying Base Objects

The view is defined over a single base object: FND_LOOKUP_VALUES, accessible through the APPS synonym. FND_LOOKUP_VALUES is the core Oracle Applications table that stores all lookup types and their corresponding lookup codes across the entire E-Business Suite, including values seeded by Oracle and those entered by users during implementation. Each row in that table belongs to a particular lookup type, language, and view application.

XLA_LOOKUPS applies three predicates to that base table: LANGUAGE = USERENV('LANG'), restricting rows to the language of the current session; VIEW_APPLICATION_ID = 602, restricting rows to Subledger Accounting lookups; and SECURITY_GROUP_ID = 0, excluding any security-group-scoped rows that are not part of the shared reference set. The view text is therefore deterministic and inexpensive, since it is a simple projection with filtering and no joins, aggregation, or analytic functions. From a maintenance perspective, the view requires no separate storage and remains synchronized with FND_LOOKUP_VALUES at all times.

Key Columns

The view exposes seven columns inherited directly from FND_LOOKUP_VALUES:

  • LOOKUP_TYPE — the name of the lookup category (for example, an XLA-specific lookup type), identifying the group to which a code belongs.
  • LOOKUP_CODE — the internally stored code value used by Subledger Accounting logic and foreign-key references.
  • MEANING — the display name presented to users, translated according to the session language.
  • DESCRIPTION — an optional longer explanation of the lookup value.
  • ENABLED_FLAG — indicates whether the value is currently active (Y) or disabled (N) for selection.
  • START_DATE_ACTIVE and END_DATE_ACTIVE — the effective date range during which the lookup value is valid.

Common Use Cases and Queries

Typical usage includes validating configuration values, joining descriptive meanings to transactional or setup tables, and building LOV-style reports within Subledger Accounting. A representative query lists all enabled XLA lookups for a given type:

SELECT lookup_code, meaning, description, start_date_active, end_date_active FROM xla_lookups WHERE lookup_type = :p_lookup_type AND enabled_flag = 'Y' AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE) ORDER BY meaning;

Because the view is restricted to VIEW_APPLICATION_ID = 602, it should not be used as a general-purpose replacement for FND_LOOKUPS or FND_LOOKUP_VALUES. For lookups belonging to other applications, the broader FND views remain appropriate.