Results for “cz_page_element_children_v”

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

Overview

CZ_PAGE_ELEMENT_CHILDREN_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Configurator (CZ) product module. Its role is to expose the relationships between parent page elements and the child page elements that may be rendered beneath them inside a configurator user interface. In the Configurator runtime model, a "page element" (PGE) is a building block of the configuration UI, and the hierarchy of parent-to-child page elements determines which child elements are available for a given parent, in which sequence, and under which binding requirements.

The view consolidates this hierarchy by joining UI content bindings, parent/child relationship metadata, lookup-driven child element categories, and UI template definitions. The result is a single denormalized result set describing, for each parent page element, the candidate child page elements together with their labels, sequence numbers, required binding types, and the JRad tag and attribute set used to render them. Systems status in ETRM 12.2.2 is VALID, and the object is documented both for 12.1.1 and 12.2.2.

Underlying Base Objects

The documented referenced base objects are CZ_CREATEUICONTENT_LKV (VIEW), CZ_LOOKUP_VALUES_VL (VIEW), CZ_PARENT_CHILD_RELS_V (VIEW), CZ_SIGNATURES (SYNONYM), and CZ_UI_TEMPLATES (SYNONYM). The view text is built from three inline subqueries that are themselves joined:

• ENCLCAT: selects from CZ_CREATEUICONTENT_LKV and CZ_SIGNATURES, restricting to non-deleted signatures of type 'PGE'. This supplies the parent page element identifier, name, content category sequence, category label, and the required binding type identifier.
• CHLCAT: selects from CZ_PARENT_CHILD_RELS_V and CZ_LOOKUP_VALUES_VL, matching the relationship object type to the lookup numeric identifier. This yields the child page element identifier, sequence, and label.
• TPL: selects from CZ_UI_TEMPLATES, providing ROOT_REGION_TYPE as the JRad tag and JRAD_DOC as the attribute set.

The three result sets are combined using outer joins keyed on the UI content data value, the lookup list name, and the subject type, which allows parent page elements to appear even where no matching child or template row exists.

Key Columns

• PARENT_PGELEMENT_TYPE_ID / PARENT_PGELEMENT_NAME — identifier and name of the parent page element signature.
• CONTENT_CATEGORY_SEQ / CONTENT_CATEGORY_LABEL — sequence and display label of the UI content category associated with the parent.
• REQUIRED_BINDING_TYPE_ID — binding type required for the parent; resolved from the template message type, otherwise from the content binding signature.
• CAT_CHILD_ELS_AVAIL_FLAG — derived flag ('0' or '1') indicating whether child elements are available for the parent.
• CHILD_PGELEMENT_TYPE_ID / CHILD_PGELEMENT_TYPE_SEQ / CHILD_PGELEMENT_TYPE_LABEL — the child page element identifier, ordering sequence, and display label.
• CHILD_PGELEMENT_JRAD_TAG and CHILD_PGELEMENT_ATTR — the JRad root region type and JRad document used to render the child element.

Common Use Cases and Queries

Typical uses include validating that every parent page element resolves at least one child element, auditing the sequencing of child elements, and extracting the JRad rendering metadata for integration or debugging of the configurator UI.

SELECT parent_pgelement_name,
       content_category_label,
       child_pgelement_type_label,
       child_pgelement_type_seq,
       cat_child_els_avail_flag
FROM   apps.cz_page_element_children_v
WHERE  cat_child_els_avail_flag = '0'
ORDER  BY parent_pgelement_name, content_category_seq;

A second common pattern inspects the rendering a child element resolves to:

SELECT parent_pgelement_name,
       child_pgelement_type_label,
       child_pgelement_jrad_tag,
       child_pgelement_attr
FROM   apps.cz_page_element_children_v
WHERE  child_pgelement_type_id IS NOT NULL;

As with all Configurator metadata views, query access should be granted through the standard APPS reporting responsibilities, and the view should be treated as read-only.