Search Results qa_results_n13

Overview

QA.QA_RESULTS is the central data repository for Oracle Quality in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores every quality result collected against a collection plan, whether captured interactively at the point of a transaction, through the Quality Workbench, via integration, or loaded by the Collection Import program. Consequently, the table occupies a foundational position within the Quality Management module: specifications, collection plans, and collection elements define what should be measured, while QA_RESULTS records what was actually measured and under which business context.

The table is physically large and conceptually wide, carrying 236 documented columns in the 12.2.2 schema. It resides in the APPS_TS_TX_DATA tablespace, with indexes allocated to APPS_TS_TX_IDX. From a Data Vault modeling perspective, the metadata's heuristic classification is satellite-leaning: QA_RESULTS primarily captures descriptive result attributes and context keyed by the collection plan and occurrence, rather than serving as a pure hub of business entities or a pure many-to-many link. This should be treated as a modeling suggestion rather than an architectural mandate.

Key Information Stored

The table's identifying structure rests on two unique business-key candidates. QA_RESULTS_U1 enforces uniqueness across PLAN_ID, COLLECTION_ID, and OCCURRENCE, while QA_RESULTS_U2 enforces uniqueness across PLAN_ID and OCCURRENCE. The declared primary key, QA_RESULTS_PK, is COLLECTION_ID plus OCCURRENCE. PLAN_ID supplies the collection plan context, and OCCURRENCE distinguishes successive collections under the same plan.

• COLLECTION_ID / OCCURRENCE — the composite primary key identifying each collection event.
• PLAN_ID — foreign key to QA_PLANS, identifying the governing collection plan.
• SPEC_ID — the specification referenced by the result, joining to QA_SPECS.
• ORGANIZATION_ID / ITEM_ID / REVISION — the inventory item and organization against which quality was measured.
• WIP_ENTITY_ID / LINE_ID / FROM_OP_SEQ_NUM / TO_OP_SEQ_NUM — work-in-process context for shop-floor collections.
• PO_HEADER_ID / PO_RELEASE_ID / VENDOR_ID / RECEIPT_NUM — procurement and receiving context.
• CUSTOMER_ID / SO_HEADER_ID / RMA_HEADER_ID / PARTY_ID — order management and customer context.
• SERIAL_NUMBER / LOT_NUMBER / COMP_SERIAL_NUMBER / ASSET_NUMBER — traceability identifiers.
• STATUS / TRANSACTION_DATE — lifecycle state and collection timestamp.
• CHARACTER1 through CHARACTER100 — generic result columns whose use is dictated by QA_CHARS.HARDCODED_COLUMN; a null there means one of these generic columns stores the element's value.

Additional hardcoded columns (for example DISPOSITION, NONCONFORMANCE_CODE, PROCESS_BATCH_ID, ASSET_GROUP_ID) support the Nonconformance, Disposition, Process Manufacturing, and Enterprise Asset Management extensions.

Common Use Cases and Queries

Typical reporting retrieves results by plan, item, occurrence, or time period. A minimal query joining plan context to results:

• SELECT r.collection_id, r.occurrence, r.item_id, r.character1, r.transaction_date FROM qa.qa_results r WHERE r.plan_id = :plan_id AND r.occurrence = :occ;
• Defect and yield analysis filters on DISPOSITION, NONCONFORMANCE_CODE, or NONCONFORMANCE_STATUS across a date range using QA_RESULTS_N14 (PLAN_ID, CREATION_DATE).
• Traceability reporting joins ITEM_ID and ORGANIZATION_ID, serviced by QA_RESULTS_N1, or SERIAL_NUMBER and ORGANIZATION_ID via QA_RESULTS_N2.
• WIP quality queries use QA_RESULTS_N13 (WIP_ENTITY_ID, ORGANIZATION_ID, FROM_OP_SEQ_NUM); process manufacturing queries use QA_RESULTS_N12 (PROCESS_BATCH_ID, PROCESS_BATCHSTEP_ID).
• Related-parent and child collection hierarchies are resolved through QA_PC_RESULTS_RELATIONSHIP using PARENT_COLLECTION_ID and CHILD_COLLECTION_ID.

Related Objects

• QA.QA_PLANS — joined on PLAN_ID; defines the collection plan.
• QA.QA_SPECS — joined on SPEC_ID; defines the specification governing the result.
• QA.QA_CHARS — maps collection elements to hardcoded or generic CHARACTERx columns.
• QA.QA_PC_RESULTS_RELATIONSHIP — links parent and child collections via PARENT_COLLECTION_ID and CHILD_COLLECTION_ID.
• MTL_SYSTEM_ITEMS_B — joined on ITEM_ID, ASSET_GROUP_ID, or ASSET_ACTIVITY_ID.
• WIP_ENTITIES — joined on WORK_ORDER_ID or WIP_ENTITY_ID.
• PO_VENDORS / PO_RELEASES_ALL — joined on VENDOR_ID and PO_RELEASE_ID.
• HZ_PARTIES / RA_CUSTOMERS — joined on PARTY_ID and CUSTOMER_ID.
• FND_USER — joined on QA_CREATED_BY for result provenance.