Search Results wsh_exception_definitions_s

Overview

The APPS.WSH_XC_PURGE_PKG package body is a PL/SQL administrative utility within the Oracle E-Business Suite Shipping execution module (WSH). Its principal business function is to manage the lifecycle of seeded exception definitions used by the exception management framework. Exception definitions stored in the WSH_EXCEPTION_DEFINITIONS entity drive the rules that flag shipment, delivery, and trip anomalies throughout the order-to-shipment flow. Because these definitions are seeded by Oracle as part of the base application, environments accumulate obsolete or superseded seed rows across upgrades, patches, and localization cycles. This package provides a controlled programmatic mechanism to purge those seeded definitions rather than requiring direct DML against Shipping base tables.

The object is classified with an API classification of OTHER in the ETRM 12.2.2 metadata and carries a VALID status in the APPS schema. It is a package body without a companion public specification of note, indicating it is intended primarily for internal or administrative invocation rather than as a threaded caller of other modules. Notably, the package is not referenced by any other database object, confirming its role as a terminal utility rather than a shared library dependency.

Key Procedures and Functions

The documented metadata lists a single public program unit:

• PURGE_SEED_DEFINITION — Removes a seeded exception definition from the Shipping exception definitions repository. It is the sole documented entry point and encapsulates the logic required to identify and delete a seed-originated definition safely. Because no parameter list is documented in the ETRM metadata, parameter details should be confirmed against the live package specification in the target environment before invocation.

The package body also depends on several supporting units: WSH_DEBUG_INTERFACE and WSH_DEBUG_SV for diagnostic logging, and WSH_XC_UTIL for shared exception-management utilities. These dependencies indicate that the purge operation is instrumented for debugging and reuses standard Shipping exception helper logic rather than issuing raw deletes.

Tables Accessed

• WSH_EXCEPTION_DEFINITIONS_S — The primary base table holding the definition records subject to purging. The package reads and deletes rows here.
• WSH_EXCEPTION_DEFINITIONS_VL — The translated view over the definitions entity, referenced to resolve the definition identity (including language-specific attributes) prior to removal.
• DUAL — Referenced via both the APPS and PUBLIC/SYS synonyms for standard singleton evaluation and function-style result construction.

Usage Notes

Because WSH_XC_PURGE_PKG is not referenced by any other database object, it is not invoked automatically by standard Shipping transaction processing. It is typically called from administrative contexts: a DBA or support engineer executing the procedure manually during cleanup activities, a custom concurrent program wrapper built to schedule periodic purges, or remediation scripts supplied with Oracle patches and service requests. The absence of downstream dependencies means changes to or removal of the seeded definitions cannot cascade through other packages, but it also means the processor does not enforce referential cleanup of dependent exception instances and transaction data. Callers should therefore purge seed definitions only after confirming that no active shipment, delivery, or trip records still reference the definitions, and only with the appropriate APPS-schema privileges. The WSH_DEBUG_SV and WSH_DEBUG_INTERFACE dependencies allow the operation to be traced when Shipping debug logging is enabled.