Results for “cz_layout_ui_style_lkv”

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

Overview

CZ_LAYOUT_UI_STYLE_LKV is a read-only lookup view owned by the APPS schema within the Oracle Configurator (CZ) product in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the set of valid values for the LAYOUT_UI_STYLE lookup type, providing the enumerated styles that govern how a Configurator user interface layout is rendered. Rather than presenting a physical table, the view acts as a filtered, denormalized window onto the shared lookup infrastructure, isolating exactly those rows relevant to layout UI style selection.

Because Configurator runtime and administrative pages must validate and present UI style options consistently, this view centralizes that logic. Reporting tools, concurrent programs, and integration layers can query it to retrieve the canonical list of active UI styles without re-implementing the underlying filter, ensuring that any downstream consumer reads the same controlled vocabulary that the Configurator application itself uses.

Underlying Base Objects

According to the 12.2.2 documented metadata, the view is defined over a single referenced object: the view CZ_LOOKUP_VALUES_VL. That base view is the Configurator-specific, language-enabled layer over Oracle's generic lookup values, supplying translated labels and descriptions alongside the coded values. CZ_LAYOUT_UI_STYLE_LKV narrows this base by applying a constant predicate, LIST_NAME = 'LAYOUT_UI_STYLE', and projects a fixed column list. No base tables are directly referenced; the dependency chain routes through CZ_LOOKUP_VALUES_VL to the underlying Configurator lookup tables. This design means the view inherits the translation and multi-language behavior of the base view, including the LANGUAGE and SOURCE_LANG columns used to resolve installed language variants.

Key Columns

• LIST_NAME — The lookup type name; for every row returned this equals LAYOUT_UI_STYLE, confirming the view's fixed scope.
• DATA_VALUE — The internally stored lookup code for the style, used programmatically when a style is assigned or compared.
• NUMERIC_ID_VALUE — A numeric identifier accompanying the value where a lookup requires a numeric key.
• VALUE_SEQ — The display sequence controlling the ordering in which styles appear in lists of values.
• DATA_TYPE_ID — Identifies the data type associated with the lookup value.
• NULL_VALUE_FLAG — Indicates whether the value represents a null or "no selection" option.
• VALUE_LABEL — The translated, user-facing label shown in the Configurator UI.
• VALUE_DESCRIPTION and VALUE_NOTES — Longer descriptive and supplementary text for the style.
• LANGUAGE and SOURCE_LANG — The language of the returned translation and its source language, enabling language-aware reporting.

Common Use Cases and Queries

Typical scenarios include generating code-to-label cross-reference reports, validating that a stored layout UI style is still an active lookup value, and feeding pick lists in custom Configurator extensions. A simple enumeration follows:

• Listing all defined UI styles in display order: SELECT DATA_VALUE, VALUE_LABEL, VALUE_SEQ FROM CZ_LAYOUT_UI_STYLE_LKV ORDER BY VALUE_SEQ;
• Retrieving only populated (non-null) styles: SELECT DATA_VALUE, VALUE_LABEL FROM CZ_LAYOUT_UI_STYLE_LKV WHERE NULL_VALUE_FLAG = 'N';
• Filtering by language in a multilingual environment: SELECT DATA_VALUE, VALUE_LABEL FROM CZ_LAYOUT_UI_STYLE_LKV WHERE LANGUAGE = USERENV('LANG');
• Joining to configuration data to resolve the label for a stored style code: SELECT l.VALUE_LABEL FROM CZ_LAYOUT_UI_STYLE_LKV l, your_ui_config_t c WHERE l.DATA_VALUE = c.LAYOUT_UI_STYLE;

Because the view is APPS-owned and VALID in both 12.1.1 and 12.2.2, these queries are portable across the two releases, subject to the standard language and security considerations applied to Configurator lookups.