Results for “gmd_sampling_events”

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

Overview

GMD_SAMPLING_EVENTS is the core transaction table for quality sampling events in Oracle Process Manufacturing (OPM) Product Development, part of the GMD schema. It records the outcome of a sampling activity performed against a sampling plan — the request for a given number of samples, the actual quantity taken, and the resulting disposition — and acts as the anchor point for downstream quality activities including sample evaluation, specification disposition, retest/recomposite handling, and material source tracking.

From a modeling perspective, GMD_SAMPLING_EVENTS is best treated as a hub at the center of a star of related detail tables. It is documented as standalone (no parent chain above it), and it is referenced by numerous dependent tables — GMD_SAMPLES, GMD_SS_TIME_POINTS, GMD_SS_VARIANTS, GMD_CHANGE_DISPOSITION, GMD_SS_MATERIAL_SOURCES, GMD_MASS_RESULTS_GT, GMD_EVENT_SPEC_DISP, and MTL_LOT_NUMBERS — each pointing back via SAMPLING_EVENT_ID. Its own foreign keys reach out to QA_SAMPLING_PLANS, GMD_RECIPES_B, GMD_SS_TIME_POINTS, and GMD_SS_VARIANTS, making it a central link between plans, recipes, and detailed sampling structures.

Key Information Stored

The table is documented with 69 physical columns in 12.2.2. The single-column surrogate primary key is SAMPLING_EVENT_ID, defined by index GMD_SAMPLING_EVENTS_PK; no other unique index is documented, so this column is the sole business-key candidate.

• SAMPLING_EVENT_ID — primary key; the join column used by all child tables.
• SAMPLING_PLAN_ID — FK to QA_SAMPLING_PLANS, identifying the governing plan.
• EVENT_TYPE_CODE and EVENT_ID — classify the triggering event and link to its source record.
• RECIPE_ID and FORMULA_ID — FK to GMD_RECIPES_B and the associated formula.
• ITEM_ID, LOT_ID, LOT_NO, SUBLOT_NO — identify the sampled material and lot.
• TIME_POINT_ID and VARIANT_ID — FKs to GMD_SS_TIME_POINTS and GMD_SS_VARIANTS, defining when and how samples are taken.
• SAMPLE_REQ_CNT, SAMPLE_TAKEN_CNT, SAMPLE_ACTIVE_CNT — requested, taken, and active sample quantities.
• DISPOSITION — the quality outcome recorded for the event.
• SAMPLE_ID_TO_EVALUATE and COMPOSITE_ID_TO_EVALUATE — point to the sample or composite selected for evaluation.
• ORG_ID, ORGANIZATION_ID, WHSE_CODE — multi-org and warehouse context.
• SUPPLIER_ID, PO_HEADER_ID, RECEIPT_ID — supplier and receiving context for incoming-material sampling.
• COMPLETE_IND, LOT_RETEST_IND, RECOMPOSITE_IND — status and retest flags.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — standard audit columns supporting date-range reporting.

Common Use Cases and Queries

Typical reporting includes open sampling events by plan, samples taken versus requested, disposition trending, and traceability of sampling to lots and receipts.

• Sampling events for a plan: SELECT sampling_event_id, event_type_code, sample_req_cnt, sample_taken_cnt FROM gmd_sampling_events WHERE sampling_plan_id = :plan_id ORDER BY creation_date;
• Incomplete events by organization: SELECT sampling_event_id, item_id, lot_no FROM gmd_sampling_events WHERE complete_ind = 'N' AND organization_id = :org_id;
• Events for a lot with disposition: SELECT sampling_event_id, lot_no, disposition, sample_taken_cnt FROM gmd_sampling_events WHERE lot_no = :lot_no;
• Samples produced by an event: SELECT s.sample_id FROM gmd_samples s JOIN gmd_sampling_events e ON s.sampling_event_id = e.sampling_event_id WHERE e.sampling_event_id = :id;

Related Objects

The documented FK relationships define the principal dependencies and join paths that matter most:

• QA_SAMPLING_PLANS — via SAMPLING_PLAN_ID; the governing sampling plan.
• GMD_RECIPES_B — via RECIPE_ID; the recipe being sampled.
• GMD_SS_TIME_POINTS — via TIME_POINT_ID; defines sampling time points, and also references this table through SAMPLING_EVENT_ID.
• GMD_SS_VARIANTS — via VARIANT_ID; defines sampling variants (also references this table).
• GMD_SAMPLES — samples produced for the event, joined on SAMPLING_EVENT_ID.
• GMD_CHANGE_DISPOSITION and GMD_EVENT_SPEC_DISP — disposition outcomes tied to the event.
• GMD_SS_MATERIAL_SOURCES and GMD_MASS_RESULTS_GT — material source and mass-result detail referenced by the event.
• MTL_LOT_NUMBERS — inventory lot linkage through SAMPLING_EVENT_ID.