Search Results gme_process_parameters




Overview
Explore in AI Chat

Overview

GME_PROCESS_PARAMETERS is a table in the GME schema (Process Manufacturing Process Execution) that stores the actual measured or recorded values of process parameters attached to a resource during batch execution. It is the transactional sibling to the parameter definition setup: where process parameter definitions specify target, minimum, and maximum tolerances for a resource, GME_PROCESS_PARAMETERS records what was actually observed against those definitions on a specific batch step activity and resource.

The table carries 49 documented columns, consistent with a transactional detail row that includes a full 30-column DESCRIPTIVE flexfield block plus standard WHO audit columns. Its primary key is GME_PROCESS_PARAMETERS_PK, defined on the single column PROCESS_PARAM_ID, a system-generated surrogate identifier.

The heuristic Data Vault classification mined from the foreign key structure is standalone, meaning the table does not participate in a classic hub-and-link pattern with other tables in the mined FK set. As a modeling suggestion, this implies the row is best treated as an independent transactional record keyed by its own surrogate, with its dimensional context (batch, step, resource, parameter) carried as descriptive foreign keys rather than as explicit hub references.

Key Information Stored

The most significant columns of GME_PROCESS_PARAMETERS are:

Only PROCESS_PARAM_ID is documented as a unique index and therefore the sole business-key candidate; the remaining columns are descriptive or referential.

Common Use Cases and Queries

Typical usage centers on batch execution reporting, quality exception analysis, and electronic batch record (EBR) extraction. Analysts extract actual versus target values to identify out-of-tolerance process parameters and to satisfy regulatory traceability requirements.

A representative query retrieving all parameter readings for a batch, joined to the step activity, is:

  • SELECT p.process_param_id, p.batch_id, p.batchstep_id, p.batchstep_activity_id, p.parameter_id, p.actual_value, p.target_value, p.minimum_value, p.maximum_value, p.parameter_uom FROM gme.gme_process_parameters p WHERE p.batch_id = :batch_id ORDER BY p.batchstep_activity_id;

An exception report comparing actual against the specification window uses the same columns with a predicate such as WHERE p.actual_value NOT BETWEEN p.minimum_value AND p.maximum_value. Traceability reporting joins to GME_BATCH_STEP_ACTIVITIES on BATCHSTEP_ACTIVITY_ID to attach activity and operation context, and to resource tables via BATCHSTEP_RESOURCE_ID or RESOURCES.

Related Objects

The documented relationships around GME_PROCESS_PARAMETERS are:

  • GME_BATCH_STEP_ACTIVITIES — Referenced by BATCHSTEP_ACTIVITY_ID; the parent step activity definition for each reading.
  • GME_PROCESS_PARAMETERS_MIG — References PROCESS_PARAM_ID; a migration staging table mirroring this structure.
  • GMP_RESOURCE_DEVICE_MESSAGES — References PROCESS_PARAM_ID; device message records linked to a parameter reading, supporting equipment integration.

Because the table is classified as standalone, these are the principal documented dependencies; broader reporting typically reaches batch and resource context indirectly through BATCH_ID, BATCHSTEP_ID, and BATCHSTEP_RESOURCE_ID rather than through further parent tables.