Results for “qa_results_v”

50+ results




Overview
Explore in AI Chat

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

Overview

QA_RESULTS_V is a predefined Oracle E-Business Suite view owned by the APPS schema and validated against releases 12.1.1 and 12.2.2. It belongs to the QA (Quality) product family and, per the ETRM documentation, "shows all quality results." Functionally, the view presents a denormalized, reporting-friendly projection of quality results captured in the QA module, joining the core QA_RESULTS transactional table to a broad set of reference objects across manufacturing, inventory, order management, purchasing, projects, service, and process manufacturing. It therefore serves as the principal read layer for quality collection-element outcomes, exposing both the raw measurement context and the descriptive attributes needed for human-readable reporting.

Because the view is a database object (not a concurrent program or report), it is typically consumed by custom reports, Discoverer workbooks, BI Publisher data templates, OBIEE extracts, and downstream integrations that need quality result detail without reconstructing the underlying joins. The view is documented as VALID in the APPS schema.

Underlying Base Objects

The view text is anchored on QA_RESULTS QR, aliased in the SELECT list, and enriched through the QA_FLEX_UTIL package plus a large set of synonyms and views. Documented referenced objects include:

These objects are predominantly accessed via APPS synonyms, so the view is insensitive to the physical owner of each base table.

Key Columns

Common Use Cases and Queries

Typical scenarios include quality results by plan or specification, defect/collection trends by organization, supplier quality tied to receipts, and WIP in-process inspection reporting.

SELECT transaction_number, plan_id, spec_id, quantity, uom, status
FROM   apps.qa_results_v
WHERE  organization_id = :org
AND    transaction_date >= :from_date;
SELECT vendor_name, COUNT(*) results, SUM(quantity) qty
FROM   apps.qa_results_v
WHERE  vendor_id IS NOT NULL
GROUP  BY vendor_name;
SELECT job_name, production_line, from_op_seq_num, to_op_seq_num, quantity
FROM   apps.qa_results_v
WHERE  wip_entity_id IS NOT NULL;

Because the SELECT list resolves foreign keys to descriptive names, these queries avoid additional joins; however, callers should still restrict by ORGANIZATION_ID and TRANSACTION_DATE to keep runtime acceptable on large quality result volumes.