Search Results wsh_delivery_lines_dpw_v

Overview

WSH_DELIVERY_LINES_DPW_V is a reporting view in the Oracle E-Business Suite Order Entry (OE) module that exposes delivery line information specifically structured for the Departure Planning Workbench (DPW). The Departure Planning Workbench is the shipping execution interface in Oracle Shipping (WSH) that allows planners and warehouse personnel to group delivery lines into departures — logical shipments scheduled to leave a warehouse on a planned departure date. This view presents one row per delivery line detail ranked with its associated departure, delivery, order header, and shipping attributes, providing the data foundation that the DPW form and its associated concurrent programs consume.

The view is not implemented as a physical database object in every environment; ETRM documentation for 12.2.2 notes it as "Not implemented in this database." Consequently, it is referenced primarily by Oracle Forms and internal shipping logic rather than by customer-written reports, and it should be treated as a read-only, Oracle-owned object. Its principal value to technical consultants is as a reference for the column-level semantics of delivery line data during departure planning.

Underlying Base Objects

The view is defined over a set of Shipping Execution and Order Management tables, joined to produce a flattened delivery-line-plus-departure record. The documented view text references the following base objects:

• WSH_DELIVERY_DETAILS (aliased SLD) — the driving table, supplying line_detail_id, delivery_id, departure_id, warehouse_id, item, lot, revision, subinventory, quantity, and scheduling attributes.
• WSH_DELIVERY_ASSIGNMENTS (SLD/SL relationship) and WSH_NEW_DELIVERIES (DEL) — delivery header context, including delivery name, status code, and pooled ship-to.
• WSH_TRIPS or WSH_DEPARTURES (DEP) — departure name, status, and planned departure date.
• OE_ORDER_HEADERS_ALL (SH) — order number, order type, customer, currency, FOB, freight terms, and open flag.
• OE_ORDER_LINES_ALL (SL) — line number, ship-to and intermediate ship-to site uses, ship method, model/serial attributes, parent line linkage, and descriptive flexfield segments.
• HZ_CUST_ACCOUNTS / customer tables (CUST) and location tables (USHIP, ISHIP, PSHIP) — customer name and location descriptions for the ship-to chain.
• WIP_ENTITIES (WIP) — manufacturing work order name for ATO/configured items.
• OE_ORDER_SOURCES or order type tables (SOTA) — order type name.
• WSH_ITEM_ATTRIBUTES or item default tables (SLA) — industry context and industry attribute flexfield columns used for DPW planning.

The join produces one row per delivery line detail, with departure and delivery header data denormalised onto each row.

Key Columns

• LINE_DETAIL_ID — primary key of the delivery line detail; the granular identifier for the row.
• DELIVERY_ID, DEPARTURE_ID — foreign keys to the delivery and departure headers, with corresponding NAME and STATUS_CODE columns from the delivery and departure records.
• PLANNED_DEPARTURE_DATE — the scheduled departure date used by the DPW to sequence and plan shipments.
• DEP_PLAN_REQUIRED_FLAG, DPW_ASSIGNED_FLAG — flags indicating whether departure planning is required and whether the line has already been assigned in the DPW.
• ORDER_NUMBER, ORDER_TYPE_ID, LINE_NUMBER — order identification for traceability back to Order Management.
• SHIP_TO_SITE_USE_ID, LOCATION — resolved ship-to address, taken from the line or defaulting to the header.
• QUANTITY, UNIT_CODE, SCHEDULE_DATE — shipping quantity and requested schedule date.
• RELEASED_FLAG, SHIPPABLE_FLAG, INCLUDED_ITEM_FLAG — status flags governing which lines the DPW may plan.
• LOAD_SEQ_NUMBER — sequencing value for load ordering within a departure.
• INDUSTRY_CONTEXT and INDUSTRY_ATTRIBUTE1..15 — analytics flexfield columns exposed for reporting and planning filters.
• WIP_ENTITY_NAME — work order reference for configured/ATO items.

Common Use Cases and Queries

Because the view is Oracle-owned and used by the Departure Planning Workbench, direct customer queries are uncommon, but it is frequently inspected for troubleshooting departure planning behaviour and for building custom DPW-style reports. A representative query listing unplanned delivery lines by warehouse is:

SELECT departure_id, delivery_id, order_number, line_number,
       inventory_item_id, quantity, planned_departure_date,
       dep_plan_required_flag, dpw_assigned_flag
  FROM wsh_delivery_lines_dpw_v
 WHERE warehouse_id = :warehouse_id
   AND NVL(dpw_assigned_flag,'N') = 'N'
 ORDER BY planned_departure_date, load_seq_number;

Another common scenario is identifying lines attached to a departure with a given status:

SELECT dd.name delivery, d2.name departure, h.order_number,
       dl.line_number, dl.quantity
  FROM wsh_delivery_lines_dpw_v dl,
       wsh_delivery_details dd,
       oe_order_headers_all h
 WHERE dl.delivery_id = dd.delivery_id
   AND dl.header_id = h.header_id
   AND dl.status_code = :departure_status;

The view is also used to confirm that lines have been correctly flagged for departure planning after order booking, and to reconcile departure assignments during deployment or upgrade validation.