Search Results not_handled

Overview

APPS.WSH_EXCEPTIONS_DLVY_V is a shipping-execution reporting view in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It presents exception records captured by the Warehouse Management and Shipping Execution modules, flattened against their delivery, trip, container, and location context. The view resolves coded values into user-facing meanings through the WSH_XC_UTIL package and FND_LOOKUP_VALUES, so that severity, status, and logging entity are returned as readable labels rather than raw codes. This makes the view suitable for operational dashboards, delivery-exception worklists, and integration extracts where exception data must be presented in business terms without additional decoding logic. The "_DLVY_" suffix indicates that the projection emphasises delivery-oriented context (delivery_id, delivery_name, delivery_detail_id, delivery_assignment_id) alongside general exception attributes.

Underlying Base Objects

The view draws from the following documented base objects: WSH_EXCEPTIONS (the driving synonym and primary exception table), WSH_EXCEPTION_DEFINITIONS_B and WSH_EXCEPTION_DEFINITIONS_TL (definition base and translated tables supplying the description), FND_LOOKUP_VALUES (meaning lookup), WSH_LOCATIONS (source and exception locations), HR_LOCATIONS_ALL (for location resolution), MTL_PARAMETERS (inventory organisation context), WSH_DELIVERY_ASSIGNMENTS_V (delivery assignment context), and the WSH_XC_UTIL package used at query time to return lookup meanings. Joins are primarily outer joins: exception_name is joined to the definition tables with (+), and exception_location_id is joined outward, allowing exceptions to appear even when their definitions or locations are unresolved. The view is a straightforward relational projection with no aggregation; row identity is preserved by carrying xc.rowid.

Key Columns

• exception_id, exception_name, description — identity and description of the logged exception.
• severity — decoded from the stored value into ERROR, WARNING, or INFO via DECODE on HIGH/MEDIUM/LOW.
• status — normalised: MANUAL, LOGGED, IN_PROCESS, ERROR, and NOT_HANDLED are mapped to OPEN or NO_ACTION_REQUIRED.
• logging_entity, logged_at_location_id, ui_location_code — where and by what the exception was raised.
• exception_location_id, wlo.ui_location_code — the location the exception concerns.
• trip_id, trip_name, trip_stop_id — trip context for transportation exceptions.
• assigned_delivery_id, delivery_id, delivery_name, delivery_detail_id, delivery_assignment_id — delivery context.
• container_name, inventory_item_id, lot_number, revision, serial_number, unit_of_measure, quantity, subinventory, locator_id — inventory detail of the affected shipment line.
• arrival_date, departure_date, error_message, message — timing and diagnostic text.
• organization_id, organization_code — owning inventory organisation from MTL_PARAMETERS.
• attribute1–15, attribute_category — descriptive flexfield content.
• who-columns and request_id, program_id — audit and concurrent-program traceability.

Common Use Cases and Queries

A typical use is to retrieve all open, high-severity exceptions for a delivery:

SELECT exception_id, exception_name, severity, status, delivery_name, message
FROM apps.wsh_exceptions_dlvy_v
WHERE delivery_id = :p_delivery_id AND severity = 'ERROR' AND status = 'OPEN';

The view also supports organisation-level extract jobs that feed exception queues or alerting mechanisms, and joins to WSH_DELIVERY_ASSIGNMENTS-based data for shipment reconciliation. Note that status and logging_entity meanings are produced at runtime by WSH_XC_UTIL, and that occurrence of Windows error code 0Xc1900000 is unrelated to this database view; it is an environment-level client error and does not originate from WSH_EXCEPTIONS_DLVY_V.