Results for “gmp_parameter_values_b”

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

Overview

GMP_PARAMETER_VALUES_B is a base table within the GMP schema, owned by the Oracle Process Manufacturing Process Planning module (GMP). It stores the permissible parameter values that may be assigned to a process parameter during process planning and execution. In the EBS 12.1.1 and 12.2.2 data model, this table acts as the value-domain definition layer that constrains the set of valid entries a planner can select for any given process parameter defined in GMP_PROCESS_PARAMETERS_B.

Under a heuristic Data Vault classification, GMP_PARAMETER_VALUES_B exhibits satellite-leaning characteristics. Its primary key is composite, combining PARAMETER_ID and PARAMETER_VALUE, which indicates the table functions primarily as a descriptor of allowable values attached to a parent parameter entity rather than as an independent hub of business identity. The PARAMETER_ID column carries the foreign-key relationship back to the parent parameter definition, reinforcing the satellite interpretation.

Key Information Stored

The documented physical schema for GMP_PARAMETER_VALUES_B contains seven columns. The most significant are:

• PARAMETER_ID — Part of the composite primary key (GMP_PARAM_VALUES_B_PK) and a foreign key to GMP_PROCESS_PARAMETERS_B. Identifies the process parameter to which the value belongs.
• PARAMETER_VALUE — The second component of the composite primary key. Holds the specific allowable value associated with the parent parameter.
• CREATED_BY — The user identifier responsible for creating the row.
• CREATION_DATE — Timestamp of row creation.
• LAST_UPDATED_BY — The user identifier of the most recent update.
• LAST_UPDATE_DATE — Timestamp of the most recent modification.
• LAST_UPDATE_LOGIN — Login identifier associated with the last update, used for audit and concurrency tracking.

The unique index GMP_PARAM_VALUES_B_PK on (PARAMETER_ID, PARAMETER_VALUE) represents the business-key candidate: no duplicate value may exist for the same parameter. The table does not employ a single-column surrogate key; identity is expressed entirely through the composite business key. The final four columns are standard EBS "WHO" audit columns maintained automatically by the application framework.

Common Use Cases and Queries

Typical reporting and configuration scenarios include retrieving the list of permissible values for a specific parameter, validating parameter entries before loading process plans, and auditing parameter value assignments across recipes and batches. A representative query pattern is:

• Listing values for a parameter: SELECT parameter_value FROM gmp_parameter_values_b WHERE parameter_id = :p_id ORDER BY parameter_value;
• Auditing changes within a date range: filter on LAST_UPDATE_DATE and LAST_UPDATED_BY to trace configuration drift.
• Joining to the parent definition: SELECT p.parameter_id, p.parameter_name, v.parameter_value FROM gmp_process_parameters_b p, gmp_parameter_values_b v WHERE p.parameter_id = v.parameter_id; (column names on the parent should be confirmed against that table's own documentation).

These queries support configuration reviews, migration validation between environments, and data-quality checks prior to process plan deployment.

Related Objects

• GMP_PROCESS_PARAMETERS_B — Parent table. Joined on GMP_PARAMETER_VALUES_B.PARAMETER_ID = GMP_PROCESS_PARAMETERS_B.PARAMETER_ID.
• GMP_PARAMETER_VALUES_TL — Translation table. References GMP_PARAMETER_VALUES_B through the composite key columns PARAMETER_ID and PARAMETER_VALUE, supplying language-specific value descriptions.
• GMP_PARAM_VALUES_B_PK — The primary-key constraint/index enforcing uniqueness of PARAMETER_ID and PARAMETER_VALUE.
• GMP_PROCESS_PARAMETERS_TL — Companion translation table to the parent parameter definition, frequently joined alongside these objects for multilingual reporting.

Together these objects form the parameter definition and value-domain layer within Process Manufacturing Process Planning, and any extraction or integration touching parameter values should account for the parent-child and translation relationships described above.