Search Results assay_class

Overview

GMD_QC_ASSAY_CLASS is a table in the Oracle E-Business Suite Process Manufacturing Product Development (GMD) schema. It stores Quality Assay Class definitions, where an assay class represents a logical grouping of quality tests. Assay classes allow quality specifications to be organized by category — for example, chemical, physical, or microbiological test groupings — so that tests are applied, inherited, and reported consistently across formulas and products. The table is marked VALID in the ETRM 12.2.2 physical schema and contains 41 documented columns.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign-key structure is standalone. In practice this suggests GMD_QC_ASSAY_CLASS can be modeled as a hub-like reference entity: its business key is the assay class code itself, and descriptive columns (description, text code, attributes) are said to function as satellite-style descriptive data. The classification is a modeling suggestion only; the table is not physically implemented with generated surrogate hub keys beyond the primary key described below.

Key Information Stored

The primary key is defined by constraint GMD_QC_ASSAY_CLASS_PK over the column ASSAY_CLASS. Notable columns include:

• ASSAY_CLASS — the primary key and the business identifier for the assay class grouping.
• ASSAY_CLASS_DESC — the descriptive name or label presented to users.
• TEXT_CODE — a short code/abbreviation used for display or lookup purposes.
• TRANS_CNT — transaction counter, typically maintained by Process Manufacturing logic.
• DELETE_MARK — soft-delete indicator used instead of physical row deletion.
• MIGRATION_STATUS — status flag used during data migration or conversion activity.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE30 — the standard Oracle EBS descriptive flexfield (DFF) columns, providing extensible customer-defined fields.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit (WHO) columns.

The surrogate-vs-business-key distinction is straightforward here: ASSAY_CLASS serves as both the primary key and the business key candidate, since no separate generated sequence column is documented.

Common Use Cases and Queries

Assay classes are queried for quality setup, specification control, and reporting. Typical uses include listing available classes for a lookup, resolving descriptions for reporting, and validating that a referenced class is active.

• List active (non-deleted) assay classes:

  SELECT ASSAY_CLASS, ASSAY_CLASS_DESC, TEXT_CODE FROM GMD_QC_ASSAY_CLASS WHERE DELETE_MARK = 0;

• Resolve a description for a specific class:

  SELECT ASSAY_CLASS_DESC FROM GMD_QC_ASSAY_CLASS WHERE ASSAY_CLASS = :p_class;

• Report on customer DFF values:

  SELECT ASSAY_CLASS, ATTRIBUTE_CATEGORY, ATTRIBUTE1 FROM GMD_QC_ASSAY_CLASS;

• Audit recently changed rows using LAST_UPDATE_DATE and LAST_UPDATED_BY.
• Identify rows pending migration via MIGRATION_STATUS.

Related Objects

The ETRM metadata classifies this table as standalone, meaning no foreign-key relationships were mined. Nonetheless, in the broader GMD quality model it is referenced conceptually by related setup and specification objects. Significant objects include:

• GMD_QC_ASSAY_CLASS-based lookups and value sets — used by form and DFF validation.
• Quality test/specification tables in GMD — which group or reference assay classes when defining test groupings.
• GMD_QC_ASSAY_CLASS_PK — the primary key constraint over ASSAY_CLASS.
• Process Manufacturing HTML/forms UI — which consumes assay classes for specification maintenance.

Because the documented relationship data shows no enforced foreign keys, joins to downstream quality test objects are business-key based on ASSAY_CLASS and should be validated against the specific GMD quality table used.