Search Results query_reservation

Overview

APPS.GMI_RESERVATION_PUB is the public PL/SQL API for the Oracle Process Manufacturing (OPM) reservation process. It exposes the reservation operations that OPM applications and external integrations must use to query, create, modify, and move inventory reservations against process manufacturing material. The package is declared AUTHID CURRENT_USER and is classified as a PUB (public) API, meaning its signatures are treated as a supported interface for callers rather than as internal implementation detail. Its stated scope is to contain the global procedures used by the OPM reservation process, and it is documented as version 1.0 with an original creation date of 21-FEB-2000.

In Oracle EBS 12.1.1 and 12.2.2 the package continues to serve as the supported entry point for reservation manipulation in the process manufacturing inventory domain. It encapsulates the business rules that govern whether a reservation is valid, how it is stored, and how it interacts with downstream shipping and delivery data. Because the package carries an AVAILABLE and PUBLIC classification in the ETRM registry, it is also the object most commonly surfaced when users search for reservation-related APIs such as "query_reservation".

Key Procedures and Functions

The package documents five procedures, all of which are declared in the public specification and are therefore callable by external code:

• QUERY_RESERVATION — Retrieves existing reservation records based on caller-supplied criteria. It accepts a validation flag, a query input record, an optional record-locking flag, sorting and cancellation-mode controls, and returns a reservation table plus a count and an error code. This is the procedure most often referenced in searches for "query_reservation".
• CREATE_RESERVATION — Establishes a new reservation for the specified material and demand source, applying the standard API validation and messaging conventions.
• UPDATE_RESERVATION — Modifies the attributes of an existing reservation, such as quantity or reference, while preserving referential integrity.
• DELETE_RESERVATION — Removes a reservation record, releasing the reserved quantity back to available inventory.
• TRANSFER_RESERVATION — Moves a reservation from one demand source or location to another without a full delete-and-recreate cycle.

The specification uses the standard Oracle API conventions: p_api_version_number, p_init_msg_lst, x_return_status, x_msg_count, and x_msg_data, allowing callers to adopt consistent error handling. Query_Reservation additionally uses inv_reservation_global record and table types, and the package header comments note two global variables (organization_id and oe_line_id) used in branching logic.

Tables Accessed

The ETRM metadata records one table referenced by this package through APPS synonyms: WSH_DELIVERY_DETAILS. This is the shipping execution delivery detail table that stores the line-level detail of outbound deliveries. Reservation logic in OPM must reconcile reserved process manufacturing material with the delivery lines to which it is committed, so access to WSH_DELIVERY_DETAILS supports validating that a reservation corresponds to a genuine, shippable demand. Write activity against this table, if any, would be limited to the reservation-related columns that shipping execution expects to see updated.

Usage Notes

GMI_RESERVATION_PUB is intended for programmatic and integration use rather than direct table manipulation. Typical callers include OPM inventory and shipping forms, concurrent programs that perform bulk reservation processing, and custom extensions or third-party integrations that need to create or query reservations without bypassing the supported API layer. The package is referenced by two other packages in the ETRM dependency graph, indicating that it is consumed by additional OPM or shipping logic rather than being an isolated endpoint.

Callers should always pass the API version and initialize the message list, then inspect x_return_status and the message stack before proceeding. Query_Reservation should be used with the validation flag set only when input records are complete, and the lock-records parameter should be reserved for cases where the caller intends to update immediately afterwards. Because the specification exposes oe_line_id as a global used in branching, callers should set context values consistently before invoking the procedures. All calls should be issued against the APPS schema synonyms in 12.1.1 and 12.2.2 so that the standard EBS security and synonym resolution apply.