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
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
Fields
16 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | DELIVERY_ID | Surrogate key of the delivery | NUMBER | Key |
| 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 | Filter date |
| 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_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.
-- ============================================================
-- 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
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_ID