Search Results del_waybill

Overview

WSH_PURGE_SET_V is a Shipping Execution (WSH) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a flattened, denormalized projection of the trip, stop, delivery leg, delivery, delivery detail, and document instance hierarchy used by the shipping purge process. The view is designed to expose the full container-chain for a trip — from the trip header down through stops, legs, deliveries, and individual delivery details — so that purge and archival logic can identify related records by a single query. In practice, it functions as a read-only data source for purge set evaluation, operational reporting on shipment contents, and integration extracts where consumers need both the trip-level attributes and the line-level delivery detail attributes in one row. Because it joins many base objects, it is not intended as an update target; it is a query surface.

Underlying Base Objects

The view is defined over the following documented base objects: WSH_TRIPS, WSH_TRIP_STOPS, WSH_DELIVERY_LEGS, WSH_NEW_DELIVERIES, WSH_DELIVERY_ASSIGNMENTS_V, WSH_DELIVERY_DETAILS, WSH_DOCUMENT_INSTANCES, MTL_UNITS_OF_MEASURE_VL, MTL_PARAMETERS, WSH_LOOKUPS, WSH_LOCATIONS, HZ_CUST_ACCOUNTS, HZ_PARTIES, and PO_VENDORS. The core driver is WSH_TRIPS (aliased WT), joined to WSH_TRIP_STOPS (WTS) for pickup-stop information, WSH_DELIVERY_LEGS (WDL) for leg-level weight data, and WSH_NEW_DELIVERIES (WND) for delivery headers. WSH_DELIVERY_ASSIGNMENTS_V (WDA) links deliveries to details, while WSH_DELIVERY_DETAILS (WDD) supplies the detail-level attributes keyed by DELIVERY_DETAIL_ID. WSH_DOCUMENT_INSTANCES (WDI) provides the bill-of-lading sequence number. The view further resolves descriptive meanings through lookups: WSH_LOOKUPS supplies the delivery-detail source meaning, while MTL_UNITS_OF_MEASURE_VL resolves unit-of-measure codes into translated meanings. MTL_PARAMETERS and WSH_LOCATIONS supply organization and location codes, and HZ_CUST_ACCOUNTS / HZ_PARTIES provide the customer name, truncated to 50 bytes for the DEL_CUSTOMER_NAME column, with PO_VENDORS available for vendor-side resolution.

Key Columns

Representative columns include TRIP_ID, TRIP_NAME, TRIP_STATUS, TRIP_CREATION_DATE, and TRIP_SHIPMENTS_TYPE for the trip header. Stop-level columns include PICKUP_STOP_ID, PICKUP_STOP_SHIPMENTS_TYPE, PICKUP_STOP_GROSS_WEIGHT, PICKUP_STOP_WEIGHT_UOM, PICKUP_STOP_WEIGHT_UOM_MEANING, and PICKUP_STOP_SHIP_DATE. Leg-level columns include LEG_ID, LEG_GROSS_WEIGHT, and LEG_WEIGHT_UOM. Delivery columns include DEL_ID, DEL_NAME, DEL_SHIP_FROM_ORG and DEL_SHIP_FROM_ORG_CODE, DEL_PICKUP_DATE, DEL_CREATION_DATE, DEL_SHIPPING_CONTROL, DEL_SHIPMENT_DIRECTION, DEL_WAYBILL, DEL_GROSS_WEIGHT, DEL_WEIGHT_UOM, DEL_CUSTOMER_ID, DEL_CUSTOMER_NAME, DEL_ULT_DO_LOCATION_ID, DEL_UI_LOCATION_CODE, DEL_DROPOFF_DATE, and DEL_SHIP_DATE. Detail columns center on DD_ID (DELIVERY_DETAIL_ID), DD_LINE_DIRECTION, DD_SHIPPING_CONTROL, DD_SOURCE_CODE, DD_SOURCE_MEANING, DD_SOURCE_HEADER_ID, DD_SOURCE_HEADER_NUMBER, DD_SOURCE_HEADER_TYPE_ID, DD_SOURCE_HEADER_TYPE_NAME, DD_PO_SHIPMENT_LINE_ID, and the BOL sequence number drawn from WSH_DOCUMENT_INSTANCES. The user search term "dd_id" corresponds directly to the DD_ID alias of WSH_DELIVERY_DETAILS.DELIVERY_DETAIL_ID.

Common Use Cases and Queries

Typical use cases include locating all delivery details belonging to a trip before purge, auditing trip weights against summed leg and detail weights, and extracting shipment contents by customer or organization. The following queries illustrate common patterns:

• Retrieve all details for a trip: SELECT DD_ID, DEL_ID, DEL_NAME, TRIP_NAME FROM APPS.WSH_PURGE_SET_V WHERE TRIP_ID = :p_trip_id;
• Resolve a delivery detail back to its trip and stop: SELECT DD_ID, TRIP_ID, TRIP_NAME, PICKUP_STOP_ID FROM APPS.WSH_PURGE_SET_V WHERE DD_ID = :p_dd_id;
• Report shipment contents by customer: SELECT DEL_CUSTOMER_NAME, DEL_NAME, DD_ID, BOL, DD_SOURCE_MEANING FROM APPS.WSH_PURGE_SET_V WHERE DEL_CUSTOMER_ID = :p_customer_id ORDER BY DEL_NAME;
• Audit weights: SELECT TRIP_ID, LEG_GROSS_WEIGHT, PICKUP_STOP_GROSS_WEIGHT, DEL_GROSS_WEIGHT FROM APPS.WSH_PURGE_SET_V.

Because the view joins several high-volume shipping tables, queries should be filtered on TRIP_ID, DEL_ID, or DD_ID to avoid full scans, and consumers should confirm the view remains VALID in the target instance before relying on it in purge or integration logic.