Results for “inv_reservation_pub”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
INV_RESERVATION_PUB is the public application programming interface for material reservation processing within Oracle Inventory. Owned by the APPS schema and classified as a PUB API, it exposes a stable, supported entry point through which external modules and custom code create, modify, and release reservations against inventory on-hand quantity. Its principal internal consumer is Oracle Order Management, which draws down available stock to guarantee fulfillment against sales order lines, but the same interface is used by any EBS module that needs to hard-allocate inventory to a demand source before picking and shipping occur. The package body is a wrapper layer: it validates inputs, resolves profile options and messages, and delegates the substantive transactional work to the private package INV_RESERVATION_PVT. This separation keeps the published signature stable across releases while allowing the reservation engine itself to evolve. In the ETRM 12.2.2 repository the body is VALID, is referenced by 55 other database objects, and depends on FND_API, FND_MSG_PUB, FND_PROFILE, INV_LOG_UTIL, INV_RESERVATION_GLOBAL, and INV_RESERVATION_PVT.
Key Procedures and Functions
- CREATE_RESERVATION — Establishes a reservation linking a demand source to a specific inventory location, lot, revision, and quantity, thereby reducing available on-hand for other demand.
- UPDATE_RESERVATION — Modifies attributes of an existing reservation, such as reserved quantity or detail-level allocation, without terminating the reservation record.
- DELETE_RESERVATION — Removes a reservation that is no longer required, returning the affected quantity to available on-hand.
- RELIEVE_RESERVATION — Releases or consumes reserved quantity, typically when shipment or issue processing relieves the reservation rather than deleting it outright.
- TRANSFER_RESERVATION — Moves an existing reservation from one inventory location or detail record to another while preserving the reservation's link to its originating demand.
- QUERY_RESERVATION — Returns reservation information for a given demand reference or reservation identifier, supporting inquiry and validation logic.
- QUERY_RESERVATION_OM_HDR_LINE — A specialized inquiry that retrieves reservation data keyed to an Order Management header and line context, reflecting the dominant usage pattern of the API set.
Tables Accessed
The package body operates primarily through INV_RESERVATION_PVT and the shared state held in INV_RESERVATION_GLOBAL rather than querying base tables directly. The only documented table reference via APPS synonyms is PLITBLM, the PL/SQL integer table type used to pass bulk identifier and quantity arrays into reservation calls. The underlying reservation columns and demand detail rows are managed by the private layer against the Inventory reservation tables, which the public API shields callers from touching directly.
Usage Notes
INV_RESERVATION_PUB is normally invoked programmatically rather than from a standalone concurrent program. Oracle Order Management calls it during order booking, pick release, and shipment confirmation to create, relieve, or transfer reservations as the order lifecycle advances. Custom integrations and extensions should call the PUB layer, never INV_RESERVATION_PVT, to remain upgrade-safe and to inherit the standard validation and message handling provided through FND_API and FND_MSG_PUB. Typical prerequisites include a valid inventory organization context, a profile-option-driven reservation environment, and initialized error-handling structures. Because the procedures participate in the caller's transaction, custom code must handle COMMIT and ROLLBACK explicitly and check the returned API status rather than assuming success.