Search Results cz_rule_exprdetls_v




Overview
Explore in AI Chat

Overview

CZ_RULE_EXPRDETLS_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the CZ (Configurator) product. Its status is VALID in both the 12.1.1 and 12.2.2 releases. The view does not store data; it projects a denormalized result set derived from the configurator rule repository. Its principal purpose is to expose rule headers together with the root node of their associated expression trees, so that callers can identify each rule, determine its effective presentation type, and locate the expression root from which the rule's logic is evaluated.

The view joins the rule master table to a filtered subset of the expression-nodes table. That subset returns only nodes whose parent identifier is null, whose expression type is not 208, and whose deleted flag is '0'. In other words, it returns only the top-level expression node of each rule. This makes the view suitable for reporting, integration, and troubleshooting where a compact rule-plus-root-expression listing is required without traversing the full node hierarchy. It is also frequently used as a lookup during rule migration and comparison, since the root template identifier is exposed directly as a column rather than requiring a separate query against CZ_EXPRESSION_NODES.

Underlying Base Objects

The view is defined over two synonyms that resolve to configurator base tables: CZ_RULES and CZ_EXPRESSION_NODES. CZ_RULES supplies the rule header attributes, while CZ_EXPRESSION_NODES supplies the root expression node. The join is an outer join driven from CZ_RULES, so every non-deleted rule is returned even when no matching root expression row is found. The three join predicates are RULE_TYPE, RULE_ID, and PRESENTATION_FLAG, all outer-joined from the expression subquery side. A filter of RUL.DELETED_FLAG = '0' restricts the result to active records.

The join to the root-node subquery carries an internal selection of 200 for RULE_TYPE and 1 for PRESENTATION_FLAG, indicating that this view targets template-based (presentation) rules rather than other rule categories. Because the subquery excludes expression type 208, table or reference style nodes are not treated as roots.

Key Columns

Common Use Cases and Queries

A frequent requirement is to list all active rules together with the template at the root of their expression tree. The following query returns that relationship:

  • SELECT rule_id, rule_name, detailed_rule_type, expr_root_rule_template_id FROM cz_rule_exprdetls_v ORDER BY rule_name;

To isolate rules that have no root expression node — often an indicator of incomplete or corrupted rule definitions — the integration or support analyst filters on the outer-joined template column:

  • SELECT rule_id, rule_name, rule_type FROM cz_rule_exprdetls_v WHERE expr_root_rule_template_id IS NULL;

Where a rule repository must be audited by folder or project, the folder and project columns support grouping and reconciliation:

  • SELECT rule_folder_id, COUNT(*) FROM cz_rule_exprdetls_v GROUP BY rule_folder_id;
  • SELECT rule_id, rule_name, seq_nbr FROM cz_rule_exprdetls_v WHERE devl_project_id = :project_id ORDER BY rule_folder_id, seq_nbr;

Because RULE_TEXT and NOTES are deliberately blank, the view should not be used to retrieve rule body text or documentation. For the full expression hierarchy, callers must query CZ_EXPRESSION_NODES directly using the returned EXPR_NODE_ID. For rule bodies or comments, alternate views and the base CZ_RULES table are required. All access should be granted through the APPS schema, consistent with standard EBS view security conventions.