Search Results departure_gross_weight




Overview
Explore in AI Chat

Overview

APPS.WSHBV_TRIP_STOPS is a read-only business view (identified by the "BV" naming convention) in the Oracle E-Business Suite transportation model. It presents one row for each stop on a trip, enriched with the resolved source location identifier and several lookups translated to their display meanings. The view is defined WITH READ ONLY, so it is intended strictly for query, reporting, and integration consumption rather than for direct DML.

The view plays a dual role. First, it is an operational reporting surface for transportation planners and logistics analysts who need to see the sequence of stops, planned versus actual arrival and departure timestamps, and the departure metrics captured at each stop. Second, because it decodes coded columns through _LA: lookup attributes (STATUS_CODE, PENDING_INTERFACE_FLAG) and joins the location master, it serves as a convenience layer for downstream integrations and BI extracts that would otherwise have to replicate the same joins and lookup resolution. The user's search term, "departure_gross_weight," corresponds directly to the DEPARTURE_GROSS_WEIGHT column exposed by this view, which is one of the departure quantity attributes captured when a trip stop is closed out.

Underlying Base Objects

The view is defined over two base objects, both exposed to APPS as synonyms:

  • WSH_TRIP_STOPS (alias WTS) — the driving table. It holds the physical stop records for each trip, including stop sequencing, planned and actual dates, departure weights and volumes, seal and fill information, audit columns, and the SHIPMENTS_TYPE_FLAG.
  • WSH_LOCATIONS (alias LOC) — the location master. The join is WTS.STOP_LOCATION_ID = LOC.WSH_LOCATION_ID, and the view projects LOC.SOURCE_LOCATION_ID so that consumers see the underlying location reference rather than the surrogate WSH location key.

A restrictive predicate is applied in the WHERE clause: NVL(WTS.SHIPMENTS_TYPE_FLAG, 'O') IN ('O', 'M'). This means the view returns only stop records whose shipments-type flag is either 'O' (the default when null) or 'M', filtering out other stop classifications. Analysts should be aware of this filter, as it can explain apparent discrepancies between row counts in this view and the full contents of WSH_TRIP_STOPS.

Key Columns

Common Use Cases and Queries

Typical uses include trip stop schedule reporting, variance analysis between planned and actual departure times, and extracting departure weight and volume for load or capacity analysis. The following query retrieves stops for a given trip in stop sequence order:

  • SELECT stop_id, trip_id, stop_sequence_number, source_location_id, planned_departure_date, actual_departure_date, departure_gross_weight, weight_uom_code FROM apps.wshbv_trip_stops WHERE trip_id = :trip_id ORDER BY stop_sequence_number;
  • SELECT trip_id, stop_id, departure_net_weight, departure_volume FROM apps.wshbv_trip_stops WHERE departure_gross_weight IS NOT NULL;
  • SELECT s.stop_id, s.status_code_meaning, s.pending_interface_flag_meaning FROM apps.wshbv_trip_stops s WHERE s.pending_interface_flag_meaning = 'Yes';

Because the view is read-only, it should be used for selection only; any corrections to departure weights or stop status must be made against the base WSH_TRIP_STOPS table through supported application flows.