Search Results gmp_parameter_values

Overview

GME_PROCESS_PARAMETERS_PVT is the private implementation package for Process Manufacturing (OPM) process parameter maintenance within Oracle E-Business Suite. In the OPM data model a process parameter defines a measurable attribute — temperature, pressure, pH, concentration, or any other defined characteristic — that applies to a batch, a step, or a specific step activity or resource. The public counterpart, GME_PROCESS_PARAMETERS_PUB, exposes the supported PL/SQL interface to callers; this private package holds the actual procedural logic, validation, and DML that the public wrapper delegates to. The dependencies listed in the ETRM metadata, including FND_API, FND_MSG_PUB, and FND_MESSAGE, confirm that the package observes the standard EBS API error-handling model by raising errors through the Applications message stack rather than relying on native exceptions alone.

Key Procedures and Functions

The documented API surface consists of four procedures, all declared in the package specification and implemented in this body:

• INSERT_PROCESS_PARAMETER — creates a new process parameter record, populating GME_PROCESS_PARAMETERS and the associated GMP_PARAMETER_VALUES rows, and performing the attribute, flexfield, and business-rule validations required before the record is committed.
• UPDATE_PROCESS_PARAMETER — modifies an existing process parameter, allowing changes to parameter values and descriptive attributes while preserving the relationships to the owning batch, step, activity, or resource.
• DELETE_PROCESS_PARAMETER — removes a process parameter and its dependent value rows, applying referential and status checks before removal.
• VALIDATE_PROCESS_PARAM — the reusable validation routine invoked by the insert and update paths to confirm that a supplied parameter instance is valid against the process parameter definition, including key flexfield segments validated through GME_VALIDATE_FLEX_FLD_PVT.

No parameter lists are documented in the metadata; callers should obtain the exact signatures from the package specification in the target EBS instance.

Tables Accessed

The package operates across the OPM batch and parameter schema:

• GME_PROCESS_PARAMETERS — the primary header table holding process parameter instances attached to a batch or batch element.
• GMP_PARAMETER_VALUES — stores the captured values for each parameter; this is the table most often queried by users searching for gmp_parameter_values, and it is written and read directly by this package.
• GMP_PROCESS_PARAMETERS — the parameter definition or template repository against which instance data is validated.
• GME_BATCH_HEADER, GME_BATCH_STEPS, GME_BATCH_STEP_ACTIVITIES, GME_BATCH_STEP_RESOURCES — the batch hierarchy tables used to confirm that the target of a parameter assignment is a valid, existing batch element.

Access to these tables is routed through their corresponding DBL (database library) packages, such as GME_PROCESS_PARAMETERS_DBL and GME_BATCH_HEADER_DBL, consistent with OPM coding standards.

Usage Notes

GME_PROCESS_PARAMETERS_PVT is normally invoked indirectly. OPM batch entry and process parameter forms call the public API, which delegates here; concurrent programs and workflow activities that record or correct parameter data likewise route through the public layer. Custom extensions, interfaces, and unit tests may call the private package directly, but doing so bypasses the public API contract and is not recommended unless the calling code fully manages FND_MSG_PUB initialization and error retrieval. Because the package is not referenced by any other database object per the ETRM dependency report, its dependents are external callers rather than other PL/SQL units, so recompilation gaps are unlikely. The behavior of the four procedures is unchanged between EBS 12.1.1 and 12.2.2; only the online patching and editioning framework around APPS objects differs.