Search Results user_maintainable_flag

Overview

AS_LOOKUP_TYPES is an APPS-owned database view that exposes a filtered and product-scoped subset of Oracle Application Object Library (FND) lookup type definitions for the Sales Foundation (AS) product. In Oracle E-Business Suite 12.1.1 and 12.2.2, it is catalogued as a VALID object with the description "Lookup type view." Its purpose is to present lookup types belonging to a specific application context — the view restricts rows to VIEW_APPLICATION_ID = 279 — so that only the lookup types owned by or registered against the Sales Foundation application are returned. This makes the view a convenient reporting and integration surface, since consumers do not need to re-implement application filtering or lookup security-group resolution logic themselves. The view is commonly referenced in forms, concurrent programs, and ad hoc queries that need to enumerate the valid lookup types available to Sales Foundation functionality.

Underlying Base Objects

The view is defined over the FND_LOOKUP_TYPES_VL view (via the FND_LOOKUP_TYPES synonym), the FND_GLOBAL package, and the FND_LOOKUP_TYPES base table through the synonym and view chain. The documented ETRM metadata records three referenced base objects: FND_GLOBAL (PACKAGE), FND_LOOKUP_TYPES (SYNONYM), and FND_LOOKUP_TYPES_VL (VIEW). The core SELECT joins to FND_LOOKUP_TYPES_VL LV, applies the constant application filter (LV.VIEW_APPLICATION_ID = 279), and further restricts rows to the maximum security group for each lookup type. That security restriction is resolved by calling FND_GLOBAL.LOOKUP_SECURITY_GROUP(LT.LOOKUP_TYPE, LT.VIEW_APPLICATION_ID), a standard FND function that returns the appropriate security group for the current user's context. The subquery selects MAX(LT.SECURITY_GROUP_ID) from FND_LOOKUP_TYPES for the matching lookup type and application, ensuring that each lookup type surfaces only its highest-priority security group row. Because it is a view and not a table, AS_LOOKUP_TYPES holds no data of its own and always reflects the current state of the underlying FND lookup type definitions.

Key Columns

• LOOKUP_TYPE — The internal name of the lookup type, which is the primary business key used to reference a set of lookup codes.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns recording when and by whom the lookup type was last modified.
• CREATION_DATE, CREATED_BY — Audit columns recording the creation of the lookup type definition.
• USER_MAINTAINABLE_FLAG — Indicates whether the lookup type is user-maintainable, i.e., whether end users are permitted to add or modify lookup values. This is the column flagged in the user's search and is a frequent filter in queries that separate extensible lookups from system-owned ones. Note that this flag is present in the documented column list for the view.
• CUSTOMIZATION_LEVEL — Identifies the customization level of the lookup type, commonly used to distinguish Oracle-supplied versus user-defined content.
• DESCRIPTION — The descriptive text associated with the lookup type, useful for reporting and user-facing displays.

Common Use Cases and Queries

This view is typically queried to enumerate the Sales Foundation lookup types available in the current environment, to drive validation lists or LOVs, or to audit which lookup types are user-maintainable. A representative query listing user-maintainable lookup types is:

SELECT lookup_type, description, user_maintainable_flag, customization_level
FROM apps.as_lookup_types
WHERE user_maintainable_flag = 'Y';

A broader inventory query that includes audit information might be:

SELECT lookup_type, description, creation_date, last_update_date, last_updated_by
FROM apps.as_lookup_types
ORDER BY lookup_type;

Because the view already scopes results to application 279 and resolves the applicable security group through FND_GLOBAL, it is well suited for reporting and integration tasks that must respect Oracle's lookup security model without duplicating that logic. Queries against it should be run in the APPS schema context or with appropriate synonyms and privileges, consistent with standard EBS practice for FND-based lookup objects.