Search Results wsh_delivery_details




Overview
Explore in AI Chat

Overview

The WSH_DELIVERY_DETAILS table is a core transactional entity within the Oracle E-Business Suite Shipping Execution (WSH) module, central to the fulfillment and logistics processes in versions 12.1.1 and 12.2.2. It serves as the master repository for all items or lines that are candidates for shipping. Each record represents a specific quantity of an item sourced from an order line, return line, or other transaction that requires physical shipment. The table's primary role is to track the lifecycle of these shippable entities from their initial release for shipping through picking, packing, and final delivery confirmation, acting as the critical link between Order Management (OM), Inventory (INV), and Shipping Execution.

Key Information Stored

Each row is uniquely identified by the primary key column DELIVERY_DETAIL_ID. The table stores extensive metadata about the shippable item, including references to its source transaction (e.g., OE_ORDER_LINES_ALL.SOURCE_LINE_ID), the inventory organization, item identifier, and requested quantity. Key operational columns track the current shipping status, such as RELEASED_STATUS, which indicates if the line is 'B' for Backordered, 'C' for Shipped, 'D' for Cancelled, 'R' for Ready to Release, or 'S' for Released. The table also maintains relationships to logistical constructs, including links to a delivery (DELIVERY_ID), trip (TRIP_ID), and stop (STOP_ID). The SPLIT_FROM_DELIVERY_DETAIL_ID column, which is part of a self-referential foreign key, is crucial for tracking when a source line has been divided for partial shipments or consolidation.

Common Use Cases and Queries

A primary use case is generating a pick slip or delivery report for a specific delivery. A typical query joins WSH_DELIVERY_DETAILS to order and item tables to list all lines. Another common scenario is analyzing the shipping backlog by querying lines where RELEASED_STATUS is 'R' (Ready) and DELIVERY_ID is NULL. For troubleshooting, developers often trace the lineage of split lines using the SPLIT_FROM_DELIVERY_DETAIL_ID column. A standard pattern for fetching delivery detail information for reporting is:

  • SELECT wdd.source_line_id, wdd.source_header_id, wdd.requested_quantity, wdd.shipped_quantity, wdd.released_status, wdd.delivery_id
  • FROM wsh_delivery_details wdd
  • WHERE wdd.delivery_id = :p_delivery_id;

Integration points, such as interfacing shipped quantities back to Order Management or generating custom shipping documents, consistently use this table as the source of truth for shippable lines.

Related Objects

As indicated by the foreign key metadata, WSH_DELIVERY_DETAILS is highly interconnected. It is the parent table for assignment history (WSH_DELIVERY_ASSIGNMENTS), freight charges (WSH_FREIGHT_COSTS), and exceptions (WSH_EXCEPTIONS). Crucially, it is referenced by key interface tables like WSH_DEL_DETAILS_INTERFACE for importing data and WMS_SHIPPING_TRANSACTION_TEMP for processing material transactions. Its relationship with Order Management is often indirect via the SOURCE_LINE_ID column linking to OE_ORDER_LINES_ALL. The provided metadata also shows integrations with specialized localizations (JAI_OM_* tables) and Project Contracts (OKE_K_DELIVERABLES_B). The table's central role is further evidenced by its self-referencing foreign key, which manages line splits within the shipping process itself.