Search Results insert_process_parameter

Overview

GME_PROCESS_PARAMETERS_PVT is a private PL/SQL package in the Oracle EBS Process Manufacturing (OPM) product family. Its business purpose is to manage the process parameter records associated with batch steps and batch step activities. Process parameters capture the specific values, targets, and specifications that govern how a batch step executes — for example, temperature, pressure, pH, or quantity ranges that a step must satisfy. This package provides a programmatic API layer for inserting, updating, deleting, and validating those parameter records against the underlying GME and GMP schema tables.

The package is declared with AUTHID CURRENT_USER, and the source header indicates it was authored in 2005 (GMEVPPRS.pls version 120.1). It is classified as a PVT package, meaning it is an internal, private API. It is not intended to be called directly by end users or external integrations; rather it is invoked by other OPM packages and forms that require process parameter manipulation and validation. The ETRM metadata records that the package is referenced by one other package.

Because the parameters default to NULL and validation of descriptive flexfields is controlled by p_validate_flexfields, the procedures are designed to be flexible for both single-record maintenance and bulk operations driven by higher-level business logic.

Key Procedures and Functions

The package exposes four documented procedures, each corresponding to a standard DML operation on process parameters:

• INSERT_PROCESS_PARAMETER — Creates a new process parameter record for a given batch, organization, batch step, activity, and parameter. It accepts the parameter record as a row type and returns the persisted record along with a return status.
• UPDATE_PROCESS_PARAMETER — Modifies an existing process parameter record. This is the procedure a user locates when searching for "update_process_parameter." It identifies the target record using batch number, organization code, batch step number, activity, and parameter name, then applies the supplied changes and returns the updated record and status.
• DELETE_PROCESS_PARAMETER — Removes a process parameter record identified by the same key attributes, returning only a return status.
• VALIDATE_PROCESS_PARAM — Performs referential and business validation prior to DML. It resolves organization, batch, batch step, activity, resource, and parameter identifiers into their internal IDs and returns step status and return status, but does not itself persist data.

All three DML procedures share a signature pattern: descriptive key parameters followed by a gme_process_parameters%ROWTYPE input record and an output record (except delete), and an x_return_status out parameter. The validate procedure uses scalar IN parameters and a series of numeric OUT parameters for resolved identifiers.

Tables Accessed

The package reads and writes the following tables via APPS synonyms:

• GME_PROCESS_PARAMETERS — The primary table holding process parameter records; the target of insert, update, and delete operations.
• GME_BATCH_HEADER, GME_BATCH_STEPS, GME_BATCH_STEP_ACTIVITIES, GME_BATCH_STEP_RESOURCES — Batch structure tables used during validation to resolve the batch, step, activity, and resource context for a parameter.
• GMP_PARAMETER_VALUES, GMP_PROCESS_PARAMETERS — Parameter definition and value tables used to validate the parameter name and its associated values.

These tables together represent the OPM batch execution and process parameter data model.

Usage Notes

GME_PROCESS_PARAMETERS_PVT is normally invoked indirectly. Higher-level OPM packages, batch execution forms, or orchestration logic call these procedures to maintain process parameter records as batches are defined, released, or updated. Because the package is private and AUTHID CURRENT_USER, custom code calling it must run under an APPS schema context with appropriate privileges.

Developers customizing OPM batch logic should prefer calling the supported public API where one exists; direct use of this PVT package carries upgrade risk, as its signature is not a public commitment. When invoked, callers should always inspect x_return_status against FND_API constants to detect failures, and should supply p_validate_flexfields as fnd_api.g_true when descriptive flexfield validation is required.