Search Results gmd_operation_resources_pvt




Overview
Explore in AI Chat

Overview

GMD_OPERATION_RESOURCES_PVT is a private PL/SQL package in the Oracle E-Business Suite Process Manufacturing (OPM) product family, owned by the APPS schema and defined with AUTHID CURRENT_USER. It provides the internal implementation layer for maintaining the resource assignments attached to operation activities within a routing or recipe. In Oracle Process Manufacturing, an operation activity (stored in GMD_OPERATION_ACTIVITIES) represents a discrete step in a manufacturing process, and each step can consume or be performed by one or more resources — equipment, labor, or other capacity elements — recorded in GMD_OPERATION_RESOURCES. This private package encapsulates the create, modify, and delete logic for those operation-resource records, keeping the underlying table manipulation out of the public API surface.

The package header carries the version marker 115.3 and was originally authored in September 2002 by Sandra Dulyk, with the most recent header revision dated 25-November-2002. It is classified as a private (PVT) API and is referenced by one other package — the logical counterpart GMD_OPERATION_RESOURCES_PUB, which exposes the public entry points and delegates here. Users searching for delete_operation_resource are typically looking for the procedure that removes a specific resource from an operation activity, so this package is the correct technical target.

Key Procedures and Functions

The package exposes three documented procedures:

  • INSERT_OPERATION_RESOURCES — Creates new resource assignments for a given operation activity. It accepts the operation line identifier and a table-structured payload of resource rows, and returns standard messaging outputs indicating message count, message list, and return status.
  • UPDATE_OPERATION_RESOURCES — Modifies existing resource assignments on an operation activity. It accepts the operation line identifier, a resource identifier, and an update-table structure describing the attributes to change, and likewise returns message count, message list, and return status.
  • DELETE_OPERATION_RESOURCE — Performs the deletion of a specific resource from an operation activity, identified by the operation line identifier and the resource value. Like the other procedures it returns x_message_count, x_message_list, and x_return_status so callers can detect success or failure through the standard EBS API error-handling convention.

All three procedures follow the consistent signature pattern used throughout OPM private APIs: identifier inputs, a structured data payload, and three OUT NOCOPY parameters for diagnostics. No public functions are declared in this package.

Tables Accessed

  • GMD_OPERATION_ACTIVITIES — The operation activity header. The p_oprn_line_id parameter derives from its oprn_line_id column, establishing the parent step to which resources belong.
  • GMD_OPERATION_RESOURCES — The primary transaction table. Insert, update, and delete operations are performed here against the resource rows keyed by operation line and resource.
  • GMD_ACTIVITIES — Accessed to validate or resolve activity context associated with the operation step.
  • PLITBLM — A standard OPM PL/SQL index-by table utility used for bulk message and row handling within the API framework.

Usage Notes

Because this is a private package, it is not intended for direct invocation by end users or external integrations. It is normally called indirectly through GMD_OPERATION_RESOURCES_PUB, which acts as the supported public interface. The most common runtime entry point is the OPM routing and recipe maintenance forms, where users add, change, or remove resources on operation activities; those form events trigger the public wrapper, which delegates to these private procedures. The same private logic can be reached from concurrent programs or custom PL/SQL code that has been granted execute on the APPS synonyms.

When troubleshooting a delete_operation_resource issue, note that the procedure returns status through x_return_status rather than raising unhandled exceptions; the x_message_list should always be inspected for validation failures, such as attempts to delete a resource still referenced elsewhere. Callers should check x_return_status for the standard success indicator and commit or roll back the transaction explicitly, since the procedure performs DML only and does not manage transaction boundaries.