Results for “property_type_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CZ_NODE_ALL_PROPERTIES_V is a Configurator (CZ) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a consolidated, denormalized listing of model node properties for Oracle Configurator, joining node-level metadata from the explanation hierarchy with the properties applicable to each node's detailed signature. The view is defined as a UNION ALL of two branches: system-defined properties (rule type sourced from CZ_SIGNATURE_SYSPROPS_V) and user-defined or item-type-derived properties, both projected onto a common column list. As a result, the view returns one row per model-node/property combination, annotated with the parent hierarchy identifiers, node type information, and property characteristics.

Because Configurator models are stored as internal PS_NODE and signature structures rather than flat relational rows, CZ_NODE_ALL_PROPERTIES_V is principally used as a read-only integration and reporting surface — for example, extracting model content for BOM/order validation analysis, populating external configuration tools, or supporting custom inquiry screens. It is not an entity used for transactional data entry.

Underlying Base Objects

The documented base objects include the following:

• CZ_EXPLNODES_WITHIMAGES_V (VIEW) — supplies the PS_NODE hierarchy: model identifier, parent node, PS_NODE_ID, node type, detailed type ID, description, and image path.
• CZ_SIGNATURE_SYSPROPS_V (VIEW) — supplies system-defined property rules, including rule type, return type, mutability, and collection flags.
• CZ_SIGNATURES (SYNONYM) and CZ_TYPES (PACKAGE) — resolve the data type of each property return value.
• CZ_TYPE_RELATIONSHIPS (SYNONYM) — restricts the join to active conversion ('CNV') relationships between detailed signatures and object types.
• CZ_PROPERTIES, CZ_ITEM_TYPE_PROPERTIES, CZ_ITEM_MASTERS (SYNONYMS) — provide the user-defined property branch matched to item master/type property definitions.
• CZ_PS_NODES, CZ_PS_PROP_VALS (SYNONYMS) — the underlying node and property-value storage used to derive the user-property branch.
• CZ_DEVELOPER_UTILS_PVT, CZ_UTILS (PACKAGE) and FND_PROFILE (PACKAGE) — Configurator utility and profile-option lookups referenced within the view logic.

All references are synonyms or views owned by APPS; the view depends on the standard CZ schema objects and inherits their validation state.

Key Columns

• MODEL_ID — identifies the Configurator model to which the node belongs.
• PS_NODE_ID, PS_NODE_TYPE, PS_NODE_NAME, PS_NODE_DESCRIPTION — the node identifier, type, display name, and descriptive text.
• PARENT_PSNODE_EXPL_ID, EFFECTIVE_PARENT_ID, MODEL_REF_EXPL_ID, DETAILED_TYPE_ID, DETAILED_TYPE_LABEL — parent hierarchy and detailed signature information for the node.
• PROPERTY_TYPE_CODE — the discriminator requested in this search: returns the system property rule type code for system-defined properties, and the literal 'PRP' for the user-defined branch. Use it to separate system properties from user/item properties.
• PROPERTY_RULE_TYPE — numeric rule type; the user-property branch returns -1.
• PROPERTY_ID, PROPERTY_NAME — the property rule identifier and its display name (system properties are suffixed with '()').
• PROPERTY_DATA_TYPE, PROPERTY_DATA_TYPE_NAME, DATA_TYPE_ID, DATA_TYPE_NAME — the return signature of the property and its associated data type.
• PROPERTY_MUTABLE_FLAG, PROPERTY_COLLECTION_FLAG — indicate whether the property can be modified and whether it returns a collection; both are hard-coded to '0' for user properties.
• PS_NODE_TYPE_IMAGE_PATH — image path for the node type icon.

Common Use Cases and Queries

The most common scenario is listing all properties for a given model or node type, filtering by property_type_code to isolate system versus user-defined properties. For example:

SELECT model_id, ps_node_name, ps_node_type,
       property_type_code, property_name, property_data_type_name
FROM   apps.cz_node_all_properties_v
WHERE  model_id = :p_model_id
  AND  property_type_code = 'PRP';

To identify mutable, single-valued system properties applicable to a node:

SELECT ps_node_id, ps_node_name, property_name
FROM   apps.cz_node_all_properties_v
WHERE  property_type_code <> 'PRP'
  AND  property_mutable_flag = '1'
  AND  property_collection_flag = '0'
ORDER BY ps_node_name, property_name;

Reporting on node hierarchies uses the parent columns to reconstruct the model tree, while data-type joins support validation checks against configuration rules. Because the view is read-only and performs a UNION ALL across many underlying tables, queries should always filter on MODEL_ID or PS_NODE_ID to avoid full scans of the Configurator model population.