Search Results cz_ps_nodes

Overview

The CZ_PS_NODES table is a core data structure within the Oracle E-Business Suite Configurator (CZ) module. It serves as the master repository for all nodes within a configurable model's project structure. Each row represents a distinct element, such as a component, feature, option, or logical item, that can be assembled into a configured product. The table is fundamental to the definition, storage, and runtime evaluation of configuration models, enabling the complex, rules-based product configurations central to Oracle's CPQ (Configure, Price, Quote) and manufacturing solutions. Its integrity is maintained through a primary key and numerous foreign key relationships that link nodes to their properties, textual descriptions, validation rules, and hierarchical parent-child structures.

Key Information Stored

The table's primary identifier is the PS_NODE_ID column. Key relational and descriptive columns include DEVL_PROJECT_ID, which links the node to its parent development project in CZ_DEVL_PROJECTS, and PARENT_ID, which self-references the table to establish the hierarchical project structure. Critical foreign key columns define the node's type and attributes: ITEM_ID links to a master item in CZ_ITEM_MASTERS, ITEM_TYPE_BACKPTR and PROPERTY_BACKPTR define the node's classification and characteristics, and INTL_TEXT_ID holds multilingual descriptive text. Functional columns such as EFFECTIVITY_SET_ID, FROM_POPULATOR_ID, and SUB_CONS_ID manage rule effectivity, data population logic, and subscription sets, respectively. The REFERENCE_ID column allows nodes to be linked across different development projects.

Common Use Cases and Queries

This table is central to technical analysis, data fixes, and reporting on the Configurator model. Common use cases include tracing the hierarchical structure of a configuration model, analyzing node usage across different projects, and diagnosing runtime configuration issues by examining specific node properties. A foundational query retrieves the node hierarchy for a given project:

• SELECT node_name, ps_node_id, parent_id FROM cz_ps_nodes WHERE devl_project_id = <project_id> CONNECT BY PRIOR ps_node_id = parent_id START WITH parent_id IS NULL;

Another typical query joins with CZ_ITEM_MASTERS to list all component nodes with their associated item numbers:

• SELECT im.item_number, pn.* FROM cz_ps_nodes pn, cz_item_masters im WHERE pn.item_id = im.item_id AND pn.devl_project_id = <project_id>;

Data integrity checks often involve verifying orphaned nodes or validating foreign key relationships, such as ensuring all ITEM_ID values have a corresponding master record.

Related Objects

The CZ_PS_NODES table has extensive relationships, as indicated by its foreign keys. It is a parent table to numerous critical Configurator entities. Key child tables include CZ_CONFIG_ITEMS and CZ_CONFIG_INPUTS for runtime configuration data, CZ_EXPRESSION_NODES for rule logic, and CZ_CONFIG_MESSAGES for validation. It is referenced by design objects like CZ_DES_CHART_CELLS and CZ_DES_CHART_FEATURES. The table also has foreign key dependencies on master data tables such as CZ_DEVL_PROJECTS, CZ_ITEM_MASTERS, CZ_INTL_TEXTS, CZ_PROPERTIES, and CZ_ITEM_TYPES. The self-referencing PARENT_ID foreign key is essential for managing the node hierarchy itself.