Search Results ui_components

Overview

In Oracle E-Business Suite 12.1.1 and 12.2.2, APPS.CZ_UICOMPONENTS_LKV is a filtered lookup view belonging to the Oracle Application Object Library (Common Modules / ETRM) schema. As the _LKV suffix implies ("lookup view"), the object does not store data independently; it presents a restricted subset of a more general lookup-values view, returning only those lookup rows whose LIST_NAME equals 'UI_COMPONENTS'. The view therefore acts as a convenience access point for the enumeration of user-interface component types used by the Oracle EBS flexfield and UI-generation infrastructure.

Because the view is defined in the APPS schema and joins directly to seeded lookup metadata, it is intended for read-only reporting, validation, and integration purposes. It is not a transactional object, and it should not be updated directly. Its role is to expose the canonical list of UI component codes together with their multilingual display labels, descriptions, and sequence ordering, so that reports and interfaces can translate stored codes into user-facing text.

Underlying Base Objects

The ETRM metadata documents a single referenced base object for this view: CZ_LOOKUP_VALUES_VL, itself a view. The definition is a simple projection with a fixed predicate:

• SELECT LIST_NAME, DATA_VALUE, NUMERIC_ID_VALUE, VALUE_SEQ, DATA_TYPE_ID, NULL_VALUE_FLAG, VALUE_LABEL, VALUE_DESCRIPTION, VALUE_NOTES, LANGUAGE, SOURCE_LANG FROM CZ_LOOKUP_VALUES_VL WHERE LIST_NAME = 'UI_COMPONENTS'

Consequently, CZ_UICOMPONENTS_LKV inherits its structure and its translation behavior from CZ_LOOKUP_VALUES_VL. The _VL designation on the base view indicates that it surfaces the "view language" rows, resolving the rows appropriate to the runtime language (including the LANGUAGE and SOURCE_LANG translation columns). The _LKV layer adds only the LIST_NAME filter, narrowing the result set to the UI_COMPONENTS lookup type. No tables are listed as directly referenced; the dependency is exclusively on the underlying view.

Key Columns

The columns exposed mirror those of the parent lookup view and carry standard lookup semantics:

• LIST_NAME — Identifies the lookup type. In this view it is always UI_COMPONENTS, since the predicate fixes the value.
• DATA_VALUE — The internal lookup code, i.e., the stored UI component identifier referenced by application data.
• NUMERIC_ID_VALUE — A numeric identifier for the lookup value where one is maintained, useful for joins that key on a numeric ID.
• VALUE_SEQ — The display ordering sequence; determines the sort order in list-of-values popups and reports.
• DATA_TYPE_ID — Indicates the data type associated with the lookup value.
• NULL_VALUE_FLAG — Flag indicating whether the value represents a null or "no selection" entry.
• VALUE_LABEL — The translated display label shown to users.
• VALUE_DESCRIPTION — The translated descriptive text for the value.
• VALUE_NOTES — Additional free-text notes attached to the value.
• LANGUAGE — The language code of the returned (translated) row.
• SOURCE_LANG — The source language from which the translation was derived.

Common Use Cases and Queries

Typical uses include populating selection lists in custom forms, validating that a stored code is a legitimate UI component, and generating reference reports. A straightforward enumeration sorted for display is:

• SELECT DATA_VALUE, VALUE_LABEL, VALUE_DESCRIPTION, VALUE_SEQ FROM APPS.CZ_UICOMPONENTS_LKV ORDER BY VALUE_SEQ;

To resolve a single stored code to its translated label:

• SELECT VALUE_LABEL FROM APPS.CZ_UICOMPONENTS_LKV WHERE DATA_VALUE = :component_code;

To restrict output to the current session language for reporting, filter on LANGUAGE using USERENV('LANG'). Because the view is read-only and seeded, it should be queried only; customizations should reference it rather than duplicate its contents.