Search Results qa_pc_criteria_columns_v




Overview
Explore in AI Chat

Overview

QA_PC_CRITERIA_COLUMNS_V is a Quality (QA) module view owned by the APPS schema. It is defined to retrieve all elements that constitute the criteria elements of the current plan. In practical terms, the view resolves the relationship between a parent plan and the characteristics (criteria) attached to it, exposing for each criterion both the runtime form field name and the underlying database column that stores the value. This makes it a metadata bridge: it tells integration and reporting layers which database column corresponds to which user-facing form field for a given plan criterion.

Because the view derives the FORM_FIELD value through a DECODE against the hardcoded column indicator on QA_CHARS and then applies a REPLACE to translate 'CHARACTER' to 'DISPLAY', it provides a presentation-ready label alongside the physical column name. This dual-column output is significant for dynamic form generation, criteria-driven data extraction, and any customization that must map UI-level criterion elements to their storage locations without hardcoding column names.

Underlying Base Objects

The view text is defined over four base objects, all referenced through APPS synonyms in the EBS 12.1.1 and 12.2.2 environments:

Joins are established on PLAN_RELATIONSHIP_ID between QA_PC_CRITERIA and QA_PC_PLAN_RELATIONSHIP, on CHAR_ID between QA_PLAN_CHARS and QA_CHARS as well as between QA_PLAN_CHARS and QA_PC_CRITERIA, and on PLAN_ID between QA_PLAN_CHARS and PARENT_PLAN_ID from the plan relationship. The net effect is a set of criteria rows scoped to the current (parent) plan.

Key Columns

  • PLAN_ID — the parent plan identifier to which the criterion belongs; the scoping key for retrieval.
  • CHAR_ID — the characteristic identifier of the criterion element.
  • FORM_FIELD — the presentation-layer field name. Computed as REPLACE(DECODE(QC.HARDCODED_COLUMN, NULL, QPC.RESULT_COLUMN_NAME, QC.DEVELOPER_NAME), 'CHARACTER', 'DISPLAY'). When the characteristic is not hardcoded, the result column name is used; otherwise the developer name is used, with 'CHARACTER' substituted by 'DISPLAY'.
  • DATABASE_COLUMN — the physical result column name (QPC.RESULT_COLUMN_NAME) where the criterion value is persisted.
  • DATATYPE — the declared data type of the characteristic (QC.DATATYPE), indicating whether the criterion is numeric, character, date, or similar.

Common Use Cases and Queries

The view is typically used to discover which columns to select when extracting plan criteria results, and to drive dynamic form or report field generation. A representative query returns all criteria columns for a specific plan:

  • SELECT plan_id, char_id, form_field, database_column, datatype FROM qa_pc_criteria_columns_v WHERE plan_id = :plan_id;
  • To filter by data type: SELECT char_id, form_field, database_column FROM qa_pc_criteria_columns_v WHERE plan_id = :plan_id AND datatype = 'NUMBER';
  • To resolve a form field back to its storage column: SELECT database_column FROM qa_pc_criteria_columns_v WHERE plan_id = :plan_id AND form_field = :field_name;

These patterns support criteria-driven extracts, report builders, and integrations that must remain independent of hardcoded schema column names across EBS releases.