Skip to content
EBS Reference

WSH_DELIVERY_LEGS

Schema: WSHtransaction

Delivery 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

Notes

One row per leg: a delivery on a multi-leg route multiplies through a stop join — pick the leg (lowest SEQUENCE_NUMBER for the origin departure) before aggregating.

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.

Structural facts — how the table is partitioned, not a trap by itself

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 with ORGANIZATION_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 LANGUAGE column (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to one LANGUAGE or a join multiplies rows (see the quirks guide).

Join & extract hazards — verify before you rely on this

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.
In field listings, the Key chip marks a primary-key field.

Fields

8 fields · 1 key

8 fields.

Table fields: position, field name, description, data type, and flags. 8 fields.
#FieldDescriptionTypeFlags
1DELIVERY_LEG_IDSurrogate key of the legNUMBER
Primary-key field
2DELIVERY_IDThe delivery the leg movesNUMBER
3SEQUENCE_NUMBERLeg order within the delivery's route — pick the lowest for the origin departureNUMBER
4PICK_UP_STOP_IDThe trip stop the leg picks up at (spelled PICK_UP, not PICKUP)NUMBER
5DROP_OFF_STOP_IDThe trip stop the leg drops off atNUMBER
6STATUS_CODELeg statusVARCHAR2
7ACTUAL_ARRIVAL_DATEActual arrival at the drop-off stopDATE
8ACTUAL_DEPARTURE_DATEActual departure from the pickup stopDATE

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading WSH_DELIVERY_LEGS 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.

Query parameters

4 parameters not filled: <catalog>, <schema>, <DELIVERY_LEG_ID>, <watermark>

-- ============================================================
-- Table  : WSH_DELIVERY_LEGS — Delivery 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
-- Purpose: Column-selected read of WSH_DELIVERY_LEGS — auto-generated from field metadata
-- Grain  : One row per DELIVERY_LEG_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_LEG_ID AS "Surrogate key of the leg",
  t.DELIVERY_ID AS "The delivery the leg moves",
  t.SEQUENCE_NUMBER AS "Leg order within the delivery's route — pick the lowest for the origin departure",
  t.PICK_UP_STOP_ID AS "The trip stop the leg picks up at (spelled PICK_UP, not PICKUP)",
  t.DROP_OFF_STOP_ID AS "The trip stop the leg drops off at",
  t.STATUS_CODE AS "Leg status",
  t.ACTUAL_ARRIVAL_DATE AS "Actual arrival at the drop-off stop",
  t.ACTUAL_DEPARTURE_DATE AS "Actual departure from the pickup stop"
FROM <catalog>.<schema>.WSH_DELIVERY_LEGS t
WHERE
  1 = 1  -- no partition column on this table; the filters below are optional
  -- AND t.DELIVERY_LEG_ID = <DELIVERY_LEG_ID>
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.DELIVERY_LEG_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

  • WSH_DELIVERY_LEGSWSH_NEW_DELIVERIESforeign key · N:1
    ON WSH_DELIVERY_LEGS.DELIVERY_ID = WSH_NEW_DELIVERIES.DELIVERY_ID
  • WSH_DELIVERY_LEGSWSH_TRIP_STOPSforeign key · N:1
    ON WSH_DELIVERY_LEGS.PICK_UP_STOP_ID = WSH_TRIP_STOPS.STOP_ID
  • WSH_DELIVERY_LEGSWSH_TRIP_STOPSforeign key · N:1
    ON WSH_DELIVERY_LEGS.DROP_OFF_STOP_ID = WSH_TRIP_STOPS.STOP_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 E-Business Suite are registered trademarks of Oracle and/or its affiliates.