Search Results cz_rule_expression_v




Overview
Explore in AI Chat

Overview

CZ_RULE_EXPRESSION_V is a read-only reporting view owned by the APPS schema in Oracle E-Business Suite, belonging to the CZ – Configurator product family. It presents decoded, human-readable representations of the expression trees that back Configurator rules. Rather than exposing the raw numeric identifiers stored in the underlying expression node tables, the view resolves rule type codes, expression type codes, punctuation subtypes, and node references into descriptive text, making the internal rule model accessible to reporting tools, diagnostics, and integration extracts.

The view is particularly significant for anyone investigating the PS_NODE_ID column. Because expression nodes can reference product structure nodes, the view surfaces PS_NODE_ID in several expression type branches and joins to CZ_PS_NODES to return a readable label of the form PSN: <id>: <name>. This makes CZ_RULE_EXPRESSION_V the natural starting point for tracing which product structure nodes participate in a given Configurator rule expression.

Underlying Base Objects

ETRM metadata documents the following referenced base objects:

  • CZ_RULES – the master rule header table, providing the rule name and rule type.
  • CZ_EXPRESSION_NODES – the core table holding the individual expression tree nodes.
  • CZ_PS_NODES – the product structure node table used to resolve PS_NODE_ID into a node name.
  • CZ_PROPERTIES – the property definitions referenced by property expression nodes.
  • CZ_CREATERULEOBJECT_LKV and CZ_EXNEXPRTYPE_LKV – lookup views supplying code/meaning pairs used in the decoding logic.

The view is a denormalised join over these objects. The driving table is CZ_EXPRESSION_NODES (aliased EXN), left-joined conceptually to CZ_RULES (aliased RUL) for the rule header, with scalar subqueries against CZ_PS_NODES, CZ_PROPERTIES, and CZ_RULES providing the descriptive values in the SELECT list. Because it is defined purely as a query, it holds no data of its own and inherits the privileges and synonyms of the APPS schema in which it resides.

Key Columns

Common Use Cases and Queries

The most frequent use case is auditing which product structure nodes appear in rule expressions. A representative query is:

SELECT rule_name, expr_node_id, expr_parent_id, expr_type, ps_node_id
FROM   apps.cz_rule_expression_v
WHERE  ps_node_id IS NOT NULL
AND    rule_id = :p_rule_id
ORDER  BY expr_parent_id, expr_node_id;

A second scenario extracts a decoded inventory of expression types for documentation or migration analysis:

SELECT expr_type, ps_node_id
FROM   apps.cz_rule_expression_v
WHERE  rule_type IN (200, 900)
ORDER  BY rule_name, expr_node_id;

Because the view is exposed in the APPS schema and references only synonyms and lookup views, it is safe for read-only operational reporting. It should not be used for updates, and its decoded text output makes it unsuitable for high-volume batch processing where the raw CZ_EXPRESSION_NODES table would be more efficient.