Search Results wsh_deliveries




Overview
Explore in AI Chat

Overview

The WSH_DELIVERIES table is a core data object within the Oracle E-Business Suite (EBS) Shipping Execution module (WSH), owned by the Order Entry (OE) schema. It serves as the master record for a delivery, which is a logical grouping of shipping tasks representing the movement of goods from a source location to a customer destination. A delivery is a fundamental unit for planning, executing, and tracking the shipment of order lines. It acts as a critical junction between Order Management fulfillment lines and the physical shipping process, enabling functions like trip planning, freight consolidation, and delivery documentation.

Key Information Stored

The table's primary key is DELIVERY_ID, which uniquely identifies each delivery record. Key columns, as indicated by its foreign key relationships, store essential shipment planning and execution data. These include CUSTOMER_ID (referencing RA_CUSTOMERS), and ULTIMATE_SHIP_TO_ID and INTERMEDIATE_SHIP_TO_ID (both referencing RA_SITE_USES_ALL) to define the delivery's destination hierarchy. The table links to the departure process via PLANNED_DEPARTURE_ID and ACTUAL_DEPARTURE_ID, which reference the WSH_DEPARTURES table to track scheduled and real departure events. Other significant columns include REPORT_SET_ID (linking to SO_REPORT_SETS for documentation) and status fields that track the delivery's lifecycle from initial creation through to completion.

Common Use Cases and Queries

This table is central to shipping operations and reporting. Common use cases include generating delivery notes and packing slips, tracking delivery status for customer service inquiries, and analyzing shipment consolidation efficiency. A typical query might join WSH_DELIVERIES with order and customer tables to create an open delivery report. For example:

  • Tracking deliveries by customer and status: SELECT d.delivery_id, d.name, c.customer_number, d.status_code FROM wsh_deliveries d, ra_customers c WHERE d.customer_id = c.customer_id AND d.status_code = 'OP';
  • Linking deliveries to their associated departure and ship-to address: SELECT d.delivery_id, dep.name as departure, site_ship_to.address_line_1 FROM wsh_deliveries d, wsh_departures dep, ra_site_uses_all site_ship_to WHERE d.planned_departure_id = dep.departure_id AND d.ultimate_ship_to_id = site_ship_to.site_use_id;

Related Objects

WSH_DELIVERIES has extensive integration across the shipping and order fulfillment modules. As per the metadata, it is referenced by numerous key transactional tables, including SO_PICKING_HEADERS_ALL, SO_PICKING_LINE_DETAILS, SO_LINE_DETAILS, and WSH_PACKED_CONTAINERS, establishing it as the anchor for pick release and packing processes. It is also referenced by SO_FREIGHT_CHARGES for rating and WSH_INVOICE_NUMBERS for invoicing. The table itself references master data tables like RA_CUSTOMERS and RA_SITE_USES_ALL for customer and address information, and WSH_DEPARTURES for transportation planning. This network of relationships underscores its pivotal role in the order-to-ship lifecycle.