Search Results mode_of_transport




Overview
Explore in AI Chat

Overview

WSH_TRIPS_OB_GRP_V is an Oracle E-Business Suite view owned by the APPS schema within the WSH – Shipping Execution product. In Release 12.1.1 and 12.2.2 this view exposes trip-level records that support outbound (OB) and group-oriented shipping operations, including both regular outbound trips and consolidated or multi-stop shipments. The view is a filtered projection of the base trip entity, restricted to rows whose SHIPMENTS_TYPE_FLAG resolves to 'O' (outbound) or 'M', using the predicate NVL(SHIPMENTS_TYPE_FLAG,'O') IN ('O','M'). It therefore provides a stable, denormalized read surface for trips that participate in outbound and grouped movement, excluding trip types not relevant to those flows. Its principal role is reporting and integration: it is commonly referenced by shipping reports, freight cost analyses, carrier and tender extracts, and interface programs that require trip header attributes without joining directly to the WSH_TRIPS table. Because it carries the full standard WHO columns and concurrent program columns, it supports audit-aware and request-aware reporting. For the search term "mode_of_transport", the view is directly relevant: MODE_OF_TRANSPORT is one of the columns projected by the view and provides the transportation mode associated with the trip (for example, air, ocean, ground, or rail), which drives rating, routing, and carrier selection logic.

Underlying Base Objects

The documented base object is WSH_TRIPS, accessed via the APPS.WSH_TRIPS synonym. WSH_TRIPS is the Shipping Execution table that stores trip headers, including assignments of vehicles, carriers, routes, and freight terms. WSH_TRIPS_OB_GRP_V selects from this table with a WHERE clause that retains only outbound and 'M' type trips, based on SHIPMENTS_TYPE_FLAG with NVL defaulting nulls to 'O'. It performs no aggregation, joins, or expressions beyond the filter; each qualified row in WSH_TRIPS surfaces as one row in the view. Because the view is a direct, unfiltered projection apart from the flag predicate, all common audit and workflow columns remain available and behave identically to their base table equivalents. This one-to-one relationship simplifies tuning, since predicates on TRIP_ID, STATUS_CODE, or CARRIER_ID can be pushed to the underlying table.

Key Columns

Common Use Cases and Queries

Typical uses include outbound trip dashboards, mode-of-transport analysis, carrier and tender reporting, and interface extracts requiring trip headers. A common query lists shipped and unshipped outbound trips by mode:

  • SELECT trip_id, name, status_code, carrier_id, mode_of_transport, ship_method_code FROM wsh_trips_ob_grp_v WHERE status_code = 'CLOSED' ORDER BY name;
  • SELECT mode_of_transport, COUNT(*) FROM wsh_trips_ob_grp_v WHERE creation_date >= :from_date GROUP BY mode_of_transport;
  • SELECT t.trip_id, t.name, t.load_tender_status, t.carrier_response FROM wsh_trips_ob_grp_v t WHERE t.load_tender_status = 'TENDERED';

Because the view is a thin projection over WSH_TRIPS, performance depends on effective indexing of the base table; filter and join on TRIP_ID, CARRIER_ID, STATUS_CODE, and MODE_OF_TRANSPORT to access the underlying indexes efficiently. Reports requiring trip stops, delivery details, or freight costs should join TRIP_ID to the corresponding shipping tables rather than expecting those details within the view.