Results for “maximum_value”

50+ results




Overview
Explore in AI Chat

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

Overview

GMD_OPRN_PROCESS_PARAMETERS_V1 is an APPS-owned database view within the Oracle E-Business Suite Process Manufacturing (GMD) module, specifically the Process Manufacturing Product Development product. The view resolves the effective set of process parameters that apply to an operation resource by merging two sources: parameter values defined explicitly at the operation resource level (overrides) and parameter values inherited from the generic resource definition. Its name reflects this dual purpose — it joins the overrides originating from the operation resource and the generic resource to present a single, unified result set.

Because process parameters control target, minimum, and maximum values used during manufacturing execution and quality evaluation, this view plays a critical role in reporting and integration. Rather than requiring downstream consumers to reproduce the inheritance logic manually, the view encapsulates it, allowing reports, interfaces, and custom extensions to obtain the effective parameter set for each operation line with a single query.

Underlying Base Objects

The documented ETRM metadata identifies the view's referenced base objects as synonym-backed tables: GMD_OPRN_PROCESS_PARAMETERS, GMD_OPERATION_RESOURCES, and GMP_RESOURCE_PARAMETERS. Structurally, the view text is a UNION of two SELECT statements:

  • Operation override branch (OPERATION_OVERRIDE = 1): Joins GMD_OPRN_PROCESS_PARAMETERS (alias O) to GMP_RESOURCE_PARAMETERS (alias R) on RESOURCES and PARAMETER_ID, taking the explicit operation-level values from O while drawing SEQUENCE_NO from the generic resource parameter.
  • Inherited branch (OPERATION_OVERRIDE = 0): Selects from GMP_RESOURCE_PARAMETERS joined to GMD_OPERATION_RESOURCES, returning generic resource parameter values only where no matching override exists in GMD_OPRN_PROCESS_PARAMETERS. This is enforced by a NOT EXISTS subquery keyed on RESOURCES, PARAMETER_ID, and OPRN_LINE_ID.

This design ensures that operation-level overrides take precedence over generic resource parameters, but only where an override is actually defined; elsewhere the generic values are surfaced. Notably, the inherited branch sources OPRN_LINE_ID from GMD_OPERATION_RESOURCES, whereas the override branch sources it from GMD_OPRN_PROCESS_PARAMETERS.

Key Columns

  • OPERATION_OVERRIDE: Discriminator flag. A value of 1 indicates an operation-specific override from GMD_OPRN_PROCESS_PARAMETERS; 0 indicates an inherited generic value from GMP_RESOURCE_PARAMETERS.
  • OPRN_LINE_ID: Identifier of the operation line to which the resource and its parameters belong.
  • RESOURCES: Identifier of the resource (for example, a generic resource) associated with the parameter.
  • PARAMETER_ID: Identifier of the process parameter being evaluated.
  • SEQUENCE_NO: Ordering sequence, derived from GMP_RESOURCE_PARAMETERS in the override branch, and from the same source in the inherited branch.
  • TARGET_VALUE, MINIMUM_VALUE, MAXIMUM_VALUE: The parameter's target, lower bound, and upper bound values. In the operation override branch these originate from the operation-level record; in the inherited branch they originate from the generic resource parameter.
  • Audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN): Standard audit attributes. Because the view is a UNION, these reflect the underlying record that produced each row (the override record or the generic resource parameter record, respectively).

Common Use Cases and Queries

The view supports operational reporting, parameter auditing, and integration of effective parameter values into downstream systems. A frequent requirement is to identify which operation lines have overridden a generic resource parameter and which still inherit the generic value. The OPERATION_OVERRIDE flag answers this directly:

  • Inspect all overrides for an operation line: SELECT oprn_line_id, resources, parameter_id, target_value, minimum_value, maximum_value FROM gmd_oprn_process_parameters_v1 WHERE oprn_line_id = :oprn_line_id AND operation_override = 1 ORDER BY sequence_no;
  • Inspect inherited parameters (no override): use the same query with operation_override = 0 to isolate rows that exist only through inheritance from the generic resource.
  • Compare effective values against generic defaults: join the view (operation_override = 1) back to GMP_RESOURCE_PARAMETERS on RESOURCES and PARAMETER_ID to compare the operation target and limits against the generic target and limits.
  • Resolve effective parameter limits for a resource: query the view filtered by RESOURCES and PARAMETER_ID to obtain the applicable TARGET_VALUE, MINIMUM_VALUE, and MAXIMUM_VALUE, honoring precedence automatically without writing custom UNION logic.

Because the object is a view, it carries no storage of its own and reflects the current state of the underlying tables at query time. The user's original search term, "gmp_resource_parameters," maps directly to GMP_RESOURCE_PARAMETERS, one of the three referenced base objects, confirming that the view is the appropriate integration point for consolidating generic resource parameters with their operation-level overrides.