Results for “parent_plan_id”

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

Overview

The QA_PC_RESULTS_RELATIONSHIP_V view is a Quality (QA) module reporting object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. As its description states, it is a "Parent/child relationship view" that exposes the linkage between parent and child quality collection plans, together with the transactional results that have been recorded against the child plan. The view consolidates relationship metadata from the plan-to-plan definition level with the actual result rows captured at execution time, allowing consumers to traverse from a parent plan down to its associated child transactions without writing multi-table joins manually.

Because it is a view rather than a table, no data is stored redundantly; the object presents a read-only, denormalized projection that is suitable for reporting, ad-hoc SQL, and integration extracts. The parent_plan_id column, which is the search term associated with this documentation, is the primary correlation key that links the parent side of the hierarchy to the child side and ultimately to the results records.

Underlying Base Objects

The view is defined over three base objects, all referenced through APPS synonyms:

• QA_PC_RESULTS_RELATIONSHIP — supplies the parent/child plan, collection, and occurrence identifiers, the enabled flag, and the standard WHO audit columns.
• QA_PC_PLAN_RELATIONSHIP — supplies the relationship definition attributes such as PLAN_RELATIONSHIP_ID, PLAN_RELATIONSHIP_TYPE, DATA_ENTRY_MODE, AUTO_ROW_COUNT, DEFAULT_PARENT_SPEC, and LAYOUT_MODE.
• QA_RESULTS — supplies the child transaction header identifier (TXN_HEADER_ID) surfaced as CHILD_TXN_HEADER_ID.

The join predicates bind the three objects together: the parent plan, child plan, child collection, and child occurrence in QA_PC_RESULTS_RELATIONSHIP must match the corresponding keys in QA_PC_PLAN_RELATIONSHIP, and the child plan, collection, and occurrence must additionally match QA_RESULTS. This structure means a row is only returned when a result row exists for the child definition, which is an important behavioral consideration for outer-join style reporting.

Key Columns

• PARENT_PLAN_ID — identifier of the parent collection plan; the primary drill-down key.
• PARENT_COLLECTION_ID / PARENT_OCCURRENCE — collection and occurrence qualifiers for the parent instance.
• CHILD_PLAN_ID / CHILD_COLLECTION_ID / CHILD_OCCURRENCE — the corresponding identifiers on the child side of the relationship.
• ENABLED_FLAG — indicates whether the relationship is currently active.
• CHILD_TXN_HEADER_ID — the transaction header from QA_RESULTS, linking the child plan to its recorded results transaction.
• PLAN_RELATIONSHIP_ID / PLAN_RELATIONSHIP_TYPE — definition-level identifiers describing the nature of the parent/child plan relationship.
• DATA_ENTRY_MODE, AUTO_ROW_COUNT, DEFAULT_PARENT_SPEC, LAYOUT_MODE — configuration attributes that govern how the child results are presented and entered.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard audit columns inherited from QA_PC_RESULTS_RELATIONSHIP.

Common Use Cases and Queries

Typical uses include reconciling parent/child plan hierarchies, reporting on all child transactions spawned from a parent plan, and feeding integration extracts that need relationship plus transaction identifiers in one row set.

To retrieve all relationships and child transactions for a specific parent plan:

SELECT parent_plan_id,
       child_plan_id,
       child_collection_id,
       child_occurrence,
       child_txn_header_id,
       plan_relationship_type,
       enabled_flag
FROM   apps.qa_pc_results_relationship_v
WHERE  parent_plan_id = :p_parent_plan_id
AND    enabled_flag = 'Y';

To list only the configuration attributes of each defined relationship:

SELECT plan_relationship_id,
       parent_plan_id,
       child_plan_id,
       data_entry_mode,
       layout_mode,
       auto_row_count
FROM   apps.qa_pc_results_relationship_v
ORDER  BY parent_plan_id, child_plan_id;

Note that because the view performs inner joins to QA_RESULTS, relationships that have no recorded child results will not appear. Reporting that must include relationship definitions regardless of result existence should query QA_PC_PLAN_RELATIONSHIP directly or use an outer join against QA_RESULTS.