Search Results defect_code

Overview

QA_BIS_RESULTS_V is a business intelligence summary view owned by the APPS schema within the Oracle E-Business Suite Quality (QA) module. It is classified as a BIS (Business Intelligence System) summary table view and is documented as VALID at release levels 12.1.1 and 12.2.2. The view exposes denormalized collection-plan quality results in a flattened, reporting-friendly form, joining transactional defect quantity data to plan, item, lot, and organization attributes so that downstream reporting and integration consumers do not need to reconstruct those relationships themselves.

Its principal role is analytical: it supports quality-result reporting, ad hoc inquiry, and extract processes that monitor defective quantities by collection plan, item, lot, and organization. Because it is a view rather than a stored summary table, data is derived at query time from the underlying QA and inventory entities.

Underlying Base Objects

The view is defined over six referenced base objects, all resolved through APPS synonyms: QA_BIS_RESULTS, QA_PLANS, HR_ALL_ORGANIZATION_UNITS_TL, MTL_SYSTEM_ITEMS_B, MTL_SYSTEM_ITEMS_TL, and FND_LOOKUP_VALUES. The driving table is QA_BIS_RESULTS, aliased QB, which supplies the transactional and audit columns.

• QA_PLANS (QP) is joined on PLAN_ID to supply PLAN_NAME and PLAN_TYPE_CODE.
• HR_ALL_ORGANIZATION_UNITS_TL (HAOT) is joined on ORGANIZATION_ID to supply the translated ORGANIZATION_NAME.
• MTL_SYSTEM_ITEMS_B (MSIB) is outer-joined on ORGANIZATION_ID and ITEM_ID to supply the lot control code.
• MTL_SYSTEM_ITEMS_TL (MSIT) is outer-joined to supply the translated item description.
• FND_LOOKUP_VALUES (FL) is joined on LOOKUP_TYPE = 'COLLECTION_PLAN_TYPE' to translate PLAN_TYPE_CODE into PLAN_TYPE_MEANING.

All translated columns are filtered by USERENV('LANG') to return the session language.

Key Columns

The view exposes twenty-five columns. Audit and concurrency columns—REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN, LAST_UPDATED_BY, and LAST_UPDATE_DATE—identify the concurrent program and user context that produced each row.

Of direct interest to users searching for qa_creation_date, the view surfaces both QA_CREATION_DATE and QA_LAST_UPDATE_DATE, distinct from the standard CREATION_DATE and LAST_UPDATE_DATE audit columns. These reflect the quality-specific creation and modification timestamps of the underlying result record.

• ORGANIZATION_ID / ORGANIZATION_NAME — inventory organization and its translated name.
• PLAN_ID / PLAN_NAME / PLAN_TYPE_CODE / PLAN_TYPE_MEANING — collection plan identity and its lookup-derived type meaning.
• COLLECTION_ID / OCCURRENCE — collection instance and its occurrence sequence.
• ITEM_ID / ITEM / LOT_CONTROL_CODE / LOT_NUMBER — item identity, description, lot control setting, and lot.
• DEFECT_CODE / QUANTITY_DEFECTIVE — the defect recorded and the quantity found defective.

Common Use Cases and Queries

Typical uses include defect trending by plan type, lot-level quality analysis, and extraction of quality results into external BI repositories. The QA_CREATION_DATE column supports period-based filtering of results.

The following query returns defective quantities for a given organization, filtered by QA creation date:

• SELECT organization_name, plan_name, plan_type_meaning, item, lot_number, defect_code, quantity_defective, qa_creation_date FROM qa_bis_results_v WHERE organization_id = :org_id AND qa_creation_date >= :from_date AND qa_creation_date < :to_date ORDER BY qa_creation_date DESC;
• SELECT plan_name, SUM(quantity_defective) total_defective FROM qa_bis_results_v GROUP BY plan_name ORDER BY total_defective DESC;
• SELECT item, lot_number, defect_code, quantity_defective FROM qa_bis_results_v WHERE lot_number IS NOT NULL ORDER BY qa_last_update_date DESC;

Because it is a view, no DML is permitted; all access is read-only, and performance depends on the indexes of the underlying QA_BIS_RESULTS and QA_PLANS tables.