Search Results qa_results_view

Overview

APPS.QA_RESULTS_QWB_V is a reporting and integration view in Oracle E-Business Suite that exposes quality results collected against collection plans in the Quality module. The name suffix "QWB" refers to the Quality Workbench, the consolidated analysis and data-entry interface used by quality engineers and inspectors to review inspection outcomes. In both EBS 12.1.1 and 12.2.2 the view is owned by the APPS schema and is defined over the QA_RESULTS synonym together with supporting lookups, organization and plan metadata. It presents a denormalized, horizontally flattened representation of quality results: transactional context, plan and specification attributes, item and lot identification, quantity, status, and a wide block of descriptive flexfield columns (CHARACTER1 through CHARACTER28 and beyond). Because the underlying QA_RESULTS table is the central repository for all plan-driven quality data, this view serves as a convenient read-only access point for custom reports, OBIEE/XML Publisher data sources, and interface extracts that need quality outcomes without joining multiple QA tables manually.

Underlying Base Objects

The documented base objects underlying the view are:

• QA_RESULTS (SYNONYM) — the primary source of all result rows; supplies collection, occurrence, transaction and status data.
• QA_PLANS (SYNONYM) — joined to provide plan name, description and template plan information.
• FND_LOOKUP_VALUES (SYNONYM) — resolves the plan type code to its user-facing meaning.
• FND_USER_VIEW (VIEW) — resolves CREATED_BY identifiers to user names (QA_CREATED_BY_NAME).
• MTL_PARAMETERS (SYNONYM) — supplies the organization code (MP.ORGANIZATION_CODE) for the inventory organization.
• QA_PARENT_CHILD_PKG (PACKAGE), QA_PLAN_ELEMENT_API (PACKAGE) and QA_WEB_TXN_API (PACKAGE) — API packages referenced in the view logic to derive plan element and transaction attributes that are not stored directly on QA_RESULTS.

The join pattern is driven by COLLECTION_ID, OCCURRENCE, PLAN_ID and TRANSACTION_ID, with QA_PLANS keyed on PLAN_ID and MTL_PARAMETERS on ORGANIZATION_ID.

Key Columns

• ROW_ID, COLLECTION_ID, OCCURRENCE — unique identity of a result row and its occurrence within a collection.
• TRANSACTION_NUMBER, TXN_HEADER_ID, TRANSACTION_ID, TRANSACTION_DATE — the quality transaction context.
• PLAN_ID, TEMPLATE_PLAN_ID, NAME, DESCRIPTION, PLAN_TYPE — plan and specification metadata derived from QA_PLANS and FND_LOOKUP_VALUES.
• ORGANIZATION_ID, ORGANIZATION_CODE — inventory organization of the result.
• ITEM_ID, REVISION, LOT_NUMBER, SERIAL_NUMBER, UOM, SUBINVENTORY, LOCATOR_ID, QUANTITY — item and quantity attributes for the tested or inspected entity.
• COMP_* columns — component-level counterparts used for composition or multi-level results.
• WIP_ENTITY_ID, DEPARTMENT_ID, TO_DEPARTMENT_ID, FROM_OP_SEQ_NUM, TO_OP_SEQ_NUM, RESOURCE_ID, LINE_ID — work-in-process and routing context.
• VENDOR_ID, RECEIPT_NUM, PO_HEADER_ID, PO_LINE_NUM, PO_SHIPMENT_NUM — receiving and purchasing context.
• PROJECT_ID, TASK_ID, CUSTOMER_ID, SO_HEADER_ID, RMA_HEADER_ID, CONTRACT_ID, DELIVERABLE_ID — project, order and contract references.
• STATUS, LPN_ID — workflow/validation status and license plate number.
• CHARACTER1 … CHARACTER28+ — descriptive flexfield segments storing user-defined result attributes.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, QA_CREATED_BY_NAME — audit and ownership columns.

Common Use Cases and Queries

Typical scenarios include inspection-result extraction for quality dashboards, lot disposition reporting, supplier quality scorecards, and reconciliation of results to inventory transactions. Query by plan, organization or date range for periodic reporting:

• List recent results for a plan: SELECT collection_id, occurrence, transaction_number, item_id, quantity, status FROM apps.qa_results_qwb_v WHERE plan_id = :plan_id ORDER BY transaction_date DESC;
• Filter by organization and result date: SELECT organization_code, transaction_number, lot_number, quantity FROM apps.qa_results_qwb_v WHERE organization_id = :org_id AND transaction_date BETWEEN :from_date AND :to_date;
• Resolve flexfield attributes: SELECT collection_id, occurrence, character1, character2, created_by_name FROM apps.qa_results_qwb_v WHERE plan_id = :plan_id;

Because the view is read-only and owned by APPS, custom code should select from it rather than update it, and any query should filter on indexed columns such as COLLECTION_ID, PLAN_ID or TRANSACTION_ID to avoid full scans of the large QA_RESULTS base table.