Search Results expr_feat_prop

Overview

APPS.CZ_RULE_EXPRESSION_V is a reporting and diagnostic view within the Oracle E-Business Suite (EBS) configuration and rules engine, typically associated with Oracle Configurator / ETRM (Enterprise Trade and Rule Management) style rule storage. The view exposes a flattened, human-readable representation of the expression nodes that comprise rule definitions stored in the CZ_RULES and CZ_EXPRESSION_NODES structures. Its primary purpose is to translate the terse numeric codes used internally to represent rule types, expression types, punctuation, and node references into descriptive text (such as "Explicit Compatibility", "Expression Rule", "EXPR_FIELD_NAME", or "PSN: 1234: Name").

Because the underlying expression data is stored in a normalized, encoded form, this view is used by technical consultants and report developers who need to inspect, troubleshoot, or extract rule and expression logic without manually joining dozens of lookup tables. It plays a role in both on-premise EBS 12.1.1 and 12.2.2 environments wherever rule-expression diagnostics, migration validation, or audit reporting is required.

Underlying Base Objects

The view is defined over the following base objects, all accessed through APPS synonyms:

• CZ_RULES — the master rule header table (RULE_ID, NAME, RULE_TYPE, RULE_FOLDER_TYPE).
• CZ_EXPRESSION_NODES — the core table storing each expression node, including EXPR_NODE_ID, EXPR_PARENT_ID, EXPR_TYPE, PS_NODE_ID, PROPERTY_ID, FIELD_NAME, DATA_VALUE, and TEMPLATE_ID.
• CZ_PS_NODES — the product/structure node table, joined to resolve PS_NODE_ID values into descriptive node names.
• CZ_PROPERTIES — resolves PROPERTY_ID into a descriptive property name.
• CZ_EXNEXPRTYPE_LKV — the lookup view mapping expression type codes to their meaning.
• CZ_CREATERULEOBJECT_LKV — a supporting lookup view used in rule-object relationship resolution.

The view performs correlated sub-queries against CZ_RULES, CZ_PS_NODES, and CZ_PROPERTIES to produce readable descriptions, so it functions essentially as a decoding layer over the raw expression metadata.

Key Columns

• RULE_ID / RULE_NAME — identifier and user-assigned name of the parent rule.
• RULE_TYPE / RULE_TYPE_DESC — the numeric rule type code and its decoded description (e.g., 200 = "Expression Rule", 500 = "System Property").
• EXPR_NODE_ID / EXPR_PARENT_ID — the node's own identifier and its parent, enabling hierarchical reconstruction of an expression tree.
• EXPR_TYPE — the encoded node type (e.g., 205 = PS node, 207 = property, 208 = punctuation).
• PS_NODE_ID — the product structure node referenced by the expression; the view decodes this into a "PSN: <id>: <name>" string. This is the column most commonly searched by users searching for "ps_node_id".
• PROPERTY_ID / FIELD_NAME / DATA_VALUE — supporting attributes used to resolve property names, field references, and literal values.

Common Use Cases and Queries

Typical uses include identifying which rules reference a specific product structure node, auditing expression structure, and validating rule migration between environments.

• Find rules referencing a given PS node:

  SELECT rule_id, rule_name, expr_node_id, ps_node_id
  FROM   apps.cz_rule_expression_v
  WHERE  ps_node_id = :p_node_id;

• List decoded expression nodes for one rule, in tree order:

  SELECT expr_node_id, expr_parent_id, expr_type,
         rule_type_desc, ps_node_id
  FROM   apps.cz_rule_expression_v
  WHERE  rule_id = :p_rule_id
  ORDER  BY expr_parent_id, expr_node_id;

• Report only expression rules and their node references:

  SELECT rule_id, rule_name, expr_node_id, ps_node_id
  FROM   apps.cz_rule_expression_v
  WHERE  rule_type = 200;

These queries allow consultants to trace rule logic back to specific product structure nodes and properties, making the view an essential diagnostic asset for rule troubleshooting and reporting in Oracle EBS.