Search Results parent_form_field

Overview

The view APPS.QA_PC_RESULT_COLUMNS_V is a reporting and integration construct within the Oracle E-Business Suite Quality Management (QA) module, specifically in the Process Capability and SPC (Statistical Process Control) area. It exposes the relationship between parent and child QA collection plans together with the result columns (characteristics) that populate each plan's form and underlying database storage. The view's distinguishing feature is its handling of the HARDCODED_COLUMN attribute: when a characteristic is not hardcoded, the view returns the plan-level result column name; when a characteristic is hardcoded, it returns the developer name defined on the characteristic itself. This decode logic, combined with a REPLACE transformation that maps the token 'CHARACTER' to 'DISPLAY', produces the form field label that an end-user would see at runtime.

Because the view joins plan relationships, element relationships, and characteristic definitions, it effectively answers the question "which result field on the parent plan corresponds to which field on the child plan, and what is the form field and database column name for each?" That correspondence is essential for building Dynamic Views, integrating SPC data with external systems, and generating reports that must reconcile child-plan chart results against parent-plan storage.

Underlying Base Objects

Per the documented metadata, the view is owned by APPS and is defined over four base objects, all referenced through public synonyms:

• QA_CHARS — defines the characteristics, including HARDCODED_COLUMN, DEVELOPER_NAME, and DATATYPE.
• QA_PC_PLAN_RELATIONSHIP — links a parent plan to a child plan via PLAN_RELATIONSHIP_ID.
• QA_PC_ELEMENT_RELATIONSHIP — links a parent characteristic to a child characteristic through the same plan relationship, providing ELEMENT_RELATIONSHIP_TYPE.
• QA_PLAN_CHARS — the plan-to-characteristic assignment with RESULT_COLUMN_NAME and ENABLED_FLAG.

The characteristic table is aliased twice (QC1 for the parent, QC2 for the child) and QA_PLAN_CHARS likewise (QPC1 and QPC2). The joins are equated on PLAN_RELATIONSHIP_ID, CHAR_ID, and PLAN_ID, binding definitions to plan assignments and element relationships, so each row represents one parent/child characteristic pairing within a plan relationship.

Key Columns

• PARENT_PLAN_ID / CHILD_PLAN_ID — identify the participating plans.
• PARENT_CHAR_ID / CHILD_CHAR_ID — identify the parent and child characteristics.
• PARENT_FORM_FIELD / CHILD_FORM_FIELD — the user-visible field name, computed as REPLACE(DECODE(HARDCODED_COLUMN, NULL, RESULT_COLUMN_NAME, DEVELOPER_NAME), 'CHARACTER', 'DISPLAY').
• PARENT_DATABASE_COLUMN / CHILD_DATABASE_COLUMN — the physical result column (RESULT_COLUMN_NAME) where values are stored.
• ELEMENT_RELATIONSHIP_TYPE — classifies how the parent element relates to the child element.
• PARENT_ENABLED_FLAG / CHILD_ENABLED_FLAG — indicate whether each characteristic is active on its plan.
• DATATYPE (for QC1 and QC2) — the characteristic data type.

Common Use Cases and Queries

Typical uses include generating mapping reports that compare a child SPC plan's result columns to the parent plan's storage, and driving dynamic form generation where the form field label must honor hardcoded characteristics. A representative query to list the mapping for a plan relationship:

• SELECT PARENT_PLAN_ID, CHILD_PLAN_ID, PARENT_FORM_FIELD, PARENT_DATABASE_COLUMN, CHILD_FORM_FIELD, CHILD_DATABASE_COLUMN, ELEMENT_RELATIONSHIP_TYPE FROM APPS.QA_PC_RESULT_COLUMNS_V WHERE PARENT_PLAN_ID = :p_plan_id;

To surface only enabled, hardcoded-driven labels, filter on PARENT_ENABLED_FLAG = 'Y' and inspect the PARENT_FORM_FIELD values. Because the view resolves the HARDCODED_COLUMN decode and the CHARACTER-to-DISPLAY replacement, reports and integrations can rely on PARENT_FORM_FIELD and CHILD_FORM_FIELD as the authoritative presentation labels while using the database column names for direct data retrieval.