Search Results qa_skiplot_plan_states_pk1

Overview

QA_SKIPLOT_PLAN_STATES is a transaction and state-tracking table in the Oracle E-Business Suite Quality (QA) module, owned by the QA schema. It holds the runtime state of skip lot sampling plans used in receiving and inspection. Skip lot processing allows an organization to reduce inspection frequency on a supplier or item once quality performance is proven acceptable, and to automatically revert to tighter inspection when failures occur. This table records where each skip lot process plan currently stands within that logic — the rule in effect, the current round and lot counters, and the most recent receipt outcome that drove the state forward.

Based on the foreign key structure, the metadata suggests a Data Vault classification of link. The table does not behave as a pure reference hub; instead it resolves the association between a skip lot process plan and the receiving criteria that govern it, while carrying the mutable current-state attributes that change with each receipt event. This makes it a stateful intersection between two parent entities rather than an independent master record.

Key Information Stored

The table is composed of 15 documented columns, with the primary key defined by QA_SKIPLOT_PLAN_STATES_PK1 on the composite of PROCESS_PLAN_ID and CRITERIA_ID. A separate unique index, QA_SKIPLOT_PLAN_STATES_U1, covers the same pair (PROCESS_PLAN_ID, CRITERIA_ID), confirming this combination as the business-key candidate that enforces one state row per plan and criteria pairing.

The most significant columns are:

• PROCESS_PLAN_ID — identifies the skip lot process plan whose state is being tracked; foreign key to QA_SKIPLOT_PROCESS_PLANS.
• CRITERIA_ID — identifies the receiving/skip lot criteria applied; foreign key to QA_SL_SP_RCV_CRITERIA.
• CURRENT_RULE — the skip lot rule currently in force for the plan, indicating the active inspection level or skip stage.
• CURRENT_ROUND — the round number within the skip lot cycle, tracking progression through the sampling sequence.
• CURRENT_LOT — the current lot counter used to determine when the next skip or inspection action applies.
• LAST_RECEIPT_LOT_ID — the receipt lot that most recently affected the plan state.
• LAST_RECEIPT_DATE — the date of that most recent receipt event.
• LOT_ACCEPTED — the outcome flag for the last lot, driving whether the plan advances, holds, or resets.
• RULE_START_LOT_ID and RULE_START_DATE — the lot and date on which the current rule began, supporting audit of rule transitions.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard EBS who-audit columns capturing creation and modification history.

Common Use Cases and Queries

Quality and purchasing analysts use this table to determine the current inspection posture for a supplier or item, to report how many lots have been skipped, and to audit rule transitions. A typical query joins the state row to its parents to present plan and criteria context:

• Retrieve current rule and counters for a given plan: SELECT CURRENT_RULE, CURRENT_ROUND, CURRENT_LOT, LOT_ACCEPTED FROM QA_SKIPLOT_PLAN_STATES WHERE PROCESS_PLAN_ID = :plan_id;
• Join to QA_SKIPLOT_PROCESS_PLANS on PROCESS_PLAN_ID and to QA_SL_SP_RCV_CRITERIA on CRITERIA_ID to resolve descriptive plan and criteria attributes.
• Report plans awaiting reset following a rejected lot by filtering on LOT_ACCEPTED = 'N'.
• Audit rule changes by comparing RULE_START_DATE and CURRENT_RULE against LAST_RECEIPT_DATE, or by tracking LAST_UPDATE_DATE across refreshes.

Related Objects

The table's relationships are anchored by its two documented foreign keys and the parent entities they reference:

• QA_SKIPLOT_PROCESS_PLANS — referenced via QA_SKIPLOT_PLAN_STATES.PROCESS_PLAN_ID; the plan configuration this state belongs to.
• QA_SL_SP_RCV_CRITERIA — referenced via QA_SKIPLOT_PLAN_STATES.CRITERIA_ID; the skip lot receiving criteria governing sampling behavior.
• QA_SKIPLOT_PLAN_STATES_PK1 — the primary key constraint enforcing uniqueness on (CRITERIA_ID, PROCESS_PLAN_ID).
• QA_SKIPLOT_PLAN_STATES_U1 — the unique index on (PROCESS_PLAN_ID, CRITERIA_ID) reinforcing the business key.

Downstream, receiving and inspection processes read this state to decide whether a receipt lot is inspected or skipped, and skip lot plan definition and criteria maintenance forms depend on consistent state rows for correct defaulting and progression behavior.