Results for “sub_nodetype_id”

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

Overview

CZ_PSNODETYPE_IMAGES_V is a Configurator (CZ) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to associate every specific type of configuration node (psnode) with the icon used to depict it in the Configurator user interface. In practical terms, the view answers the question: "For a given node type, which image file and alternate text should be rendered?"

The view is exposed as a read-only reporting and integration surface. Because Oracle Configurator stores node imagery, usage codes, and node-type relationships across several normalized tables, the view flattens that model into a denormalized projection suitable for reporting, UI metadata lookups, and downstream integrations. The search term "psnodetype_id" maps directly to the exposed column of the same name, which is aliased from the underlying entity code. This makes the view the natural entry point when a report or interface must resolve a psnodetype_id to its associated icon, name, or sub-node type.

Underlying Base Objects

The ETRM 12.2.2 metadata documents the referenced base objects as CZ_SIGNATURES (synonym), CZ_TYPE_RELATIONSHIPS (synonym), and CZ_UI_PATHED_IMAGES_V (view). The view's SQL joins these sources as follows:

• CZ_UI_PATHED_IMAGES_V (aliased IMG) supplies image usage codes, entity codes, image files, full image paths, UI definition identifiers, and deletion flags.
• CZ_TYPE_RELATIONSHIPS (aliased CNV) supplies the object type and rel_type_code, restricted to 'CNV', linking a subject type to a sub-node type.
• CZ_SIGNATURES is joined twice: as ISIG to resolve signature ID to the psnode type name, and as ATTSIG to resolve the entity code to the attach node type alternate text.

Join predicates tie ATTSIG.SIGNATURE_ID to IMG.ENTITY_CODE, ISIG.SIGNATURE_ID to CNV.OBJECT_TYPE, and IMG.ENTITY_CODE to CNV.SUBJECT_TYPE. Filter predicates require non-deleted rows on all three sources, restrict IMG.UI_DEF_ID to 0, and constrain IMG.IMAGE_USAGE_CODE to the values 10 and 11, which represent the referenced usages encoded by REFERENCED_USAGE_FLAG.

Key Columns

• PSNODETYPE_ID — The identifier of the node type, aliased from IMG.ENTITY_CODE. This is the column users most often query by when searching for "psnodetype_id".
• PSNODETYPE_NAME — The descriptive name of the node type, sourced from the CZ_SIGNATURES row matched on CNV.OBJECT_TYPE.
• IMAGE_USAGE_CODE — The usage code of the image (10 or 11), distinguishing the two referenced image roles.
• REFERENCED_USAGE_FLAG — A decoded flag derived from IMAGE_USAGE_CODE, returning '0' for code 10 and '1' for code 11.
• IMAGE_FILE and FULL_IMAGE_PATH — The image file name and its fully qualified path, used for rendering the icon.
• ALT_TEXT — Alternate text for accessibility, sourced from the ISIG (node type) signature description.
• SUB_NODETYPE_ID — The related sub-node type, aliased from CNV.OBJECT_TYPE.
• UI_DEF_ID — The UI definition identifier; the view is restricted to UI_DEF_ID = 0.
• ATTACH_NODETYPE_ALT_TEXT — Alternate text associated with the attach node type, from the ATTSIG signature description.

Common Use Cases and Queries

The view is commonly used to build icon-resolution reports, validate that every active node type has imagery, and feed external rendering engines that map psnodetype_id values to image assets. A typical lookup by node type is:

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

To identify which node types use each referenced usage role:

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

To find node types lacking an associated icon in reporting extracts:

SELECT s.signature_id AS psnodetype_id, s.name
FROM   apps.cz_signatures s
WHERE  s.deleted_flag = '0'
AND    NOT EXISTS (SELECT 1 FROM apps.cz_psnodetype_images_v v
                   WHERE v.psnodetype_id = s.signature_id);

Because the view joins three base sources and applies deletion and usage filters, queries should always run against the view rather than reconstructing the joins manually, ensuring consistent results across both 12.1.1 and 12.2.2 environments.