Results for “cz_lookup_values_vl”

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

Overview

CZ_LOOKUP_VALUES_VL is a seeded, read-only view owned by the APPS schema within the Oracle E-Business Suite Configurator (CZ) module. It presents a language-translated, denormalized view of Configurator lookup values, joining the untranslated lookup value base table to its translation table so that display label, description, and notes are returned for the session's active language. Functionally it mirrors the behavior of Oracle's standard _VL ("view with language") convention used throughout EBS, where multilingual columns are resolved through a join to the corresponding _TL table rather than being read directly.

Within ETRM 12.1.1 and 12.2.2 the object is documented as a VALID view in the CZ – Configurator product. Its primary role is to support reporting queries, interface extraction, and integration logic that needs human-readable descriptions of Configurator lookup values without the caller writing the language join manually. Because it filters on the runtime session language via USERENV('LANG'), it always returns the translated strings appropriate to the current user's language setting.

Underlying Base Objects

The ETRM metadata lists two referenced base objects, exposed to the view through synonyms:

• CZ_LOOKUP_VALUES — the untranslated lookup value definition table, supplying the list name, data value, sequence, data type, null-value flag, numeric identifier, and audit columns.
• CZ_LOOKUP_VALUES_TL — the translation table holding the language-specific VALUE_LABEL, VALUE_DESCRIPTION, VALUE_NOTES, LANGUAGE, and SOURCE_LANG.

The two are joined on LIST_NAME and DATA_VALUE. The view additionally restricts rows with LKT.LANGUAGE = USERENV('LANG') and eliminates soft-deleted records by requiring DELETED_FLAG = '0' on both the base and translation rows. Audit columns (CREATION_DATE, LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) are sourced from the translation table.

Key Columns

• LIST_NAME — identifies the lookup list (lookup type) to which the value belongs; the primary grouping key.
• DATA_VALUE — the stored, untranslated code value used in data relationships.
• VALUE_LABEL — the translated display label for the value in the session language.
• VALUE_DESCRIPTION, VALUE_NOTES — translated supplementary descriptive text.
• VALUE_SEQ — display ordering sequence for the value within its list.
• DATA_TYPE_ID — reference to the value's data type definition.
• NULL_VALUE_FLAG — indicates whether the value represents a null/blank selection.
• NUMERIC_ID_VALUE — numeric identifier form of the value where applicable.
• LANGUAGE, SOURCE_LANG — the installed language of the returned translation and the source language from which it was derived.

Common Use Cases and Queries

Typical scenarios include building Configurator validation reports, extracting pick-list values for downstream integrations, and populating LOVs in custom concurrent programs or BI Publisher reports where translated labels are required. Because the view already enforces the language and soft-delete filters, querying it is preferable to joining the base tables directly.

Retrieve all active values for a given lookup list:

• SELECT list_name, data_value, value_label, value_description, value_seq FROM cz_lookup_values_vl WHERE list_name = :p_list_name ORDER BY value_seq;

Resolve a single value's translated label:

• SELECT value_label FROM cz_lookup_values_vl WHERE list_name = :p_list_name AND data_value = :p_data_value;

Because LANGUAGE is always resolved by USERENV('LANG'), callers cannot force an alternate language without changing the session locale (for example, via ALTER SESSION SET NLS_LANGUAGE), which should be considered when designing multilingual extracts.