Results for “wsh_trip_stops_interface_u1”

12 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

WSH_TRIP_STOPS_INTERFACE is a Shipping Execution (WSH) interface table that serves as the inbound staging area for trip stop information. It holds operational data for the scheduled and actual stops along a trip — arrival and departure dates, location details, weight and volume readings, carrier estimates, and the associated shipping transaction references — before that data is validated and transferred into the permanent trip stop tables. In Oracle EBS 12.1.1 and 12.2.2, records in this table are typically populated by external transportation management, integration, or carrier-facing loaders that push planned trip and stop information into Shipping Execution for processing.

From a modeling perspective, the ETRM metadata classifies this table as "hub-leaning" based on its foreign key structure. A Data Vault design would suggest treating STOP_INTERFACE_ID as the hub business key, with the referenced trip, stop, and location identifiers acting as link relationships. The table is anchored by the primary key WSH_TRIP_STOPS_INTERFACE_PK on STOP_INTERFACE_ID, and it is also cross-referenced by unique index WSH_TRIP_STOPS_INTERFACE_U1 on the same column.

Key Information Stored

The table is documented as containing 87 columns. The most consequential include:

Common Use Cases and Queries

Typical use cases include monitoring pending interface records before the trip stop processor runs, reconciling successful versus failed loads, and diagnosing processing errors via the process flags.

SELECT stop_interface_id, trip_interface_id, stop_location_id,
       status_code, process_flag, process_mode
FROM   wsh_trip_stops_interface
WHERE  process_flag IS NULL
   OR  process_flag = 'N';

A second common pattern joins the interface table to WSH_TRIPS_INTERFACE to audit trips awaiting stop processing:

SELECT ti.trip_interface_id, ts.stop_interface_id, ts.stop_sequence_number
FROM   wsh_trips_interface ti, wsh_trip_stops_interface ts
WHERE  ti.trip_interface_id = ts.trip_interface_id
AND    ts.interface_action_code = 'CREATE';

Reporting over planned versus actual arrival dates supports on-time performance analysis, while weight and volume columns feed capacity and load utilization reports. Interface action codes distinguish insert, update, and delete operations for reconciliation.

Related Objects