Results for “qa_skiplot_rcv_results_v”
49 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
QA_SKIPLOT_RCV_RESULTS_V is an APPS-owned reporting view within the Oracle E-Business Suite Quality (QA) module. It consolidates skip lot inspection outcomes generated against received material, exposing a single denormalized row for each skip lot result tied to a receiving inspection lot. Skip lot processing allows an organization to inspect only a calculated fraction of incoming receipts when a supplier or item has demonstrated a consistent quality history; this view surfaces the result of that sampling decision together with the full receiving, purchasing, and item context required for analysis and audit.
The view is defined in the APPS schema and is marked VALID. Its principal value in EBS 12.1.1 and 12.2.2 is as a reporting and integration surface: it spares downstream reports, OBIEE extracts, and custom concurrent programs from joining QA_SKIPLOT_RCV_RESULTS to RCV_SHIPMENT_LINES, RCV_SHIPMENT_HEADERS, purchasing tables, and item key flexfields manually. Because it exposes SHIPMENT_LINE_NUM alongside the internal SHIPMENT_LINE_ID, it directly supports user-facing queries that reconcile skip lot results to the receiving transaction line the user sees on the receipt form.
Underlying Base Objects
The view's row source is the QA_SKIPLOT_RCV_RESULTS base table (QSRR), joined to QA_SKIPLOT_PROCESSES (QSP) to retrieve PROCESS_CODE, and to two instances of QA_LOOKUPS (QL1, QL2) that decode INSPECTION_STATUS and INSPECTION_RESULT into their MEANING values using the lookup types QA_SKIPLOT_STATUS and QA_SKIPLOT_RESULT. These decode joins are outer joins, so a result row is retained even when no lookup meaning is defined.
Receiving context is supplied through RCV_SHIPMENT_LINES (RSL) and RCV_SHIPMENT_HEADERS (RSH), which provide SHIPMENT_LINE_NUM, SHIPMENT_NUM, and RECEIPT_NUM. Item and category descriptions arrive via MTL_SYSTEM_ITEMS_KFV and MTL_CATEGORIES_KFV concatenated key flexfield views. Purchasing attributes are drawn from PO_HEADERS_ALL, PO_LINES_ALL, and PO_DISTRIBUTIONS_ALL, while supplier identity comes from AP_SUPPLIERS, AP_SUPPLIER_SITES_ALL, and HZ_PARTIES. Manufacturer data is sourced from MTL_MANUFACTURERS, project and task data from PA_TASKS in conjunction with the QA_FLEX_UTIL package functions SALES_ORDER and PROJECT_NUMBER, and license plate information from WMS_LICENSE_PLATE_NUMBERS. The documented metadata for 12.2.2 additionally lists PO_DISTRIBUTIONS_TRX_V, PO_LINE_LOCATIONS_ALL, and PO_CLM_INTG_GRP as referenced objects, reflecting the purchasing join path in later point releases.
Key Columns
- INSP_LOT_ID — Primary identifier of the skip lot inspection lot; the natural key linking a result to its inspection record.
- SHIPMENT_LINE_ID / SHIPMENT_LINE_NUM — Internal and user-visible identifiers of the receiving shipment line. SHIPMENT_LINE_NUM is the value users search for when reconciling a receipt to its skip lot outcome.
- SHIPMENT_HEADER_ID / SHIPMENT_NUM / RECEIPT_NUM — Receiving document and receipt identifiers for grouping results by receipt.
- INSPECTION_STATUS / INSPECTION_RESULT — Decoded lookup meanings from QA_SKIPLOT_STATUS and QA_SKIPLOT_RESULT.
- PROCESS_ID / PROCESS_CODE — The skip lot process (sampling plan) applied to the result.
- LOT_QTY / TRANSACTED_QTY / SOURCE_INSPECTED — Quantities governing the skip lot decision and the inspected source.
- ITEM / ITEM_ID / ITEM_DESCRIPTION / ITEM_REVISION — Item key flexfield concatenation and descriptive attributes.
- CATEGORY_ID / CATEGORY_DESC — Item category context.
- PO_NUMBER / PO_LINE_NUMBER — Purchasing document references; VENDOR_NAME, VENDOR_SITE_CODE, and MANUFACTURER_NAME complete supplier context.
- ORGANIZATION_ID — Receiving inventory organization, sourced from RSL.TO_ORGANIZATION_ID.
- LPN — License plate number when the receipt is under license plate control.
Common Use Cases and Queries
Typical usage includes supplier quality scorecards that correlate skip lot results to vendors, receipt-level exception reports where INSPECTION_RESULT indicates a failure requiring escalation, and reconciliation between a user-supplied shipment line number and the underlying skip lot record.
The most direct query for a user searching by shipment line number:
SELECT insp_lot_id, shipment_line_num, receipt_num, shipment_num, item, vendor_name, inspection_status, inspection_result, lot_qty, transacted_qty FROM qa_skiplot_rcv_results_v WHERE shipment_line_num = :p_line_num;
Aggregate reporting by supplier and process:
SELECT vendor_name, process_code, inspection_result, COUNT(*) result_count, SUM(lot_qty) total_lot_qty FROM qa_skiplot_rcv_results_v WHERE receipt_date >= :p_from_date GROUP BY vendor_name, process_code, inspection_result ORDER BY vendor_name, process_code;
Because all critical joins are contained within the view, these queries run without additional application table access, making the view suitable for both ad hoc discovery and scheduled extract routines.
-
Skip Lot results for Receiving
APPS.QA_SKIPLOT_RCV_RESULTS_V·↳ AP_SUPPLIERS·↳ AP_SUPPLIER_SITES_ALL·↳ HZ_PARTIES·Explore QA module →
-
Skip Lot results for Receiving
APPS.QA_SKIPLOT_RCV_RESULTS_V·↳ AP_SUPPLIERS·↳ AP_SUPPLIER_SITES_ALL·↳ HZ_PARTIES·Explore QA module →
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
VIEW: APPS.QA_LOOKUPS 12.2.2
-
VIEW: APPS.QA_LOOKUPS 12.1.1
-
SYNONYM: APPS.AP_SUPPLIERS 12.1.1
-
SYNONYM: APPS.AP_SUPPLIERS 12.2.2
-
SYNONYM: APPS.PA_TASKS 12.2.2
-
SYNONYM: APPS.PA_TASKS 12.1.1
-
SYNONYM: APPS.PO_LINES_ALL 12.1.1
-
SYNONYM: APPS.PO_LINES_ALL 12.2.2
-
SYNONYM: APPS.PO_HEADERS_ALL 12.1.1
-
SYNONYM: APPS.PO_HEADERS_ALL 12.2.2
-
eTRM - QA Tables and Views 12.1.1
Define information on applicability of a collection plan for a Quality Collection transaction
-
eTRM - QA Tables and Views 12.2.2
Define information on applicability of a collection plan for a Quality Collection transaction
-
SYNONYM: APPS.HZ_PARTIES 12.2.2
-
SYNONYM: APPS.HZ_PARTIES 12.1.1
-
eTRM - QA Tables and Views 12.1.1
Define information on applicability of a collection plan for a Quality Collection transaction
-
12.2.2 DBA Data 12.2.2
-
eTRM - QA Tables and Views 12.2.2
Define information on applicability of a collection plan for a Quality Collection transaction
-
12.1.1 DBA Data 12.1.1
-
eTRM - PO Tables and Views 12.2.2
Temporary table for tracking a receiving upgrade from Release 9 to Release 10
-
eTRM - PO Tables and Views 12.2.2
Temporary table for tracking a receiving upgrade from Release 9 to Release 10