Search Results psnodetype_id




Overview
Explore in AI Chat

Overview

APPS.CZ_PSNODETYPE_IMAGES_V is a reporting and integration view in the Oracle E-Business Suite ETRM (Enterprise Territory and Resource Management / Oracle Commerce-specific configuration) schema. It presents image metadata associated with personalization node types, joining image path records to node-type signatures and to the type relationships that define node-type conversions. The view is typically used by configuration and personalization utilities that need to resolve the icon, image, or asset bound to a given personalization node type, along with the descriptive text used as alternative (alt) text.

The view carries no data of its own; it is a read-only projection built over existing base tables and one supporting view. In Oracle EBS 12.1.1 and 12.2.2 the object is owned by APPS and is exposed to the applications schema through synonyms. It is commonly queried during setup verification, migration of personalization content, and in custom reporting or OAF-based configuration pages that render node-type imagery.

Underlying Base Objects

The ETRM metadata documents three referenced objects, each accessed via a synonym:

  • CZ_UI_PATHED_IMAGES_V (VIEW) — the driving source, aliased as IMG in the view text. It supplies the image usage code, entity code, image file, UI definition identifier, and full image path.
  • CZ_SIGNATURES (SYNONYM) — aliased twice: as ISIG to obtain the node-type name and description (alt text), and as ATTSIG to obtain the attachment node-type alternative text. The two aliases reference the same signature table through different join predicates.
  • CZ_TYPE_RELATIONSHIPS (SYNONYM) — aliased as CNV, which supplies the conversion relationship linking a subject type to an object type, thereby resolving the sub-node-type identifier.

All three are resolved through APPS synonyms in a standard EBS installation. The join architecture is deliberately restrictive: it filters to non-deleted signatures, non-deleted images, non-deleted type relationships, a single UI definition (UI_DEF_ID = 0), specific image usage codes, and a relationship type code of 'CNV'.

Key Columns

  • IMAGE_USAGE_CODE — numeric code indicating the role of the image; only values 10 and 11 qualify.
  • REFERENCED_USAGE_FLAG — a derived flag produced by DECODE: usage code 10 yields '0', usage code 11 yields '1'. This distinguishes the two qualifying image usages for consumers.
  • PSNODETYPE_ID — the entity code of the image, identifying the personalization node type.
  • PSNODETYPE_NAME — the signature name of the node type, sourced from CZ_SIGNATURES via ISIG. This is the column most frequently searched by users looking up node-type imagery.
  • IMAGE_FILE and FULL_IMAGE_PATH — the image file name and its resolved full path, used to render or reference the asset.
  • ALT_TEXT — the node-type signature description, intended as alternative text for accessibility.
  • SUB_NODETYPE_ID — the object type from CZ_TYPE_RELATIONSHIPS, identifying the related sub-node-type.
  • UI_DEF_ID — UI definition identifier, always 0 under the view's own filter.
  • ATTACH_NODETYPE_ALT_TEXT — alternative text derived from the attachment signature (ATTSIG).

Common Use Cases and Queries

Typical scenarios include auditing which node types have both referenced and unreferenced imagery, extracting image paths for content migration, and building custom OAF or BI Publisher reports that show node-type icons alongside descriptive text.

A basic listing of node types and their images:

  • SELECT psnodetype_name, psnodetype_id, image_file, full_image_path, referenced_usage_flag FROM apps.cz_psnodetype_images_v ORDER BY psnodetype_name;

Filtering by usage flag to find referenced images only:

  • SELECT psnodetype_name, image_file FROM apps.cz_psnodetype_images_v WHERE referenced_usage_flag = '1';

Looking up a specific node type by name (the typical user search pattern):

  • SELECT psnodetype_id, image_file, full_image_path, alt_text FROM apps.cz_psnodetype_images_v WHERE psnodetype_name = :name;

Because the view pre-applies deletion, relationship-type, and usage-code filters, wrapper queries remain simple and do not require re-implementing the underlying join logic. Callers should nonetheless supply a WHERE clause on PSNODETYPE_NAME or PSNODETYPE_ID where possible, as the view performs multiple joins across CZ_SIGNATURES and CZ_TYPE_RELATIONSHIPS.