Search Results data_value




Overview
Explore in AI Chat

Overview

APPS.CZ_UITEMPL_RTCOND_BINDSRC_LKV is a reporting and lookup view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments. It belongs to the Oracle ETRM (Enterprise Taxation and Regulatory Management) product family and is owned by the APPS schema. The view functions as a filtered lookup (LK) presentation layer, projecting a restricted subset of lookup value rows used to drive condition and binding source definitions within the user interface template framework.

The "_LKV" suffix denotes a "lookup view," a naming convention Oracle uses for read-only views that expose reference data. This particular object supplies the permissible entries that appear when a runtime condition or object setting must be bound to a source value. Rather than exposing the entire lookup repository, the view deliberately narrows the result set to a single list of values and excludes a specific reserved entry, making it a purpose-built source for user-interface configuration and validation logic.

Underlying Base Objects

The view is defined over a single documented base object: CZ_LOOKUP_VALUES_VL, itself a view in the APPS schema. CZ_LOOKUP_VALUES_VL is the "viewable language" variant of the core lookup values table, meaning it applies language-filtering logic (typically through a _TL or translation-aware join) so that each row is returned in the session language or the source language. Because CZ_UITEMPL_RTCOND_BINDSRC_LKV selects from a _VL view, it inherits that language-resolution behavior and returns values already localized to the caller's environment.

No additional tables or joins are introduced beyond this base view. The relationship is therefore one of simple delegation: the lookup view applies two predicates to the rows of CZ_LOOKUP_VALUES_VL, and all column semantics are inherited unchanged.

Key Columns

  • LIST_NAME — The lookup type identifier. For this view the value is always constrained to 'RT_COND_OBJ_SETTINGS', labeling the entries as runtime condition object settings.
  • DATA_VALUE — The internal value of each lookup entry, serving as the key used by binding logic. This is the column most commonly searched by users and the primary filter target in ad hoc queries.
  • NUMERIC_ID_VALUE — An optional numeric identifier associated with the entry, used where downstream logic requires a numeric rather than textual key.
  • VALUE_SEQ — The ordering sequence that governs presentation order of the lookup entries.
  • DATA_TYPE_ID — Identifies the data type or class of the lookup value, supporting typed handling of the bound source.
  • NULL_VALUE_FLAG — Indicates whether the entry represents a null-value or empty-selection option.
  • VALUE_LABEL — The display label shown to users in the UI.
  • VALUE_DESCRIPTION and VALUE_NOTES — Longer descriptive and annotative text for the entry.
  • LANGUAGE and SOURCE_LANG — The language of the returned row and the original source language, respectively, as supplied by the _VL layer.

Two filters are baked into the view definition and cannot be removed by the caller: LIST_NAME must equal 'RT_COND_OBJ_SETTINGS', and DATA_VALUE must not equal 'OTHER_MODEL_NODE'. The latter exclusion removes a generic catch-all node that is unsuitable for direct binding selection.

Common Use Cases and Queries

The view is typically consumed by ETRM configuration logic and by administrators diagnosing why a particular binding source is or is not available in a template. It is well suited to ad hoc data validation, since the filter guarantees only relevant binding sources are returned.

A basic listing of available binding sources ordered for display:

  • SELECT DATA_VALUE, VALUE_LABEL, VALUE_SEQ FROM APPS.CZ_UITEMPL_RTCOND_BINDSRC_LKV ORDER BY VALUE_SEQ;

Targeted lookup for a known binding key, reflecting the user search for "data_value":

  • SELECT LIST_NAME, DATA_VALUE, VALUE_LABEL FROM APPS.CZ_UITEMPL_RTCOND_BINDSRC_LKV WHERE DATA_VALUE = :bind_value;

Type and null-handling audit across the entry set:

  • SELECT DATA_VALUE, DATA_TYPE_ID, NUMERIC_ID_VALUE, NULL_VALUE_FLAG FROM APPS.CZ_UITEMPL_RTCOND_BINDSRC_LKV ORDER BY VALUE_SEQ;

Because the view is read-only and language-filtered, it is safe for concurrent reporting use and requires no special privileges beyond SELECT on the APPS-owned object.