Search Results qa_sampling_plans




Overview
Explore in AI Chat

Overview

QA.QA_SAMPLING_PLANS is the master reference table for sampling plan definitions in the Oracle E-Business Suite Quality (QA) module. A sampling plan specifies the statistical rules by which a lot, batch, or inventory quantity is translated into a required number of sample units and the acceptance or rejection criteria applied to the inspected population. The table is central to Quality inspection execution, since sampling plans govern how much material must be drawn and tested before a disposition decision can be reached.

The object carries a status of VALID in the QA schema and is documented for both EBS 12.1.1 and 12.2.2. Its primary key index is QA_SAMPLING_PLANS_PK1 on SAMPLING_PLAN_ID, and the documented physical schema for 12.2.2 lists twelve columns. Because the table is referenced by a large number of foreign keys and is not itself dependent on a parent entity for its identity, the ETRM metadata heuristic classifies it as hub-leaning in a Data Vault model — a modeling suggestion indicating that QA_SAMPLING_PLANS behaves as a durable business entity rather than a transactional or associative record.

Key Information Stored

Each row defines one sampling plan, identified internally by the surrogate primary key SAMPLING_PLAN_ID. The user-facing business key is captured by the unique index QA_SAMPLING_PLANS_U2 on SAMPLING_PLAN_CODE; a second unique index, QA_SAMPLING_PLANS_U1, corresponds to SAMPLING_PLAN_ID itself. The most significant columns include:

  • SAMPLING_PLAN_ID — surrogate primary key and the value propagated to every referencing table.
  • SAMPLING_PLAN_CODE — the unique, user-visible identifier for the plan.
  • DESCRIPTION — free-text description of the plan's purpose or scope.
  • ORGANIZATION_ID — the inventory organization to which the plan belongs, enforcing multi-org partitioning.
  • INSP_LEVEL_CODE — the inspection level (for example, tightened, normal, or reduced) that selects the appropriate sampling intensity.
  • SAMPLING_STD_CODE — the sampling standard on which the plan is based (such as ANSI/ASQ Z1.4 or an ISO variant).
  • AQL — the Acceptable Quality Level, the defect-rate threshold used to compute accept/reject numbers.
  • Audit columns LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN — standard WHO-column tracking of row creation and modification.

Common Use Cases and Queries

Sampling plans are surfaced during inspection setup, specification linkage, and quality reporting. Typical queries resolve a plan code to its governing parameters for a given organization, or join plans to the specifications and events that consume them.

  • Plan lookup by code and organization: SELECT sampling_plan_id, sampling_plan_code, description, aql, insp_level_code FROM qa_sampling_plans WHERE sampling_plan_code = :code AND organization_id = :org_id;
  • Reporting all active plans ordered by AQL: SELECT sampling_plan_code, aql, sampling_std_code FROM qa_sampling_plans ORDER BY aql;
  • Usage analysis joining to associations: SELECT p.sampling_plan_code, a.* FROM qa_sampling_plans p, qa_sampling_association a WHERE p.sampling_plan_id = a.sampling_plan_id;
  • Cross-module reconciliation against process manufacturing specifications and sampling events via GMD_* views.

Related Objects

QA_SAMPLING_PLANS is referenced by numerous dependent tables, confirming its hub role. The most significant are: