Search Results ax_lookups




Overview
Explore in AI Chat

Overview

The AX_LOOKUPS view is a Global Accounting Engine (AX) reporting object in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the lookup codes that the Global Accounting Engine uses to normalize and control accounting-related values, giving AX users, report developers, and integration specialists read access to the descriptive values associated with AX lookup types without having to query the underlying flexfield and lookup infrastructure directly.

Functionally, the view behaves as a filtered presentation of Oracle Application Object Library (FND) lookup values. Every row is a single lookup code belonging to a given lookup type, together with its meaning, description, and effective dating. Because the view already restricts results to a language and an application context, it provides a cleaner and more stable query surface than the base lookup table for AX-specific reporting.

Underlying Base Objects

The view text retrieves from a single base object, FND_LOOKUP_VALUES LV. No other tables are joined, and no alternate base objects are documented for this view. The relationship is a straightforward projection: AX_LOOKUPS selects columns from FND_LOOKUP_VALUES and applies three restricting predicates.

  • VIEW_APPLICATION_ID = 600 — restricts the result set to lookups registered under the AX application.
  • LANGUAGE = USERENV('LANG') — returns only the lookup rows matching the language of the current session.
  • SECURITY_GROUP_ID = FND_GLOBAL.LOOKUP_SECURITY_GROUP(LV.LOOKUP_TYPE, LV.VIEW_APPLICATION_ID) — applies the standard lookup security group filter so that only values visible to the current security context are returned.

Because the view derives entirely from FND_LOOKUP_VALUES, its content is maintained through the standard lookup maintenance path for the AX application rather than through a dedicated AX maintenance entity. The ETRM metadata records the owner as undocumented and lists no referenced base objects, which reflects the fact that the definition is held entirely in the view text rather than in a separately catalogued data model.

Key Columns

The view selects thirteen columns from FND_LOOKUP_VALUES. The most frequently used are the following.

  • LOOKUP_TYPE — identifies the lookup category to which the code belongs; together with LOOKUP_CODE this forms the logical key of a value.
  • LOOKUP_CODE — the internal code stored on transactional data.
  • MEANING and DESCRIPTION — the user-facing label and, where populated, a fuller explanation of the code; both are language-dependent.
  • ENABLED_FLAG — indicates whether the code is currently active and selectable; only active codes should normally be reported as valid values.
  • START_DATE_ACTIVE and END_DATE_ACTIVE — the effective date range for the code, allowing historical reporting that reflects which values were valid at a point in time.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — standard audit columns recording who created the row, when, and subsequent modifications.

Common Use Cases and Queries

Typical uses include decoding AX accounting codes on reports, validating reference values before integration loads, and extracting AX lookup sets for migration or reconciliation. Enumerating all available AX lookup types is a frequent first step.

  • SELECT lookup_type, lookup_code, meaning, enabled_flag FROM ax_lookups WHERE lookup_type = 'AX_LOOKUP_TYPE' ORDER BY lookup_code;
  • SELECT DISTINCT lookup_type FROM ax_lookups ORDER BY lookup_type; — inventory of AX lookup types.
  • SELECT lookup_code, meaning FROM ax_lookups WHERE enabled_flag = 'Y' AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE); — currently effective values only.
  • SELECT COUNT(*) FROM ax_lookups WHERE description IS NULL AND enabled_flag = 'Y'; — data-quality check for enabled codes lacking descriptions.

Because the view filters on session language and lookup security group, results depend on the environment and responsibility context in which it is queried; reports should not assume identical output across sessions or languages.