Skip to content
EBS Reference

WSH_NEW_DELIVERIES

Schema: WSHtransactionPer inventory org

The delivery header — a named grouping of delivery details shipped together from one location toward one final drop-off, carrying the ship-confirm date, carrier, waybill, and weights

Module: Shipping & DeliveriesInventory-org partitioned (ORGANIZATION_ID)
Notes

The "NEW_" prefix is naming history, not a status. CONFIRM_DATE is the ship-confirm timestamp most shipped-date analytics want. Status codes are two-character values Oracle documents by name only.

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

16 fields · 1 key

Table fields: position, field name, description, data type, and flags. 16 fields.
#FieldDescriptionTypeFlags
1DELIVERY_IDSurrogate key of the deliveryNUMBER
Key
2NAMEThe delivery name users see — the delivery numberVARCHAR2
3ORGANIZATION_IDShip-from inventory orgNUMBER
4STATUS_CODETwo-character delivery status ('OP' open…) — statuses documented by name only, codes ship undecodedVARCHAR2
5PLANNED_FLAGY once the delivery is plannedVARCHAR2
6DELIVERY_TYPEStandard vs consolidated deliveryVARCHAR2
7INITIAL_PICKUP_DATEFirst pickup date of the deliveryDATE
8ULTIMATE_DROPOFF_DATEFinal drop-off dateDATE
9ULTIMATE_DROPOFF_LOCATION_IDFinal destination locationNUMBER
10CUSTOMER_IDThe customer account (TCA id)NUMBER
11SHIP_METHOD_CODEShip methodVARCHAR2
12CARRIER_IDFreight carrierNUMBER
13CONFIRM_DATEShip-confirm date — the natural shipped-date for delivery-grain analyticsDATE
Filter date
14GROSS_WEIGHTGross weight of the deliveryNUMBER
15WEIGHT_UOM_CODEWeight UOMVARCHAR2
16WAYBILLWaybill number — often the tracking numberVARCHAR2

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading WSH_NEW_DELIVERIESon 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_NEW_DELIVERIES — The delivery header — a named grouping of delivery details shipped together from one location toward one final drop-off, carrying the ship-confirm date, carrier, waybill, and weights
-- 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 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_ID AS "Surrogate key of the delivery",
  t.NAME AS "The delivery name users see — the delivery number",
  t.ORGANIZATION_ID AS "Ship-from inventory org",
  t.STATUS_CODE AS "Two-character delivery status ('OP' open…) — statuses documented by name only, codes ship undecoded",
  t.PLANNED_FLAG AS "Y once the delivery is planned",
  t.DELIVERY_TYPE AS "Standard vs consolidated delivery",
  t.INITIAL_PICKUP_DATE AS "First pickup date of the delivery",
  t.ULTIMATE_DROPOFF_DATE AS "Final drop-off date",
  t.ULTIMATE_DROPOFF_LOCATION_ID AS "Final destination location",
  t.CUSTOMER_ID AS "The customer account (TCA id)",
  t.SHIP_METHOD_CODE AS "Ship method",
  t.CARRIER_ID AS "Freight carrier",
  t.CONFIRM_DATE AS "Ship-confirm date — the natural shipped-date for delivery-grain analytics",
  t.GROSS_WEIGHT AS "Gross weight of the delivery",
  t.WEIGHT_UOM_CODE AS "Weight UOM",
  t.WAYBILL AS "Waybill number — often the tracking number"
FROM <catalog>.<schema>.WSH_NEW_DELIVERIES t
WHERE
  t.ORGANIZATION_ID = <inventory_org_id>  -- inventory org, NOT the operating unit — see quirks guide #two-orgs
  -- 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>'  -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.DELIVERY_ID;

7 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <DELIVERY_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_ASSIGNMENTSWSH_NEW_DELIVERIESforeign key · N:1
    ON WSH_DELIVERY_ASSIGNMENTS.DELIVERY_ID = WSH_NEW_DELIVERIES.DELIVERY_ID
  • WSH_NEW_DELIVERIESMTL_PARAMETERSforeign key · N:1
    ON WSH_NEW_DELIVERIES.ORGANIZATION_ID = MTL_PARAMETERS.ORGANIZATION_ID
  • WSH_DELIVERY_LEGSWSH_NEW_DELIVERIESforeign key · N:1
    ON WSH_DELIVERY_LEGS.DELIVERY_ID = WSH_NEW_DELIVERIES.DELIVERY_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.