Search Results rt_cond_obj_settings




Overview
Explore in AI Chat

Overview

APPS.CZ_RTCONDOBJSETTINGS_LKV is a filtered lookup view within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environment, delivered as part of the Oracle Enterprise Trade Management (ETRM) / Contracts Intelligence application stack. The suffix "LKV" denotes a "lookup values" construct, and the view is designed to expose a single, targeted lookup type — RT_COND_OBJ_SETTINGS — to EBS reports, forms, concurrent programs, and integration interfaces. Rather than allowing a caller to interrogate the entire lookup repository, this view hard-codes the WHERE predicate LIST_NAME = 'RT_COND_OBJ_SETTINGS', ensuring that consumers receive only the seed and configuration rows relevant to real-time condition object settings.

The lookup type RT_COND_OBJ_SETTINGS governs configurable behavior associated with "condition objects" in ETRM. Condition objects represent the pricing, quantity, or eligibility conditions evaluated during contract and pricing engine processing. The view therefore plays a supporting configuration role: it surfaces the lookup codes, labels, descriptions, and ordering that the application reads at runtime to drive condition object behavior.

Underlying Base Objects

The view is defined exclusively over a single documented base object: CZ_LOOKUP_VALUES_VL, itself a view (the "_VL" suffix indicating a "view with language" pattern common throughout EBS lookup architecture). The APPS-owned definition is a straightforward projection:

CZ_LOOKUP_VALUES_VL is the multilingual runtime view over the lookup values base table (CZ_LOOKUP_VALUES_B / _TL), which stores the translation-enabled label and description columns keyed to the session language. Because the base is language-aware, CZ_RTCONDOBJSETTINGS_LKV automatically returns rows in the caller's current language, falling back to the source language where a translation is absent. The view introduces no joins, unions, or aggregation of its own; all filtering is the single LIST_NAME predicate.

Key Columns

  • LIST_NAME — Always 'RT_COND_OBJ_SETTINGS' in this view; retained for schema parity with the base view.
  • DATA_VALUE — The internal lookup code stored in the database and referenced by application logic.
  • NUMERIC_ID_VALUE — Optional numeric identifier where the setting is numeric rather than alphabetic.
  • VALUE_SEQ — Display ordering sequence used when rendering the lookup values in a list of values (LOV).
  • DATA_TYPE_ID — Indicates the data type of the value (e.g., character, number).
  • NULL_VALUE_FLAG — Flags rows permitting or representing a null/blank selection.
  • VALUE_LABEL / VALUE_DESCRIPTION / VALUE_NOTES — User-facing translated text describing the setting.
  • LANGUAGE / SOURCE_LANG — Session language and the original (source) language of the translation, enabling multilingual reporting.

Common Use Cases and Queries

Typical consumers include ETRM concurrent programs and diagnostic queries validating that condition object settings are seeded and correctly translated. A simple listing ordered for LOV presentation:

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

To confirm multilingual coverage across languages in a 12.2.2 environment:

  • SELECT DATA_VALUE, VALUE_LABEL, LANGUAGE, SOURCE_LANG FROM APPS.CZ_RTCONDOBJSETTINGS_LKV ORDER BY DATA_VALUE, LANGUAGE;

Because the view is already restricted to a single lookup type, no additional LIST_NAME predicate is required. Access is granted through the APPS schema and is typically read-only for reporting and integration purposes.