Search Results dpw_assigned_flag




Overview
Explore in AI Chat

Overview

SO_DELIVERIES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the Order Entry (OE) product family. It presents a consolidated, order-centric picture of outbound shipping activity by joining order header, order line, delivery, and departure information into a single denormalized structure. Its stated purpose, reflected in the inline comment "ASSIGNED, UNRELEASED LINE DETAILS," is to expose order lines that have been assigned to a delivery or departure but not yet fully released or closed, thereby supporting shipment tracking, delivery scheduling, and carrier coordination reporting.

The view is registered as VALID at the APPS level and is available in both Oracle EBS 12.1.1 and 12.2.2. Because it is a view rather than a table, it carries no independent storage and derives all content at query time from its underlying base objects. This makes it a convenient integration and reporting surface for shipping-related data without requiring consumers to reconstruct the complex join logic between order management and warehouse shipping tables themselves.

The user search term "departure_date" maps directly to a computed column in this view. The DEPARTURE_DATE column is derived conditionally from the parent WSH_DEPARTURES record, selecting the actual departure date when the departure status is CLOSED, and the planned departure date for PLANNED or OPEN statuses, with a default fallback to the planned date in all other cases. This makes the column a reliable single source for the effective departure timestamp regardless of lifecycle stage.

Underlying Base Objects

SO_DELIVERIES_V is built from synonyms referencing the following documented base objects: MTL_PARAMETERS, SO_HEADERS_ALL, SO_LINES_ALL, SO_LINE_DETAILS, SO_LOOKUPS, SO_PICKING_HEADERS_ALL, SO_PICKING_LINES_ALL, SO_PICKING_LINE_DETAILS, WSH_DELIVERIES, and WSH_DEPARTURES, along with the FND_GLOBAL package. The published view text joins SO_HEADERS_ALL to SO_LINES_ALL on HEADER_ID, then to SO_LINE_DETAILS on LINE_ID. SO_LINE_DETAILS is the pivotal table linking order lines to deliveries (DELIVERY_ID) and departures (DEPARTURE_ID). MTL_PARAMETERS supplies the warehouse organization code, WSH_DELIVERIES supplies delivery attributes, and WSH_DEPARTURES supplies departure attributes. SO_LOOKUPS is outer-joined twice against the SHIPPING_STATUS lookup type to translate departure and delivery status codes into descriptive meanings.

Key Columns

Common Use Cases and Queries

Typical uses include reporting open shipments by departure, tracking expected arrival against planned departure, and reconciling carrier waybills to order lines. The DISTINCT clause and the shippable/ATO filters in the view text mean it returns only shippable, non-service lines, which suits shipment-status dashboards rather than order-entry validation.

A representative query retrieving departure timing for a specific order:

  • SELECT order_number, delivery_name, departure_name, departure_date, expected_arrival_date, freight_carrier_code FROM apps.so_deliveries_v WHERE order_number = :p_order_number ORDER BY departure_date;

All access should respect the view's APPS ownership and standard EBS security conventions.