Search Results request_source




Overview
Explore in AI Chat

Overview

QA_RESULTS_VAL_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite. It resides in the Quality (QA) product module and, per its ETRM documentation, presents "only valid quality results." In practice, the view acts as a filtered projection over the QA_RESULTS base entity, returning collection and occurrence rows that have not been invalidated or superseded, thereby relieving report authors and integration developers of the burden of applying validity filters themselves.

Because quality results are consumed across many EBS modules — Inventory, WIP, Purchasing, Order Management, and Projects — the view serves as a stable, denormalized read model. Its column list carries not only QA-specific identifiers such as COLLECTION_ID, OCCURRENCE, SPEC_ID, and PLAN_ID, but also the full set of cross-module context identifiers (WIP_ENTITY_ID, PO_HEADER_ID, SO_HEADER_ID, RMA_HEADER_ID, PROJECT_ID, TASK_ID) that link a result back to its originating business transaction. This makes it suitable for ad hoc querying, custom concurrent programs, and inbound interfaces that must resolve a quality result to its transactional source.

Underlying Base Objects

The documented view metadata for 12.2.2 records a single referenced base object: QA_RESULTS, accessed through a synonym. The view text confirms this relationship, projecting the base table alias QR with an explicit column list and adding QR.ROWID as ROW_ID so that consumers retain a stable row identifier even though the view itself is not directly updateable. Columns are drawn directly from QA_RESULTS without aggregation or joining, meaning the "valid only" semantics are implemented as a row-level filter in the view's WHERE clause rather than through a join to a separate specification table. QA_RESULTS is the parent result entity in the Quality schema; related specification and collection definitions remain in their own tables and are not exposed through this view.

Key Columns

Common Use Cases and Queries

The view is typically queried to report quality results by work order, receipt, or sales order, and to feed downstream systems that require only current, valid records.

Results for a given work order:

  • SELECT collection_id, occurrence, item_id, wip_entity_id, quantity, uom, status FROM qa_results_val_v WHERE wip_entity_id = :work_order_id;

Inspection history for a received lot:

  • SELECT receipt_num, po_header_id, item_id, lot_number, character1, character2 FROM qa_results_val_v WHERE po_header_id = :po_header_id ORDER BY creation_date DESC;

Quality results tied to a project task, joined to inventory for item descriptions, follow the same pattern, filtering on project_id and task_id. Because the view already restricts output to valid results, no additional validity predicate is required in these queries.