Search Results load_seq_number




Overview
Explore in AI Chat

Overview

WSH_SHIPPING_DETAILS_V is a shipping execution view owned by the APPS schema in Oracle E-Business Suite, classified under the WSH - Shipping Execution product. It presents a consolidated, order-line-oriented projection of delivery detail activity, joining order management data to warehouse execution data so that shipping, inventory, and receiving processes can query a single flat source. In Release 12.1.1 and 12.2.2 the view carries a VALID status and forms part of the standard seeded object set delivered with the Shipping Execution module. Its principal role is to expose shipping state at the delivery-detail grain while retaining order header and order line context, which makes it suitable for reports, concurrent programs, and interface extracts that need to correlate ordered quantities, requested quantities, and shipped quantities without navigating the full WSH_DELIVERY_DETAILS structure.

Underlying Base Objects

The view is defined over a combination of synonyms, views, and a package. Documented referenced objects include OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL, which supply order header and line context such as ship-to organisation, ship-to contact, demand class, item type, component code, and component sequence. WSH_DELIVERY_DETAILS provides the delivering detail grain, sourced through WSH_DELIVERY_ASSIGNMENTS_V to link delivery details to deliveries. WSH_NEW_DELIVERIES, WSH_DELIVERY_LEGS, WSH_TRIP_STOPS, WSH_LOCATIONS, WSH_LOOKUPS, and HR_LOCATIONS_ALL supply delivery, leg, trip stop, warehouse, and inventory organisation attributes. OE_INSTALL is referenced as a package. The view text aliases these sources as OL, WDD, WND, HRLOC, and WTS, confirming a direct join between order lines and delivery details.

Key Columns

Order context columns include ORDER_HEADER_ID and ORDER_LINE_ID from the order tables, along with SHIP_TO_SITE_USE_ID, SHIP_TO_CONTACT_ID, DEMAND_CLASS_CODE, COMPONENT_CODE, and COMPONENT_SEQUENCE_ID.

The user search term invoiced_quantity corresponds directly to the INVOICED_QUANTITY column in the view text. Notably, it is defined as TO_NUMBER(NULL), meaning the column is present for interface compatibility but is not populated by this view.

Common Use Cases and Queries

Typical uses include shipping reports that compare requested versus shipped quantities, warehouse workload extracts by warehouse and demand class, and integration feeds that need order line context at the delivery detail grain. Filtering on INVENTORY_STATUS, MVT_STAT_STATUS, or RELEASED_STATUS supports operational monitoring of open and interfaced deliveries.

A common query pattern selects shipping detail attributes for a given order or warehouse:

  • SELECT ORDER_HEADER_ID, ORDER_LINE_ID, PICKING_LINE_DETAIL_ID, INVENTORY_ITEM_ID, WAREHOUSE_ID, REQUESTED_QUANTITY, SHIPPED_QUANTITY, REQUESTED_QUANTITY_UOM, CONFIRM_DATE, INVENTORY_STATUS FROM WSH_SHIPPING_DETAILS_V WHERE ORDER_HEADER_ID = :p_header_id;
  • SELECT WAREHOUSE_ID, INVENTORY_ITEM_ID, SUM(REQUESTED_QUANTITY), SUM(SHIPPED_QUANTITY) FROM WSH_SHIPPING_DETAILS_V GROUP BY WAREHOUSE_ID, INVENTORY_ITEM_ID;

Because INVOICED_QUANTITY is not populated in this view, reporting requirements that depend on invoiced quantities must source data from the appropriate Receivables interface tables rather than from WSH_SHIPPING_DETAILS_V. Users should also be aware that the NULL placeholder columns exist to preserve a stable interface signature and should not be relied upon for data retrieval.