Results for “aso_lookups”

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

Overview

ASO_LOOKUPS is a reporting view owned by the APPS schema in Oracle E-Business Suite, registered as VALID and delivered with the ASO – Order Capture product family. It exposes Order Capture QuickCode values, the configurable code/meaning pairs that drive list-of-values behavior, validation logic, and default values across the Order Capture module. Rather than maintaining its own storage, the view filters the centralized Oracle Application Object Library dictionary table FND_LOOKUP_VALUES to the Order Capture application context. This design ensures that QuickCode maintenance performed through the standard Application Developer responsibility is immediately visible to any query, report, or integration that reads ASO_LOOKUPS.

In both EBS 12.1.1 and 12.2.2 the object remains a view with identical column and filtering semantics; only the online patching and editioning mechanics of the file system differ. Because it is a view and not a table, it is read-only, carries no indexes of its own, and relies entirely on the underlying FND_LOOKUP_VALUES indexes. It is frequently embedded in custom reports, BI Publisher data templates, and interface programs that must translate stored QuickCode values into user-facing meanings.

Underlying Base Objects

The view is defined over FND_LOOKUP_VALUES (referenced through a synonym) and selects only those rows whose VIEW_APPLICATION_ID equals 697, the application identifier for ASO – Order Capture. Two predicates govern visibility:

• Language filtering — LV.LANGUAGE = USERENV('LANG') restricts rows to the session's current language, so a user running in French sees French meanings while the underlying LOOKUP_CODE remains unchanged.
• Security filtering — LV.SECURITY_GROUP_ID = FND_GLOBAL.LOOKUP_SECURITY_GROUP(LV.LOOKUP_TYPE, LV.VIEW_APPLICATION_ID) enforces row-level security on lookup types, preventing exposure of secured QuickCode sets.

No joins, aggregations, or unions are present; the view is a straightforward projection with a WHERE clause. Consequently, performance is a function of FND_LOOKUP_VALUES access paths and the selectivity of the application and security predicates.

Key Columns

• LOOKUP_TYPE — Identifies the QuickCode category (for example, order or line-level code sets used by Order Capture).
• LOOKUP_CODE — The stored value referenced by Order Capture transaction data; this is the internal code persisted on business records.
• MEANING — The translated, user-facing label displayed on forms and reports for the corresponding code.
• DESCRIPTION — Optional longer text elaborating on the code's intent.
• ENABLED_FLAG — Y/N indicator of whether the QuickCode is active and selectable.
• START_DATE_ACTIVE — First date the code becomes valid; null implies no lower bound.
• END_DATE_ACTIVE — Last date the code is valid; null implies no expiry.

Common Use Cases and Queries

The most common requirement is decoding a stored code into its translated meaning. To retrieve all enabled QuickCodes for a specific lookup type:

• SELECT lookup_code, meaning, description FROM aso_lookups WHERE lookup_type = :p_type AND enabled_flag = 'Y' ORDER BY meaning;

To validate that a code was active on the transaction date, the effective-date columns are used:

• SELECT lookup_code FROM aso_lookups WHERE lookup_type = :p_type AND lookup_code = :p_code AND enabled_flag = 'Y' AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, TRUNC(SYSDATE)) AND NVL(end_date_active, TRUNC(SYSDATE));

Integration and ETL programs frequently extract the full set for a given lookup type to build reference-data caches, while BI Publisher reports join ASO_LOOKUPS to Order Capture base tables on LOOKUP_CODE to render labels. Because the view applies language and security filtering automatically, queries inherit correct translation and access control without additional predicates. When troubleshooting missing values, verify the View Application ID, the enabled flag, the effective dates, and the session language, as each can independently suppress rows.