Search Results loading_end_datetime




Overview
Explore in AI Chat

Overview

WSH_TRIP_STOPS_OB_GRP_V is an APPS-owned database view in the Oracle E-Business Suite Shipping Execution (WSH) module. It is a restricted projection of the WSH_TRIP_STOPS table, designed to expose trip stop records that belong to outbound or "OB" shipment groupings. The view filters the parent table with the predicate NVL(SHIPMENTS_TYPE_FLAG, 'O') IN ('O', 'M'), meaning it returns only stops whose shipment type flag is "O" (outbound) or "M", or is null (defaulted to "O"). Stops associated with inbound or other shipment type flags are excluded.

The view is informational and read-only; it carries no DML logic of its own and inherits all column definitions from WSH_TRIP_STOPS. It is typically consumed by reports, concurrent programs, and integration extracts that need a clean, outbound-scoped list of trip stops without additional filtering. In ETRM 12.2.2 the object is documented as VALID in the APPS schema.

Underlying Base Objects

The view is defined over a single base object, WSH_TRIP_STOPS, referenced through a synonym in the APPS schema. WSH_TRIP_STOPS stores the physical stop records that make up a trip in Transportation Execution, including arrival and departure timings, weight and volume, and both descriptive and developer flexfield segments. Because the view selects from this table without joins, it does not expand or denormalize data; every row in the view corresponds one-to-one with an eligible row in WSH_TRIP_STOPS. The only transformation applied is the SHIPMENTS_TYPE_FLAG filter described above.

Key Columns

Common Use Cases and Queries

Typical uses include outbound trip stop reporting, carrier departure/arrival tracking, and flexfield-based extracts. Because TP_ATTRIBUTE15 is exposed directly, it is commonly queried when a customer has repurposed that segment for a business-specific value such as a dock code or carrier reference.

SELECT stop_id, trip_id, stop_sequence_number,
       planned_arrival_date, actual_arrival_date,
       tp_attribute_category, tp_attribute15
FROM   apps.wsh_trip_stops_ob_grp_v
WHERE  trip_id = :p_trip_id
ORDER  BY stop_sequence_number;

To locate stops by a specific TP_ATTRIBUTE15 value:

SELECT stop_id, trip_id, stop_location_id, status_code
FROM   apps.wsh_trip_stops_ob_grp_v
WHERE  tp_attribute15 = :p_value;

Because the view already restricts rows to outbound-style groupings, additional filtering on SHIPMENTS_TYPE_FLAG is unnecessary, though it can be added for clarity. Users requiring inbound or all shipment types should query WSH_TRIP_STOPS directly.