Search Results wsh_exceptions_pub




Overview
Explore in AI Chat

Overview

WSH_EXCEPTIONS_PUB is a public PL/SQL package residing in the APPS schema that encapsulates the business logic governing shipping exceptions within Oracle Shipping Execution. The Shipping Execution module generates exceptions when shipment, delivery, or trip records violate user-defined validation rules, tolerance thresholds, or operational constraints. WSH_EXCEPTIONS_PUB serves as the programmatic interface through which those exception conditions are queried and subsequently resolved or acknowledged. Because the package is classified as a PUBLIC API (API classification: PUB), it is intended for direct invocation by external programs, including Oracle's own E-Business Suite components, Oracle Fusion middleware, and customer-written extensions. The package depends on FND_API, the standard Oracle Application Object Library utility package that supplies the common API framework, including message handling, error stacks, and the standard return-status convention (success, warning, or error). This dependency confirms that WSH_EXCEPTIONS_PUB adheres to Oracle's documented API programming standards, making it a supported integration point rather than a private implementation detail. In releases 12.1.1 and 12.2.2, the package remains valid and available in the APPS schema, with the same two documented entry points.

Key Procedures and Functions

The ETRM metadata documents two callable units within the package:

  • GET_EXCEPTIONS — Retrieves shipping exception records that satisfy the supplied filtering criteria. This procedure provides the read-side interface to the exception repository, allowing callers to obtain the set of exceptions associated with a shipment, delivery, trip, or other shipping entity. It is the entry point custom programs use when they need to surface exception information outside the standard Shipping Execution forms and concurrent programs.
  • EXCEPTION_ACTION — Performs an action against an identified shipping exception, such as resolving, acknowledging, or otherwise updating its status. This procedure supplies the write-side interface, enabling controlled transitions of exception state through the supported API rather than through direct table manipulation.

Parameter lists are not reproduced here; callers should obtain exact signatures from the package specification in the ETRM or from the database source in their environment. Both units follow the FND_API conventions for return status and message propagation.

Tables Accessed

The ETRM metadata for this object does not enumerate specific base tables referenced through APPS synonyms; the documented dependency view lists only FND_API and the SYS STANDARD package at the PL/SQL dependency level. Functionally, the package operates against the Shipping Execution exception data model, which centers on the WSH_EXCEPTIONS entity and its associated reference and assignment structures. GET_EXCEPTIONS reads these structures to return exception details, while EXCEPTION_ACTION updates exception status and resolution attributes.

Usage Notes

WSH_EXCEPTIONS_PUB is referenced by three other packages documented in ETRM: WSH_EXCEPTIONS_GRP (the exceptions group, which the user appears to have been searching for via the term "wsh_exceptions_grp"), FTE_MLS_WRAPPER, and WSH_PO_CMG_PVT. The reference from WSH_EXCEPTIONS_GRP is the most significant for functional users, since the group package typically supplies the user-interface and concurrent-program layer that drives exception display and maintenance in the Shipping Transactions and Delivery forms. The reference from WSH_PO_CMG_PVT indicates that the change-management logic for shipping also consumes the API. Typical invocation patterns include Oracle Forms calls from the Shipping Execution workbench, concurrent programs that scan and clear exceptions, and custom PL/SQL extensions requiring a supported, upgrade-safe interface. Because the package is a public API built on FND_API, direct DML against the underlying exception tables should be avoided in favor of GET_EXCEPTIONS and EXCEPTION_ACTION.