Search Results as_lookups




Overview
Explore in AI Chat

Overview

AS_LOOKUPS is a read-only lookup view owned by the APPS schema within the Oracle E-Business Suite environment. It belongs to the Sales Foundation product, registered under the AS application short name, and carries a status of VALID in the ETRM data dictionary. The view exposes translated lookup values maintained in the Oracle Application Object Library (FND) so that Sales Foundation forms, concurrent programs, and API logic can resolve coded values into descriptive meanings without querying the base dictionary tables directly.

From the perspective of Oracle EBS 12.1.1 and 12.2.2, AS_LOOKUPS functions as an application-scoped window into the shared lookup repository. Rather than presenting every lookup type defined in the instance, it filters the lookup values to those registered against the Sales Foundation application, which in the documented definition corresponds to an application identifier of 279. This scoping is intentional: it prevents Sales Foundation code from inadvertently consuming lookup codes owned by other products and enforces a clean boundary for extension and customization. Because the view is a simple projection with row-level filtering, it inherits the multilingual behavior, security group enforcement, and descriptive flexfield attribute capacity of the underlying dictionary object.

Underlying Base Objects

The documented base object for this view is FND_LOOKUP_VALUES, accessed through a synonym. The view text confirms a direct, unfiltered column projection over FND_LOOKUP_VALUES rather than a join or aggregation, meaning every column exposed by AS_LOOKUPS maps one-to-one to a column in the base table:

  • The FROM clause references FND_LOOKUP_VALUES (aliased FNDLKPV) via its synonym.
  • The WHERE clause applies two predicates: LANGUAGE = USERENV('LANG') restricts rows to the session's current language, returning the appropriate translated meaning; VIEW_APPLICATION_ID = 279 restricts rows to Sales Foundation lookups.
  • The predicate SECURITY_GROUP_ID = FND_GLOBAL.LOOKUP_SECURITY_GROUP(LOOKUP_TYPE, VIEW_APPLICATION_ID) invokes a server-side function to enforce lookup security group membership, so only lookup types accessible to the caller's security context are returned.

Because no DML is possible against a view of this construction, AS_LOOKUPS is strictly a query interface. Lookup maintenance must be performed through the Application Developer responsibility or the corresponding FND APIs, which write to FND_LOOKUP_VALUES directly.

Key Columns

The columns exposed by AS_LOOKUPS carry the full descriptive attribute capacity of the lookup value model:

  • LOOKUP_TYPE — the internal name of the lookup set (for example, a sales-specific encoded value list). This is the primary grouping key.
  • LOOKUP_CODE — the stored, non-translated code used in transactional data and referenced by application logic.
  • MEANING — the translated, user-facing description of the code; this is the column most commonly displayed on forms and reports.
  • DESCRIPTION — optional extended explanation of the lookup value, also translatable.
  • ENABLED_FLAG — indicates whether the value is active; disabled values should typically be excluded from validation lists.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — descriptive flexfield segments attached to the lookup value, allowing installations to capture site-specific metadata without schema change.
  • Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, and CREATED_BY provide the standard Oracle who-did-what auditing trail.

Common Use Cases and Queries

AS_LOOKUPS is most frequently used as a validation source in custom reports, concurrent programs, and inbound interface routines that must convert a stored code into a display meaning, or conversely verify that a supplied code is valid and enabled. A typical retrieval for a single lookup type is:

SELECT lookup_code, meaning, description
FROM apps.as_lookups
WHERE lookup_type = 'AS_SOME_LOOKUP_TYPE'
AND enabled_flag = 'Y'
ORDER BY meaning;

Because the view already enforces the session language and Sales Foundation application scope, developers do not need to add LANGUAGE or VIEW_APPLICATION_ID predicates in their own SQL, although adding ENABLED_FLAG = 'Y' is recommended for any list presented to users. A common join pattern is to link AS_LOOKUPS to a Sales Foundation transaction table on LOOKUP_CODE and LOOKUP_TYPE so that reports display the translated MEANING alongside stored codes. When a query returns no rows unexpectedly, the usual causes are a disabled value, a lookup type belonging to a different application, or a security group that excludes the lookup from the caller's context. In Oracle EBS 12.1.1 and 12.2.2 these behaviors are consistent, since the underlying FND_LOOKUP_VALUES model and the FND_GLOBAL.LOOKUP_SECURITY_GROUP function are shared across both releases.