Results for “gmd_samples”

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

Overview

GMD_SAMPLES is the core quality specimen table within the Oracle E-Business Suite Process Manufacturing (OPM) Product Development module. It stores records of physical samples drawn during manufacturing, quality inspection, and receipt processes, capturing the full lifecycle from sample creation through laboratory analysis, approval, and final disposition. In EBS 12.1.1 and 12.2.2 the table resides in the GMD schema and is classified as VALID in the ETRM data dictionary. The table carries 119 documented columns, reflecting its role as a broad transactional record that spans sampling events, inventory references, supplier and customer context, and OPM quality specifications.

Under the heuristic Data Vault classification mined from its foreign key structure, GMD_SAMPLES is identified as a standalone object. From a dimensional modeling perspective this suggests the table behaves as an independent entity rather than a pure hub, link, or satellite, though its foreign key relationships to sampling events, recipes, time points, and variants indicate it also functions as a link between quality execution and product definition. Modelers should treat it as both a transactional fact source and a junction to master quality setup data.

Key Information Stored

The surrogate primary key is SAMPLE_ID, defined by the constraint GMD_SAMPLES_PK. A secondary unique index, GMD_SAMPLES_U1, enforces the business key on ORGN_CODE and SAMPLE_NO, ensuring each sample number is unique within an organization. The most significant columns include:

• SAMPLE_NO and SAMPLE_DESC — the human-readable identifier and description of the sample.
• SAMPLING_EVENT_ID — links the sample to the parent sampling event.
• RECIPE_ID, FORMULA_ID, and FORMULALINE_ID — tie the sample to the OPM recipe or formula under which it was produced.
• ITEM_ID and LOT_ID or LOT_NO — identify the sampled item and its lot or batch.
• SAMPLE_QTY and SAMPLE_UOM — record the quantity drawn and its unit of measure.
• DATE_DRAWN, DATE_RECEIVED, and DATE_REQUIRED — timeline fields for sampling and laboratory workflow.
• SAMPLER_ID, SAMPLE_APPROVER_ID, and INV_APPROVER_ID — identify the personnel responsible for drawing and approving the sample.
• SAMPLE_DISPOSITION and SAMPLE_TYPE — capture the outcome and category assigned to the specimen.
• ORG_ID, ORGANIZATION_ID, and ORGN_CODE — organizational context for multi-org reporting.
• TIME_POINT_ID and VARIANT_ID — connect the sample to stability study time points and variants.
• SAMPLE_INV_TRANS_IND and MIGRATED_IND — control flags for inventory transfer and data migration.

Common Use Cases and Queries

Quality managers routinely query GMD_SAMPLES to track pending laboratory analyses, overdue samples, and disposition decisions. A typical reporting query joins the table to GMD_SAMPLING_EVENTS to obtain event context:

• SELECT s.sample_no, s.date_drawn, s.sample_disposition FROM gmd_samples s WHERE s.orgn_code = :org AND s.date_drawn >= :from_date;
• Joining to GMD_RECIPES_B on RECIPE_ID to trace the formula associated with each sample.
• Aggregating SAMPLE_QTY by ITEM_ID and ORGN_CODE for consumption reporting.
• Filtering on SAMPLE_APPROVER_ID to build workload reports for quality approvers.

Integration scenarios frequently reference SAMPLE_ID when writing analytical results to downstream LIMS interfaces or when reconciling inventory transfers flagged by SAMPLE_INV_TRANS_IND.

Related Objects

The following objects are the most significant dependencies based on the documented foreign key structure:

• GMD_SAMPLING_EVENTS — joined on SAMPLING_EVENT_ID; the parent event record for the sample.
• GMD_RECIPES_B — joined on RECIPE_ID; supplies recipe definition context.
• GMD_SS_TIME_POINTS — joined on TIME_POINT_ID; used in stability study sampling.
• GMD_SS_VARIANTS — joined on VARIANT_ID; defines stability study variants.
• OPM Quality APIs and the Process Manufacturing Product Development module generally use SAMPLE_ID as the reference handle for sample transactions.

Because the table is classified as standalone, no reverse foreign keys from child tables are documented, but application logic and reporting queries commonly treat SAMPLE_ID as a natural reference point for analytical results and disposition records.