WSH_NEW_DELIVERIES
Schema: WSHtransactionPer inventory orgThe 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
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
- Schema: INV
- Schema: the Oracle product schema that owns the table (INV, ONT, WSH, PO, BOM, WIP, MRP, MSC, AR, AP, GL, HR, APPLSYS) — tells you which product family the object belongs to, not who can query it.
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
- OU-striped (ORG_ID)
- Rows are scoped to an operating unit. A landed extract carries every operating unit’s rows — filter or join on
ORG_ID, and don’t confuse it withORGANIZATION_ID(see the quirks guide). - Per inventory org
- Rows are scoped to an inventory organization (plant or warehouse) via
ORGANIZATION_ID— a different partition from OU-striped tables (see the quirks guide). - Language-striped
- The table carries a
LANGUAGEcolumn (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to oneLANGUAGEor a join multiplies rows (see the quirks guide). - View
- This is an APPS-schema convenience view, not a physical table. Extract the base tables it joins instead — views can be slow at scale and aren't guaranteed stable across patches.
Structural facts — how the table is partitioned, not a trap by itself
Join & extract hazards — verify before you rely on this
Fields
16 fields · 1 key
16 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | DELIVERY_ID | Surrogate key of the delivery | NUMBER | Primary-key field |
| 2 | NAME | The delivery name users see — the delivery number | VARCHAR2 | |
| 3 | ORGANIZATION_ID | Ship-from inventory org | NUMBER | |
| 4 | STATUS_CODE | Two-character delivery status ('OP' open…) — statuses documented by name only, codes ship undecoded | VARCHAR2 | |
| 5 | PLANNED_FLAG | Y once the delivery is planned | VARCHAR2 | |
| 6 | DELIVERY_TYPE | Standard vs consolidated delivery | VARCHAR2 | |
| 7 | INITIAL_PICKUP_DATE | First pickup date of the delivery | DATE | |
| 8 | ULTIMATE_DROPOFF_DATE | Final drop-off date | DATE | |
| 9 | ULTIMATE_DROPOFF_LOCATION_ID | Final destination location | NUMBER | |
| 10 | CUSTOMER_ID | The customer account (TCA id) | NUMBER | |
| 11 | SHIP_METHOD_CODE | Ship method | VARCHAR2 | |
| 12 | CARRIER_ID | Freight carrier | NUMBER | |
| 13 | CONFIRM_DATE | Ship-confirm date — the natural shipped-date for delivery-grain analytics | DATE | The table's primary analysis date — a real DATE column, no conversion needed |
| 14 | GROSS_WEIGHT | Gross weight of the delivery | NUMBER | |
| 15 | WEIGHT_UOM_CODE | Weight UOM | VARCHAR2 | |
| 16 | WAYBILL | Waybill number — often the tracking number | VARCHAR2 |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading WSH_NEW_DELIVERIES on Databricks — real DATE columns need no conversion, and the org anchor is already in place. The optional LAST_UPDATE_DATE watermark is included. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.
7 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <DELIVERY_ID>, <DATE_FROM>, <DATE_TO>, <watermark>
-- ============================================================
-- 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;Verified September 2026
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
ON WSH_DELIVERY_ASSIGNMENTS.DELIVERY_ID = WSH_NEW_DELIVERIES.DELIVERY_IDON WSH_NEW_DELIVERIES.ORGANIZATION_ID = MTL_PARAMETERS.ORGANIZATION_IDON WSH_DELIVERY_LEGS.DELIVERY_ID = WSH_NEW_DELIVERIES.DELIVERY_IDON WSH_NEW_DELIVERIES.CUSTOMER_ID = HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID
More Shipping & Deliveries tables
- WSH_TRIP_STOPSTrip stops — one row per pickup or drop-off point on a trip, with planned and actual arrival/departure timestamps; the actual departure at the pickup stop is the gate-out time ship confirm writes
- WSH_TRIPSThe trip header — a carrier/vehicle journey over an ordered set of stops, with ship method, carrier, and vehicle attributes
- WSH_DELIVERY_ASSIGNMENTSThe assignment bridge between delivery details and deliveries — also encodes container nesting, where a detail's parent row is the LPN it is packed into; a detail reaches its delivery only through this table
- WSH_DELIVERY_DETAILSThe 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
- WSH_DELIVERY_LEGSDelivery legs — the mapping from a delivery to the trip stops where it is picked up and dropped off; the only path from deliveries to trips