Search Results wsh_trip_stops




Overview
Explore in AI Chat

Overview

The WSH_TRIP_STOPS table is a core data object within the Oracle E-Business Suite Shipping Execution (WSH) module. It serves as the master repository for all stop locations associated with a transportation trip. A trip, defined in the WSH_TRIPS table, represents a journey undertaken by a carrier or vehicle to fulfill deliveries. This table stores the sequential itinerary for that journey, detailing each physical stop point, which can be a warehouse, customer site, cross-dock, or carrier terminal. Its primary role is to model the route's geography and schedule, enabling the system to plan, execute, and track the movement of delivery legs and their associated freight activities throughout the logistics lifecycle.

Key Information Stored

The table's central entity is the STOP_ID, which serves as the primary key. The most critical foreign key is TRIP_ID, linking each stop to its parent trip in WSH_TRIPS. While the provided metadata does not list all columns, the table's relationships and purpose indicate it typically stores information such as the stop sequence number, location ID (linking to HR_LOCATIONS), planned and actual arrival/departure dates, stop type (e.g., Pick Up, Drop Off), and status. It acts as the anchor point for associating appointments, freight charges, exceptions, and delivery legs that occur at a specific point in the trip's route.

Common Use Cases and Queries

This table is essential for trip scheduling, real-time tracking, and post-trip analysis. Common operational queries involve listing all stops for a given trip to view the route or checking the status of specific stops. For reporting, it is frequently joined to WSH_TRIPS and WSH_DELIVERY_LEGS to analyze on-time performance, stop density, or route efficiency. A typical pattern is to query stops for deliveries due on a specific date.

  • Sample Query (Stops for a Trip): SELECT * FROM WSH_TRIP_STOPS WHERE TRIP_ID = <trip_id> ORDER BY SEQUENCE_NUMBER;
  • Sample Query (Stops with Leg Details): SELECT ts.STOP_ID, ts.STOP_SEQUENCE, dl.DELIVERY_ID FROM WSH_TRIP_STOPS ts, WSH_DELIVERY_LEGS dl WHERE ts.STOP_ID = dl.PICK_UP_STOP_ID AND ts.TRIP_ID = <trip_id>;

Related Objects

As per the documented foreign keys, WSH_TRIP_STOPS has extensive integration within the Shipping and adjacent modules. WSH_TRIPS is its direct parent table. Key child tables include WSH_DELIVERY_LEGS (linking deliveries to pick-up and drop-off stops), WSH_FREIGHT_COSTS, and WSH_EXCEPTIONS. It is also referenced by WMS_DOCK_APPOINTMENTS_B for dock scheduling and WSH_PICKING_BATCHES. This network of relationships underscores its position as a critical junction point connecting trip planning, delivery execution, warehouse operations, and freight costing.