Search Results property_orig_sys_ref




Overview
Explore in AI Chat

Overview

APPS.CZ_PSNODE_DIRECTPROP_INFO_V is a reporting and integration view within the Oracle E-Business Suite (EBS) product configuration and rules engine schema, historically associated with Oracle Configurator and its ETRM (Enterprise Transaction and Rules Management) lineage. It exposes the property values assigned directly to a Product Structure Node (PS node), together with the descriptive metadata required to render those properties in a user interface: data types, translated display text, default values, attached property flags, originating system references, and associated seeded imagery.

The view is a denormalized projection rather than a base storage object. It joins property-value rows from CZ_PSNODE_PROPVAL_V to image and lookup metadata so that a single query returns both the semantic content of a node property and the presentation attributes associated with the PRP ("Property") object type. The name searched by the user, PROP_ATTACHES, is a column carried by CZ_PSNODE_PROPVAL_V that indicates whether a property has attached documents, media, or supplementary records. Because the view selects this column, queries against CZ_PSNODE_DIRECTPROP_INFO_V are frequently used to identify nodes whose properties carry attachments — for example, during migration validation, attachment auditing, or UI configuration review.

Underlying Base Objects

The view is documented as being defined over four referenced base objects:

The supplementary metadata confirms CZ_RPOBJECTTYPES_LKV as a view object type and lists CZ_UI_PATHED_IMAGES_V as a view, while CZ_INTL_TEXTS is presented as a synonym. The inner join to CZ_RPOBJECTTYPES_LKV and CZ_UI_PATHED_IMAGES_V means a row is only returned when a matching seeded PRP image record exists, which is an important behavioral constraint when reporting on large property sets.

Key Columns

Common Use Cases and Queries

Typical scenarios include auditing which node properties carry attachments, reviewing UI rendering metadata for properties, validating multilingual defaults, and reconciling properties by originating system reference.

Listing properties with attachments for a given node:

SELECT ps_node_name, property_name, data_type, prop_attaches
FROM   apps.cz_psnode_directprop_info_v
WHERE  prop_attaches IS NOT NULL
AND    ps_node_id = :p_node_id;

Retrieving translated display text and default values for multilingual properties:

SELECT property_name, property_value, translated_text,
       default_value, def_translated_text
FROM   apps.cz_psnode_directprop_info_v
WHERE  data_type = 8
AND    ps_node_id = :p_node_id;

Inventory by originating system for integration checks:

SELECT orig_sys_ref, value_orig_sys_ref, property_orig_sys_ref,
       COUNT(*) rows_count
FROM   apps.cz_psnode_directprop_info_v
WHERE  src_application_id = :p_app_id
GROUP  BY orig_sys_ref, value_orig_sys_ref, property_orig_sys_ref;

Because the view is not indexed independently, performance-sensitive queries should constrain on PS_NODE_ID, PROPERTY_ID, or ITEM_ID, and the mandatory seeded-image join must be considered when counting properties expected to lack imagery.