Results for “move_order_line_id”

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

Overview

The WSH_INV_DELIVERY_DETAILS_V view is an APPS-owned database object within the Oracle E-Business Suite Shipping Execution (WSH) module, validated as a standard reporting and integration interface across release levels 12.1.1 and 12.2.2. It presents a denormalized, order-centric projection of delivery detail records, resolving the association between outbound sales order lines, shipping deliveries, and the trip stops that carry those deliveries. The view is defined over both base tables and other views, and it applies strict filtering logic that restricts output to outbound or internal outbound line directions and to deliveries of type STANDARD, which makes it suitable for downstream integration points, custom reports, and data extracts where only standard outbound shipments are relevant.

Because the view exposes the TRIP_STOP_ID column directly, it is frequently searched in the context of transportation and trip planning. Users performing the search for "trip_stop_id" typically seek the association between a delivery detail and the pickup stop on the delivery leg, which is central to carrier manifests, stop-level routing queries, and intersection of order data with trip scheduling. The synonym-based references to WSH base objects mean the view is deployed consistently in both the 12.1.1 and 12.2.2 schemas, though the underlying implementation of referenced objects may vary slightly by patch level.

Underlying Base Objects

The view is constructed from a join of eight documented objects. Four are synonyms to WSH base tables — WSH_DELIVERY_DETAILS, WSH_NEW_DELIVERIES, WSH_DELIVERY_LEGS, WSH_LOCATIONS, and WSH_TRIP_STOPS — while WSH_DELIVERY_ASSIGNMENTS_V is itself a view. HZ_CUST_ACCOUNTS and OE_ORDER_LINES_ALL provide customer and order line context respectively.

• WSH_DELIVERY_DETAILS — the primary driver, supplying delivery detail grain and released status.
• WSH_DELIVERY_ASSIGNMENTS_V / WSH_NEW_DELIVERIES — resolve the delivery header and delivery type.
• WSH_DELIVERY_LEGS — correlated with a subquery selecting the minimum sequence number per delivery, ensuring only the first leg contributes the stop.
• WSH_TRIP_STOPS — supplies TRIP_STOP_ID via the pickup stop of that first leg (outer joined).
• OE_ORDER_LINES_ALL — joins on SOURCE_LINE_ID to bring shipment number.
• HZ_CUST_ACCOUNTS — inner joined on customer ID to expose account number.
• WSH_LOCATIONS — outer joined twice for ship-to and ship-from location IDs.

Key Columns

The projection renames several base columns, which can be non-obvious to consumers. TRIP_STOP_ID maps to WTS.STOP_ID from the outer-joined first delivery leg's pickup stop, so it is null for deliveries without a qualifying leg. OE_HEADER_ID and OE_LINE_ID expose the source order header and line. SHIPPING_DELIVERY_ID is the delivery ID from assignments, and DELIVERY_DETAIL_ID remains the delivery-detail primary key. Other notable columns include CUSTOMER_NUMBER (HZ account number), SHIP_TO_LOCATION and SHIP_FROM_LOCATION (WSH location IDs), SHIPMENT_PRIORITY_CODE, SHIPMENT_NUMBER (from the order line), FREIGHT_CODE (from SHIP_METHOD_CODE), MOVE_ORDER_LINE_ID, and RELEASED_STATUS.

Common Use Cases and Queries

Typical scenarios include retrieving trip stop assignments for outbound order lines, reconciling shipments against customer accounts, and feeding downstream transportation or manifest systems. A common query joins order and trip context:

• Extracting all delivery details for a given trip stop, used in stop-level dispatch reports.
• Listing shipments with null TRIP_STOP_ID to identify unplanned deliveries.
• Reporting freight code and ship-to location by customer for outbound STANDARD shipments.

SELECT TRIP_STOP_ID, SHIPMENT_NUMBER, CUSTOMER_NUMBER,
       SHIP_TO_LOCATION, FREIGHT_CODE, DELIVERY_DETAIL_ID
  FROM APPS.WSH_INV_DELIVERY_DETAILS_V
 WHERE TRIP_STOP_ID = :stop_id
   AND RELEASED_STATUS = 'R';

Because line-direction and delivery-type filters are embedded in the view definition, no additional predicates are required to exclude non-standard or inbound rows.