Search Results qa_pc_results_relationship




Overview
Explore in AI Chat

Overview

The QA_PC_RESULTS_RELATIONSHIP table is a core data structure within the Oracle E-Business Suite Quality (QA) module, present in both releases 12.1.1 and 12.2.2. It serves as a relational junction table, explicitly designed to store and manage hierarchical linkages between quality inspection results. Its primary role is to establish and maintain parent-child relationships between different result rows, enabling the modeling of complex inspection workflows where one result (the child) is dependent on or derived from another (the parent). This functionality is essential for tracking the lineage and dependencies of quality data throughout the manufacturing and inspection processes.

Key Information Stored

The table's structure is defined by foreign key relationships that identify the linked parent and child entities. The critical columns are pairs that reference the related quality plans and specific result occurrences. For the parent entity, the key columns are PARENT_PLAN_ID, PARENT_COLLECTION_ID, and PARENT_OCCURRENCE. For the child entity, the corresponding columns are CHILD_PLAN_ID, CHILD_COLLECTION_ID, and CHILD_OCCURRENCE. The PARENT_PLAN_ID and CHILD_PLAN_ID columns reference the QA_PLANS table, defining the inspection plans involved. The collection ID and occurrence columns for both parent and child reference the QA_RESULTS table, pinpointing the exact result records that participate in the relationship.

Common Use Cases and Queries

A primary use case is tracing the dependency chain of inspection results, such as when a final assembly test result (child) is contingent upon the successful results of its component tests (parents). This is critical for root cause analysis and audit trails. Common reporting needs include listing all child results for a given parent result or identifying all parent results for a specific child. A sample query to find all child results for a known parent result would join QA_PC_RESULTS_RELATIONSHIP to QA_RESULTS twice—once for the child results and once to filter on the parent's details. Another typical pattern is validating data integrity by checking for orphaned relationships where a referenced plan or result no longer exists.

Related Objects

This table has direct dependencies on two other fundamental Quality tables, as defined by its foreign keys:

  • QA_PLANS: Referenced by both PARENT_PLAN_ID and CHILD_PLAN_ID. This table stores the definition of quality inspection plans.
  • QA_RESULTS: Referenced by the combination of PARENT_COLLECTION_ID/PARENT_OCCURRENCE and CHILD_COLLECTION_ID/CHILD_OCCURRENCE. This is the primary table storing all collected quality inspection results.

Given its function, it is also intrinsically related to the Quality module's user interfaces and public APIs for managing collection elements and result hierarchies, though these are not explicitly named in the provided metadata.