Search Results ui_section




Overview
Explore in AI Chat

Overview

CZ_COMPATCELL_NODE_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2, delivered as part of the Oracle Configurator (CZ) product family. The view joins the compatibility rule repository to the configuration model node repository, presenting one row per active compatibility cell linked to its corresponding secondary option node. It exposes metadata about the rule (rule identifier, primary and secondary option references, and the cell marking character) alongside the full descriptive attribute set of the affected model node, including node type, feature type, BOM treatment, effectivity attributes, and quantity constraints. Because Configurator stores model structure and rule definitions across several normalized tables, this view serves as a denormalized access point for technical consultants building reports, conversion scripts, and integration extracts that must reason about which model nodes participate in compatibility relationships. The view filters both underlying sources on DELETED_FLAG = '0', so consumers see only logically active rows without needing to encode soft-delete predicates themselves.

Underlying Base Objects

The view text references two base objects, both documented in ETRM 12.2.2 as synonyms resolvable to the underlying CZ tables: CZ_DES_CHART_CELLS and CZ_PS_NODES. CZ_DES_CHART_CELLS (aliased DCL in the view text) is the design chart cell table that stores individual compatibility rule cells, keyed by RULE_ID and identifying the primary and secondary options that participate in the rule. CZ_PS_NODES (aliased PSN) is the configuration model node table, holding the runtime representation of model nodes, their hierarchy through PARENT_ID, and attributes governing BOM explosion, optionality, and UI presentation. The join condition is DCL.SECONDARY_OPT_ID = PSN.PS_NODE_ID, meaning each row couples a compatibility cell with the node that acts as its secondary (dependent) option. No outer joins are present, so cells whose secondary option node is missing or deleted do not appear in the result set. Both tables participate in the Configurator run-time and design-time data model, and the view should be treated as read-only reference data.

Key Columns

The projection divides broadly into compatibility rule columns and node columns. Rule-side columns include RULE_ID, PRIMARY_OPT_ID, SECONDARY_OPT_ID, MARK_CHAR, DELETED_FLAG, SECONDARY_FEAT_EXPL_ID, and SECONDARY_FEATURE_ID, which together identify the rule and the feature explosion context of the dependent option. Node-side columns include PS_NODE_ID (the join key), PARENT_ID, PS_NODE_TYPE, FEATURE_TYPE, NAME, ITEM_ID, ITEM_TYPE_BACKPTR, and SUB_CONS_ID, which describe the node's identity and placement in the model. Optionality and validation semantics are carried by MINIMUM, MAXIMUM, MINIMUM_SELECTED, MAXIMUM_SELECTED, and COUNTED_OPTIONS_FLAG. BOM-related behavior is expressed through COMPONENT_SEQUENCE_ID, COMPONENT_SEQUENCE_PATH, BOM_TREATMENT, BOM_REQUIRED_FLAG, and BOM_SORT_ORDER; the component_sequence_path value is of particular interest to consultants tracing how a configured option maps onto an Oracle Bills of Material component sequence. Effectivity is governed by EFFECTIVE_FROM, EFFECTIVE_UNTIL, EFFECTIVITY_SET_ID, and EFFECTIVE_USAGE_MASK. Tenancy and extensibility are supported by the USER_NUM01–04 and USER_STR01–04 attribute columns.

Common Use Cases and Queries

Typical usage includes auditing compatibility rules against model structure, extracting the component sequence path for a configured node, and diagnosing why an option behaves as required or excluded. The following query lists active rules with the name and BOM sequence path of the dependent node:

  • SELECT RULE_ID, PRIMARY_OPT_ID, SECONDARY_OPT_ID, MARK_CHAR, PS_NODE_ID, NAME, COMPONENT_SEQUENCE_ID, COMPONENT_SEQUENCE_PATH FROM APPS.CZ_COMPATCELL_NODE_V ORDER BY RULE_ID;
  • Filtering by rule: SELECT PS_NODE_ID, NAME, BOM_TREATMENT FROM APPS.CZ_COMPATCELL_NODE_V WHERE RULE_ID = :rule_id;
  • Locating nodes with a populated BOM sequence path: SELECT PS_NODE_ID, NAME, COMPONENT_SEQUENCE_PATH FROM APPS.CZ_COMPATCELL_NODE_V WHERE COMPONENT_SEQUENCE_PATH IS NOT NULL;

Because the view performs no aggregation, it can be joined directly to other CZ model objects on PS_NODE_ID or to BOM tables through COMPONENT_SEQUENCE_ID.