Search Results qa_results_full_v




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

QA_RESULTS_FULL_V is a denormalized reporting view owned by the APPS schema in Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. It consolidates quality results recorded by the Oracle Quality (QA) module together with the surrounding transactional, inventory, manufacturing, purchasing, and order management context. Where the base table QA_RESULTS stores the raw quality data, this view resolves the foreign keys and joins the descriptive attributes required for meaningful analysis — item numbers, organization codes, plan names, department and resource codes, lot and serial numbers, job and production line names, vendor and customer names, and order references.

Because the view is defined with STATUS = VALID in the ETRM repository, it is a supported read-only object that can be embedded directly in reports, concurrent programs, Discoverer worksheets, BI Publisher data templates, and integration extracts. It is not a maintenance interface; inserts and updates against quality results must still flow through the QA forms or APIs into QA_RESULTS.

Underlying Base Objects

The view is constructed over QA_RESULTS as its driving synonym, enriched by a large set of joined synonyms and one view. Documented referenced objects include QA_PLANS, QUALITY plan flexfields resolved through the QA_FLEX_UTIL package (ITEM2, LOCATOR2, PROJECT_NUMBER), FND_LOOKUP_VALUES for decoded meanings, and FND_USER_VIEW and HR_ALL_ORGANIZATION_UNITS_TL for the user name and organization name translations. Inventory and warehouse attributes come from MTL_PARAMETERS, MTL_SECONDARY_INVENTORIES, MTL_MATERIAL_STATUSES_B and MTL_MATERIAL_STATUSES_TL, and WMS_LICENSE_PLATE_NUMBERS. Manufacturing linkage uses WIP_ENTITIES and WIP_LINES alongside BOM_DEPARTMENTS and BOM_RESOURCES. Process manufacturing results draw on GME_BATCH_HEADER, GME_BATCH_STEPS, GME_BATCH_STEP_ACTIVITIES, GME_BATCH_STEP_RESOURCES, GMD_OPERATIONS_B, and GMP_PROCESS_PARAMETERS_B. Service and asset context is supplied by CSI_ITEM_INSTANCES, QA_CSI_ITEM_INSTANCES, CSI_COUNTERS_TL, CSI_COUNTER_READINGS, CS_INCIDENTS_ALL_B, CSD_REPAIRS, and QA_AHL_MR. Commercial references are joined from PO_HEADERS_ALL, PO_RELEASES_ALL, AP_SUPPLIERS, OE_ORDER_HEADERS_ALL, MTL_SALES_ORDERS, HZ_CUST_ACCOUNTS, HZ_PARTIES, JTF_TASKS_B, PA_TASKS, HZ-related parties, and the application flex utility.

Key Columns

Common Use Cases and Queries

Typical applications include quality escape analysis by supplier, first-pass yield and defect trending by production line, certificate of analysis reporting, and asset or counter inspection history where quality results are tied to item instances. A frequent need is locating activity against a specific asset, which maps to the CSI and asset-management joins exposed by the view.

A representative query for asset-linked quality results is:

  • SELECT transaction_number, item_id, organization_code, lot_number, serial_number, plan_type, transaction_date, quantity FROM apps.qa_results_full_v WHERE organization_id = :org AND transaction_date >= :from_date ORDER BY transaction_date DESC;

Supplier-oriented analysis can filter on vendor_name and po_number, while work-in-process analysis typically groups by job_name and production_line. Because the view performs many outer joins, queries should always constrain ORGANIZATION_ID and a date range to limit the result set before applying narrower predicates.