Search Results outstanding_order_value

Overview

WSH_PICK_CUSTOM is a customization hook package owned by the APPS schema in Oracle E-Business Suite. In Oracle Warehouse Management and Shipping (WSH), picking and release logic frequently needs to sequence or prioritize sales order lines during the release-to-warehouse process. The package body provides a single public customization point, Outstanding_Order_Value, whose purpose is to calculate the total monetary value of a sales order so that the order's value can be used within an ORDER BY clause when releasing order lines. By supplying this value, the shipping release engine can prioritize larger-value orders ahead of smaller ones, supporting business rules that favor high-value fulfillment.

The package is classified in the ETRM metadata as an OTHER API type, indicating it is not a standard, supported business API but rather an extension point intended for site-specific sourcing modification. It is referenced by one other package, confirming it participates in the shipping release call chain rather than standing alone.

Key Procedures and Functions

• OUTSTANDING_ORDER_VALUE — A function that computes the value of an order given its order header identifier. The function accepts the order header as input and returns an integer representing the order value, or 0 on failure. Internally it derives the value by aggregating line-level ordered quantity multiplied by unit selling price across all lines belonging to the header. The returned value is consumed as a sort key for releasing lines, enabling ordering by monetary magnitude. The function defensively returns 0 in its OTHERS exception handler, so callers should treat a zero result as either a legitimately zero-value order or a computation failure, and no distinct status is propagated.

No other documented procedures or functions exist in the package. The body also declares a package-level constant, G_PKG_NAME, used for module identification and error context.

Tables Accessed

• OE_ORDER_HEADERS_ALL — The order header base table. It is read to anchor the query to the specific header passed in and to confirm the order under evaluation.
• OE_ORDER_LINES_ALL — The order line base table. It supplies the ORDERED_QUANTITY and UNIT_SELLING_PRICE columns that are multiplied and summed to produce the order value.

Both tables are accessed through APPS synonyms and are queried read-only; the package performs no DML. The aggregation joins lines to the header on HEADER_ID and filters by the supplied header identifier, so the function returns the sum across all lines of that order.

Usage Notes

This package is typically invoked during the shipping release process, where its return value feeds the ORDER BY clause used to sequence lines for picking. Because the ETRM metadata lists it as a custom package referenced by another package, it is embedded in the release logic rather than called directly by end users or concurrent programs. It is not exposed through a standard form, and it is not a supported public API.

Administrators and developers encountering the search term "outstanding_order_value" are usually tracing why orders are being released in a particular sequence. The practical implication is that modifying this function changes release prioritization: a site may replace the default quantity-times-price computation with a different valuation rule, such as including tax, freight, or a weighting factor. Because failures are silently collapsed to 0, debugging should verify that the header identifier passed is valid and that the line-level values are populated. Care must be taken when customizing the body, since the package is an unsupported extension point and changes carry upgrade risk across EBS 12.1.1 and 12.2.2.