Search Results psn_created_by




Overview

The APPS.CZ_PSNODES_FOR_UIELEMS_CV view is a customer-facing (CV) database object within the Oracle E-Business Suite Configure-to-Order (Cto) and Oracle Configurator schema. It is owned by the APPS schema and is registered in FND Design Data under the designation CZ.CZ_PSNODES_FOR_UIELEMS_CV. The view presents configuration model node information in a flattened, UI-oriented format, exposing product structure nodes (PS nodes) together with the presentation attributes required to render user interface elements within Oracle Configurator.

Its principal role is to serve as a queryable interface over the Configurator model definition tables. Rather than requiring direct joins against multiple internal CZ tables, the view consolidates node identity, hierarchy, effectivity, instantiation behavior, and UI presentation metadata into a single relational shape. This makes it suitable for reporting on model structure, for integration routines that need to resolve node identifiers to UI elements, and for diagnostics during Configurator implementation. The presence of the PSN_CREATED_BY column, which is the term the user searched for, confirms that the view tracks the audit identity of the user who created the underlying PS node record.

Underlying Base Objects

The documented dependency list for this view includes both packages and views: CZ_DEVELOPER_UTILS_PVT (PACKAGE), CZ_EXPLNODES_WITHIMAGES_V (VIEW), CZ_PDT_2_PGE_RELS_V (VIEW), CZ_SIGNATURES (SYNONYM), CZ_TYPES (PACKAGE), CZ_TYPE_RELATIONSHIPS (SYNONYM), CZ_UTILS (PACKAGE), and DUAL (SYNONYM). The view is therefore defined over a layered set of CZ objects, typically using scalar function calls from the CZ_UTILS, CZ_TYPES, and CZ_DEVELOPER_UTILS_PVT packages to derive computed columns such as NODE_DEPTH, FULL_IMAGE_PATH, and the effective usage mask.

The two referenced views, CZ_EXPLNODES_WITHIMAGES_V and CZ_PDT_2_PGE_RELS_V, supply exploded node and page-relationship data respectively, while CZ_SIGNATURES and CZ_TYPE_RELATIONSHIPS provide the type and relationship definitions that populate the DETAILED_TYPE_ID and FEATURE_TYPE columns. Because the object is a view rather than a table, it stores no data itself; all values are derived at query time from the base Configurator model tables and the referenced package APIs.

Key Columns

Common Use Cases and Queries

Typical scenarios include auditing which user created model nodes, reporting on model structure depth, and extracting UI element metadata. A query to identify nodes created by a specific user is:

  • SELECT PS_NODE_ID, NAME, PSN_CREATED_BY, PSN_CREATION_DATE FROM APPS.CZ_PSNODES_FOR_UIELEMS_CV WHERE PSN_CREATED_BY = :user_id;
  • SELECT PS_NODE_ID, NAME, NODE_DEPTH, INSTANTIABLE_FLAG FROM APPS.CZ_PSNODES_FOR_UIELEMS_CV WHERE NODE_DEPTH <= 3 ORDER BY TREE_SEQ;
  • SELECT PS_NODE_ID, FULL_IMAGE_PATH, ALT_TEXT FROM APPS.CZ_PSNODES_FOR_UIELEMS_CV WHERE UI_OMIT = 'N' AND P_PAGE_ELEMENT_TYPE IS NOT NULL;

Because the view references packaged API functions, query performance is best when filters on PS_NODE_ID or PARENT_ID are applied. The view is read-only and should be treated as a reporting and integration surface rather than a data maintenance object.