Search Results wsh_trip_stops_interface




Overview
Explore in AI Chat

Overview

The WSH_TRIP_STOPS_INTERFACE table is a critical staging table within the Oracle E-Business Suite Shipping Execution (WSH) module. Its primary role is to serve as an interface for importing and validating trip stop data before it is processed into the application's core transactional tables. This table is fundamental to the Open Interface program for trips and stops, enabling the bulk loading of shipping logistics data from external systems, such as Transportation Management Systems (TMS) or legacy applications, or from internal custom programs. In the context of Oracle EBS releases 12.1.1 and 12.2.2, it facilitates the integration and automation of freight management processes by providing a standardized, programmatic method for creating and updating trip itineraries.

Key Information Stored

While the provided metadata does not list specific columns, the table's primary key is documented as STOP_INTERFACE_ID, which uniquely identifies each interface record. Based on its function and standard interface table design, it typically stores attributes for each planned stop on a trip. Common data elements include the associated TRIP_INTERFACE_ID (linking to WSH_TRIPS_INTERFACE), sequence number, location details (address, site ID), planned arrival and departure dates/times, and status flags. The table also holds control columns standard to Oracle interface tables, such as PROCESS_STATUS to indicate if a record is pending processing, has errors, or has been successfully processed, and ERROR_MESSAGE for validation feedback.

Common Use Cases and Queries

The primary use case is the execution of the "Load Trips and Stops" concurrent program, which validates records in this interface table and creates corresponding trip stops in the base table WSH_TRIP_STOPS. Common operational queries involve monitoring the interface for errors or processing status. A typical diagnostic SQL pattern is:

  • SELECT trip_interface_id, stop_interface_id, process_status, error_message FROM wsh_trip_stops_interface WHERE process_status = 'ERROR';

For reporting on pending interface data before submission, a join to the trip interface table is standard:

  • SELECT tsi.*, ti.trip_name FROM wsh_trip_stops_interface tsi, wsh_trips_interface ti WHERE tsi.trip_interface_id = ti.trip_interface_id AND tsi.process_status = 'PENDING';

Integration developers use this table as the target for data inserts from flat files or APIs when building custom inbound shipping interfaces.

Related Objects

The WSH_TRIP_STOPS_INTERFACE table has defined relationships with other key interface tables, as per the provided metadata.

  • WSH_TRIPS_INTERFACE: This table is the parent. A foreign key constraint exists where WSH_TRIP_STOPS_INTERFACE.TRIP_INTERFACE_ID references WSH_TRIPS_INTERFACE. Every stop must be associated with a trip staged in this parent interface.
  • WSH_DEL_LEGS_INTERFACE: This table is a child. It references WSH_TRIP_STOPS_INTERFACE twice to define delivery legs: This relationship allows the interface to model the complete movement of deliveries between specific stops on a trip itinerary.

Upon successful processing by the interface concurrent program, data is propagated to the base transactional tables, primarily WSH_TRIP_STOPS.