Results for “insp_lot_id”

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

Overview

QA_SKIPLOT_LOT_PLANS is a Quality (QA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores skip lot lot-inspection results per plan. Skip lot inspection is a sampling strategy in which only a defined fraction of incoming lots is inspected, provided that prior lots have met acceptance criteria. This table records the outcome of each lot evaluated against a skip lot plan, capturing status, result, quantities, and dates at the intersection of an inspection lot and a skip lot plan. It therefore serves as the operational record of skip lot decisions applied to receiving inspection activity.

Under the heuristic Data Vault classification mined from the foreign key structure, QA_SKIPLOT_LOT_PLANS is satellite-leaning. This classification is offered as a modeling suggestion: the table behaves as a descriptive satellite attached to the inspection lot/plan relationship rather than as a standalone hub or a pure link. Its primary key, QA_SKIPLOT_LOT_PLANS_PK1, is composite, comprising INSP_LOT_ID and PLAN_ID, which reinforces its role as a per-lot, per-plan detail record.

Key Information Stored

The table contains seventeen documented columns. The most significant are described below, distinguishing key identifiers from descriptive measures.

• INSP_LOT_ID — Surrogate identifier of the inspection lot; part of the composite primary key QA_SKIPLOT_LOT_PLANS_PK1 and a foreign key to QA_SKIPLOT_RCV_RESULTS.
• PLAN_ID — Identifier of the skip lot plan applied to the lot; the remaining component of the composite primary key.
• COLLECTION_ID — Reference to the collection element (such as a specification or collection plan) associated with the inspection.
• ALTERNATE_FLAG — Indicates whether an alternate plan or alternate inspection path was used for this lot.
• SHIPMENT_LINE_ID — Links the record to the receiving shipment line that generated the inspection lot.
• PLAN_INSP_STATUS — Current inspection status of the lot under the plan, driving skip/reinspect decisions.
• PLAN_INSP_RESULT — Outcome of the inspection (for example, accept or reject) at the plan level.
• SAMPLE_SIZE — Number of units selected for inspection under the plan.
• INSPECTED_QTY, ACCEPTED_QTY, REJECTED_QTY — Quantity metrics recording inspected, accepted, and rejected units respectively.
• LAST_INSP_DATE — Date of the most recent inspection activity for the lot/plan combination.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS auditing columns.

The composite primary key (INSP_LOT_ID, PLAN_ID) is mirrored by the unique index QA_SKIPLOT_LOT_PLANS_U1, making that pair the documented business-key candidate. No separate single-column surrogate key is documented.

Common Use Cases and Queries

Typical scenarios include auditing skip lot compliance, reporting acceptance rates by plan, and tracing inspection results back to receiving shipments.

• Retrieve all plan results for a given inspection lot:
  SELECT plan_id, plan_insp_status, plan_insp_result, sample_size FROM qa_skiplot_lot_plans WHERE insp_lot_id = :lot;
• Summarize acceptance and rejection quantities per plan:
  SELECT plan_id, SUM(accepted_qty), SUM(rejected_qty) FROM qa_skiplot_lot_plans GROUP BY plan_id;
• Identify lots awaiting or failing inspection:
  SELECT insp_lot_id, plan_id FROM qa_skiplot_lot_plans WHERE plan_insp_result NOT IN ('ACCEPT');
• Trace results to receiving details by joining on SHIPMENT_LINE_ID or INSP_LOT_ID.
• Report skip lot history with LAST_INSP_DATE filters for periodic quality reviews.

Related Objects

The principal relationship is the foreign key from QA_SKIPLOT_LOT_PLANS.INSP_LOT_ID to QA_SKIPLOT_RCV_RESULTS, which supplies the receiving inspection results for the same lot. The composite primary key also ties each row to a skip lot plan definition through PLAN_ID. Downstream, quality reporting and skip lot decision logic consume PLAN_INSP_STATUS and PLAN_INSP_RESULT to determine whether subsequent lots require full or reduced inspection. Related areas include receiving inspection lot tables, collection/specification tables referenced by COLLECTION_ID, and shipment line records referenced by SHIPMENT_LINE_ID. Together these objects form the receiving-quality chain surrounding the skip lot plan results.