Search Results exception_action

Overview

WSH_EXCEPTIONS_PUB is a public PL/SQL API owned by the APPS schema that provides programmatic access to shipping exceptions within Oracle E-Business Suite Release 12.1.1 and 12.2.2. Shipping exceptions represent deviations or conditions detected against a logistics entity during the order-to-shipment lifecycle — for example, a delivery that has not been picked up on schedule, a trip that is at risk of missing a scheduled date, or a container-level irregularity. The package exists so that Oracle Shipping Execution and dependent modules can detect, retrieve, and act upon these exceptions without directly querying the underlying WSH exception tables.

The header of the package body references source control version 115.12 2004/05/24, indicating the core logic has been stable since the 11.5.x lineage and has been carried forward with minimal change into 12.x. Its public (PUB) classification means the procedures are intended as a supported integration point for forms, concurrent programs, and customer extensions, as opposed to private helper packages that Oracle may modify without notice.

Key Procedures and Functions

The ETRM documentation records two public procedures for this package:

• GET_EXCEPTIONS — Constructs and returns a collection of exceptions for a single shipping entity. The caller supplies an entity identifier together with an entity name, which the package header documents as being one of TRIP, STOP, DELIVERY, DETAIL, or CONTAINER. The procedure returns a PL/SQL associative-array style table typed as WSH_EXCEPTIONS_PUB.XC_TAB_TYPE, allowing the caller to iterate over every exception raised against the specified entity in a single call. It follows the standard Oracle API contract: an p_api_version for call compatibility, p_init_msg_list to control message-stack initialisation, and the conventional x_return_status, x_msg_count, and x_msg_data output parameters. The body also integrates with the WSH debugging framework (WSH_DEBUG_INTERFACE and WSH_DEBUG_SV), enabling trace output when debug mode is enabled.
• EXCEPTION_ACTION — The procedure implied by the user search term "exception_action". It applies an action to a detected shipping exception, allowing callers to resolve, acknowledge, or otherwise process an exception returned by GET_EXCEPTIONS. This pairing of a read procedure with an action procedure is a common Oracle pattern that separates detection from remediation.

Tables Accessed

Although the ETRM excerpt lists no explicitly documented base tables, the package operates against the WSH exception schema. In a standard 12.1.1/12.2.2 installation the relevant objects include WSH_EXCEPTIONS and its associated definition and action tables, which store the exception identifier, the logging entity type and identifier, severity, and the action taken. The package accesses these through APPS synonyms rather than qualified schema names, which is why the metadata shows no direct table references. GET_EXCEPTIONS performs the read, and EXCEPTION_ACTION performs the write.

Usage Notes

WSH_EXCEPTIONS_PUB is most commonly invoked from Oracle Shipping Execution forms, from concurrent programs that scan deliveries and trips for exception conditions, and from custom PL/SQL that needs to surface or clear shipping exceptions. External callers should always pass the correct p_api_version, check x_return_status for FND_API.G_RET_STS_SUCCESS, and, when messages are returned, call FND_MSG_PUB utilities to extract them. Note that the ETRM metadata records three other packages referencing this API, so changes to its behaviour can propagate into broader shipping flows. Because only two procedures are documented publicly, callers should avoid relying on any other routine visible in the package body, as those are not part of the supported interface.