Results for “departure_tare_weight”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

WSH_DELIVERY_STOPS_V is a Shipping Execution (WSH) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents the association between a delivery and the trip stops that the delivery traverses, exposing one row per delivery/stop combination. The view is a UNION of two queries that resolve stops from two different route legs on the same trip: the leg where the delivery is picked up and the leg where it is dropped off. This delivery-to-stop bridging makes the view useful for reporting on planned and actual stop timings, seal codes, weight and volume readings at departure, and tracking attributes at the granularity of a delivery movement rather than a whole trip.

The user query "departure_tare_weight" maps directly to DEPARTURE_TARE_WEIGHT, a column passed straight through from the underlying trip stop source. It records the tare (empty) weight measured at the point of departure and is typically paired with DEPARTURE_GROSS_WEIGHT and DEPARTURE_NET_WEIGHT, all three expressed in the unit designated by WEIGHT_UOM_CODE.

Underlying Base Objects

The documented base objects referenced by the view are WSH_DELIVERY_LEGS (via a synonym) and WSH_TRIP_STOPS_V (itself a view). WSH_DELIVERY_LEGS supplies the delivery and its pickup/drop-off stop identifiers (PICK_UP_STOP_ID and the corresponding drop-off stop), while WSH_TRIP_STOPS_V supplies the stop-level detail: identifiers, timings, statuses, weights, volumes, and descriptive flexfield attributes. The two are joined on stop identity within each branch of the UNION. Because WSH_DELIVERY_LEGS drives the relationship, a delivery appears in the view once for its pickup stop and once for its drop-off stop, provided those stops exist on the associated trip.

Key Columns

• DELIVERY_ID — delivery identifier; the second SELECT-list position carries a TO_NUMBER(NULL) placeholder, so delivery is identified through DELIVERY_ID.
• STOP_ID, TRIP_ID, TRIP_NAME, ROW_ID — stop and trip identity and name.
• STOP_LOCATION_ID, WSH_LOCATION_ID, PHYSICAL_LOCATION_ID — location references for the stop.
• STATUS_CODE, STATUS_NAME — stop status; a DECODE expression maps OP and AR to AP and CL to PU for a derived status value.
• PLANNED_ARRIVAL_DATE, PLANNED_DEPARTURE_DATE, ACTUAL_ARRIVAL_DATE, ACTUAL_DEPARTURE_DATE — scheduled versus actual stop timings.
• DEPARTURE_TARE_WEIGHT, DEPARTURE_GROSS_WEIGHT, DEPARTURE_NET_WEIGHT, WEIGHT_UOM_CODE — departure weight measurements and their unit of measure.
• DEPARTURE_VOLUME, VOLUME_UOM_CODE, DEPARTURE_FILL_PERCENT — departure volume and fill metrics.
• DEPARTURE_SEAL_CODE, STOP_SEQUENCE_NUMBER, WV_FROZEN_FLAG — seal, sequence, and freeze indicators.
• CARRIER_EST_DEPARTURE_DATE, CARRIER_EST_ARRIVAL_DATE — carrier-estimated timings.
• LOADING_START_DATETIME, LOADING_END_DATETIME, UNLOADING_START_DATETIME, UNLOADING_END_DATETIME — loading and unloading windows.
• ATTRIBUTE1–15, TP_ATTRIBUTE1–15 — descriptive flexfield contexts and segments for the stop.
• TRACKING_DRILLDOWN_FLAG, TRACKING_REMARKS, TMS_INTERFACE_FLAG, SHIPMENTS_TYPE_FLAG — tracking and integration controls.
• Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and concurrent program columns (PROGRAM_ID, REQUEST_ID, PROGRAM_UPDATE_DATE).

Common Use Cases and Queries

Typical uses include weight verification at departure, stop-level tracking reports, and integration extracts feeding transportation or carrier systems. A query retrieving departure weights for a delivery:

• SELECT delivery_id, stop_id, trip_id, departure_tare_weight, departure_gross_weight, departure_net_weight, weight_uom_code FROM apps.wsh_delivery_stops_v WHERE delivery_id = :delivery_id;
• SELECT stop_id, departure_tare_weight FROM apps.wsh_delivery_stops_v WHERE departure_tare_weight IS NOT NULL AND status_code = 'CL';
• SELECT delivery_id, trip_id, planned_departure_date, actual_departure_date, departure_seal_code FROM apps.wsh_delivery_stops_v WHERE trip_id = :trip_id ORDER BY stop_sequence_number;

Because the view unions pickup and drop-off legs, filtering on STATUS_CODE or STOP_SEQUENCE_NUMBER may be necessary to isolate the intended stop, and callers should expect duplicate delivery rows where both legs map to the same trip.