Search Results gmd_samples_pk




Overview
Explore in AI Chat

Overview

The GMD_SAMPLES table is a core data object within Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the Process Manufacturing (OPM) product family. It belongs to the GMD (Process Manufacturing Product Development) module and serves as the primary repository for quality sample records. In the context of OPM Quality Management, a sample represents a discrete quantity of material collected for inspection and testing. This table is fundamental for tracking the lifecycle of physical samples, from their creation during a sampling event through subsequent laboratory analyses and results recording. Its existence is critical for linking raw material, in-process, and finished good batches to their corresponding quality specifications and test outcomes.

Key Information Stored

The table's structure is designed to uniquely identify and describe each quality sample. Based on the provided metadata, the primary keys are particularly significant for understanding data relationships. The table enforces uniqueness through two primary key constraints: GMD_SAMPLES_PK on SAMPLE_ID (a system-generated unique identifier) and GMD_SAMPLES_U1 on the composite of ORGN_CODE and SAMPLE_NO. This indicates that while each sample has a unique internal ID, the combination of organization code and a user-defined sample number must also be unique within the application. Although the full column list is not provided in the excerpt, typical columns in such a table would include fields for sample status, the date and time of collection, a link to the source batch or lot (BATCH_ID, LOT_NUMBER), the item being sampled (INVENTORY_ITEM_ID), the reason for sampling, the quantity sampled, and references to the sampling plan and specification used.

Common Use Cases and Queries

This table is central to quality assurance workflows. Common operational use cases include creating a new sample record via the Oracle Forms interface, querying all pending samples for a laboratory technician, and tracing quality results back to a specific manufacturing batch. For reporting and data extraction, analysts frequently join GMD_SAMPLES to related inventory and quality tables. A foundational query pattern involves retrieving sample headers for a specific organization and date range:

  • SELECT sample_no, creation_date, sample_status FROM gmd_samples WHERE orgn_code = '&org' AND TRUNC(creation_date) BETWEEN :p_start_date AND :p_end_date ORDER BY creation_date DESC;

Another critical use case is linking a sample to its associated test results, which typically requires a join to tables like GMD_SPECIFICATIONS and GMD_TEST_RESULTS via the SAMPLE_ID.

Related Objects

GMD_SAMPLES is a parent table within a complex quality management data model. Key related objects include:

  • GMD_SAMPLE_SPEC_DISP: Likely stores the specification and disposition details assigned to a sample.
  • GMD_TEST_RESULTS: Child table storing individual analytical results performed on the sample.
  • GMD_SPECIFICATIONS: References the quality standard against which the sample is tested.
  • GMD_SAMPLING_EVENTS: May serve as a parent table, as samples are often collected as part of a defined sampling event.
  • API and Views: Public interfaces such as GMD_QC_SAMPLE_PUB provide validated procedures for creating and updating sample data programmatically, ensuring business rule integrity.