Skip to content
Fusion Reference

WSH_DELIVERY_DETAILS

Product: WSHtransactionBU-striped (ORG_ID)Per inventory org

The atomic shipment line — one row per shippable unit of demand, tracking the source order line, item, warehouse, and the requested/picked/shipped quantity lifecycle through pick, stage, and ship confirm

Grain note

Lines split as they process (SPLIT_FROM_DELIVERY_DETAIL_ID points at the original) — one order line commonly fans out to several rows

Notes

The catalog's first dual-anchored table: ORG_ID is the business unit and ORGANIZATION_ID the ship-from inventory org — both anchors render in the generated SQL. Unlike EBS there are NO container rows here — packing goes through license plate numbers (PARENT_LPN_ID). SOURCE_LINE_ID is polymorphic across source documents, so no shipping→order edge is drawn; RELEASED_STATUS codes are not enumerated in the dictionary and ship undecoded.

What the badges mean
Product: EGP
Product: the Oracle product family that owns the object — the short code Oracle's Tables and Views documentation lists as the object owner. Fusion is SaaS, so this isn't a database schema; there's no SQL path to the tables at all (see the quirks guide).
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.

Structural facts — how the table is partitioned, not a trap by itself

BU-striped (ORG_ID)
Rows are scoped to a business unit. The column is still named ORG_ID, but in Fusion it means business unit, not the EBS operating unit — treat any migrated “operating unit” filter as suspect (see the quirks guide).
Per inventory org
Rows are scoped to an inventory organization via ORGANIZATION_ID — always pair it with INVENTORY_ITEM_ID on item-level joins (see the quirks guide).
Set / ledger / named-BU striped
Some tables stripe by a named column instead of ORG_ID: reference data set (SET_ID — see the quirks guide), ledger (LEDGER_ID on the GL journal tables), or a named business-unit column (PRC_BU_ID / REQ_BU_ID in procurement). The table page’s partition line names the column, and the generated SQL anchors on it — never treat these tables as unpartitioned.
Language-striped
The table carries a LANGUAGE column (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to one LANGUAGE or a join multiplies rows.

Join & extract hazards — verify before you rely on this

Date-effective
This is an _F table — one row per entity per effectivity window, with EFFECTIVE_START_DATE and EFFECTIVE_END_DATE part of the key. Join without a window filter and every fact multiplies by history (see the quirks guide).
View
This is a documented convenience view, not a physical table. Extract through the BICC data store that fronts its base objects instead of assuming the view lands as-is.
In field listings, the Key chip marks a key field — a member of the documented primary key or of a documented unique index.

Extract access

The delivered surfaces that reach this table — the BICC extract data store (PVO) for bulk extraction and the OTBI subject areas for real-time queries. There is no SQL path to the SaaS database.

Fields

18 fields · 1 key

18 fields.

Table fields: position, field name, description, data type, and flags. 18 fields.
#FieldDescriptionTypeFlags
1DELIVERY_DETAIL_IDSurrogate key of the shipment lineNUMBER
Key
2ORG_IDThe business unit associated to the row — one of the table's two org anchorsNUMBER
3ORGANIZATION_IDShip-from inventory organization — the other org anchorNUMBER
4INVENTORY_ITEM_IDItem being shippedNUMBER
5SOURCE_HEADER_IDSource document header (a sales order header, most commonly)NUMBER
6SOURCE_LINE_IDSource line id — polymorphic across order/WIP/PO sources, so no order edge is drawnNUMBER
7SOURCE_DOCUMENT_TYPE_IDWhich document type fed the rowNUMBER
8RELEASED_STATUSLine lifecycle status (ready, released, staged, shipped, backordered) — single-character codes, not enumerated in the dictionaryVARCHAR2
9REQUESTED_QUANTITYQuantity to shipNUMBER
10REQUESTED_QUANTITY_UOMUOM of the quantity columnsVARCHAR2
11PICKED_QUANTITYQuantity pickedNUMBER
12SHIPPED_QUANTITYQuantity shipped, in the requested-quantity UOMNUMBER
13CANCELLED_QUANTITYQuantity canceled by the source systemNUMBER
14DATE_SCHEDULEDScheduled date for the lineDATE
Filter date
15SHIP_TO_PARTY_IDShip-to customer party (TCA)NUMBER
16PARENT_LPN_IDThe license plate (container) the line is packed into — packing goes through LPNs, not container rowsNUMBER
17SPLIT_FROM_DELIVERY_DETAIL_IDThe original line this row split fromNUMBER
18TRACKING_NUMBERCarrier tracking number for the lineVARCHAR2

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading the BICC-landed copy of WSH_DELIVERY_DETAILS on Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark (the column incremental BICC extracts key on) 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

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

-- ============================================================
-- Table  : WSH_DELIVERY_DETAILS — The atomic shipment line — one row per shippable unit of demand, tracking the source order line, item, warehouse, and the requested/picked/shipped quantity lifecycle through pick, stage, 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: Lines split as they process (SPLIT_FROM_DELIVERY_DETAIL_ID points at the original) — one order line commonly fans out to several rows
-- Notes  : Auto-generated skeleton for Oracle Fusion Cloud data landed in your lakehouse by a BICC extract — there is no SQL path to the SaaS database. Column names follow Oracle's table documentation — if your landed data still carries PVO attribute headers, map names first; see quirks #pvo-drift. 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 shipment line",
  t.ORG_ID AS "The business unit associated to the row — one of the table's two org anchors",
  t.ORGANIZATION_ID AS "Ship-from inventory organization — the other org anchor",
  t.INVENTORY_ITEM_ID AS "Item being shipped",
  t.SOURCE_HEADER_ID AS "Source document header (a sales order header, most commonly)",
  t.SOURCE_LINE_ID AS "Source line id — polymorphic across order/WIP/PO sources, so no order edge is drawn",
  t.SOURCE_DOCUMENT_TYPE_ID AS "Which document type fed the row",
  t.RELEASED_STATUS AS "Line lifecycle status (ready, released, staged, shipped, backordered) — single-character codes, not enumerated in the dictionary",
  t.REQUESTED_QUANTITY AS "Quantity to ship",
  t.REQUESTED_QUANTITY_UOM AS "UOM of the quantity columns",
  t.PICKED_QUANTITY AS "Quantity picked",
  t.SHIPPED_QUANTITY AS "Quantity shipped, in the requested-quantity UOM",
  t.CANCELLED_QUANTITY AS "Quantity canceled by the source system",
  t.DATE_SCHEDULED AS "Scheduled date for the line",
  t.SHIP_TO_PARTY_ID AS "Ship-to customer party (TCA)",
  t.PARENT_LPN_ID AS "The license plate (container) the line is packed into — packing goes through LPNs, not container rows",
  t.SPLIT_FROM_DELIVERY_DETAIL_ID AS "The original line this row split from",
  t.TRACKING_NUMBER AS "Carrier tracking number for the line"
FROM <catalog>.<schema>.WSH_DELIVERY_DETAILS t
WHERE
  t.ORG_ID = <business_unit_id>  -- business unit — Fusion _ALL means BU, not the EBS operating unit; see quirks guide #all-means-bu
  AND t.ORGANIZATION_ID = <inventory_org_id>  -- inventory org, NOT the business unit — see quirks guide #item-org-striping
  -- 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>'  -- the column incremental BICC extracts key on
ORDER BY t.DELIVERY_DETAIL_ID;

Verified September 2026 · docs release 26C

Column names differ in BICC extracts — see PVO header drift.

Relationships

Diagram of 1-hop neighbors — join details below. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.

Join details

  • 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
  • WSH_DELIVERY_DETAILSEGP_SYSTEM_ITEMS_Bforeign key · N:1
    ON WSH_DELIVERY_DETAILS.INVENTORY_ITEM_ID = EGP_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID AND WSH_DELIVERY_DETAILS.ORGANIZATION_ID = EGP_SYSTEM_ITEMS_B.ORGANIZATION_ID
  • WSH_DELIVERY_DETAILSINV_ORG_PARAMETERSforeign key · N:1
    ON WSH_DELIVERY_DETAILS.ORGANIZATION_ID = INV_ORG_PARAMETERS.ORGANIZATION_ID
  • WSH_DELIVERY_DETAILSFUN_ALL_BUSINESS_UNITS_Vforeign key · N:1
    ON WSH_DELIVERY_DETAILS.ORG_ID = FUN_ALL_BUSINESS_UNITS_V.BU_ID

Browse more Shipping & Deliveries tables

More Shipping & Deliveries tables

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 Fusion Cloud Applications are registered trademarks of Oracle and/or its affiliates.