Results for “deleted_flag”

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

Overview

CZ_PDT_2_PGE_RELS_V is a database view owned by the APPS schema in Oracle E-Business Suite, classified under the CZ (Configurator) product family. It exposes a curated, filtered slice of the Configurator's type relationship model, specifically the relationships that govern how product or subject types map to page elements within the Configurator user interface. The view is registered as a VALID object in both Oracle EBS 12.1.1 and 12.2.2, and its definition is identical across releases because it depends solely on the CZ_TYPE_RELATIONSHIPS base table via a synonym.

Functionally, the view answers a narrow but recurring question: which detailed type identifiers are currently linked to which page element types, excluding any records that have been logically deleted. The name itself encodes this intent — "PDT to PGE" denotes Product/Detailed Type to Page Element relationships. In reporting and integration scenarios, the view presents a simplified projection that removes soft-deleted rows and restricts the relationship category to 'N2E', sparing consumers from repeatedly restating those filter conditions.

Underlying Base Objects

The view is defined over a single documented base object: CZ_TYPE_RELATIONSHIPS, accessed through a synonym in the APPS schema. The complete view text is:

• SELECT SUBJECT_TYPE DETAILED_TYPE_ID, OBJECT_TYPE PAGE_ELEMENT_TYPE, DELETED_FLAG, SEEDED_FLAG
• FROM CZ_TYPE_RELATIONSHIPS
• WHERE REL_TYPE_CODE = 'N2E' AND DELETED_FLAG = '0'

Two predicate conditions shape the result set. The REL_TYPE_CODE filter of 'N2E' isolates one specific relationship category from the broader relationship taxonomy maintained in CZ_TYPE_RELATIONSHIPS, while the DELETED_FLAG = '0' clause suppresses logically deleted entries. The underlying table stores the full relationship graph used by Oracle Configurator, and this view projects only the columns and rows relevant to the page element mapping concern. Because the definition references a synonym rather than the table directly, the same view text resolves consistently in both 12.1.1 and 12.2.2 environments.

Key Columns

The view exposes four columns, two of which are renamed from their base table equivalents to reflect the reporting context:

• DETAILED_TYPE_ID — aliases SUBJECT_TYPE from the base table. Identifies the source type in the relationship, representing the detailed product or subject type participating in the mapping.
• PAGE_ELEMENT_TYPE — aliases OBJECT_TYPE. Identifies the target page element type that the subject type is related to, defining the UI construct onto which the type is projected.
• DELETED_FLAG — retained for completeness, but always evaluates to '0' in this view because the WHERE clause already excludes deleted rows. It remains useful for downstream joins or for symmetry with the base table.
• SEEDED_FLAG — indicates whether the relationship was delivered as seed data by Oracle or created by a customer or implementation. This distinction is valuable when determining whether a mapping is upgradeable and supportable.

Common Use Cases and Queries

Typical usage centers on inspection and troubleshooting of Configurator page element mappings. The view is convenient for identifying which page element types are attached to a given detailed type, and for separating Oracle-seeded relationships from customer-defined ones. A representative query lists all mappings with their seeding status:

• SELECT detailed_type_id, page_element_type, seeded_flag FROM cz_pdt_2_pge_rels_v;

To isolate customer-defined relationships, add a filter on the seeded flag:

• SELECT detailed_type_id, page_element_type FROM cz_pdt_2_pge_rels_v WHERE seeded_flag = 'N';

Because the view is a thin projection over CZ_TYPE_RELATIONSHIPS, it introduces no aggregation or transformation overhead and can be joined directly to other Configurator metadata views when tracing the full model from type definition through to page element presentation. It is most useful during implementation validation, regression testing after patches, and diagnostic analysis of unexpected Configurator UI behaviour.