Results for “cz_rtcondobjsettings_lkv”

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

Overview

CZ_RTCONDOBJSETTINGS_LKV is a read-only database view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the CZ (Configurator) product family and is documented as VALID in the ETRM repository. The view is a filtered presentation layer over the seeded lookup values used by Oracle Configurator, specifically the lookup type identified internally as RT_COND_OBJ_SETTINGS. Rather than exposing every lookup value defined in the Configurator lookup repository, the view restricts output to the single list name RT_COND_OBJ_SETTINGS, which governs settings applied to runtime conditional object definitions.

The suffix convention of "_LKV" identifies this object as a lookup-values view, a common ETRM pattern in which a dedicated view name is registered for a specific lookup list so that reports, concurrent programs, and integrations can reference a stable, pre-filtered object without hard-coding the underlying lookup table or the list name predicate. In this way, the view functions as a semantic alias and satisfies reporting and integration requirements that need enumeration or validation of the runtime conditional object settings available in a given environment.

Underlying Base Objects

The view is defined exclusively over a single documented base object: CZ_LOOKUP_VALUES_VL, itself a view within the APPS schema. CZ_LOOKUP_VALUES_VL is the Configurator lookup-values view that carries language-specific translated label and description columns, and it ultimately derives from the Configurator lookup values base tables. Because the documented base object is itself a view rather than a table, CZ_RTCONDOBJSETTINGS_LKV inherits the language handling and translation semantics of the Configurator lookup framework.

The join or filter between the two objects is not a relational join but an equality predicate on the LIST_NAME column. The view text selects all standard lookup columns and applies the restriction LIST_NAME = 'RT_COND_OBJ_SETTINGS'. No additional WHERE clause, DISTINCT, GROUP BY, or ordering is documented, and no external keys are exposed beyond the columns inherited from CZ_LOOKUP_VALUES_VL.

Key Columns

The view projects eleven columns, each inherited directly from CZ_LOOKUP_VALUES_VL without transformation:

• LIST_NAME — The lookup type name. In this view it is always the constant value RT_COND_OBJ_SETTINGS.
• DATA_VALUE — The internal stored value of the lookup entry, normally the value carried by transactional or configuration data.
• NUMERIC_ID_VALUE — A numeric surrogate identifier associated with the lookup value, useful where numeric keys are preferred over character values.
• VALUE_SEQ — The display or sort sequence controlling the order in which values are presented.
• DATA_TYPE_ID — Identifier of the data type of the lookup value, allowing consumers to interpret DATA_VALUE and NUMERIC_ID_VALUE correctly.
• NULL_VALUE_FLAG — Flag indicating whether a null value is permitted or meaningful for the entry.
• VALUE_LABEL — The translated, user-facing label for the lookup value.
• VALUE_DESCRIPTION — The translated description, providing more verbose text than the label.
• VALUE_NOTES — Additional descriptive notes captured for the lookup value.
• LANGUAGE — The language of the returned label, description, and notes, determined by the session language through the _VL translation mechanism.
• SOURCE_LANG — The source language from which the translated row was derived, following standard EBS MLS conventions.

Common Use Cases and Queries

Typical uses include validating which runtime conditional object settings exist in an instance, driving value lists in custom forms or OAF pages, and building extract or reconciliation reports for Configurator configuration. Because the view already restricts to a single list, queries are simple and do not require a LIST_NAME predicate.

Enumerating all settings in display order:

SELECT value_seq, data_value, value_label
FROM   apps.cz_rtcondobjsettings_lkv
ORDER  BY value_seq;

Looking up a label for a known stored value, and inspecting descriptive metadata:

SELECT data_value, value_label, value_description, value_notes
FROM   apps.cz_rtcondobjsettings_lkv
WHERE  data_value = :p_setting;

Checking language behavior, useful when diagnosing translation gaps:

SELECT language, source_lang, value_label
FROM   apps.cz_rtcondobjsettings_lkv
ORDER  BY language, value_seq;

Because the object is a view with no DML capability, it should be used strictly for query and reference purposes; modifications to the underlying lookup values must be performed through the supported Configurator lookup maintenance interface, after which the view reflects changes immediately.