Skip to content
EBS Reference

WSH_DELIVERY_DETAILS

Schema: WSHtransactionOU-striped (ORG_ID)Per inventory org

The atomic shipping line — one row per shippable unit of demand from order lines (or WIP/PO sources), plus container rows, tracking requested/picked/shipped quantities through pick release and ship confirm

Module: Shipping & DeliveriesOperating-unit striped (ORG_ID)
Grain note

Container rows (CONTAINER_FLAG = 'Y') are packaging, not demand — filter them out of quantity aggregates; one order line commonly fans out to several rows through splits and backorders

Notes

The catalog's first dual-anchored table: ORG_ID is the operating unit and ORGANIZATION_ID the ship-from inventory org — both anchors render in the generated SQL. RELEASED_STATUS is a one-character pick-release code whose values Oracle documents by name only, so it ships undecoded. SOURCE_CODE says which system fed the row ('OE' for sales orders).

What the badges mean
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
In field listings, K marks a primary-key field.

Fields

20 fields · 1 key

Table fields: position, field name, description, data type, and flags. 20 fields.
#FieldDescriptionTypeFlags
1DELIVERY_DETAIL_IDSurrogate key of the delivery line / container rowNUMBER
Key
2ORG_IDOperating unit — the only WSH table carrying the MOAC stripe; push OU filters down to hereNUMBER
3ORGANIZATION_IDShip-from inventory org (warehouse) — the org half of the item joinNUMBER
4SOURCE_CODEWhich system fed the row — 'OE' for sales orders, or WIP/PO sourcesVARCHAR2
5SOURCE_HEADER_IDThe source document header — the sales order header for OE rowsNUMBER
6SOURCE_LINE_IDThe source document line — the sales order line for OE rowsNUMBER
7RELEASED_STATUSOne-character pick-release status — Oracle documents the statuses by name only, so the codes ship undecoded hereVARCHAR2
8INVENTORY_ITEM_IDThe item being shippedNUMBER
9REQUESTED_QUANTITYQuantity requested to ship on this rowNUMBER
10REQUESTED_QUANTITY_UOMUOM of the requested quantityVARCHAR2
11PICKED_QUANTITYQuantity pickedNUMBER
12SHIPPED_QUANTITYQuantity ship-confirmed — SUM by source line, one order line fans out across rowsNUMBER
13CANCELLED_QUANTITYQuantity cancelledNUMBER
14CUSTOMER_IDThe customer account (TCA id) the row ships toNUMBER
15DATE_REQUESTEDCustomer-requested date carried from the source lineDATE
16DATE_SCHEDULEDScheduled date — the backlog analysis date; actual ship time lives on the trip stopDATE
Filter date
17SHIP_METHOD_CODEShip method for the rowVARCHAR2
18CONTAINER_FLAGY for container (LPN) rows — packaging, not demand; filter from quantity aggregatesVARCHAR2
19SUBINVENTORYSourcing subinventory for the pickVARCHAR2
20LOT_NUMBERLot allocated to the row, for lot-controlled itemsVARCHAR2

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading WSH_DELIVERY_DETAILSon Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark are already in place. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.

Query parameters
-- ============================================================
-- Table  : WSH_DELIVERY_DETAILS — The atomic shipping line — one row per shippable unit of demand from order lines (or WIP/PO sources), plus container rows, tracking requested/picked/shipped quantities through pick release and ship confirm
-- Purpose: Column-selected read of WSH_DELIVERY_DETAILS — auto-generated from field metadata
-- Grain  : One row per inventory org (ORGANIZATION_ID) + DELIVERY_DETAIL_ID
-- Caution: Container rows (CONTAINER_FLAG = 'Y') are packaging, not demand — filter them out of quantity aggregates; one order line commonly fans out to several rows through splits and backorders
-- Notes  : Auto-generated skeleton for Oracle EBS R12 data landed in your lakehouse. Dates are real DATE/TIMESTAMP columns — no conversion needed. WHO audit columns omitted (see the quirks guide); the optional LAST_UPDATE_DATE watermark filter supports incremental extracts.
-- ============================================================
SELECT
  t.DELIVERY_DETAIL_ID AS "Surrogate key of the delivery line / container row",
  t.ORG_ID AS "Operating unit — the only WSH table carrying the MOAC stripe; push OU filters down to here",
  t.ORGANIZATION_ID AS "Ship-from inventory org (warehouse) — the org half of the item join",
  t.SOURCE_CODE AS "Which system fed the row — 'OE' for sales orders, or WIP/PO sources",
  t.SOURCE_HEADER_ID AS "The source document header — the sales order header for OE rows",
  t.SOURCE_LINE_ID AS "The source document line — the sales order line for OE rows",
  t.RELEASED_STATUS AS "One-character pick-release status — Oracle documents the statuses by name only, so the codes ship undecoded here",
  t.INVENTORY_ITEM_ID AS "The item being shipped",
  t.REQUESTED_QUANTITY AS "Quantity requested to ship on this row",
  t.REQUESTED_QUANTITY_UOM AS "UOM of the requested quantity",
  t.PICKED_QUANTITY AS "Quantity picked",
  t.SHIPPED_QUANTITY AS "Quantity ship-confirmed — SUM by source line, one order line fans out across rows",
  t.CANCELLED_QUANTITY AS "Quantity cancelled",
  t.CUSTOMER_ID AS "The customer account (TCA id) the row ships to",
  t.DATE_REQUESTED AS "Customer-requested date carried from the source line",
  t.DATE_SCHEDULED AS "Scheduled date — the backlog analysis date; actual ship time lives on the trip stop",
  t.SHIP_METHOD_CODE AS "Ship method for the row",
  t.CONTAINER_FLAG AS "Y for container (LPN) rows — packaging, not demand; filter from quantity aggregates",
  t.SUBINVENTORY AS "Sourcing subinventory for the pick",
  t.LOT_NUMBER AS "Lot allocated to the row, for lot-controlled items"
FROM <catalog>.<schema>.WSH_DELIVERY_DETAILS t
WHERE
  t.ORG_ID = <operating_unit_id>  -- operating unit (MOAC does not filter extracts)
  AND t.ORGANIZATION_ID = <inventory_org_id>  -- inventory org, NOT the operating unit — see quirks guide #two-orgs
  -- AND t.DELIVERY_DETAIL_ID = <DELIVERY_DETAIL_ID>
  -- AND t.DATE_SCHEDULED >= DATE '<DATE_FROM>'
  -- AND t.DATE_SCHEDULED <= DATE '<DATE_TO>'
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.DELIVERY_DETAIL_ID;

8 parameters not filled: <catalog>, <schema>, <operating_unit_id>, <inventory_org_id>, <DELIVERY_DETAIL_ID>, <DATE_FROM>, <DATE_TO>, <watermark>

Relationships

1-hop neighbors — click a table to navigate there. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.

Join details

  • WSH_DELIVERY_DETAILSOE_ORDER_HEADERS_ALLforeign key · N:1
    ON WSH_DELIVERY_DETAILS.SOURCE_HEADER_ID = OE_ORDER_HEADERS_ALL.HEADER_ID AND WSH_DELIVERY_DETAILS.ORG_ID = OE_ORDER_HEADERS_ALL.ORG_ID
  • WSH_DELIVERY_DETAILSOE_ORDER_LINES_ALLforeign key · N:1
    ON WSH_DELIVERY_DETAILS.SOURCE_LINE_ID = OE_ORDER_LINES_ALL.LINE_ID AND WSH_DELIVERY_DETAILS.ORG_ID = OE_ORDER_LINES_ALL.ORG_ID
  • WSH_DELIVERY_DETAILSMTL_SYSTEM_ITEMS_Bforeign key · N:1
    ON WSH_DELIVERY_DETAILS.INVENTORY_ITEM_ID = MTL_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID AND WSH_DELIVERY_DETAILS.ORGANIZATION_ID = MTL_SYSTEM_ITEMS_B.ORGANIZATION_ID
  • WSH_DELIVERY_ASSIGNMENTSWSH_DELIVERY_DETAILSforeign key · N:1
    ON WSH_DELIVERY_ASSIGNMENTS.DELIVERY_DETAIL_ID = WSH_DELIVERY_DETAILS.DELIVERY_DETAIL_ID
  • WSH_DELIVERY_ASSIGNMENTSWSH_DELIVERY_DETAILSforeign key · N:1
    ON WSH_DELIVERY_ASSIGNMENTS.PARENT_DELIVERY_DETAIL_ID = WSH_DELIVERY_DETAILS.DELIVERY_DETAIL_ID

Browse more Shipping & Deliveriestables →

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice →

Not affiliated with or endorsed by Oracle. Oracle and Oracle E-Business Suite are registered trademarks of Oracle and/or its affiliates.