Results for “ui_struct_code”

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

Overview

CZ_PSNODE_WITH_UIREFS_V is an APPS-owned reporting and integration view within the Oracle E-Business Suite Configurator (CZ) product family. It presents a denormalized, query-ready projection that correlates Configurator persistent nodes (PS nodes) with the user-interface reference structures that drive model configuration pages and elements. In effect, the view answers the question: for a given model node in a Configurator development project, which UI definition, page, and page element reference that node, and where does that element sit within the UI hierarchy?

The object resides in the APPS schema and carries a VALID status in ETRM 12.2.2 metadata. Because it is a view rather than a table, it enforces no independent storage and inherits the read-consistency characteristics of its base objects. It is used principally for reporting on Configurator model internals, for diagnosing mismatches between model structure and runtime UI presentation, and as a convenient join point for custom extensions that must relate a node identifier to a UI element without replicating the underlying three-way joins.

Underlying Base Objects

The view is defined over four referenced base objects, all exposed through APPS synonyms: CZ_PS_NODES, CZ_UI_DEFS, CZ_UI_PAGES, and CZ_UI_PAGE_ELEMENTS. Internally, the view text composes an inline subquery (aliased UIREF2ND) that unions UI pages with UI page elements, joining both to CZ_UI_DEFS to obtain the owning development project (MODEL_ID) and the UI definition name and style. The outer query then joins this UI structure set to CZ_PS_NODES on PERSISTENT_NODE_ID and, critically, on the development project identifier, ensuring the UI references and the PS node belong to the same model.

The view applies deleted-flag filtering at every level: CZ_PS_NODES.DELETED_FLAG = '0', CZ_UI_DEFS.DELETED_FLAG = '0', CZ_UI_PAGES.DELETED_FLAG = '0', and CZ_UI_PAGE_ELEMENTS.DELETED_FLAG = '0'. Soft-deleted model nodes, UI definitions, pages, and elements are therefore excluded from all results.

Key Columns

• MODEL_ID — The development project identifier (DEVL_PROJECT_ID) of the Configurator model to which the node and UI reference belong.
• PS_NODE_ID / PARENT_ID / PERSISTENT_NODE_ID — The node identifier, its hierarchical parent within the model, and the persistent node key used to correlate the model node with UI structures.
• PS_NODE_TYPE — The classification of the model node, distinguishing model, component, and atomic node roles.
• NAME — The name of the persistent node as stored in CZ_PS_NODES.
• UI_DEF_ID — The UI definition to which the page or element belongs.
• PAGE_ID — The identifier of the UI page containing the referenced structure item.
• ELEMENT_ID / PARENT_ELEMENT_ID — The page element identifier and the identifier of its parent element, enabling reconstruction of the UI element hierarchy. For page-level rows these are NULL, and for element-level rows PARENT_ELEMENT_ID points to the containing element.
• PAGE_STRUCTURE_NAME — The name of the page or page element, depending on the row type.
• STRUCT_SIGNATURE_ID — The structure signature. Page-level rows use the constant 6044, while element rows use the element's own signature identifier.
• ELEMENT_TYPE / UI_STRUCT_CODE — The element type and a discriminator code; the code is 'PAG' for page-level rows and 'PGE' for page-element rows.
• UI_DEF_NAME / UI_STYLE — The UI definition name and the styling attribute drawn from CZ_UI_DEFS.

Common Use Cases and Queries

A typical use is locating all UI elements that reference a particular node within a model, which supports impact analysis before modifying model structure. The query below returns the UI hierarchy for a given persistent node:

SELECT model_id, ps_node_id, name, ui_struct_code, page_structure_name, element_id, parent_element_id FROM cz_psnode_with_uirefs_v WHERE persistent_node_id = :node_id ORDER BY ui_struct_code, page_id, element_id;

Because the view surfaces PARENT_ELEMENT_ID, it also supports recursive traversal of the UI element tree for a page:

SELECT element_id, parent_element_id, page_structure_name, element_type FROM cz_psnode_with_uirefs_v WHERE model_id = :model_id AND page_id = :page_id AND ui_struct_code = 'PGE' ORDER BY parent_element_id, element_id;

Finally, the PAG versus PGE discriminator allows page-level inventory reporting, for example listing every page per model alongside its element count, which is useful when validating that each persistent node carries the expected UI coverage before a deployment or migration cycle.