Results for “per_common_lookup_types_v”

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

Overview

PER_COMMON_LOOKUP_TYPES_V is an APPS-owned database view in the Oracle E-Business Suite Human Resources (PER) product family. It is designated in the ETRM metadata as a view that is "used to support user interface" functionality, meaning it is referenced by Oracle Forms, OAF pages, or related UI components rather than being an end-user reporting object in its own right. The view exposes rows drawn from FND_COMMON_LOOKUP_TYPES, filtered and enriched by a join to the FND_LOOKUPS view through the CUSTOMIZATION_LEVEL column. In the 12.1.1 and 12.2.2 releases the object remains a VALID view in the APPS schema. Because it surfaces lookup type metadata together with human-readable meaning text, it also serves integration and diagnostic scenarios where application code, extensions, or ad hoc queries need to resolve a lookup type's customization classification into a display label.

Underlying Base Objects

The view is defined over two documented referenced objects and one package. The primary source is the FND_COMMON_LOOKUP_TYPES view (aliased FCLT), which supplies the application identifier, lookup type, customization level, and standard WHO audit columns. The second source is the FND_LOOKUPS view (aliased FL), which supplies the meaning text for the customization level. The join condition is FCLT.CUSTOMIZATION_LEVEL = FL.LOOKUP_CODE combined with FL.LOOKUP_TYPE = 'CUSTOMIZATION_LEVEL', so every row returned is matched against the seeded CUSTOMIZATION_LEVEL lookup. A reference to the FND_GLOBAL package is documented in the ETRM metadata, consistent with the standard EBS pattern in which client-side and server-side code resolves the current application, responsibility, and user context through FND_GLOBAL rather than storing those values directly in the view definition. Because the view selects FCLT.ROWID and inherits the underlying security behavior of the FND lookup views, access to rows is governed by the same lookup and application context rules that apply to the base objects.

Key Columns

• ROWID — the row identifier of the FND_COMMON_LOOKUP_TYPES row, exposed to support updatable or navigable UI behavior.
• APPLICATION_ID — identifies the application that owns the lookup type.
• CUSTOMIZATION_LEVEL — the lookup code indicating the customization classification (for example, the seeded core levels such as User or Extensible) that drives extensibility and upgrade behavior.
• D_CUSTOMIZATION_LEVEL — the display or derived form of the customization level column, included in the documented column list for UI rendering.
• MEANING — the translated meaning associated with the customization level, sourced from FND_LOOKUPS.
• LOOKUP_TYPE — the lookup type identifier defined on FND_COMMON_LOOKUP_TYPES.
• LOOKUP_TYPE_MEANING — the descriptive name of the lookup type.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — the standard EBS WHO audit columns for change tracking.

Common Use Cases and Queries

The view is most often used to display lookup type information with a readable customization level, and to audit which lookup types are seeded as core versus user-extensible. A typical query joins the view to application context to list extensible lookup types for a given application:

• Listing all lookup types and their customization levels for review before an upgrade.
• Identifying user-defined lookup types that may require validation or remediation during patching.
• Resolving a customization level code to its meaning for diagnostic reports.

A representative query:

SELECT v.application_id, v.lookup_type, v.lookup_type_meaning, v.customization_level, v.meaning
FROM apps.per_common_lookup_types_v v
WHERE v.application_id = 800
ORDER BY v.lookup_type;

Because the object is documented as UI-supporting rather than as a public interface, customizations should treat its column list as stable within a release but avoid depending on it for persistent data storage or bulk extraction.