Search Results qa_function

Overview

APPS.QA_CRITERIA_V is a reporting and integration view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that exposes quality collection plan criteria together with their descriptive, validation, and functional attributes. It is owned by the APPS schema and is built on the QA_CRITERIA_V1 view, joined to QA_CHARS, QA_PLAN_CHARS, and MFG_LOOKUPS. The view presents a flattened, user-readable picture of the criteria that define how a quality result is captured, validated, and processed within Oracle Quality.

In practice, QA_CRITERIA_V supports both inquiry and integration workloads. Quality setup users, report developers, and interface developers rely on it to retrieve criteria definitions without needing to navigate the normalized underlying entities. Because it joins plan-level overrides to specification-level defaults, the view is particularly useful when the same characteristic is reused across multiple collection plans with different prompts, precision, or result column mappings.

Underlying Base Objects

The documented referenced objects are MFG_LOOKUPS (VIEW), QA_CHARS (SYNONYM), QA_CRITERIA_V1 (VIEW), QA_FLEX_UTIL (PACKAGE), and QA_PLAN_CHARS (SYNONYM).

• QA_CRITERIA_V1 is the core criteria view supplying CRITERIA_ID, CRITERIA_SEQUENCE, ORDER_SEQUENCE, operators, low/high values, FXN, TOTAL, and SQL_TYPE.
• QA_CHARS (QA_CHARS_B/TL base tables) supplies characteristic definition attributes: NAME, DATATYPE, DISPLAY_LENGTH, PROMPT, DECIMAL_PRECISION, VALUES_EXIST_FLAG, SQL_VALIDATION_STRING, and foreign-key lookup metadata.
• QA_PLAN_CHARS supplies plan-specific characteristic overrides such as RESULT_COLUMN_NAME, DECIMAL_PRECISION, and VALUES_EXIST_FLAG. The (+) outer-join notation preserves criteria rows that lack a plan-level override.
• MFG_LOOKUPS is outer-joined on LOOKUP_TYPE = 'QA_FUNCTION' and LOOKUP_CODE = FXN, providing FXN_MEANING for the validation or computation function applied to the criterion.
• QA_FLEX_UTIL is referenced in the metadata as a supporting package, typically used for flexfield-related resolution rather than direct row shaping.

Key Columns

• CRITERIA_ID / CRITERIA_SEQUENCE / ROW_ID — identify the criterion and its ordering within the plan.
• CHAR_ID / CHAR_NAME — the characteristic and its displayed name.
• SQL_TYPE, SQL_STRING_FLAG, DATATYPE, DISPLAY_LENGTH, PROMPT — control how the criterion is presented and rendered.
• OPERATOR, LOW_VALUE, HIGH_VALUE, LOW_VALUE_ID, HIGH_VALUE_ID — define the specification range and its coded values.
• FXN, FXN_MEANING — the functional routine resolved through the QA_FUNCTION lookup; this is the column pair most relevant to searches on "qa_function."
• TOTAL, SORT_BY, ORDER_SEQUENCE — drive aggregation and sequencing behavior in collection plans.
• RESULT_COLUMN_NAME, DECIMAL_PRECISION, VALUES_EXIST_FLAG, HARDCODED_COLUMN — plan-level overrides and result-storage mapping.
• FK_LOOKUP_TYPE, FK_TABLE_NAME, FK_ID, PK_ID, FK_MEANING, FK_ADD_WHERE — foreign-key resolution metadata for value-list display.

Common Use Cases and Queries

The view is commonly queried to audit criteria definitions, retrieve operator and value ranges, and drive dynamic validation interfaces. A typical query locating criteria for a particular function is:

• SELECT criteria_id, char_name, operator, low_value, high_value, fxn_meaning FROM apps.qa_criteria_v WHERE fxn_meaning = 'Range Validation';
• SELECT criteria_id, char_name, prompt, datatype, sql_type FROM apps.qa_criteria_v WHERE criteria_sequence > 0 ORDER BY criteria_sequence;
• SELECT criteria_id, result_column_name, decimal_precision FROM apps.qa_criteria_v WHERE total = 'Y';

Because the view exposes both specification defaults and plan overrides via NVL and outer joins, queries should account for the possibility of NULL plan-level values. When filtering on FXN, joining to MFG_LOOKUPS through FXN_MEANING is safer than relying on lookup codes, which may vary by installation.