Skip to content
Fusion Reference

WSH_NEW_DELIVERIES

Product: WSHtransactionPer inventory org

The delivery (shipment) header — a named grouping of shipment lines shipped together, carrying the ship-confirm and actual ship/delivery dates, carrier, ship method, waybill, and weight/volume rollups

Notes

The "NEW_" prefix is naming history, not a status. Trip-level attributes EBS kept on separate trip tables (carrier, ship method, waybill, actual departure) live directly here — Fusion has no trip layer. STATUS_CODE values are not enumerated in the data dictionary, so they ship undecoded. Customers are TCA parties (SHIP_TO_PARTY_ID; a sold-to party column exists alongside it).

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.

  • FscmTopModelAM.ScmExtractAM.WshBiccExtractAM.DeliveryExtractPVO
    OTBI: Shipping Real Time

    Shipments data store — keyed on DeliveryPEODeliveryId, mirroring DELIVERY_ID (Fusion's docs call deliveries shipments; same entity).

    Oracle data-store documentation (opens in new tab)

Fields

18 fields · 1 key

18 fields.

Table fields: position, field name, description, data type, and flags. 18 fields.
#FieldDescriptionTypeFlags
1DELIVERY_IDSurrogate key of the delivery (shipment)NUMBER
Key
2DELIVERY_NAMEUser-visible shipment nameVARCHAR2
3ORGANIZATION_IDShip-from inventory organizationNUMBER
4STATUS_CODEShipment status — code values are not enumerated in the dictionary, so they ship undecodedVARCHAR2
5DELIVERY_TYPEStandard vs consolidated shipmentVARCHAR2
6SOURCE_HEADER_IDHeader id of the order lines tied to this deliveryNUMBER
7CONFIRM_DATEWhen the shipment was ship-confirmedDATE
Filter date
8INITIAL_PICKUP_DATEFirst pickup date of the shipmentDATE
9ULTIMATE_DROPOFF_DATEFinal dropoff dateDATE
10ACTUAL_SHIP_DATEActual ship dateDATE
11ACTUAL_DELIVERY_DATEWhen delivered to the recipientDATE
12CARRIER_IDFreight carrier — trip-level attributes live here in Fusion; there is no trip tableNUMBER
13SHIP_METHOD_CODEShipping method codeVARCHAR2
14SERVICE_LEVELService level component of the ship methodVARCHAR2
15MODE_OF_TRANSPORTTransport mode component of the ship methodVARCHAR2
16WAYBILLWaybill / tracking numberVARCHAR2
17GROSS_WEIGHTShipment gross weight rollupNUMBER
18SHIP_TO_PARTY_IDShip-to customer party (TCA)NUMBER

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading the BICC-landed copy of WSH_NEW_DELIVERIES 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

7 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <DELIVERY_ID>, <DATE_FROM>, <DATE_TO>, <watermark>

-- ============================================================
-- Table  : WSH_NEW_DELIVERIES — The delivery (shipment) header — a named grouping of shipment lines shipped together, carrying the ship-confirm and actual ship/delivery dates, carrier, ship method, waybill, and weight/volume rollups
-- Purpose: Column-selected read of WSH_NEW_DELIVERIES — auto-generated from field metadata
-- Grain  : One row per inventory org (ORGANIZATION_ID) + DELIVERY_ID
-- 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_ID AS "Surrogate key of the delivery (shipment)",
  t.DELIVERY_NAME AS "User-visible shipment name",
  t.ORGANIZATION_ID AS "Ship-from inventory organization",
  t.STATUS_CODE AS "Shipment status — code values are not enumerated in the dictionary, so they ship undecoded",
  t.DELIVERY_TYPE AS "Standard vs consolidated shipment",
  t.SOURCE_HEADER_ID AS "Header id of the order lines tied to this delivery",
  t.CONFIRM_DATE AS "When the shipment was ship-confirmed",
  t.INITIAL_PICKUP_DATE AS "First pickup date of the shipment",
  t.ULTIMATE_DROPOFF_DATE AS "Final dropoff date",
  t.ACTUAL_SHIP_DATE AS "Actual ship date",
  t.ACTUAL_DELIVERY_DATE AS "When delivered to the recipient",
  t.CARRIER_ID AS "Freight carrier — trip-level attributes live here in Fusion; there is no trip table",
  t.SHIP_METHOD_CODE AS "Shipping method code",
  t.SERVICE_LEVEL AS "Service level component of the ship method",
  t.MODE_OF_TRANSPORT AS "Transport mode component of the ship method",
  t.WAYBILL AS "Waybill / tracking number",
  t.GROSS_WEIGHT AS "Shipment gross weight rollup",
  t.SHIP_TO_PARTY_ID AS "Ship-to customer party (TCA)"
FROM <catalog>.<schema>.WSH_NEW_DELIVERIES t
WHERE
  t.ORGANIZATION_ID = <inventory_org_id>  -- inventory org, NOT the business unit — see quirks guide #item-org-striping
  -- AND t.DELIVERY_ID = <DELIVERY_ID>
  -- AND t.CONFIRM_DATE >= DATE '<DATE_FROM>'
  -- AND t.CONFIRM_DATE <= DATE '<DATE_TO>'
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- the column incremental BICC extracts key on
ORDER BY t.DELIVERY_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_NEW_DELIVERIESforeign key · N:1
    ON WSH_DELIVERY_ASSIGNMENTS.DELIVERY_ID = WSH_NEW_DELIVERIES.DELIVERY_ID
  • WSH_NEW_DELIVERIESINV_ORG_PARAMETERSforeign key · N:1
    ON WSH_NEW_DELIVERIES.ORGANIZATION_ID = INV_ORG_PARAMETERS.ORGANIZATION_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.