Results for “qa_pc_element_relationship”

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

Overview

The QA_PC_ELEMENT_RELATIONSHIP table is a Quality (QA) module data object within the Oracle E-Business Suite 12.1.1 and 12.2.2 environments. It stores the relationships between parent and child plan elements, thereby defining the hierarchical or associative structure that connects individual collection elements within a quality collection plan framework. Its documented owner is the QA schema, where it is maintained as a VALID table with twelve physical columns in the 12.2.2 schema.

In Data Vault modeling terms, the ETRM metadata classifies this object as a link. This is a heuristic classification mined from the foreign key structure, and should be treated as a modeling suggestion rather than a prescribed design. The designation is consistent with the table's evident purpose: it resolves relationships between parent elements, child elements, the plan relationships that contain them, and the characteristic definitions that govern collection behavior. The table therefore functions as an intersection or association entity in the collection plan configuration model rather than as a descriptive hub or an attribute satellite.

Key Information Stored

The table is anchored by the surrogate primary key ELEMENT_RELATIONSHIP_ID, enforced through the QA_PC_ELEMENT_RELATIONSHIP_PK1 constraint. A documented unique index, QA_PC_ELEMENT_RELATIONSHIP_U1, spans ELEMENT_RELATIONSHIP_ID and ZD_EDITION_NAME, indicating that the edition name participates in business-key uniqueness across the object's lifecycle. The most significant columns are:

• ELEMENT_RELATIONSHIP_ID — surrogate primary key uniquely identifying each parent-child element linkage.
• PLAN_RELATIONSHIP_ID — foreign key to QA_PC_PLAN_RELATIONSHIP, situating the element relationship within a specific plan-level relationship context.
• PARENT_CHAR_ID — foreign key to QA_CHARS, identifying the parent characteristic or element in the relationship.
• CHILD_CHAR_ID — foreign key to QA_CHARS, identifying the child characteristic or element.
• ELEMENT_RELATIONSHIP_TYPE — classifies the nature of the linkage between parent and child elements.
• LINK_FLAG — indicates whether the relationship is active or linked within the plan structure.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS audit and accountability columns tracking who created and modified each record and when.
• ZD_EDITION_NAME — the edition identifier supporting editioned data structures and referenced by the unique index.

Common Use Cases and Queries

This table is primarily exercised when reporting or validating the structure of quality collection plans, particularly where parent-child element dependencies must be resolved. A common query joins the table to QA_CHARS twice to retrieve both sides of the relationship:

• Parent-child resolution: SELECT r.ELEMENT_RELATIONSHIP_ID, p.CHARACTERISTIC_NAME AS parent_char, c.CHARACTERISTIC_NAME AS child_char FROM QA.QA_PC_ELEMENT_RELATIONSHIP r JOIN QA.QA_CHARS p ON r.PARENT_CHAR_ID = p.CHAR_ID JOIN QA.QA_CHARS c ON r.CHILD_CHAR_ID = c.CHAR_ID.
• Plan-scoped reporting: filtering by PLAN_RELATIONSHIP_ID to list all element relationships belonging to a specific plan relationship.
• Impact analysis: tracing upward from a child characteristic to all parents that reference it, useful when retiring or modifying collection elements.
• Active linkage checks: filtering on LINK_FLAG and ELEMENT_RELATIONSHIP_TYPE to isolate live relationships for configuration audits.

Related Objects

The FK relationships documented in the ETRM metadata define the table's principal dependencies:

• QA_CHARS — referenced twice, once via PARENT_CHAR_ID and once via CHILD_CHAR_ID; this is the most heavily joined table.
• QA_PC_PLAN_RELATIONSHIP — referenced via PLAN_RELATIONSHIP_ID, providing the plan-level container for element relationships.
• QA_PC_ELEMENT_RELATIONSHIP_PK1 — the primary key constraint defining row identity.
• QA_PC_ELEMENT_RELATIONSHIP_U1 — the unique index on ELEMENT_RELATIONSHIP_ID and ZD_EDITION_NAME supporting edition-aware uniqueness.

Surrounding QA plan configuration objects, including the element and plan relationship entities that share the QA_PC_ prefix, are typically accessed alongside this table when reconstructing complete plan hierarchies.