Search Results aso_reservation_int




Overview
Explore in AI Chat

Overview

APPS.ASO_RESERVATION_INT is a public PL/SQL interface package that belongs to the Oracle Advanced Supply Chain Planning / Order Capture (ASO) module, specifically the quoting and reservation component of Oracle EBS. Its primary business function is to provide a controlled, API-driven mechanism for creating, updating, deleting, and transferring inventory reservations that are associated with quote lines and their shipments. Rather than allowing direct DML against reservation tables, the package encapsulates the reservation logic and exposes it through standard, message-list-enabled APIs that conform to the Oracle Application Object Library (FND_API) conventions. The package is classified in the ETRM taxonomy as "OTHER," reflecting that it is an internal but publicly callable integration package rather than a full public business API. It is referenced by at least three other packages, indicating it serves as a shared reservation engine consumed by downstream processes within the ASO module.

Key Procedures and Functions

The package exposes four documented public procedures, all of which operate on reservation data for a supplied quote line and shipment context:

  • CREATE_RESERVATION — Creates a new inventory reservation for a given quote line and shipment. It accepts standard API control parameters (version number, initialization of the message list, and commit flag), a quote line record and shipment record, and returns the standard return status, message count, and message data outputs. It additionally returns the quantity reserved and the generated reservation identifier, allowing callers to link the new reservation to subsequent transactions.
  • UPDATE_RESERVATION — Modifies an existing reservation associated with the supplied quote line and shipment records. This is the procedure most commonly invoked when quote quantities, shipment details, or reservation attributes change. It follows the same API signature convention as the create procedure (version, init message list, commit flag, line and shipment records, and return status/message outputs) but does not return a reservation identifier, as the reservation is presumed to already exist.
  • DELETE_RESERVATION — Removes a reservation tied to the given line and shipment context. This supports scenarios where a quote line is cancelled, a shipment is removed, or reserved inventory must be released back to available stock.
  • TRANSFER_RESERVATION — Moves an existing reservation from one context to another (for example, between shipments or lines), preserving the reserved quantity without performing a delete-and-recreate cycle.

All procedures adhere to the standard ETRM/Oracle API contract: an API version number, an initialization flag for the message list, a commit flag, IN record structures based on aso_quote_pub types, and OUT NOCOPY status, message count, and message data parameters.

Tables Accessed

The ETRM metadata does not enumerate the specific base tables accessed, and no APPS-synonym table list was provided. Functionally, reservations in EBS are persisted in the inventory reservation tables (notably MTL_RESERVATIONS) and the supply-demand / order capture tables maintained by the ASO schema. Because the package accepts aso_quote_pub.qte_line_rec_type and aso_quote_pub.shipment_rec_type structures, it interacts with quote line and shipment data held in the ASO quote tables (such as ASO_QUOTE_LINES and related shipment tables) in addition to the inventory reservation records. All access is performed through APPS synonyms rather than direct owner-qualified references.

Usage Notes

ASO_RESERVATION_INT is intended to be called programmatically rather than executed directly. Typical invocation points include ASO quote forms and associated business logic (via the quote public APIs), concurrent programs and workflows that manage quote lifecycle events, and custom extensions or integrations that need to reserve, release, or reposition inventory against a quote. Callers should follow the standard FND_API calling convention: initialize the message list, pass the appropriate API version, provide the required quote line and shipment records, inspect X_Return_Status and X_Msg_Data after each call, and pass the commit flag explicitly to control transaction boundaries. Because the package is referenced by three other packages, modifications to its behavior can ripple across the ASO reservation process chain, so extensions should treat it as a stable interface and avoid bypassing it with direct DML against the underlying reservation tables.