Search Results data_value




Overview
Explore in AI Chat

Overview

The CZ_UITEMPL_RTCOND_BINDSRC_LKV view resides in the APPS schema of the Oracle E-Business Suite and belongs to the CZ (Configurator) product family. It is a filtered lookup view that exposes a constrained subset of the records held in the underlying CZ_LOOKUP_VALUES_VL base view. Specifically, the view returns only those lookup values whose LIST_NAME equals RT_COND_OBJ_SETTINGS and whose DATA_VALUE is not equal to OTHER_MODEL_NODE.

In the Configurator module, runtime condition (RT_COND) settings govern how configurable models resolve binding sources at runtime. The lookup list RT_COND_OBJ_SETTINGS stores the enumerated object settings used by the runtime condition engine. By excluding OTHER_MODEL_NODE, this view distinguishes the ordinary bind-source options from the special "other model node" value, which is typically handled through a separate code path. The view therefore functions as a curated LOV (list of values) source for reporting, integration, and user-interface queries that require only the standard bind-source candidates.

Underlying Base Objects

The view is defined over a single documented base object: CZ_LOOKUP_VALUES_VL, itself a view. The _VL suffix indicates a language-dependent view that resolves translated label and description columns against the session language, joining the lookup values table with its translation table. CZ_UITEMPL_RTCOND_BINDSRC_LKV adds a WHERE clause to that base view but introduces no joins, aggregations, or derived columns of its own. Consequently, every column exposed is inherited directly and unmodified from CZ_LOOKUP_VALUES_VL.

Because the definition is a thin filter, the view inherits the security, language resolution, and NLS behavior of the base lookup view. The object carries a VALID status in both Oracle EBS 12.1.1 and 12.2.2, and its column list is identical across those releases.

Key Columns

  • LIST_NAME — The lookup list name; always RT_COND_OBJ_SETTINGS in this view, since the filter is applied internally.
  • DATA_VALUE — The stored lookup code, representing the bind-source identifier. Values equal to OTHER_MODEL_NODE are excluded.
  • NUMERIC_ID_VALUE — A numeric identifier associated with the lookup value, useful for joins against numeric foreign keys.
  • VALUE_SEQ — Sequence controlling display order in LOVs and reports.
  • DATA_TYPE_ID — Identifier of the value's data type.
  • NULL_VALUE_FLAG — Indicates whether the value represents a null or undefined selection.
  • VALUE_LABEL, VALUE_DESCRIPTION, VALUE_NOTES — Language-resolved display text obtained from the underlying _VL view.
  • LANGUAGE, SOURCE_LANG — The language context of the returned translation and the source language from which it was derived.

Common Use Cases and Queries

The view is typically used to populate bind-source LOVs, validate configuration input, and drive reports listing the permitted runtime condition bind sources for a model. A basic query retrieves all available bind sources in display order:

  • SELECT DATA_VALUE, VALUE_LABEL, VALUE_DESCRIPTION FROM CZ_UITEMPL_RTCOND_BINDSRC_LKV ORDER BY VALUE_SEQ;
  • SELECT NUMERIC_ID_VALUE, DATA_VALUE FROM CZ_UITEMPL_RTCOND_BINDSRC_LKV WHERE NULL_VALUE_FLAG = 'N';
  • SELECT DATA_VALUE, VALUE_SEQ FROM CZ_UITEMPL_RTCOND_BINDSRC_LKV ORDER BY DATA_VALUE;

Because the list name filter and the exclusion of OTHER_MODEL_NODE are built into the definition, these queries need not repeat the WHERE clause. Note that the base view's language context determines which translation of VALUE_LABEL and VALUE_DESCRIPTION is returned.