Results for “ui_struct_code”

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

Overview

The CZ_PSNODE_REFUI_IMAGES_V view is a reporting and integration object within the Oracle E-Business Suite Configurator (CZ) module. It resides in the APPS schema and holds a VALID status in both Oracle EBS 12.1.1 and 12.2.2. The view consolidates node-level user interface reference data with the associated UI element images, producing a denormalized result set that links a Configurator model's page structure elements to the images rendered for those elements.

In the Configurator runtime and design-time model, page structures (PS nodes) drive the presentation of configurable items. Each UI element within a page structure can be associated with one or more images through a signature-based relationship. This view surfaces that relationship in a single queryable object, making it suitable for reporting, troubleshooting, and integration scenarios where the image metadata must be correlated with the node and page structure hierarchy. Because the view joins two pre-built view objects rather than base tables, it abstracts the underlying complexity of the Configurator data model.

Underlying Base Objects

Per the documented ETRM metadata, CZ_PSNODE_REFUI_IMAGES_V is defined over exactly two referenced base objects, both of which are themselves views:

• CZ_PSNODE_WITH_UIREFS_V — alias NDUI. Supplies the Configurator node and UI reference information, including model, node, page, element, and structure signature attributes.
• CZ_UIELEMENT_IMAGES_V — alias UIMG. Supplies the image-related attributes for UI elements, including image usage, file, and path information.

The join condition is NDUI.STRUCT_SIGNATURE_ID = UIMG.ELEMENT_SIGNATURE_ID. This means the view links each node UI reference to its matching UI element images through the element signature identifier rather than through a direct foreign key on element ID. The relationship is therefore signature-driven, and the cardinality of the result depends on how many image records share a given element signature.

Key Columns

The view exposes twenty-two columns. The principal identifiers and structural columns are:

• MODEL_ID — identifies the Configurator model to which the node belongs.
• PS_NODE_ID, PARENT_ID, PERSISTENT_NODE_ID — define the page structure node, its parent, and its persistent node reference.
• PS_NODE_TYPE — the type of page structure node.
• NAME — the node name.
• UI_DEF_ID, PAGE_ID, ELEMENT_ID, PARENT_ELEMENT_ID — UI definition, page, and element identifiers, including the parent element for hierarchy reconstruction.
• PAGE_STRUCTURE_NAME, STRUCT_SIGNATURE_ID, ELEMENT_TYPE, UI_STRUCT_CODE, UI_DEF_NAME, UI_STYLE — structural and presentation attributes of the page and element.
• IMAGE_USAGE_CODE, ELEMENT_SIGNATURE_ID, IMAGE_FILE, ELEMENT_TYPE_NAME, ALT_TEXT, FULL_IMAGE_PATH — image-specific attributes, providing the usage context, the file reference, accessibility text, and the fully qualified image path.

ELEMENT_SIGNATURE_ID is the join key column that carries the linkage between the two base views, and STRUCT_SIGNATURE_ID from the NDUI side matches it.

Common Use Cases and Queries

Typical scenarios include auditing which images are attached to a given model's page structure, verifying image file paths and alt text for accessibility compliance, and troubleshooting missing or misapplied images during configuration runtime. A representative query filtering by model is shown below:

• SELECT MODEL_ID, PS_NODE_ID, NAME, ELEMENT_ID, IMAGE_USAGE_CODE, IMAGE_FILE, FULL_IMAGE_PATH, ALT_TEXT FROM APPS.CZ_PSNODE_REFUI_IMAGES_V WHERE MODEL_ID = :p_model_id;
• SELECT PAGE_STRUCTURE_NAME, UI_DEF_NAME, ELEMENT_TYPE, IMAGE_FILE FROM APPS.CZ_PSNODE_REFUI_IMAGES_V WHERE FULL_IMAGE_PATH IS NULL OR IMAGE_FILE IS NULL; (identify elements lacking a resolved image)
• SELECT ELEMENT_SIGNATURE_ID, COUNT(*) FROM APPS.CZ_PSNODE_REFUI_IMAGES_V GROUP BY ELEMENT_SIGNATURE_ID HAVING COUNT(*) > 1; (detect multiple images per element signature)

Because the view is read-only and defined over other views, it is safe for ad hoc reporting but should be queried with appropriate filters to avoid full scans of the underlying Configurator structures.