Results for “qa_bis_results_pk”

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

Overview

QA_BIS_RESULTS is a summary table owned by the QA (Quality) schema in Oracle E-Business Suite, described in the ETRM documentation as a "BIS Summary Table." BIS refers to Business Intelligence System / Oracle Business Intelligence reporting structures used within the Quality module. The table functions as a denormalized reporting and aggregation object that pre-joins quality plan, collection, item, lot, and defect dimensions into a single wide structure, enabling fast query performance for quality results analysis without traversing the full transactional model in the QA schema.

From a modeling perspective, the metadata classifies QA_BIS_RESULTS heuristically as standalone, with no foreign key dependencies mined from the FK structure. This suggests it behaves less like a normalized hub or link and more like a satellite-style summary or materialized reporting table whose grain is defined by the OCCURRENCE column rather than by a business transaction key. The absence of foreign keys reinforces its role as a read-oriented, possibly refreshed, snapshot structure rather than a transactional parent.

Key Information Stored

The table contains 25 documented columns. Its surrogate/primary key is QA_BIS_RESULTS_PK, defined on the OCCURRENCE column. A unique index, QA_BIS_RESULTS_U1, is also defined on OCCURRENCE, making OCCURRENCE both the primary key and the business-key candidate for this structure.

• OCCURRENCE — Primary key; identifies each summarized result row.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program metadata indicating which request populated the row and when.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS WHO columns for auditing the row lifecycle.
• QA_CREATION_DATE, QA_LAST_UPDATE_DATE — Quality-domain date stamps distinct from the WHO columns, reflecting when the underlying QA data was created or changed.
• ORGANIZATION_ID, ORGANIZATION_NAME — Inventory organization context for the quality result.
• PLAN_ID, PLAN_NAME, PLAN_TYPE_CODE, PLAN_TYPE_MEANING — The quality plan identity, name, and its type code plus decoded meaning.
• COLLECTION_ID — Reference to the quality collection event from which results derive.
• ITEM_ID, ITEM, LOT_CONTROL_CODE, LOT_NUMBER — Item and lot dimensions, including the lot control code that governs whether the item is lot-controlled.
• DEFECT_CODE, QUANTITY_DEFECTIVE — The defect classification and the defective quantity measure, which is the primary analytic metric in this summary.

Common Use Cases and Queries

Because QA_BIS_RESULTS is a summary table, its principal use is BI reporting and quality analytics: defect rate by item, defect trends by organization, plan-type effectiveness, and lot-level defect concentration. Typical queries filter by organization, plan, or date range and aggregate QUANTITY_DEFECTIVE.

• Defects by item and organization: SELECT ITEM, ORGANIZATION_NAME, SUM(QUANTITY_DEFECTIVE) FROM QA.QA_BIS_RESULTS GROUP BY ITEM, ORGANIZATION_NAME;
• Defect trend by plan type: group by PLAN_TYPE_MEANING and QA_CREATION_DATE to trend plan effectiveness.
• Lot-level analysis: join LOT_NUMBER back to inventory lot tables using ITEM_ID and LOT_NUMBER.
• Refresh audit: inspect REQUEST_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE to confirm when the summary was last rebuilt by its concurrent program.
• Defect code frequency: SELECT DEFECT_CODE, COUNT(*), SUM(QUANTITY_DEFECTIVE) FROM QA.QA_BIS_RESULTS GROUP BY DEFECT_CODE;

Related Objects

The metadata documents no foreign keys, so relationships to other objects are logical rather than enforced. The most significant related objects are:

• QA_ORGANIZATIONS / ORG_ORGANIZATION_DEFINITIONS — joined via ORGANIZATION_ID.
• QA_PLANS — joined via PLAN_ID to PLAN_NAME / PLAN_TYPE_CODE.
• QA_COLLECTIONS — joined via COLLECTION_ID for collection-level detail.
• MTL_SYSTEM_ITEMS_B — joined via ITEM_ID for item master attributes.
• MTL_LOT_NUMBERS — joined via ITEM_ID and LOT_NUMBER.
• QA_RESULTS — the transactional results table that ultimately feeds this summary.
• QA_BIS_RESULTS_PK / QA_BIS_RESULTS_U1 — constraints and indexes enforcing the OCCURRENCE key.
• FND_CONCURRENT_REQUESTS — joined via REQUEST_ID for concurrent program audit.