Search Results gmd_sampling_plans_b

Overview

GMD_SAMPLING_PLANS_B is the base (B) table that defines OPM Quality Sampling Plans within the Oracle Process Manufacturing Product Development module (GMD). It resides in the GMD schema and carries a VALID status in Oracle EBS 12.1.1 and 12.2.2. In the process manufacturing quality workflow, sampling plans govern how frequently and in what quantities samples are drawn from lots, batches, or received materials during inspection. Each row represents a single sampling plan header, including its sampling quantity rules, frequency logic, and archival/reserve thresholds, which are subsequently referenced by quality specifications and inspection transactions.

From a data modeling perspective, the metadata classifies this object heuristically as standalone based on its foreign key structure. In Data Vault terms this suggests a satellite or reference-style object rather than a true hub, since its documented FK (SAMPLING_PLAN_ID → QA_SAMPLING_PLANS) points outward rather than receiving inbound keys. Practitioners should treat this classification as a modeling suggestion, not a definitive architectural directive.

Key Information Stored

The table documents 52 physical columns. The most operationally significant are:

• SAMPLING_PLAN_ID — surrogate primary key uniquely identifying each sampling plan record.
• SAMPLING_PLAN_NAME — the leading business-key candidate; the human-readable plan name used in specifications.
• SAMPLE_QTY and SAMPLE_QTY_UOM / SAMPLE_UOM — the quantity to be sampled and its unit of measure.
• SAMPLE_CNT_REQ — number of samples required per sampling event.
• FREQUENCY_TYPE, FREQUENCY_CNT, and FREQUENCY_PER — define how often sampling occurs (e.g., every N units, lots, or time periods).
• ARCHIVE_CNT_REQ and ARCHIVE_QTY — retention quantities reserved for archival samples.
• RESERVE_CNT_REQ and RESERVE_QTY — quantities held in reserve for retesting.
• DELETE_MARK — soft-delete flag indicating logical removal.
• MIGRATED_IND — flags records introduced through data migration.
• TEXT_CODE — flexible code reference for extensibility.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–30 — descriptive flexfield (DFF) segments supporting user-defined extensions.

Common Use Cases and Queries

Quality and production reporting frequently joins this table to quality specifications and sampling results to validate compliance. Typical SQL patterns include:

• Retrieving active sampling plans excluding soft-deleted rows: SELECT * FROM GMD.GMD_SAMPLING_PLANS_B WHERE DELETE_MARK = 0;
• Listing plans by frequency logic: SELECT SAMPLING_PLAN_NAME, FREQUENCY_TYPE, FREQUENCY_CNT, FREQUENCY_PER FROM GMD.GMD_SAMPLING_PLANS_B WHERE FREQUENCY_TYPE = :p_type;
• Reporting sample and reserve quantities for audit: SELECT SAMPLING_PLAN_NAME, SAMPLE_QTY, SAMPLE_QTY_UOM, RESERVE_QTY, ARCHIVE_QTY FROM GMD.GMD_SAMPLING_PLANS_B;
• Surfacing migrated plans: ... WHERE MIGRATED_IND = 'Y';

Because of the _B suffix, a corresponding _TL (translation) sibling typically holds language-specific names, so multilingual reporting should join accordingly.

Related Objects

• QA_SAMPLING_PLANS — referenced via SAMPLING_PLAN_ID; the principal quality-management counterpart.
• GMD_SAMPLING_PLANS_TL — translation table for plan names/descriptions in multiple languages.
• GMD_SPEC_SMPL_PLANS (or equivalent specification-to-sample mapping) — associates plans with quality specifications.
• GMD_QUALITY_SPECIFICATIONS — specifications that consume sampling plans during inspection setup.
• GMD_SAMPLE_RESULTS — captures executed sampling outcomes referencing plan identifiers.
• INV_LOTS / GMD_BATCHES — lot and batch entities against which sampling is applied.
• FND_FLEX_VALUES_VL — supports validation of ATTRIBUTE_CATEGORY and DFF segments.

Together these objects form the sampling lifecycle from plan definition through inspection and archival.