Search Results qa_skiplot_association




Overview
Explore in AI Chat

Overview

QA_SKIPLOT_ASSOCIATION is a Quality (QA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the association between skip lot criteria and the inspection processes to which those criteria apply. Skip lot inspection allows a receiving or in-process inspection to be waived for a defined number of lots once a supplier or item has demonstrated a consistent quality history. The criteria that govern when skipping is permitted are defined independently of the processes that consume them, and QA_SKIPLOT_ASSOCIATION is the resolution table that binds the two together, optionally scoped by effective dates, lot size ranges, workflow role, and inspection stage.

From a dimensional modeling perspective, the mined foreign key structure classifies this object heuristically as a link table. It resolves a many-to-many relationship between skip lot criteria and skip lot processes, and its primary key is composed entirely of the two foreign key columns rather than a system-generated surrogate. This classification is offered as a modeling suggestion; the physical implementation is a standard EBS intersection table owned by the QA schema.

Key Information Stored

The table is documented with 13 columns. The most significant are:

The composite primary key (CRITERIA_ID, PROCESS_ID) is the business key: a given criteria definition may be linked to a given process only once in the base key, with effective dating and lot size ranges providing additional contextual variation.

Common Use Cases and Queries

Typical use cases include determining which skip lot criteria apply to a given inspection process, auditing effective-dated configuration changes, and validating lot size coverage before enabling skip lot processing.

A representative query resolves the criteria names for a specific process:

  • SELECT a.criteria_id, a.process_id, a.effective_from, a.effective_to, a.lotsize_from, a.lotsize_to, a.insp_stage FROM qa_skiplot_association a WHERE a.process_id = :process_id AND SYSDATE BETWEEN a.effective_from AND NVL(a.effective_to, SYSDATE + 1);
  • Join to QA_SL_SP_RCV_CRITERIA on CRITERIA_ID to retrieve criteria descriptions and thresholds.
  • Join to QA_SKIPLOT_PROCESSES on PROCESS_ID to present the consuming process name in configuration reports.

Reporting scenarios include a "skip lot setup audit" listing all criteria-process links with effective dates, and a lot size gap analysis identifying ranges not covered by any association.

Related Objects

  • QA_SL_SP_RCV_CRITERIA — Parent table referenced via QA_SKIPLOT_ASSOCIATION.CRITERIA_ID; holds the skip lot criteria definitions.
  • QA_SKIPLOT_PROCESSES — Parent table referenced via QA_SKIPLOT_ASSOCIATION.PROCESS_ID; holds the inspection processes.
  • QA_SKIPLOT_ASSOCIATION_PK1 — The composite primary key constraint on (CRITERIA_ID, PROCESS_ID).
  • QA_SKIPLOT_HEADERS / skip lot transaction tables — Downstream tables that record actual skip decisions, dependent on the criteria-process association being valid.
  • QA Inspection and Receiving APIs — PL/SQL packages that read the association to decide whether an inspection may be skipped at a given stage.