Results for “child_occurrence”

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

Overview

The QA_PC_RESULTS_RELATIONSHIP table is a Quality (QA) module object in the Oracle E-Business Suite that stores the relationship between two parent and child result rows. In practice it acts as a connective structure linking a parent collection result to a child collection result, allowing Oracle Quality to model hierarchies in which one set of collected results rolls up to, or is derived from, another. This is the underlying mechanism used for parent-child result relationships and multi-level collection structures in Quality data.

The ETRM metadata classifies this object, heuristically, as a link table in Data Vault terms. This modeling suggestion is consistent with its structure: it carries foreign keys to both QA_PLANS (two separate references) and QA_RESULTS (two separate references), positioning it as a junction that resolves a many-to-many association between parent and child records rather than a hub or satellite. The object resides in the QA schema and is documented as VALID in both 12.1.1 and 12.2.2, with a physical schema of 13 columns.

Key Information Stored

The table's principal content is the pairing of a parent result with a child result, together with the plans that govern each side of that pairing.

• PARENT_PLAN_ID — foreign key to QA_PLANS identifying the plan associated with the parent result.
• CHILD_PLAN_ID — foreign key to QA_PLANS identifying the plan associated with the child result.
• PARENT_COLLECTION_ID — foreign key into QA_RESULTS identifying the parent collection result.
• PARENT_OCCURRENCE — the occurrence number discriminating among multiple collection occurrences of the parent result (composite key element).
• CHILD_COLLECTION_ID — foreign key into QA_RESULTS identifying the child collection result.
• CHILD_OCCURRENCE — the occurrence number for the child result, completing the composite reference to QA_RESULTS.
• CHILD_TXN_HEADER_ID — reference to the child transaction header (for example, an inventory or receiving transaction) associated with the child result.
• ENABLED_FLAG — indicates whether the parent-child relationship is active and effective.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard Oracle EBS audit columns capturing who created and last changed the row.

The documented metadata does not expose a single-column surrogate primary key; the effective business key is the composite of PARENT_COLLECTION_ID/PARENT_OCCURRENCE and CHILD_COLLECTION_ID/CHILD_OCCURRENCE, qualified by the parent and child plan identifiers. The composite foreign keys to QA_RESULTS confirm that collection identifier and occurrence together form the business-key candidate referenced by this table.

Common Use Cases and Queries

Typical scenarios include tracing how a child collection result contributes to a parent result, reporting result hierarchies for quality plans, and validating that parent-child links are enabled before publishing rollup data.

• List all child results linked to a given parent collection, joining back to QA_RESULTS for context.
• Report the plan structure associated with each relationship by joining PARENT_PLAN_ID and CHILD_PLAN_ID to QA_PLANS.
• Identify inactive relationships using ENABLED_FLAG, useful for troubleshooting missing rollups.
• Trace genealogy to the originating transaction through CHILD_TXN_HEADER_ID.

A representative query pattern:

SELECT r.PARENT_COLLECTION_ID, r.PARENT_OCCURRENCE, r.CHILD_COLLECTION_ID,
  r.CHILD_OCCURRENCE, r.CHILD_TXN_HEADER_ID, r.ENABLED_FLAG
FROM QA.QA_PC_RESULTS_RELATIONSHIP r
WHERE r.PARENT_COLLECTION_ID = :collection_id
  AND r.ENABLED_FLAG = 'Y';

To enrich with plan and result descriptions, join to QA_PLANS on PARENT_PLAN_ID/CHILD_PLAN_ID and to QA_RESULTS on the collection identifier and occurrence pairs.

Related Objects

• QA_PLANS — referenced twice, via PARENT_PLAN_ID and CHILD_PLAN_ID.
• QA_RESULTS — referenced twice, via PARENT_COLLECTION_ID/PARENT_OCCURRENCE and CHILD_COLLECTION_ID/CHILD_OCCURRENCE.
• QA_RESULTS relationship queries — parent and child result rows joined on the collection identifiers and occurrences.
• Transaction tables referenced by CHILD_TXN_HEADER_ID — the source document for the child result.
• QA collection and plan inquiry forms/reports — consume this link table to render parent-child result hierarchies.