Search Results qa_criteria_v1




Overview
Explore in AI Chat

Overview

QA_CRITERIA_V1 is an Oracle E-Business Suite view owned by the APPS schema within the Quality (QA) product module. It exposes the selection criteria that drive charts and Quality Dynamic Reportwriter output, providing a read-only, presentation-oriented projection of the underlying QA_CRITERIA storage. The view carries a VALID status in both EBS 12.1.1 and 12.2.2 and is documented in ETRM as the source of "chart and Quality Dynamic Reportwriter criterias."

In the EBS architecture, the view sits between the base criteria table and the reporting/UI layers. Oracle Forms, concurrent report programs, and OAF pages that display or evaluate Quality chart and dynamic report definitions can query QA_CRITERIA_V1 rather than the base table, ensuring consistent derivation of computed attributes such as PLAN_ID. Because the view is a simple projection (a single-table SELECT with no joins, unions, or aggregation), it imposes negligible overhead and preserves row-level traceability via the ROWID column, which allows updateable-form or DML-supporting blocks to maintain join integrity when the view is used for display.

Underlying Base Objects

According to the documented ETRM metadata, QA_CRITERIA_V1 is defined over two referenced objects:

  • QA_CRITERIA (SYNONYM) — the primary base object, aliased QCR in the view text. It holds the persisted criteria rows including sequence, values, operators, and flexfield references.
  • QA_FLEX_UTIL (PACKAGE) — a Quality flexfield utility package whose function QA_FLEX_UTIL.QCH_PLAN_ID is invoked in the SELECT list to derive the PLAN_ID value from CRITERIA_ID.

The view text selects from QA_CRITERIA QCR and applies the packaged function at runtime; therefore, the PLAN_ID value is not stored on the base table but computed dynamically each time the view is queried. All other columns map one-to-one to QA_CRITERIA columns, with ROWID exposed explicitly for row identification.

Key Columns

The view exposes twenty columns. The most significant include:

Common Use Cases and Queries

Typical scenarios include reviewing chart/report criteria for a given plan, extracting operator-and-range definitions for validation, and supporting Reportwriter configuration screens. A basic retrieval is:

SELECT CRITERIA_ID, PLAN_ID, CRITERIA_SEQUENCE, OPERATOR, LOW_VALUE, HIGH_VALUE, TOTAL, SORT_BY FROM APPS.QA_CRITERIA_V1 ORDER BY CRITERIA_SEQUENCE;

To filter by plan or by a specific criterion:

SELECT * FROM APPS.QA_CRITERIA_V1 WHERE PLAN_ID = :plan_id;

SELECT * FROM APPS.QA_CRITERIA_V1 WHERE CRITERIA_ID = :criteria_id;

Because PLAN_ID is function-derived, filtering on it invokes QA_FLEX_UTIL per row; performance-sensitive queries may prefer filtering on CRITERIA_ID where the relationship is already known. As with all APPS views, direct DML should be avoided in favor of supported APIs, and ROW_ID should be retained only when updateable block behavior is required.