Search Results parent_database_column

Overview

QA_PC_RESULT_COLUMNS_V is a Quality (QA) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its ETRM description states that the view "will be useful in dealing with copy relationship or others." In practice, it exposes the column-level mapping between a parent quality plan and its child quality plan whenever a plan-to-plan relationship, such as a copy or element relationship, exists. Rather than storing data itself, the view resolves identifiers into developer-facing form fields and database column names, enabling reports and integrations to translate abstract quality plan relationship definitions into concrete form field and database column references.

The view is read-only and is typically queried directly by custom reports, concurrent programs, or integration routines that need to copy or compare quality results across plan relationships. The user search term "parent_database_column" maps directly to one of the view's exposed columns, PARENT_DATABASE_COLUMN, confirming its relevance to column-level plan-to-plan mapping.

Underlying Base Objects

ETRM metadata lists four referenced base objects, all accessed via SYNONYM in APPS: QA_CHARS, QA_PC_ELEMENT_RELATIONSHIP, QA_PC_PLAN_RELATIONSHIP, and QA_PLAN_CHARS. QA_PC_PLAN_RELATIONSHIP supplies the parent and child plan identifiers (PARENT_PLAN_ID, CHILD_PLAN_ID). QA_PC_ELEMENT_RELATIONSHIP links parent and child characteristic (char) IDs and supplies the ELEMENT_RELATIONSHIP_TYPE. QA_CHARS and QA_PLAN_CHARS are joined twice each, once for the parent side and once for the child side, to resolve characteristic attributes (HARDCODED_COLUMN, DEVELOPER_NAME, DATATYPE) and plan-specific result column names and enabled flags.

The joins are driven by PLAN_RELATIONSHIP_ID, PARENT_CHAR_ID, CHILD_CHAR_ID, and the parent/child PLAN_ID plus CHAR_ID combinations, producing a denormalized row per related characteristic pair.

Key Columns

• PARENT_PLAN_ID / CHILD_PLAN_ID — Identifiers of the related parent and child quality plans.
• PARENT_CHAR_ID / CHILD_CHAR_ID — Characteristic identifiers on each side of the relationship.
• PARENT_FORM_FIELD / CHILD_FORM_FIELD — Form field names derived via DECODE on HARDCODED_COLUMN, falling back to DEVELOPER_NAME and substituting 'CHARACTER' with 'DISPLAY'.
• PARENT_DATABASE_COLUMN / CHILD_DATABASE_COLUMN — The underlying RESULT_COLUMN_NAME on each side; PARENT_DATABASE_COLUMN is the column matching the user's search.
• ELEMENT_RELATIONSHIP_TYPE — Classifies how the parent and child characteristics relate.
• PARENT_ENABLED_FLAG / CHILD_ENABLED_FLAG — Enabled status of each side's plan characteristic.
• PARENT_DATATYPE / CHILD_DATATYPE — Data types of the parent and child characteristics.

Common Use Cases and Queries

Typical uses include auditing copy relationships, generating column-mapping documentation, and validating that parent and child data types align before result propagation. A representative query follows:

• SELECT parent_plan_id, child_plan_id, parent_database_column, child_database_column, element_relationship_type FROM qa_pc_result_columns_v WHERE parent_plan_id = :plan_id;
• SELECT parent_database_column, child_database_column, parent_datatype, child_datatype FROM qa_pc_result_columns_v WHERE parent_datatype <> child_datatype;
• SELECT parent_form_field, parent_database_column, child_form_field, child_database_column FROM qa_pc_result_columns_v WHERE parent_enabled_flag = 'Y' AND child_enabled_flag = 'Y';

These queries support copy relationship setup, integration mapping, and diagnostic reporting across quality plans in Oracle EBS 12.1.1 and 12.2.2.