Search Results qa_criteria_v




Overview
Explore in AI Chat

Overview

QA_CRITERIA_V is an Oracle E-Business Suite 12.1.1 / 12.2.2 view owned by the APPS schema and registered under the Quality (QA) product module. Its documented status is VALID. The view presents collection plan criteria alongside their associated quality elements, charts, and Quality Dynamic Reportwriter criteria definitions. It consolidates descriptive metadata about each criterion — the character or element being evaluated, its data type, display attributes, foreign key relationships, validation behaviour, and the operator/value combinations used to filter results — into a single denormalized row per criteria sequence.

Functionally, the view serves as the reporting and integration surface for the QA collection plan criteria model. Rather than requiring report authors and interfaces to join QA_PLAN_CHARS, QA_CHARS, and lookup tables independently, QA_CRITERIA_V pre-composes these relationships and resolves the lookup meaning for the applied function. This makes it a natural source for Dynamic Reportwriter setup extracts, criteria review reports, and migration scripts that must reproduce collection plan definitions across environments.

Underlying Base Objects

Per documented ETRM metadata, QA_CRITERIA_V is defined over the following referenced objects:

The joins between QA_CRITERIA_V1 and QA_PLAN_CHARS on PLAN_ID and CHAR_ID are both outer joins, meaning criteria rows are retained even where no plan-character override exists. The DECIMAL_PRECISION and VALUES_EXIST_FLAG columns use NVL to prefer the plan-level value and fall back to the character-level value. A DECODE derives SQL_STRING_FLAG as 'Y' when SQL_VALIDATION_STRING is populated, otherwise 'N'.

Key Columns

  • CRITERIA_ID / CRITERIA_SEQUENCE / ORDER_SEQUENCE — identify the criterion and control evaluation and display ordering.
  • CHAR_ID / CHAR_NAME — the quality character (element) being tested and its user-facing name.
  • DATATYPE / DISPLAY_LENGTH / DECIMAL_PRECISION — formatting and typing attributes for the criterion value.
  • OPERATOR / LOW_VALUE / LOW_VALUE_ID / HIGH_VALUE / HIGH_VALUE_ID — the comparison operator and its bound values. HIGH_VALUE_ID is the identifier counterpart to the HIGH_VALUE display value, typically resolved through the FK metadata; searching on high_value_id returns the criteria rows whose upper bound references that identifier.
  • FXN / FXN_MEANING — the function applied to the criterion and its decoded QA_FUNCTION lookup meaning.
  • SQL_STRING_FLAG / SQL_TYPE — indicate SQL-based validation or dynamic value sources.
  • FK_LOOKUP_TYPE, FK_TABLE_NAME, FK_ID, FK_ID2, FK_ID3, FK_MEANING, FK_DESCRIPTION, FK_ADD_WHERE — flexfield and foreign key resolution metadata enabling LOV-style value derivation.
  • RESULT_COLUMN_NAME / HARDCODED_COLUMN — map the criterion to its output column in Dynamic Reportwriter.

Common Use Cases and Queries

Typical scenarios include auditing collection plan criteria, extracting Dynamic Reportwriter definitions for comparison across instances, and tracing which criteria reference a particular value or element. The following query returns criteria rows where the high value identifier is populated:

  • SELECT criteria_id, criteria_sequence, char_name, operator, low_value, high_value, high_value_id, fxn_meaning FROM apps.qa_criteria_v WHERE high_value_id IS NOT NULL ORDER BY criteria_id, criteria_sequence;
  • SELECT char_id, char_name, datatype, operator, low_value, high_value FROM apps.qa_criteria_v WHERE sql_string_flag = 'Y'; — lists criteria that rely on SQL validation strings.
  • SELECT result_column_name, prompt, fxn_meaning, total, sort_by FROM apps.qa_criteria_v ORDER BY order_sequence; — produces a reportwriter layout inventory.

Because the view exposes only metadata and resolved lookups, it is read-only in practice and is best queried directly rather than extended. Consumers should account for the outer joins to QA_PLAN_CHARS and MFG_LOOKUPS, which may return NULL for RESULT_COLUMN_NAME, DECIMAL_PRECISION overrides, and FXN_MEANING where no matching plan or lookup row exists.