Search Results volume_uom_code




Overview
Explore in AI Chat

Overview

WSHBV_TRIP_STOPS is an Oracle Shipping Execution (WSH) view owned by the APPS schema and shipped as a valid, read-only object in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes trip stop information — the individual legs of a trip — one row per trip stop, combining transportation planning attributes stored on WSH_TRIP_STOPS with the stop's physical location from WSH_LOCATIONS. The "BV" prefix and the fact that the view is defined WITH READ ONLY indicate it is a business view intended for query and reporting rather than for DML; it is a lightweight presentation layer over the underlying Shipping Execution tables.

The view restricts rows to freight or shipment trips that are of order or manifest type. Specifically, the predicate NVL(WTS.SHIPMENTS_TYPE_FLAG,'O') IN ('O','M') limits trip stops to outbound order trips ('O') and manifest trips ('M'). In reporting and integration contexts, WSHBV_TRIP_STOPS is queried by custom reports, OBIEE/BIP extracts, and interface programs that require a denormalized, joined view of trip stop scheduling and load data without accessing the base tables directly.

Underlying Base Objects

The view is defined as a join of two referenced objects, both exposed to APPS as synonyms:

  • WSH_TRIP_STOPS (WTS) — the base trip stop table holding sequence, dates, departure weights/volumes, seal, fill percent, and interface status.
  • WSH_LOCATIONS (LOC) — the shipping location table, joined via WTS.STOP_LOCATION_ID = LOC.WSH_LOCATION_ID.

The SELECT list projects the location surrogate key as LOC.SOURCE_LOCATION_ID, aliased to the STOP_LOCATION_ID column in the view. Because both underlying objects are joined in a single SELECT with no UNION or aggregate, the view is a simple equijoin with one row per qualifying trip stop. Token-translated columns (STATUS_CODE and PENDING_INTERFACE_FLAG) are resolved at runtime using the _LA: lookup syntax into WSH_LOOKUPS and FND_LOOKUPS respectively.

Key Columns

Common Use Cases and Queries

Typical usage includes trip load reporting by weight UOM, stop-level on-time analysis, and integration extracts requiring location and status lookups. The following query retrieves stops and departure weight detail for a given trip:

SELECT trip_id,
       stop_id,
       stop_sequence_number,
       stop_location_id,
       planned_arrival_date,
       actual_arrival_date,
       departure_gross_weight,
       departure_net_weight,
       weight_uom_code,
       volume_uom_code
FROM   apps.wshbv_trip_stops
WHERE  trip_id = :p_trip_id
ORDER  BY stop_sequence_number;

A second common pattern aggregates departing net weight by unit of measure across all manifest and order trips:

SELECT weight_uom_code,
       SUM(departure_net_weight) total_net_weight
FROM   apps.wshbv_trip_stops
GROUP  BY weight_uom_code;

A third pattern isolates stops with pending interface status for reconciliation:

SELECT trip_id, stop_id, stop_sequence_number
FROM   apps.wshbv_trip_stops
WHERE  wshbv_trip_stops."_LA:PENDING_INTERFACE_FLAG" = 'Yes';

Because the view is read-only and denormalized, it is well suited to read-only reporting responsibilities. Queries that require columns outside the projected set, or that target non-order/manifest trips, must fall back to the base WSH_TRIP_STOPS and WSH_LOCATIONS tables directly.