WSH_DELIVERY_DETAILS
Schema: WSHtransactionOU-striped (ORG_ID)Per inventory orgThe 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
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
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.
Fields
20 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | DELIVERY_DETAIL_ID | Surrogate key of the delivery line / container row | NUMBER | Key |
| 2 | ORG_ID | Operating unit — the only WSH table carrying the MOAC stripe; push OU filters down to here | NUMBER | |
| 3 | ORGANIZATION_ID | Ship-from inventory org (warehouse) — the org half of the item join | NUMBER | |
| 4 | SOURCE_CODE | Which system fed the row — 'OE' for sales orders, or WIP/PO sources | VARCHAR2 | |
| 5 | SOURCE_HEADER_ID | The source document header — the sales order header for OE rows | NUMBER | |
| 6 | SOURCE_LINE_ID | The source document line — the sales order line for OE rows | NUMBER | |
| 7 | RELEASED_STATUS | One-character pick-release status — Oracle documents the statuses by name only, so the codes ship undecoded here | VARCHAR2 | |
| 8 | INVENTORY_ITEM_ID | The item being shipped | NUMBER | |
| 9 | REQUESTED_QUANTITY | Quantity requested to ship on this row | NUMBER | |
| 10 | REQUESTED_QUANTITY_UOM | UOM of the requested quantity | VARCHAR2 | |
| 11 | PICKED_QUANTITY | Quantity picked | NUMBER | |
| 12 | SHIPPED_QUANTITY | Quantity ship-confirmed — SUM by source line, one order line fans out across rows | NUMBER | |
| 13 | CANCELLED_QUANTITY | Quantity cancelled | NUMBER | |
| 14 | CUSTOMER_ID | The customer account (TCA id) the row ships to | NUMBER | |
| 15 | DATE_REQUESTED | Customer-requested date carried from the source line | DATE | |
| 16 | DATE_SCHEDULED | Scheduled date — the backlog analysis date; actual ship time lives on the trip stop | DATE | Filter date |
| 17 | SHIP_METHOD_CODE | Ship method for the row | VARCHAR2 | |
| 18 | CONTAINER_FLAG | Y for container (LPN) rows — packaging, not demand; filter from quantity aggregates | VARCHAR2 | |
| 19 | SUBINVENTORY | Sourcing subinventory for the pick | VARCHAR2 | |
| 20 | LOT_NUMBER | Lot allocated to the row, for lot-controlled items | VARCHAR2 |
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.
-- ============================================================
-- 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
ON WSH_DELIVERY_DETAILS.SOURCE_HEADER_ID = OE_ORDER_HEADERS_ALL.HEADER_ID AND WSH_DELIVERY_DETAILS.ORG_ID = OE_ORDER_HEADERS_ALL.ORG_IDON WSH_DELIVERY_DETAILS.SOURCE_LINE_ID = OE_ORDER_LINES_ALL.LINE_ID AND WSH_DELIVERY_DETAILS.ORG_ID = OE_ORDER_LINES_ALL.ORG_IDON WSH_DELIVERY_DETAILS.INVENTORY_ITEM_ID = MTL_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID AND WSH_DELIVERY_DETAILS.ORGANIZATION_ID = MTL_SYSTEM_ITEMS_B.ORGANIZATION_IDON WSH_DELIVERY_ASSIGNMENTS.DELIVERY_DETAIL_ID = WSH_DELIVERY_DETAILS.DELIVERY_DETAIL_IDON WSH_DELIVERY_ASSIGNMENTS.PARENT_DELIVERY_DETAIL_ID = WSH_DELIVERY_DETAILS.DELIVERY_DETAIL_ID