Search Results qa_results_qwb_v

Overview

The QA_RESULTS_QWB_V view is a Quality (QA) module database object owned by the APPS schema in Oracle E-Business Suite. Its documented purpose is to "show all quality results," presenting a consolidated, denormalized read-only projection of quality collection data captured against the QA_RESULTS base table. The "_QWB_" suffix indicates that the view was constructed for the Quality Workbench, the Oracle Quality HTML-based user interface introduced in the E-Business Suite, which allows users to enter, query, and report on collection plans and their results through a web interface rather than the older Oracle Forms UI.

The view plays a central role in both reporting and integration. Because it consolidates decoded lookup values, user name derivations, organization codes, plan metadata, and the full set of transaction context columns into a single SQL statement, it shields downstream consumers—Discoverer workbooks, XML Publisher reports, OBIEE extracts, and custom interfaces—from needing to join QA_RESULTS to QA_PLANS, FND_USER, MTL_PARAMETERS, and FND_LOOKUP_VALUES manually. In EBS 12.1.1 and 12.2.2, the object is registered as a VALID view in the APPS schema, making it a stable, supported access point for quality result data.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, QA_RESULTS_QWB_V is defined over the following documented base objects:

• QA_RESULTS (synonym) — the primary driving table; every row of the view originates from a quality result record (aliased QR in the view text).
• QA_PLANS (synonym) — supplies collection plan metadata such as plan name, description, and template plan identifier.
• MTL_PARAMETERS (synonym) — provides the ORGANIZATION_CODE for the inventory organization in which the result was collected.
• FND_LOOKUP_VALUES (synonym) — decodes the plan type into a user-readable MEANING (for example, a collection or specification plan type).
• FND_USER_VIEW (view) — used to derive the creator's user name (QA_CREATED_BY_NAME) from the CREATED_BY identifier.
• QA_PARENT_CHILD_PKG (package), QA_PLAN_ELEMENT_API (package), and QA_WEB_TXN_API (package) — helper PL/SQL APIs referenced by the view definition to resolve specification-plan and parent/child relationships and to support the web transaction model.

The view therefore sits on top of the transactional quality results store, enriching it with descriptive attributes and organizational context.

Key Columns

The projection exposes several logical groups of columns:

• Identity and audit: ROW_ID (rowid), COLLECTION_ID, OCCURRENCE, CREATION_DATE, LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, plus QA-specific audit columns (QA_CREATION_DATE, QA_LAST_UPDATE_DATE, and their _BY counterparts) and the derived QA_CREATED_BY_NAME.
• Organization and plan context: ORGANIZATION_ID, ORGANIZATION_CODE, PLAN_ID, TEMPLATE_PLAN_ID, SPEC_ID, plan NAME/DESCRIPTION, and the decoded PLAN_TYPE meaning.
• Item and quantity data: ITEM_ID, UOM, REVISION, SUBINVENTORY, LOCATOR_ID, LOT_NUMBER, SERIAL_NUMBER, and QUANTITY, together with parallel component-level columns (COMP_ITEM_ID, COMP_UOM, COMP_LOT_NUMBER, and so on).
• Transaction and document references: TRANSACTION_NUMBER, TXN_HEADER_ID, TRANSACTION_ID, TRANSACTION_DATE, receipt and purchasing references (RECEIPT_NUM, PO_HEADER_ID, PO_LINE_NUM, PO_SHIPMENT_NUM), work in process identifiers (WIP_ENTITY_ID, LINE_ID, operation sequence numbers), project/task columns, and sales order, RMA, and contract identifiers.
• Status and flexfield data: STATUS, LPN_ID, and twenty-three generic CHARACTER1 through CHARACTER23 columns used to surface plan-defined collection elements.

Common Use Cases and Queries

Typical scenarios include quality result reporting by plan, drill-down from inventory transactions to inspection outcomes, and extracts for downstream quality analytics. A representative query filtering by organization and plan is shown below.

• Reporting all results for a collection plan within an organization, ordered by transaction date.
• Locating results by lot, serial, or receipt number for traceability and disposition.
• Extracting collection element values stored in the CHARACTERn columns for trend analysis.

SELECT qr.collection_id,
       qr.occurrence,
       qr.transaction_number,
       qr.organization_code,
       qp.name          AS plan_name,
       fl.meaning       AS plan_type,
       qr.item_id,
       qr.lot_number,
       qr.quantity,
       qr.transaction_date,
       qr.qa_created_by_name
FROM   apps.qa_results_qwb_v qr,
       apps.qa_plans           qp,
       apps.fnd_lookup_values  fl
WHERE  qr.plan_id       = qp.plan_id
AND    qr.plan_type     = fl.lookup_code
AND    fl.lookup_type   = 'QA_PLAN_TYPE'
AND    qr.organization_id = :org_id
AND    qr.plan_id         = :plan_id
ORDER BY qr.transaction_date DESC;

Because the view already joins the lookup and organization tables, this query demonstrates that consumers need only add any application-specific filters; the heavy lifting of decoding, name resolution, and context assembly is performed inside the view definition.