Results for “qa_sl_sp_rcv_criteria”

50+ results




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

Overview

The QA.QA_SL_SP_RCV_CRITERIA table is a Quality Management data object within Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2. It stores the skip lot and sampling criteria definitions that govern receiving inspection decisions. A row in this table represents a discrete criteria set identified by CRITERIA_ID and scoped to an inventory organization, which Oracle's sampling and skip lot engines then evaluate against incoming receipts. Its role is to determine whether a shipment is subject to inspection, how many samples are drawn, and whether a lot can be skipped based on prior quality history.

From a Data Vault modeling heuristic, the FK topology—one unique key (CRITERIA_ID) with a single outbound reference to MTL_MANUFACTURERS and multiple inbound references from association, state, and history tables—suggests a hub-leaning classification. In practice the table behaves as a durable business key container surrounded by its own satellites (association, state, and history tables) rather than as a transactional link.

Key Information Stored

The surrogate primary key CRITERIA_ID, backed by unique index QA_SL_SP_RCV_CRITERIA_U1 and the constraint QA_SL_SP_RCV_CRITERIA_PK1, uniquely identifies each criteria record and is also the business-key candidate. The table documents 15 columns; the most consequential are:

Collectively, ORGANIZATION_ID through TASK_ID form the composite matching key Oracle evaluates when resolving which criteria apply to a given receiving transaction.

Common Use Cases and Queries

Typical scenarios include reviewing which criteria are active for a supplier/item combination, tracing why a lot was skipped, and reconciling criteria against the state tables that drive skip lot counters.

  • Criteria lookup by item and vendor: SELECT criteria_id, organization_id, vendor_id, item_id FROM qa.qa_sl_sp_rcv_criteria WHERE item_id = :item AND vendor_id = :vendor;
  • Organization-level review of defined rules: SELECT criteria_id, item_category_id, manufacturer_id FROM qa.qa_sl_sp_rcv_criteria WHERE organization_id = :org;
  • Impact analysis before change: join to QA_SKIPLOT_ASSOCIATION to see which skip lot plans consume a criteria row.
  • Audit and compliance reporting: use CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE to report when criteria were introduced or altered.

Because criteria are matched on organization, vendor, item, category, and project dimensions, reporting queries should filter on the most selective of these columns first and confirm the organization context.

Related Objects

The table participates in several quality relationships, all joined on CRITERIA_ID:

  • QA_SAMPLING_ASSOCIATION — links criteria to sampling plans via CRITERIA_ID.
  • QA_SKIPLOT_ASSOCIATION — associates criteria with skip lot plans.
  • QA_SKIPLOT_PLAN_STATES — holds current skip lot state per criteria.
  • QA_SKIPLOT_RCV_RESULTS — records receiving results evaluated against the criteria.
  • QA_SKIPLOT_STATE_HISTORY — historical state transitions keyed by CRITERIA_ID.
  • MTL_MANUFACTURERS — referenced through the MANUFACTURER_ID foreign key.

These objects form the operational backbone of receiving skip lot processing; correct maintenance of QA_SL_SP_RCV_CRITERIA is a prerequisite for accurate sampling and skip lot behavior.