Search Results detailed_rule_type




Overview
Explore in AI Chat

Overview

CZ_CREATERULEOBJECT_LKV is a read-only database view owned by the APPS schema in Oracle E-Business Suite, belonging to the CZ (Configurator) product family. It is classified as a lookup value (LKV) view, a naming convention Oracle uses for views that expose translated, user-facing lookup values from underlying Configurator metadata tables. In this case, the view presents the set of object types that may legitimately participate in the creation of Configurator rules, filtered by the applicable configuration engine type for a given development project.

The view serves a narrow but important role: it restricts the population of rule object types exposed to the Configurator rule-authoring UI and integration interfaces so that only object types valid for the engine mode in use are surfaced. Because the Configurator supports multiple engine generations (legacy and Java-based), the view joins through CZ_LOOKUP_VALUES to resolve the engine type and then excludes object types that are governed by mutually exclusive relationships. Reporting layers, extension scripts, and OAF-based rule authoring pages query this view rather than reconstructing the logic themselves.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over four referenced objects, all resolved as synonyms or views in the APPS schema:

  • CZ_DETAILEDRULETYPES_LKV (VIEW) — aliased as RTYV; supplies the translated lookup values for detailed rule types, including value sequences, labels, and descriptions.
  • CZ_TYPE_RELATIONSHIPS (SYNONYM) — aliased as RCH; supplies the subject/object relationship pairs that determine which object types enclose or relate to others, and drives the exclusion subquery.
  • CZ_DEVL_PROJECTS (SYNONYM) — aliased as PRJ; provides the development project context and, critically, the CONFIG_ENGINE_TYPE attribute used to select the active engine. When NULL, the view defaults to engine type 'L'.
  • CZ_LOOKUP_VALUES (SYNONYM) — aliased as MODTYP; resolves the CZ_ENGINE_TYPES lookup list to obtain the numeric engine identifier used in the exclusion subquery.

The view therefore depends indirectly on the base tables underlying these synonyms while presenting a denormalized, ready-to-consume result set.

Key Columns

Common Use Cases and Queries

Typical uses include populating a List of Values (LOV) in the Configurator rule editor, validating objects submitted through APIs, and extracting metadata for reporting on rule composition. A representative query is:

SELECT list_name, enclosing_type, detailed_rule_type, value_label FROM cz_createruleobject_lkv WHERE p_model_id = :p_project_id ORDER BY enclosing_type, detailed_rule_type;

Because all filtering logic (REI_TYPE_CODE = 'RCH', DELETED_FLAG = '0', engine-type matching, and the NOT IN exclusion of MRX relationships) is already applied inside the view, callers receive only valid, non-deleted rule object types appropriate for the project's configuration engine. This makes the view safe to consume directly in custom reports and integration extracts without replicating Configurator internal logic.