Results for “cz_tlcol_rt_cond_objs_lkv”

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

Overview

In Oracle E-Business Suite releases 12.1.1 and 12.2.2, the object CZ_TLCOL_RT_COND_OBJS_LKV is a database view owned by the APPS schema within the CZ (Configurator) product module. Its status is documented as VALID. The view functions as a lookup-value access layer that exposes a specific, filtered subset of the general Oracle EBS lookup mechanism. Specifically, it restricts the underlying lookup values to the lookup type or list named TL_COL_RT_COND_OBJS, which corresponds to the runtime condition objects used by the Configurator's rule and constraint engine.

The view is not a transactional or reporting fact object; rather, it is a convenience and security abstraction over Flexfield/Lookup infrastructure. It presents label, description, and ordering information together with language-specific derivation, allowing concurrent programs, forms, and integration interfaces to resolve valid runtime condition object identifiers without directly querying the shared lookup values table. Because it inherits the translated and secure behavior of its base object, it respects the language and source-language columns required for MLS (Multi-Language Support) compliance in EBS.

Underlying Base Objects

The ETRM metadata documents a single referenced base object: CZ_LOOKUP_VALUES_VL, which is itself a view. The relationship is a simple projection with a fixed predicate. The view text is defined as:

• 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 = 'TL_COL_RT_COND_OBJS'

Because it selects from CZ_LOOKUP_VALUES_VL (the translated/secure variant of the lookup values), the view automatically inherits the language filtering and security rules applied by that underlying view. In practice, CZ_LOOKUP_VALUES_VL is backed by the FND lookup values tables, where lookup codes for Configurator are registered under the application's lookup types. The _LKV naming suffix and the fixed LIST_NAME predicate confirm that this object is a dedicated lookup-helper view rather than a general-purpose data source.

Key Columns

• LIST_NAME – The lookup type name; here always TL_COL_RT_COND_OBJS, identifying the runtime condition objects list.
• DATA_VALUE – The lookup code / data value representing the condition object or its associated identifier.
• NUMERIC_ID_VALUE – The numeric identifier associated with the lookup entry, useful for joins against internal numeric keys.
• VALUE_SEQ – The display sequence used to order values in lists of values (LOVs).
• DATA_TYPE_ID – Indicates the data type classification of the lookup value.
• NULL_VALUE_FLAG – Flag indicating whether the value represents a null or empty selection.
• VALUE_LABEL – The user-facing label rendered in forms and reports.
• VALUE_DESCRIPTION – The longer descriptive text for the value.
• VALUE_NOTES – Supplementary notes attached to the lookup value.
• LANGUAGE – The language of the returned translation.
• SOURCE_LANG – The source language from which the translation derives, used for MLS fallback.

Common Use Cases and Queries

This view is typically queried when validating or displaying the set of condition objects available to the Configurator runtime engine, or when building LOV definitions that must respect language and enabled-value rules. A representative query lists all ordered condition object values:

• SELECT DATA_VALUE, VALUE_LABEL, VALUE_SEQ FROM APPS.CZ_TLCOL_RT_COND_OBJS_LKV ORDER BY VALUE_SEQ;
• SELECT LIST_NAME, DATA_VALUE, NUMERIC_ID_VALUE FROM APPS.CZ_TLCOL_RT_COND_OBJS_LKV WHERE NULL_VALUE_FLAG = 'N';
• SELECT DATA_VALUE, VALUE_LABEL FROM APPS.CZ_TLCOL_RT_COND_OBJS_LKV WHERE LANGUAGE = USERENV('LANG');

Typical scenarios include custom Configurator rule extensions, diagnostic validation that a required condition object lookup code exists, and integrated interfaces that need to translate condition object codes into descriptive labels for downstream reporting. Because the view is read-only and constrained, it is safe for use in reports and concurrent programs without risk of exposing unrelated lookup types.