Search Results rule_type_label




Overview
Explore in AI Chat

Overview

CZ_TYPED_RULES_V is a Configurator (CZ) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents fully resolved rule definitions by joining the detailed rule expression view to the Configurator lookup view that supplies rule type metadata. The view is the canonical source for reporting on Configurator rules together with their human-readable type classification, exposing both the numeric identifiers used internally and the decoded labels, codes, and descriptions business users recognize.

Its principal value lies in the RULE_TYPE_LABEL column, which translates the internal DETAILED_RULE_TYPE identifier into a descriptive label drawn from CZ_DETAILEDRULETYPES_LKV. This makes the view suitable for ETRM (Enterprise Territory and Rules Management) style reporting, concurrent program extraction, and integration interfaces that must surface rule semantics without hard-coding lookup identifiers. Because it is a view rather than a table, it provides read-only, always-current access to Configurator rule metadata maintained through the Configurator workbench and developer APIs.

Underlying Base Objects

The view is defined over two documented base objects:

  • CZ_RULE_EXPRDETLS_V (VIEW) — the driving source, aliased DETLRULE, supplying the complete detailed rule record including rule identity, expression metadata, folder placement, effectivity, and audit columns.
  • CZ_DETAILEDRULETYPES_LKV (VIEW) — aliased RTYV, the lookup view that resolves DETAILED_RULE_TYPE to its code, label, and description values. It is joined with an outer (+) operator on DETLRULE.DETAILED_RULE_TYPE = RTYV.NUMERIC_ID_VALUE, so rules whose type has no matching lookup row are still returned, with null type label attributes.

Results are ordered by RULE_ID. No DML is permitted against the view; all maintenance occurs on the Configurator base tables beneath the referenced views.

Key Columns

Common Use Cases and Queries

Typical uses include extracting rule inventories for conversion or migration, validating rule types prior to deployment, and feeding integration interfaces that publish rule metadata.

Listing rules by readable type:

SELECT RULE_ID, RULE_NAME, RULE_TYPE_CODE, RULE_TYPE_LABEL
FROM   APPS.CZ_TYPED_RULES_V
ORDER  BY RULE_TYPE_LABEL, RULE_ID;

Finding active, non-seeded rules for a specific type:

SELECT RULE_ID, RULE_NAME, RULE_TEXT
FROM   APPS.CZ_TYPED_RULES_V
WHERE  RULE_TYPE_LABEL = :p_rule_type_label
AND    NVL(DISABLED_FLAG,'N') = 'N'
AND    NVL(INVALID_FLAG,'N') = 'N';

Auditing rule counts by type:

SELECT RULE_TYPE_LABEL, COUNT(*) RULE_COUNT
FROM   APPS.CZ_TYPED_RULES_V
GROUP  BY RULE_TYPE_LABEL
ORDER  BY RULE_COUNT DESC;

Because the type join is outer, queries filtering on RULE_TYPE_LABEL exclude rules lacking a lookup entry; use RULE_TYPE_LABEL IS NULL to surface those cases.