Results for “gmd_samples_u1”

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

Overview

GMD.GMD_SAMPLES is the operational master table for quality sampling within the Oracle Process Manufacturing (OPM) Quality Management module of Oracle E-Business Suite 12.1.1 and 12.2.2. Each row represents a discrete physical sample drawn from a lot, batch, formula, recipe, or supplier receipt, and serves as the anchor record linking the sample to laboratory testing, approval workflow, inventory disposition, and eventual retrieval or retention. The table is owned by the GMD schema and resides in the APPS_TS_TX_DATA tablespace with a PCT FREE of 10, indicating a transactional, high-write workload characteristic of shop-floor and warehouse sampling activity.

Heuristic Data Vault classification mined from the foreign-key structure marks GMD_SAMPLES as standalone. In modeling terms, it behaves predominantly as a satellite-like entity attached to several parent hubs (sampling events, recipes, time points, variants) rather than as a pure hub or a many-to-many link. This suggests that a Data Vault implementation would treat SAMPLE_ID as the grain key, with descriptive attributes—quantities, timestamps, approvers, storage locations—carried as satellite columns.

Key Information Stored

The surrogate primary key is SAMPLE_ID, defined by the unique index GMD_SAMPLES_PK in APPS_TS_TX_IDX and populated from a database sequence. Business-key candidates documented through secondary indexes include SAMPLING_EVENT_ID (nonunique, GMD_SAMPLES_N1) and the composite of ORGANIZATION_ID with SAMPLE_NO (nonunique, GMD_SAMPLES_U1). The most significant descriptive columns include:

• SAMPLING_EVENT_ID — parent sampling event that triggered the sample.
• SAMPLE_NO and SAMPLE_DESC — human-readable sampling number and description.
• TYPE and SAMPLE_TYPE — classification of the sample (e.g., retain, stability, in-process).
• ITEM_ID and INVENTORY_ITEM_ID — the item being sampled.
• LOT_ID, LOT_NO, BATCH_ID, and SUBLOT_NO — lot and batch context.
• RECIPE_ID, FORMULA_ID, ROUTING_ID, and OPRN_ID — process context for in-process samples.
• SAMPLE_QTY and SAMPLE_UOM — quantity drawn and its unit of measure.
• SAMPLER_ID and DATE_DRAWN — who drew the sample and when.
• DATE_REQUIRED and DATE_RECEIVED — laboratory scheduling timestamps.
• STORAGE_WHSE, STORAGE_LOCATION, and STORAGE_ORGANIZATION_ID — physical retention location.
• SAMPLE_APPROVER_ID and INV_APPROVER_ID — quality and inventory approval authorities.
• RETAIN_AS — retention flag governing long-term storage.
• ORGANIZATION_ID and ORG_ID — multi-org security boundaries.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE — standard WHO audit columns.
• ATTRIBUTE_CATEGORY through ATTRIBUTE30 — the DFF flexfield block for customer extensions.

Common Use Cases and Queries

Typical reporting scenarios include tracking outstanding samples awaiting laboratory results, reconciling retained samples for stability programs, and auditing approval latency between DATE_DRAWN and DATE_RECEIVED. A representative query retrieving all samples tied to a given org and lot follows:

• SELECT s.SAMPLE_ID, s.SAMPLE_NO, s.SAMPLE_DESC, s.SAMPLE_QTY, s.SAMPLE_UOM, s.DATE_DRAWN FROM GMD.GMD_SAMPLES s WHERE s.ORGANIZATION_ID = :org_id AND s.LOT_NO = :lot_no AND s.DELETE_MARK = 0;
• SELECT s.SAMPLE_ID, s.SAMPLE_NO, e.EVENT_ID FROM GMD.GMD_SAMPLES s JOIN GMD.GMD_SAMPLING_EVENTS e ON e.SAMPLING_EVENT_ID = s.SAMPLING_EVENT_ID WHERE s.DATE_DRAWN >= :from_date;
• SELECT s.SAMPLER_ID, COUNT(*) FROM GMD.GMD_SAMPLES s WHERE s.DELETE_MARK = 0 GROUP BY s.SAMPLER_ID;

Because GMD_SAMPLES carries ORGANIZATION_ID, reports should always be constrained by the active org to satisfy multi-org access and to leverage GMD_SAMPLES_U1. The DELETE_MARK column must be tested in every query to exclude logically deleted rows.

Related Objects

The documented foreign keys identify the primary parents and correlated quality objects: GMD.GMD_SAMPLING_EVENTS joined on SAMPLING_EVENT_ID, GMD.GMD_RECIPES_B joined on RECIPE_ID, GMD.GMD_SS_TIME_POINTS joined on TIME_POINT_ID, and GMD.GMD_SS_VARIANTS joined on VARIANT_ID. Beyond the mined FK set, the columns ITEM_ID, LOT_ID, BATCH_ID, FORMULA_ID, and ORDER_ID imply logical relationships to inventory items, lots, batches, formulas, and sales orders. Functional interfaces such as the OPM Quality sample entry and result maintenance APIs read and write this table, and downstream sample-test result tables key off SAMPLE_ID to record analytical outcomes.