Results for “view_application_id”

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

Overview

FND_LOOKUP_TYPES is an Oracle Application Object Library (FND) table that stores the definition of QuickCodes, commonly known as lookup types. It is owned by the APPLSYS schema and resides within the E-Business Suite database. In Oracle EBS 12.1.1 and 12.2.2, this table acts as the authoritative registry of lookup type headers — the container record that groups individual lookup values. As the parent of FND_LOOKUP_VALUES, it is central to virtually every module in EBS, since lookup types drive validation lists, list-of-values (LOVs), status codes, and user-interface dropdowns across the application.

From a modeling perspective, the metadata's heuristic Data Vault classification suggests this object is satellite-leaning. This indicates that FND_LOOKUP_TYPES is best treated as a descriptive attribute holder attached to a business hub or link keyed by LOOKUP_TYPE, rather than as a pure transactional or relationship table.

Key Information Stored

The table's unique index FND_LOOKUP_TYPES_U1 spans LOOKUP_TYPE, VIEW_APPLICATION_ID, SECURITY_GROUP_ID, and ZD_EDITION_NAME, making these the principal business-key candidates. The documented primary key FND_LOOKUP_TYPES_PK covers LOOKUP_TYPE, SECURITY_GROUP_ID, and VIEW_APPLICATION_ID.

• LOOKUP_TYPE — the unique internal name identifying the QuickCode (for example, a status or category code).
• VIEW_APPLICATION_ID — identifies the application owning the lookup type; foreign key to FND_APPLICATION.
• SECURITY_GROUP_ID — associates the lookup with a security group; foreign key to FND_SECURITY_GROUPS.
• APPLICATION_ID — the application that defines/registers the lookup.
• CUSTOMIZATION_LEVEL — controls whether the lookup type is user-extensible or system-managed.
• ASSIGN_LEAF_ONLY — a flag governing hierarchy assignment behavior.
• ZD_EDITION_NAME — editioning column (relevant to 12.2 online patching).
• Audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Developers and functional analysts query this table to enumerate lookup types, validate configuration, and join to values for reporting. A typical pattern retrieves all types for an application:

• SELECT LOOKUP_TYPE, VIEW_APPLICATION_ID, CUSTOMIZATION_LEVEL FROM FND_LOOKUP_TYPES WHERE VIEW_APPLICATION_ID = :app_id;
• Join to FND_LOOKUP_VALUES to list codes and their meanings.
• Audit who created or last modified a lookup type using the date/by columns.
• Identify user-extensible lookups via CUSTOMIZATION_LEVEL.

These queries support forms personalization, OAF list-of-values configuration, and interface development where valid values must be resolved at runtime.

Related Objects

The most significant dependencies are established through documented foreign keys:

• FND_LOOKUP_VALUES — child table; joined on LOOKUP_TYPE, SECURITY_GROUP_ID, and VIEW_APPLICATION_ID.
• FND_APPLICATION — parent of VIEW_APPLICATION_ID.
• FND_SECURITY_GROUPS — parent of SECURITY_GROUP_ID.

In practice, forms, concurrent programs, and the FND dictionary reference lookup types indirectly, making this table a foundational reference object throughout EBS.