Search Results wsh_trips

Overview

The WSH_TRIPS table is the central data repository for trip records within the Oracle E-Business Suite Shipping Execution (WSH) module. A trip is a fundamental entity representing a planned movement of goods from one or more source locations to one or more destination locations, typically managed by a carrier. This table stores the master definition of a shipment's journey, serving as the parent record for all associated stops, deliveries, and freight charges. Its integrity is critical for orchestrating the outbound logistics process, from order consolidation and load planning to carrier tendering and freight cost settlement.

Key Information Stored

The table's primary key is TRIP_ID, a unique system-generated identifier for each trip. While the full column list is not detailed in the provided metadata, based on its core function, the table typically contains columns to define the trip's operational characteristics. Common critical attributes include a TRIP_NAME or NUMBER for user identification, STATUS_CODE to track the trip's lifecycle (e.g., ENTERED, PLANNED, IN-TRANSIT, CLOSED), and dates for creation, planned departure, and actual departure. It also stores references to the assigned CARRIER_ID, VEHICLE_ITEM_ID, and the SHIP_METHOD_CODE. The table acts as an anchor for freight calculations, holding links to rate information and serving as the header for accumulating freight costs.

Common Use Cases and Queries

This table is central to shipping operations and reporting. Common use cases include generating trip manifests, auditing shipment status, and analyzing carrier performance. A frequent query involves joining WSH_TRIPS with WSH_TRIP_STOPS and WSH_DELIVERIES to list all deliveries on a specific trip. For example, to find all trips planned for a specific carrier that are not yet closed:

• SELECT trip_name, status_code, planned_departure_date FROM wsh_trips WHERE carrier_id = &carrier_id AND status_code != 'CLOSED';

Another critical pattern is summarizing freight costs by trip by joining with WSH_FREIGHT_COSTS. Data from this table is also essential for interfacing with transportation management systems and warehouse management via the WSH_TRIPS_INTERFACE table.

Related Objects

As indicated by the foreign key constraints, WSH_TRIPS has numerous dependent tables, highlighting its pivotal role. Key related objects include:

• WSH_TRIP_STOPS: Stores the sequence of pickup and drop-off locations for the trip.
• WSH_FREIGHT_COSTS: Holds detailed freight charges and adjustments associated with the trip.
• WSH_EXCEPTIONS: Logs any operational exceptions or issues raised against the trip.
• WSH_PICKING_BATCHES: Links picking batch assignments to the trip for fulfillment.
• WSH_TRIPS_INTERFACE: Serves as the staging table for creating or updating trips via open interfaces.
• WMS_SHIPPING_TRANSACTION_TEMP: References the trip during the generation of shipping transactions from Warehouse Management (WMS).