Search Results update_order

Overview

ASO_ORDER_INT is a PL/SQL integration package in the Oracle E-Business Suite Order-to-Cash (ASO) module that provides a programmatic interface between Oracle Quoting and Oracle Order Management. Its principal business function is to expose the operations required to convert a quote into a sales order, and to maintain the resulting order throughout its lifecycle. The package encapsulates the logic that copies quote headers and lines into the Order Management interface, applies order and line status transitions, performs booking and cancellation, and retrieves pricing and customer-related reference data. Because the package is designated with an API classification of OTHER, it is intended for controlled invocation rather than ad hoc querying, and it is referenced by 33 other packages within the application, indicating that it forms part of the internal infrastructure on which higher-level quoting and ordering flows depend.

Key Procedures and Functions

The package exposes seventeen documented procedures and functions. The record types Order_Header_Rec_Type and Order_Line_Rec_Type define the header and line structures used by the interface, carrying identifiers such as order number, order header identifier, quote header identifier, order line identifier, quote shipment line identifier, and status, with FND_API.G_MISS_* sentinels marking uninitialized attributes.

• CREATE_ORDER — Creates a sales order in Order Management from quote data.
• UPDATE_ORDER — Applies changes to an existing order, including status updates; this is the object most commonly associated with the search term "update_order".
• DELETE_ORDER — Removes an order created through this interface.
• BOOK_ORDER — Transitions an eligible order into booked status.
• CANCEL_ORDER — Cancels an existing order.
• GET_HEADER_STATUS / GET_LINE_STATUS — Return the current status of an order header or line.
• GET_ACCT_SITE_USES, GET_CUST_ACCT_ROLES, GET_CUST_ACCT_SITE_USES — Retrieve customer account site uses and account role assignments needed to resolve shipping and billing context.
• GET_ORDER_HEADER_ID, GET_ORDER_LINE_ID — Resolve internal identifiers for a header or line.
• GET_ORDER_NO — Returns the order number for a given order.
• GET_PROFILE_VALUE — Reads a profile option value relevant to order processing.
• GET_QUOTE_NUMBER — Returns the quote number associated with an order.
• IS_BOOKED — Determines whether an order has already been booked.
• INITIALIZE_OM_REC_TYPES — Resets the Order Management record structures before use.
• SALESREP_ID / SERVICE_INDEX — Supply sales representative and service-index reference values used during order creation.

Tables Accessed

The package reads and writes quote and order header data through ASO_QUOTE_HEADERS_ALL, and resolves customer and party information through the TCA tables HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_ORG_CONTACTS, HZ_PARTIES, HZ_PARTY_SITES, and HZ_RELATIONSHIPS, with HZ_ROLE_RESPONSIBILITY used for role-based access resolution. AMS_DELIVERABLES_ALL_B supports deliverable linkage, and PLITBLM is referenced for temporary storage of large identifiers during processing. These accesses supply the account, site, contact, and relationship context required for a valid order, together with the quote reference data that links order lines back to their originating quote line and shipment line.

Usage Notes

ASO_ORDER_INT is not intended for direct end-user invocation. It is called from Oracle Quoting and Order Management forms, from concurrent programs that process quote-to-order conversion in batch, and from custom code performing integration between quoting and order capture. When invoking UPDATE_ORDER or the other API entry points, callers should populate the header and line record types with the FND_API.G_MISS_* defaults respected, standardize any error handling through FND_API, and rely on G_DEFAULT_NUM_REC_FETCH (30) as the default fetch size for bulk processing. Modifications to quotation or order data should be routed through this package rather than by direct DML against the underlying tables, so that status transitions and cross-module dependencies remain consistent.