Search Results system_node_flag




Overview
Explore in AI Chat

Overview

In Oracle EBS 12.1.1 and 12.2.2, CZ_RUL_TYPEDPSN_V is an APPS-owned database view that exposes the node structure of the Oracle Configurator (CZ) model graph, filtered by node type. The view is defined over the CZ_PS_NODES base object and the CZ_TYPES package, and is intended to present the set of property and structure nodes (option classes, options, features) that make up a configuration model as a flat, queryable result set. It is primarily used by Configurator runtime logic and by extension code that needs to traverse model hierarchies without re-implementing the underlying recursion. Because Configurator metadata is version- and effectivity-driven, the view is one of the canonical read surfaces for model node data.

Underlying Base Objects

The ETRM metadata documents two referenced base objects: CZ_PS_NODES (SYNONYM) and CZ_TYPES (PACKAGE). CZ_PS_NODES is the persistent repository of all model structure nodes — each row is one node in the configuration model, linked to its parent via PARENT_ID. CZ_PS_NODES is exposed publicly in APPS as a synonym over the underlying CZ schema table. CZ_TYPES (PACKAGE) carries the PL/SQL type definitions and constants that the view text relies on to interpret node types, feature types, and flags. The view text enumerates the complete CZ_PS_NODES column list, meaning the view does not add computed columns; its filtering logic is applied via the node type typification supplied by CZ_TYPES.

Key Columns

Common Use Cases and Queries

The view is typically queried to report on model structure, to audit cardinality rules such as maximum selections, or to drive integration extracts into order management and BOM. A representative query isolating nodes with a maximum selection constraint is:

SELECT PS_NODE_ID, NAME, MAXIMUM, MAXIMUM_SELECTED, MINIMUM, MINIMUM_SELECTED FROM APPS.CZ_RUL_TYPEDPSN_V WHERE MAXIMUM_SELECTED IS NOT NULL AND DELETED_FLAG = 'N' ORDER BY TREE_SEQ;

To walk a single model hierarchy, filter by DEV_PROJECT_ID and order by TREE_SEQ so parent/child ordering is preserved:

SELECT LPAD(' ', 2 * LEVEL) || NAME AS INDENTED_NAME, PS_NODE_TYPE, FEATURE_TYPE, MAXIMUM_SELECTED, MINIMUM_SELECTED FROM APPS.CZ_RUL_TYPEDPSN_V START WITH PARENT_ID IS NULL AND DEVL_PROJECT_ID = :P_PROJECT CONNECT BY PRIOR PS_NODE_ID = PARENT_ID AND DEV_PROJECT_ID = :P_PROJECT ORDER SIBLINGS BY TREE_SEQ;

Because the view inherits the CZ_PS_NODES effectivity columns, queries intended for active configurations should additionally restrict on EFF_FROM/EFF_TO or EFFECTIVE_FROM/EFFECTIVE_UNTIL. Reporting extracts should also honor SECURITY_MASK and EFF_MASK where row-level security is enabled.