Search Results qa_pc_plan_columns_v




Overview
Explore in AI Chat

Overview

QA_PC_PLAN_COLUMNS_V is a PL/SQL-based view owned by the APPS schema in Oracle E-Business Suite, residing in the QA (Quality) product module. It exposes a denormalized mapping between a quality plan and the result columns defined for that plan's characteristics, resolving both the runtime form field name and the underlying database column for each characteristic. The view is documented as VALID in the ETRM repository for both 12.1.1 and 12.2.2.

Its role is integration-oriented rather than analytical. The description states that the view "will be useful in getting all elements and values from current form so that these can be passed on to child plans." In other words, it supports the copy/delegation logic in Oracle Quality where a parent plan's characteristic values must be propagated to child plans. By resolving form field names and database column names at query time, it allows the plan-copying logic to locate and transfer values dynamically, without hard-coding column names.

Underlying Base Objects

The view is defined over two base objects, both referenced as synonyms in the APPS schema:

  • QA_PLAN_CHARS (aliased QPC) — the association table linking a quality plan to its characteristics, holding PLAN_ID, CHAR_ID, the result column name, and the enabled flag.
  • QA_CHARS (aliased QC) — the characteristic definition table, supplying the hard-coded column flag, the developer (form) name, and the datatype.

The join is a simple equijoin on CHAR_ID. Because QA_PLAN_CHARS is the driving table, the view returns one row per plan-characteristic assignment, enriched with characteristic-level metadata from QA_CHARS.

Key Columns

  • PLAN_ID — Identifier of the quality plan to which the characteristic belongs.
  • CHAR_ID — Identifier of the characteristic assigned to that plan.
  • FORM_FIELD — The runtime form field name. This is computed as REPLACE(DECODE(QC.HARDCODED_COLUMN, NULL, QPC.RESULT_COLUMN_NAME, QC.DEVELOPER_NAME), 'CHARACTER', 'DISPLAY'). When the characteristic is not hard-coded, the result column name is used; otherwise the developer name is used. The literal string 'CHARACTER' is then replaced with 'DISPLAY' to align the field name with the form block naming convention.
  • DATABASE_COLUMN — Sourced directly from QPC.RESULT_COLUMN_NAME; the physical column in the results table where the characteristic value is stored.
  • ENABLED_FLAG — Indicates whether the plan-characteristic assignment is currently active.
  • DATATYPE — The Oracle datatype of the characteristic (for example NUMBER, VARCHAR2, DATE), used to interpret or format transferred values.

Common Use Cases and Queries

The primary scenario is determining which form fields and database columns must be read for a given plan so their values can be written to child plans. A typical query lists all enabled columns for a parent plan:

  • SELECT FORM_FIELD, DATABASE_COLUMN, DATATYPE FROM QA_PC_PLAN_COLUMNS_V WHERE PLAN_ID = :plan_id AND ENABLED_FLAG = 'Y';
  • Joining the view to a results table to build a dynamic SELECT list of database columns for a plan's characteristic values.
  • Filtering on DATATYPE to separate numeric characteristics from character characteristics during value propagation.
  • Comparing FORM_FIELD to DATABASE_COLUMN to detect characteristics whose form field naming differs from the stored column — a common issue when copying values across plans created from different specifications.

Because the view depends only on QA_CHARS and QA_PLAN_CHARS, it performs efficiently for single-plan lookups and is safe to use in custom plan-copy logic and QA-related concurrent programs.