WSH_DELIVERY_LEGS
Schema: WSHtransactionDelivery 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
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
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
Fields
8 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | DELIVERY_LEG_ID | Surrogate key of the leg | NUMBER | Key |
| 2 | DELIVERY_ID | The delivery the leg moves | NUMBER | |
| 3 | SEQUENCE_NUMBER | Leg order within the delivery's route — pick the lowest for the origin departure | NUMBER | |
| 4 | PICK_UP_STOP_ID | The trip stop the leg picks up at (spelled PICK_UP, not PICKUP) | NUMBER | |
| 5 | DROP_OFF_STOP_ID | The trip stop the leg drops off at | NUMBER | |
| 6 | STATUS_CODE | Leg status | VARCHAR2 | |
| 7 | ACTUAL_ARRIVAL_DATE | Actual arrival at the drop-off stop | DATE | |
| 8 | ACTUAL_DEPARTURE_DATE | Actual departure from the pickup stop | DATE |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading WSH_DELIVERY_LEGSon 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_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;4 parameters not filled: <catalog>, <schema>, <DELIVERY_LEG_ID>, <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_LEGS.DELIVERY_ID = WSH_NEW_DELIVERIES.DELIVERY_IDON WSH_DELIVERY_LEGS.PICK_UP_STOP_ID = WSH_TRIP_STOPS.STOP_IDON WSH_DELIVERY_LEGS.DROP_OFF_STOP_ID = WSH_TRIP_STOPS.STOP_ID