Results for “gmp_process_parameters_b”

50+ results




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

Overview

GMP_PROCESS_PARAMETERS_B is the base (non-translated) definition table for process parameters within the Oracle E-Business Suite Process Manufacturing Process Planning module (GMP). It stores the master definitions of the parameters that can be captured against recipes, operations, resources, and plant resources in the process manufacturing environment. Because it holds the language-independent definition rows and is paired with a translation-table counterpart, it follows the standard Oracle EBS MLS (Multi-Language Support) design pattern in which the "_B" table retains descriptive attributes and joins to a "_TL" table for translated text.

From a Data Vault modeling perspective, the FK structure provided in the ETRM metadata is heuristic and hub-leaning: the table is referenced by seven child tables through PARAMETER_ID, making it a natural candidate for a hub entity with satellites that carry the descriptive and audit columns. The physical schema documents 44 columns in Oracle EBS 12.2.2, consistent with the 12.1.1 layout, and the single unique index GMP_PROCESS_PARAM_B_PK on PARAMETER_ID confirms it as the surrogate primary key.

Key Information Stored

The table centers on a small set of business attributes and a large number of descriptive/audit columns:

  • PARAMETER_ID — The surrogate primary key (backed by GMP_PROCESS_PARAM_B_PK); the identifier used by all dependent tables.
  • PARAMETER_NAME — The user-facing name of the process parameter.
  • PARAMETER_TYPE — Classifies the parameter (for example numeric versus text-based), driving how values are validated and stored.
  • MINIMUM_VALUE / MAXIMUM_VALUE — Optional bounds applied to numeric parameters for validation and quality range checks.
  • UNITS — The unit of measure associated with the parameter, where applicable.
  • TEXT_CODE — A lookup or code value linking the parameter to reference data.
  • DELETE_MARK — The standard Oracle soft-delete flag; rows are logically deleted rather than physically removed.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — The standard five audit columns for change tracking.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE30 — The DFF (Descriptive Flexfield) columns that allow customers to extend the parameter definition without schema changes.

Because GMP_PROCESS_PARAMETERS_B is an MLS base table, PARAMETER_NAME and any translated descriptive text are effectively keyed to PARAMETER_ID and surfaced through the companion translation table.

Common Use Cases and Queries

Typical reporting and development scenarios involve enumerating parameters, validating against their bounds, and correlating parameters to the objects they qualify. A simple listing of active parameters uses:

SELECT parameter_id, parameter_name, parameter_type, minimum_value, maximum_value, units FROM gmp.gmp_process_parameters_b WHERE delete_mark = 0;

A range-check query identifies parameters with both bounds defined, useful for quality and specification setup:

SELECT p.parameter_id, p.parameter_name FROM gmp.gmp_process_parameters_b p WHERE p.minimum_value IS NOT NULL AND p.maximum_value IS NOT NULL AND p.delete_mark = 0;

To display the translated name, join the translation table: SELECT b.parameter_id, t.parameter_name FROM gmp_process_parameters_b b, gmp_process_parameters_tl t WHERE b.parameter_id = t.parameter_id AND t.language = USERENV('LANG').

Common use cases include parameter setup maintenance, migration extracts, DFF-based custom attribute reporting, and supporting recipe and operation process specification reports.

Related Objects

The ETRM metadata lists seven dependent tables that reference this table through PARAMETER_ID, indicating its central role:

These relationships confirm that GMP_PROCESS_PARAMETERS_B functions as a reference hub for process parameter definitions, with the dependent tables acting as transactional or association satellites that consume PARAMETER_ID as a foreign key.