Search Results gmd_samples_lab_pk

Overview

GMD_SAMPLES_LAB is a table in the GMD schema belonging to the Oracle Process Manufacturing (OPM) Product Development module. It represents the OPM Quality Samples Lab entity, storing laboratory sample records associated with quality control operations in process manufacturing environments. In Oracle EBS 12.1.1 and 12.2.2, this table functions as a companion structure to the core samples tables, capturing laboratory organization context for each sample and providing a flexible descriptive attribute framework through the standard DFF-style ATTRIBUTE1 through ATTRIBUTE30 columns.

The ETRM metadata classifies this object heuristically as standalone within a Data Vault modeling context. This suggests that, from a modeling perspective, GMD_SAMPLES_LAB would map to a satellite or hub-satellite construct rather than participating in a heavily joined link structure, since no foreign key relationships are documented beyond its composite primary key.

Key Information Stored

The table contains 39 documented columns. The most important are:

• SAMPLE_ID — Identifier of the quality sample; part of the composite primary key.
• QC_LAB_ORGN_CODE — Quality control laboratory organization code; the second component of the composite primary key and the column most frequently used to filter records by lab.
• TEXT_CODE — Code used to classify or describe the sample/lab record, often tied to a lookup or descriptive flexfield context.
• ATTRIBUTE_CATEGORY — Descriptive flexfield context discriminator that determines which of the 30 attribute columns are meaningful.
• ATTRIBUTE1 through ATTRIBUTE30 — The standard OPM descriptive flexfield segment columns, storing user-defined, client-specific supplemental data such as lab method, sample condition, or analytical results metadata.
• CREATION_DATE, CREATED_BY — Auditing columns capturing row creation information.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Auditing columns capturing the most recent modification.

The surrogate/business key is defined by the unique index GMD_SAMPLES_LAB_PK, comprising (SAMPLE_ID, QC_LAB_ORGN_CODE). This composite key means a single sample may be associated with more than one laboratory organization, so the pair—not SAMPLE_ID alone—uniquely identifies a row.

Common Use Cases and Queries

Typical scenarios include determining which labs processed a given sample, reporting lab activity volumes, and extracting flexfield data for quality reporting. A representative query filtering by lab organization code—the term most often searched by users—is:

• SELECT SAMPLE_ID, QC_LAB_ORGN_CODE, TEXT_CODE, ATTRIBUTE_CATEGORY, ATTRIBUTE1 FROM GMD.GMD_SAMPLES_LAB WHERE QC_LAB_ORGN_CODE = :lab_orgn_code;
• Join to sample master data using SAMPLE_ID to enrich lab records with sample descriptions and statuses.
• Aggregate counts per lab: SELECT QC_LAB_ORGN_CODE, COUNT(*) FROM GMD.GMD_SAMPLES_LAB GROUP BY QC_LAB_ORGN_CODE;
• Extract flexfield values with SELECT SAMPLE_ID, QC_LAB_ORGN_CODE, ATTRIBUTE1, ATTRIBUTE2 FROM GMD.GMD_SAMPLES_LAB WHERE ATTRIBUTE_CATEGORY = :ctx;

Reporting use cases include lab workload analysis, sample traceability audits, and integration extracts feeding external LIMS (Laboratory Information Management Systems). Because the attribute columns are client-configurable, always constrain by ATTRIBUTE_CATEGORY before consuming segment values.

Related Objects

The documented metadata identifies no foreign keys, consistent with the standalone Data Vault classification. Practically, the following objects are the most significant reference points:

• GMD_SAMPLES — The parent sample entity, joined on SAMPLE_ID.
• GMD_SAMPLES_LAB_PK — The unique index enforcing the (SAMPLE_ID, QC_LAB_ORGN_CODE) composite key.
• QC lab organization master (ORG_ORGANIZATION_DEFINITIONS / HR_ORGANIZATION_UNITS) — Provides the organization definition behind QC_LAB_ORGN_CODE.
• GMD_SPEC_TESTS / quality specification tables — Reference analytical specifications applied to samples.
• FND_FLEX_VALUES / FND_FLEX_VALUES_TL — Supply valid values for flexfield attributes and TEXT_CODE lookups.
• OPM quality APIs and concurrent programs in the GMD product that read and write sample lab data.

Because the object is documented as standalone, integration designers should rely on SAMPLE_ID as the practical bridge to broader OPM quality structures rather than expecting enforced referential integrity within GMD_SAMPLES_LAB itself.