Results for “qa_skiplot_rcv_results”

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

Overview

QA_SKIPLOT_RCV_RESULTS is a Quality (QA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the outcome of skip lot inspection processing for receiving transactions. Skip lot inspection allows an organization to inspect only a percentage of incoming shipments rather than every receipt, based on predefined acceptance criteria, inspection history, and supplier performance. This table captures the evaluated result for each receiving inspection lot, including whether the lot was inspected, the resulting status, and the quantities involved. It therefore acts as the transactional ledger linking a skip lot decision back to a specific receipt or shipment line.

From a heuristic Data Vault modeling perspective, the FK structure and the presence of a single-column unique key suggest that QA_SKIPLOT_RCV_RESULTS is satellite-leaning: it records descriptive and outcome-oriented attributes that change or persist over the lifecycle of an inspection lot, rather than functioning as a pure hub or a many-to-many link. The primary key QA_SKIPLOT_RCV_RESULTS_PK1 is defined on INSP_LOT_ID, and a unique index QA_SKIPLOT_RCV_RESULTS_U1 also exists on INSP_LOT_ID, confirming that one row exists per inspection lot.

Key Information Stored

The table contains 20 documented columns. The most significant are summarized below.

• INSP_LOT_ID — Surrogate primary key (QA_SKIPLOT_RCV_RESULTS_PK1) and business-key candidate (unique index QA_SKIPLOT_RCV_RESULTS_U1). It identifies the skip lot inspection result record and maps to the inspection lot.
• CRITERIA_ID — Foreign key to QA_SL_SP_RCV_CRITERIA, identifying the skip lot receiving criteria applied to the lot.
• MANUFACTURER_ID — Foreign key to MTL_MANUFACTURERS, capturing the manufacturer associated with the received item.
• PROCESS_ID — Identifier for the skip lot evaluation process run that produced the result.
• INTERFACE_TXN_ID — Reference to the interface transaction that introduced the record for processing.
• SHIPMENT_LINE_ID — Links the result to the receiving shipment line.
• RECEIPT_DATE — Date the underlying receipt was recorded, used for criteria evaluation and reporting.
• LAST_INSP_DATE — Date of the most recent prior inspection, relevant to skip lot frequency logic.
• SOURCE_INSPECTED — Indicator of whether inspection was performed at the source (supplier location).
• LOT_QTY — Quantity associated with the inspection lot.
• TRANSACTED_QTY — Quantity actually transacted against the lot.
• INSPECTION_STATUS — Status of the inspection (for example, pending, complete, or skipped).
• INSPECTION_RESULT — Outcome of the inspection (for example, accept or reject), driving downstream disposition.
• VALID_FLAG — Active/inactive indicator for the record.
• LPN_ID — License plate number reference for warehouse-managed (WMS) receipts.

Standard audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) track record provenance and are common to Oracle EBS tables.

Common Use Cases and Queries

Typical scenarios include auditing skip lot decisions, reporting inspection outcomes, and tracing receipt quantities against skip lot criteria. A representative query joining the criteria definition is shown below.

• Skip lot decision audit: SELECT r.INSP_LOT_ID, r.CRITERIA_ID, r.INSPECTION_STATUS, r.INSPECTION_RESULT, r.RECEIPT_DATE FROM QA.QA_SKIPLOT_RCV_RESULTS r WHERE r.VALID_FLAG = 'Y' AND r.RECEIPT_DATE BETWEEN :from_date AND :to_date;
• Criteria context: join QA_SL_SP_RCV_CRITERIA on CRITERIA_ID to report which skip lot rule drove each result and the resulting accept/reject rates.
• Manufacturer analysis: join MTL_MANUFACTURERS on MANUFACTURER_ID to compare inspection outcomes by supplier/manufacturer.
• Receipt reconciliation: use SHIPMENT_LINE_ID and LOT_QTY/TRANSACTED_QTY to reconcile inspected versus transacted quantities per shipment line.
• Lot plan linkage: join QA_SKIPLOT_LOT_PLANS.INSP_LOT_ID back to this table to relate the plan and the recorded results for the same inspection lot.

Related Objects

The FK relationships documented above identify the principal dependent and referenced objects:

• QA_SL_SP_RCV_CRITERIA — referenced via QA_SKIPLOT_RCV_RESULTS.CRITERIA_ID; defines the skip lot receiving criteria.
• MTL_MANUFACTURERS — referenced via MANUFACTURER_ID; supplies manufacturer details.
• QA_SKIPLOT_LOT_PLANS — references this table via QA_SKIPLOT_LOT_PLANS.INSP_LOT_ID; holds the skip lot plan tied to the inspection lot.
• Receiving interface and shipment line objects — accessed through INTERFACE_TXN_ID and SHIPMENT_LINE_ID for transaction tracing.
• LPN / warehouse objects — accessed through LPN_ID for WMS-integrated receipts.

Collectively, these relationships make QA_SKIPLOT_RCV_RESULTS the central results repository connecting skip lot criteria, lot plans, receipts, and manufacturer data within the Quality module.