Search Results page_element_type

Overview

APPS.CZ_PDT_2_PGE_RELS_V is a database view in the Oracle E-Business Suite (EBS) environment, resident in the APPS schema. Its purpose is to expose a filtered, renamed projection of a subset of rows from the configuration-type relationship repository. Specifically, the view isolates relationships whose relationship type code is N2E and whose DELETED_FLAG equals '0', thereby returning only active, non-deleted associations. The view is part of the ETRM (Enterprise Taxonomy / configuration relationship) layer that underpins Oracle's application configuration and setup data model, and it participates in the broader pattern of "date-effective" or "relationship" views used throughout EBS for reporting and integration purposes. Rather than presenting the full relationship set, CZ_PDT_2_PGE_RELS_V deliberately narrows the scope to one relationship code and applies column aliasing that renames the generic SUBJECT_TYPE and OBJECT_TYPE attributes into domain-specific identifiers, DETAILED_TYPE_ID and PAGE_ELEMENT_TYPE. This naming helps downstream consumers in reports, extracts, and integration interfaces reason about the data in terms of product-detail types and page-element types, rather than generic relationship endpoints.

Underlying Base Objects

The view is defined over a single base object: the synonym CZ_TYPE_RELATIONSHIPS, which resolves to the underlying relationship table maintained by the ETRM configuration framework. The base table stores pairwise associations between configuration entity types; each row carries a relationship type code (REL_TYPE_CODE), a subject type, an object type, and status flags such as DELETED_FLAG and SEEDED_FLAG. The view applies two predicates to the base object. First, REL_TYPE_CODE = 'N2E' restricts the result to relationships of the N2E variety, which in the documented ETRM model maps a detailed product-detail type ("N") to a page-element type ("E"). Second, DELETED_FLAG = '0' suppresses logically deleted records, ensuring the view presents only active relationships. Because the view is a simple single-table projection with no joins, it inherits the physical storage, indexes, and performance characteristics of CZ_TYPE_RELATIONSHIPS, and any index on REL_TYPE_CODE or DELETED_FLAG will be leveraged by queries against it.

Key Columns

• DETAILED_TYPE_ID — aliased from SUBJECT_TYPE; identifies the detailed (product-detail) type participating in the relationship. This is the column most directly relevant to the search term "detailed_type_id," and it corresponds to the subject side of the N2E association.
• PAGE_ELEMENT_TYPE — aliased from OBJECT_TYPE; identifies the page-element type that the detailed type is associated with.
• DELETED_FLAG — status indicator inherited from the base table; constrained to '0' in this view, so the column is constant for all returned rows.
• SEEDED_FLAG — indicates whether the relationship was seeded as part of the application's delivered configuration (Y) or created by customers during implementation/extensions (N). This flag is valuable for distinguishing Oracle-delivered metadata from customer-defined records.

Common Use Cases and Queries

This view is typically used to enumerate the active detailed-type-to-page-element relationships, for example when auditing configuration, building reference data for extensions, or driving conditional logic in custom forms and concurrent programs. A basic query returns the full active set:

• SELECT detailed_type_id, page_element_type, seeded_flag FROM apps.cz_pdt_2_pge_rels_v ORDER BY detailed_type_id;
• SELECT detailed_type_id, page_element_type FROM apps.cz_pdt_2_pge_rels_v WHERE seeded_flag = 'Y'; — isolates Oracle-seeded relationships.
• SELECT page_element_type FROM apps.cz_pdt_2_pge_rels_v WHERE detailed_type_id = :detail_id; — retrieves the page elements associated with a specific detailed type, a frequent lookup pattern in custom integrations.

Because the view already enforces the N2E and non-deleted filters, callers need not repeat those predicates, simplifying report and interface logic in both EBS 12.1.1 and 12.2.2.