Results for “maximum_value”

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

Overview

GMP_RESOURCE_PARAMETERS is a Process Manufacturing Process Planning table owned by the GMP schema. It defines the association between generic resources and process parameters, allowing planners and process engineers to specify which measurable or controllable parameters apply to a given resource and the acceptable operating ranges for those parameters. In Oracle EBS 12.1.1 and 12.2.2, the object is flagged as VALID within the GMP product family, confirming it remains active in both release lines.

From a Data Vault modeling perspective, the mined heuristic classification for this table is link. This classification is a modeling suggestion rather than a mandated design: the table sits at the intersection of two master entities — resources and process parameters — and its composite unique key carries the association itself. It does not behave as a hub (no single natural business key of its own) and holds only limited descriptive attributes beyond the join keys and range values, which is characteristic of a link table.

Key Information Stored

The documented physical schema contains 11 columns. The most significant are listed below, with the surrogate and business keys distinguished:

• GMP_RESOURCE_PARAM_PK — the primary key, defined as a composite unique index over RESOURCES and PARAMETER_ID. This is the business-key candidate that enforces the one-row-per-resource/parameter pairing.
• RESOURCES — foreign key to CR_RSRC_MST_B, identifying the generic resource to which the parameter is attached.
• PARAMETER_ID — foreign key to GMP_PROCESS_PARAMETERS_B, identifying the process parameter being associated.
• SEQUENCE_NO — ordering value governing the display or processing sequence of parameters for the resource.
• TARGET_VALUE — the nominal or target setpoint for the parameter on this resource.
• MINIMUM_VALUE and MAXIMUM_VALUE — the lower and upper bounds defining the acceptable operating window.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard Oracle EBS audit trail columns, providing who-created/who-updated lineage.

Common Use Cases and Queries

The primary reporting use case is retrieving the complete parameter profile of a resource, typically for process validation, batch execution checks, or engineering review. A representative query joins the resource master and parameter base:

• Resource parameter profile: SELECT rp.RESOURCES, rp.SEQUENCE_NO, pp.PARAMETER_NAME, rp.TARGET_VALUE, rp.MINIMUM_VALUE, rp.MAXIMUM_VALUE FROM GMP_RESOURCE_PARAMETERS rp JOIN GMP_PROCESS_PARAMETERS_B pp ON pp.PARAMETER_ID = rp.PARAMETER_ID WHERE rp.RESOURCES = :resource_id ORDER BY rp.SEQUENCE_NO;
• Reverse lookup by parameter: query GMP_RESOURCE_PARAMETERS filtered on PARAMETER_ID to identify every resource governed by a given parameter.
• Range validation and exception reporting: flag rows where TARGET_VALUE falls outside MINIMUM_VALUE/MAXIMUM_VALUE, or where bounds are null.
• Audit reporting: use CREATED_BY and LAST_UPDATED_BY to trace configuration changes over time.

Related Objects

The table participates in two documented foreign key relationships and is central to resource-parameter configuration:

• CR_RSRC_MST_B — joined via GMP_RESOURCE_PARAMETERS.RESOURCES = CR_RSRC_MST_B.RESOURCES; the resource master holding resource definitions.
• GMP_PROCESS_PARAMETERS_B — joined via GMP_RESOURCE_PARAMETERS.PARAMETER_ID = GMP_PROCESS_PARAMETERS_B.PARAMETER_ID; the parameter base table supplying names and definitions.
• Resource and parameter translation tables (GMP_PROCESS_PARAMETERS_TL patterns) provide localized descriptions for reporting.
• Process planning and routing objects that reference resources consume this table indirectly when resolving operating ranges.