Search Results qa_skiplot_plan_states_u1

Overview

QA.QA_SKIPLOT_PLAN_STATES is a transactional table in the Oracle E-Business Suite Quality Management (QA) schema that persists the runtime state of skip lot inspection plans. In Oracle EBS releases 12.1.1 and 12.2.2, skip lot inspection allows an organization to reduce the frequency of incoming or in-process inspections based on a defined sampling rule that alternates between inspecting and skipping lots. While the static definition of a skip lot plan is maintained in QA_SKIPLOT_PROCESS_PLANS and its associated criteria in QA_SL_SP_RCV_CRITERIA, the current position of each plan-criteria combination within its rule sequence is held in QA_SKIPLOT_PLAN_STATES. This table therefore acts as the operational memory of the skip lot engine, recording which rule step is active, how many rounds and lots have elapsed, and the outcome of the most recent receipt so that the next transaction can be evaluated correctly.

Under the heuristic Data Vault classification mined from the foreign key structure, this table is best modeled as a link. It resolves the association between a skip lot process plan (PROCESS_PLAN_ID) and its sampling criteria (CRITERIA_ID), and the intersection of those two keys forms the natural business key of the relationship. The date-stamped, WHO-audited attributes can be viewed as satellite-style descriptive context attached to that link.

Key Information Stored

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

• PROCESS_PLAN_ID and CRITERIA_ID — the composite business-key candidates. Together they are enforced by the unique index QA_SKIPLOT_PLAN_STATES_U1, and they also constitute the primary key QA_SKIPLOT_PLAN_STATES_PK1 (CRITERIA_ID, PROCESS_PLAN_ID). PROCESS_PLAN_ID is a foreign key to QA_SKIPLOT_PROCESS_PLANS; CRITERIA_ID is a foreign key to QA_SL_SP_RCV_CRITERIA.
• CURRENT_RULE — the sequence number of the rule currently active within the skip lot plan's rule set.
• CURRENT_ROUND — the round counter indicating how many complete rule cycles have been executed for this plan-criteria pair.
• CURRENT_LOT — the running lot counter used by the engine to determine whether the next receipt falls in an inspect or skip position.
• LOT_ACCEPTED — a flag recording whether the most recently evaluated lot was accepted or rejected; this value drives advancement or reset of the rule sequence.
• LAST_RECEIPT_LOT_ID and LAST_RECEIPT_DATE — identification and timestamp of the last receipt processed against this plan.
• RULE_START_LOT_ID and RULE_START_DATE — the lot and date on which the current skip rule began, providing traceability for the active state.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns showing who created and last modified the row.

Common Use Cases and Queries

The primary use case is operational: during receipt or inspection processing, the skip lot engine reads the state row for a given plan and criteria to decide whether the inbound lot must be inspected or may be skipped, then writes back the updated counters. Analysts and quality engineers query the table to audit plan behavior and reconcile inspection results. A typical retrieval query is:

• SELECT PROCESS_PLAN_ID, CRITERIA_ID, CURRENT_RULE, CURRENT_ROUND, CURRENT_LOT, LOT_ACCEPTED, LAST_RECEIPT_DATE FROM QA.QA_SKIPLOT_PLAN_STATES WHERE PROCESS_PLAN_ID = :plan_id;
• Reporting on plans stalled at a given round: SELECT * FROM QA.QA_SKIPLOT_PLAN_STATES WHERE CURRENT_ROUND > :threshold;
• Identifying plans whose last receipt was rejected: SELECT * FROM QA.QA_SKIPLOT_PLAN_STATES WHERE LOT_ACCEPTED = 2; (values reflect application lookups).
• Trending skip activity by joining LAST_RECEIPT_DATE to receipt history for skip-frequency analysis.

The non-unique index QA_SKIPLOT_PLAN_STATES_N1 on CRITERIA_ID supports queries that retrieve states across all plans sharing a criteria definition.

Related Objects

• QA.QA_SKIPLOT_PROCESS_PLANS — referenced via PROCESS_PLAN_ID; holds the parent plan definition.
• QA.SL_SP_RCV_CRITERIA — referenced via CRITERIA_ID; defines the sampling/skip criteria applied.
• QA.QA_SKIPLOT_PLAN_STATES# — the underlying base table object referenced by the synonym.
• Receiving and inspection tables keyed by LAST_RECEIPT_LOT_ID and RULE_START_LOT_ID supply the lot context for state transitions.
• Skip lot plan and criteria tables joined through the composite key form the complete view of a plan's configuration and runtime state.