Results for “qa_skiplot_status”

8 results




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

Overview

APPS.QA_SKIPLOT_RCV_RESULTS_V is a reporting view in Oracle E-Business Suite that consolidates skip-lot inspection results generated during the receiving process and enriches them with receipt, purchasing, supplier, item, project, and license plate context. It joins the QA_SKIPLOT_RCV_RESULTS transaction table to lookup views, receiving tables, purchasing tables, and several key flexfield (KFF) views so that inspection outcomes can be reported and integrated without re-implementing the same joins. The view is largely used by Quality, Receiving, and Procurement reporting, and it exposes both the raw inspection codes and their decoded meanings, most notably the INSPECTION_STATUS column derived from the QA_SKIPLOT_STATUS lookup. It is a read-only presentation layer and provides no DML capability.

Underlying Base Objects

The view is defined over QA_SKIPLOT_RCV_RESULTS (synonym) as the driving table, with QSRR aliased as the primary source of inspection data. Execution context comes from QA_SKIPLOT_PROCESSES (PROCESS_CODE/NAME). Lookup decoding uses QA_LOOKUPS twice: QL1 for INSPECTION_STATUS (lookup type QA_SKIPLOT_STATUS) and QL2 for INSPECTION_RESULT (lookup type QA_SKIPLOT_RESULT). Receiving context is supplied by RCV_SHIPMENT_LINES and RCV_SHIPMENT_HEADERS, while procurement context comes from PO_HEADERS_ALL, PO_LINES_ALL, and PO_DISTRIBUTIONS_ALL. Supplier party information is resolved through AP_SUPPLIERS, AP_SUPPLIER_SITES_ALL, and HZ_PARTIES, with the descriptive flexfield views MTL_SYSTEM_ITEMS_KFV and MTL_CATEGORIES_KFV supplying prompted item and category segments. Manufacturer information comes from MTL_MANUFACTURERS, project/task context from PA_TASKS (and PO_DISTRIBUTIONS_TRX_V), and license plate context from WMS_LICENSE_PLATE_NUMBERS. Utility logic is provided by the QA_FLEX_UTIL and PO_CLM_INTG_GRP packages, which supply SALES_ORDER and PROJECT_NUMBER derivations.

Key Columns

Common Use Cases and Queries

Typical uses include monitoring skip-lot acceptance rates by supplier, item, or process, and identifying receipts where inspection was skipped entirely or where results were rejected. A representative query filtering on the documented lookup decoding is:

SELECT INSP_LOT_ID, PROCESS_CODE, INSPECTION_STATUS, INSPECTION_RESULT,
       RECEIPT_NUM, SHIPMENT_NUM, ITEM, PO_NUMBER, VENDOR_NAME, LOT_QTY
  FROM APPS.QA_SKIPLOT_RCV_RESULTS_V
 WHERE INSPECTION_STATUS = 'Skipped'
   AND RECEIPT_DATE >= SYSDATE - 30
 ORDER BY RECEIPT_DATE DESC;

Because the view already resolves VENDOR_NAME, ITEM, CATEGORY_DESC, PROJECT_NUMBER, and LPN, it is well suited to OBIEE/BI Publisher extract queries that would otherwise require duplicating the join logic among QA_SKIPLOT_RCV_RESULTS, RCV_SHIPMENT_LINES, PO_HEADERS_ALL, and the KFF views. It is not intended for transactional updates, and because of the many outer joins (especially to QA_LOOKUPS and QA_SKIPLOT_PROCESSES), users should still include the relevant ORGANIZATION_ID or DATE predicates in ad hoc queries to limit row scope.