Search Results trip_stop_status

Overview

APPS.WSH_TRIP_STOPS_V is a reporting and integration view in the Oracle E-Business Suite Warehouse Management (WSH) module, exposing the individual stop-level details of trips managed by Oracle Transportation Management (OTM) / Transportation Execution. In Oracle EBS 12.1.1 and 12.2.2, the view consolidates a trip's stops with descriptive lookup meanings and trip names, providing a denormalized, presentation-ready result set that shields callers from joins across multiple base tables. The view is defined over WSH_TRIP_STOPS, WSH_TRIPS, and WSH_LOOKUPS, joining trip header data and decoding the stop status code into a user-facing meaning.

The view's primary value is the resolution of the status_code column. Because the search term "trip_stop_status" is addressed directly, the view's join to WSH_LOOKUPS with lookup_type = 'TRIP_STOP_STATUS' is central: it returns wl.meaning, the translated description of the stop's status. This makes the view suitable for operational dashboards, shipment tracking, and interface extracts where a coded status alone would be insufficient.

Underlying Base Objects

The documented base objects are:

• WSH_TRIP_STOPS (SYNONYM) — the driving table, aliased s; provides stop_id, trip_id, stop_location_id, status_code, planned and actual dates, weights, volumes, and descriptive flexfields.
• WSH_TRIPS (SYNONYM) — aliased t; joined on t.trip_id = s.trip_id to supply the trip name.
• WSH_LOOKUPS (VIEW) — aliased wl; joined on lookup_type = 'TRIP_STOP_STATUS' and lookup_code = s.status_code to resolve the status meaning.

The join is an inner join on all three objects, and the view is additionally filtered by NVL(s.shipments_type_flag, 'O') IN ('O', 'M'), restricting results to outbound and (by the 'M' flag) related shipment stop types.

Key Columns

The view projects two null numeric placeholders at the start, followed by s.rowid. Principal columns include:

• stop_id, trip_id, stop_sequence_number — identity and ordering of the stop within the trip.
• name — the trip name from WSH_TRIPS.
• stop_location_id, wsh_location_id, physical_location_id — location references for the stop.
• status_code / meaning — the raw stop status code and its TRIP_STOP_STATUS lookup meaning.
• planned_arrival_date, planned_departure_date, actual_arrival_date, actual_departure_date — schedule versus execution timestamps.
• departure_gross_weight, departure_net_weight, weight_uom_code, departure_volume, volume_uom_code, departure_fill_percent — load metrics.
• departure_seal_code, wv_frozen_flag, tracking_drilldown_flag, tracking_remarks — operational and tracking attributes.
• carrier_est_departure_date, carrier_est_arrival_date and loading/unloading start and end datetimes.
• attribute1–15 and tp_attribute1–15 — descriptive flexfield segments.
• creation_date, created_by, last_update_date, last_updated_by, program_application_id, program_id, request_id — standard WHO audit columns.

Common Use Cases and Queries

Typical uses include stop-status reporting, tracking extracts, and integration feeds. A basic status report:

• SELECT trip_id, name, stop_sequence_number, status_code, meaning, actual_arrival_date FROM apps.wsh_trip_stops_v ORDER BY trip_id, stop_sequence_number;

Filtering incomplete stops for operational follow-up:

• SELECT trip_id, stop_id, status_code, meaning FROM apps.wsh_trip_stops_v WHERE actual_arrival_date IS NULL AND status_code NOT IN ('CLOSED'));

Extracting load metrics for a given trip:

• SELECT stop_id, departure_gross_weight, departure_net_weight, weight_uom_code, departure_fill_percent FROM apps.wsh_trip_stops_v WHERE trip_id = :p_trip_id;

Because the view already resolves the TRIP_STOP_STATUS meaning and joins the trip name, it removes the need for downstream consumers to replicate lookup joins, simplifying both ad-hoc reporting and programmatic integration in 12.1.1 and 12.2.2 environments.