Search Results trip_status




Overview
Explore in AI Chat

Overview

APPS.WSH_PURGE_SET_V is a view owned by the APPS schema and registered in Oracle E-Business Suite under the FND design data reference WSH.WSH_PURGE_SET_V. It is classified as an internal view (View Type: Internal), and the Oracle documentation carries the explicit warning that it is Oracle Internal Use Only; Oracle Corporation does not support access to application data through this object except from standard Oracle Applications programs. Its status in both 12.1.1 and 12.2.2 is VALID.

Functionally, the view presents a denormalized shipping picture: trip headers, the stops and legs that make up a trip, the deliveries assigned to those trips, and the delivery details and document instances beneath them. Because the column list is organised hierarchically from trip to delivery detail, the view is oriented toward purge and archival processing logic rather than general inquiry. The presence of the TRIP_STATUS column—the term the user searched for—indicates that consumers of this view are expected to filter or evaluate trips by lifecycle state (for example, closed or cancelled trips eligible for removal) before acting on the associated shipping records.

Underlying Base Objects

The documented base objects underlying WSH_PURGE_SET_V span the shipping, order management, customer, and inventory schemas:

All WSH and MTL objects are referenced through APPS synonyms, and the join structure follows the natural parent-child path WSH_TRIPS → WSH_TRIP_STOPS/WSH_DELIVERY_LEGS → WSH_DELIVERY_ASSIGNMENTS_V → WSH_NEW_DELIVERIES → WSH_DELIVERY_DETAILS, with lookups, locations, customer, and inventory tables supplying descriptive attributes.

Key Columns

The view exposes a hierarchical set of columns. TRIP_ID, TRIP_NAME, TRIP_STATUS, and TRIP_CREATION_DATE identify the trip and its state; TRIP_SHIPMENTS_TYPE classifies the trip's shipment content. The pickup tier is represented by PICKUP_STOP_ID, PICKUP_STOP_SHIPMENTS_TYPE, PICKUP_STOP_GROSS_WEIGHT, PICKUP_STOP_WEIGHT_UOM, PICKUP_STOP_WEIGHT_UOM_MEANING, and PICKUP_STOP_SHIP_DATE. LEG_ID, LEG_GROSS_WEIGHT, and LEG_WEIGHT_UOM describe transportation legs.

Delivery-level columns include DEL_ID, DEL_NAME, DEL_SHIP_FROM_ORG, DEL_PICKUP_DATE, DEL_SHIP_DATE, DEL_DROPOFF_DATE, DEL_SHIPPING_CONTROL, DEL_SHIPMENT_DIRECTION, DEL_WAYBILL, DEL_GROSS_WEIGHT, DEL_WEIGHT_UOM, DEL_CUSTOMER_ID, DEL_CUSTOMER_NAME, DEL_ULT_DO_LOCATION_ID, DEL_UI_LOCATION_CODE, and DEL_CREATION_DATE. At the delivery-detail tier the view surfaces DD_ID, DD_LINE_DIRECTION, DD_SHIPPING_CONTROL, DD_SOURCE_CODE and DD_SOURCE_MEANING, DD_SOURCE_HEADER_ID and DD_SOURCE_HEADER_NUMBER, DD_SOURCE_HEADER_TYPE_ID and DD_SOURCE_HEADER_TYPE_NAME, DD_PO_SHIPMENT_LINE_ID, and the BOL column. TRIP_STATUS is the principal qualifier for purge eligibility, while DEL_GROSS_WEIGHT and LEG_GROSS_WEIGHT support assessment of trip contents.

Common Use Cases and Queries

Typical use cases are purge-eligibility analysis, shipping audit reporting, and data-extraction feeds to external archives. Although direct customer access is unsupported, the view is valuable as a reference model for understanding how trip, delivery, and delivery-detail data interrelate. A representative query filtering on trip status is:

SELECT TRIP_ID, TRIP_NAME, TRIP_STATUS, TRIP_CREATION_DATE,
       DEL_ID, DEL_NAME, DEL_SHIP_DATE, DEL_GROSS_WEIGHT
FROM   APPS.WSH_PURGE_SET_V
WHERE  TRIP_STATUS IN ('CLOSED','CANCELLED')
ORDER  BY TRIP_CREATION_DATE;

A second pattern aggregates trip weight for capacity verification:

SELECT TRIP_NAME, TRIP_STATUS,
       SUM(LEG_GROSS_WEIGHT) AS TOTAL_LEG_WEIGHT
FROM   APPS.WSH_PURGE_SET_V
GROUP  BY TRIP_NAME, TRIP_STATUS;

Because the object is internal, any custom usage should be limited to read-only queries for diagnostics or reconciliation, and the underlying WSH tables should be treated as the authoritative source.