Search Results wsh_exceptions




Overview
Explore in AI Chat

Overview

The WSH_EXCEPTIONS table is a core transactional data object within the Oracle E-Business Suite Shipping Execution (WSH) module. It serves as the central repository for logging and tracking exceptions that occur during the shipping lifecycle. An exception represents a deviation from the standard process flow, such as a delivery that cannot be assigned to a trip, a stop that violates scheduling constraints, or a detail line that fails to meet shipping requirements. The table's primary role is to provide a persistent audit trail of these issues, enabling users to identify, analyze, and resolve operational bottlenecks that prevent the successful planning and execution of shipments.

Key Information Stored

The table stores metadata that identifies the exception, its context, and its status. The primary key, EXCEPTION_ID, uniquely identifies each exception record. Crucially, the table contains foreign key columns that link the exception to the specific transactional entity it pertains to, including TRIP_ID, TRIP_STOP_ID, DELIVERY_ID, and DELIVERY_DETAIL_ID. This structure allows an exception to be associated with a broad entity like an entire trip or a granular entity like a single delivery detail line. Other important columns typically include EXCEPTION_TYPE to categorize the nature of the issue (e.g., 'PICKING', 'PACKING', 'SHIPPING'), a STATUS field to track if it is 'OPEN' or 'CLOSED', a DESCRIPTION, and standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY) for audit purposes.

Common Use Cases and Queries

The primary use case is operational exception management. Shipping clerks and managers run queries to generate open exception reports for resolution. A common SQL pattern is to join WSH_EXCEPTIONS with related transactional tables to get a comprehensive view. For example, to find all open exceptions for deliveries on a specific trip:

  • SELECT e.exception_id, e.exception_type, e.description, d.delivery_id, d.name
  • FROM wsh_exceptions e, wsh_new_deliveries d
  • WHERE e.delivery_id = d.delivery_id
  • AND e.trip_id = <trip_id>
  • AND e.status = 'OPEN';

Another critical use case is integration and data validation, where custom programs or interfaces query this table to verify that no blocking exceptions exist before proceeding with downstream processes like freight rating or carrier tendering.

Related Objects

As indicated by its foreign keys, WSH_EXCEPTIONS has direct relationships with several fundamental WSH tables. It references WSH_TRIPS (trips), WSH_TRIP_STOPS (stops on a trip), WSH_NEW_DELIVERIES (deliveries), and WSH_DELIVERY_DETAILS (individual lines on a delivery). This table is often accessed through standard Shipping Execution APIs and user interfaces, such as the Trip Stop and Delivery Exceptions forms. Reports and operational dashboards commonly join WSH_EXCEPTIONS with these related tables to present exception data in a business context.