Search Results dropoff_stop




Overview
Explore in AI Chat

Overview

APPS.WSH_DELIVERY_TRIPS_V is a shipping execution view in Oracle E-Business Suite 12.1.1 and 12.2.2 that associates a delivery with the trip, and specifically the trip stops, that service it. Where WSH_TRIPS_V exposes trip-level attributes, WSH_DELIVERY_TRIPS_V adds the delivery context by joining WSH_DELIVERY_LEGS to the pickup and dropoff stops that make up a given leg. The view therefore answers the question "which trip, and which stop sequence, is handling this delivery?" and provides a derived status that reflects the combined state of the pickup and dropoff stops.

Because it returns a delivery-to-trip-stop mapping plus a full set of trip attributes, the view is used in reporting, freight and load-tender analysis, carrier integration, and any custom process that must reconcile delivery legs against trip execution. It surfaces the trip stop codes that users search for under terms such as dropoff_stop, since a join to WSH_TRIP_STOPS on DROP_OFF_STOP_ID is central to its definition.

Underlying Base Objects

The documented base objects, per ETRM 12.2.2 metadata, are:

  • WSH_DELIVERY_LEGS (synonym) — supplies DELIVERY_ID, PICK_UP_STOP_ID and DROP_OFF_STOP_ID, the linkage between a delivery and the trip stops it uses.
  • WSH_NEW_DELIVERIES (synonym) — joined on DELIVERY_ID and filtered to SHIPMENT_DIRECTION in ('O','IO'), restricting results to outbound (and inbound/outbound) shipments.
  • WSH_TRIPS_V (view) — the source of trip-level attributes (trip_id, name, status, vehicle, carrier, routing, tender and workflow columns). Aliased T.
  • WSH_TRIP_STOPS (synonym) — referenced twice, once as PICKUP_STOP and once as DROPOFF_STOP, to read the status code of each stop.

The joins are: PICKUP_STOP.STOP_ID = DL.PICK_UP_STOP_ID, DROPOFF_STOP.STOP_ID = DL.DROP_OFF_STOP_ID, PICKUP_STOP.TRIP_ID = T.TRIP_ID, and WND.DELIVERY_ID = DL.DELIVERY_ID.

Key Columns

Common Use Cases and Queries

A typical use is to find every delivery on a trip together with its stop status:

  • SELECT trip_id, name, delivery_id, status_code FROM apps.wsh_delivery_trips_v WHERE trip_id = :trip_id;
  • SELECT delivery_id, trip_id, name, carrier_id FROM apps.wsh_delivery_trips_v WHERE delivery_id = :delivery_id;
  • SELECT name, load_tender_number, load_tender_status FROM apps.wsh_delivery_trips_v WHERE load_tender_status = 'TENDERED';

Because WSH_TRIP_STOPS is already joined internally, the view spares developers from reconstructing the pickup/dropoff stop relationship, making it the preferred source for delivery-to-trip-stop reporting, load-tender tracking, and carrier-facing extracts in both 12.1.1 and 12.2.2.