WSH_DELIVERY_ASSIGNMENTS
Schema: WSHtransactionThe 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
DELIVERY_ID is NULL while a detail is unassigned — an inner join to deliveries silently drops not-yet-assigned lines.
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
6 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | DELIVERY_ASSIGNMENT_ID | Surrogate key of the assignment | NUMBER | Key |
| 2 | DELIVERY_DETAIL_ID | The delivery detail being assigned | NUMBER | |
| 3 | DELIVERY_ID | The delivery the detail is assigned to — NULL while unassigned, so inner joins drop those rows | NUMBER | |
| 4 | PARENT_DELIVERY_DETAIL_ID | The container (LPN) row this detail is packed into — the nesting edge | NUMBER | |
| 5 | ACTIVE_FLAG | Whether the assignment is active | VARCHAR2 | |
| 6 | TYPE | Assignment type | VARCHAR2 |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading WSH_DELIVERY_ASSIGNMENTSon 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_ASSIGNMENTS — The 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
-- Purpose: Column-selected read of WSH_DELIVERY_ASSIGNMENTS — auto-generated from field metadata
-- Grain : One row per DELIVERY_ASSIGNMENT_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_ASSIGNMENT_ID AS "Surrogate key of the assignment",
t.DELIVERY_DETAIL_ID AS "The delivery detail being assigned",
t.DELIVERY_ID AS "The delivery the detail is assigned to — NULL while unassigned, so inner joins drop those rows",
t.PARENT_DELIVERY_DETAIL_ID AS "The container (LPN) row this detail is packed into — the nesting edge",
t.ACTIVE_FLAG AS "Whether the assignment is active",
t.TYPE AS "Assignment type"
FROM <catalog>.<schema>.WSH_DELIVERY_ASSIGNMENTS t
WHERE
1 = 1 -- no partition column on this table; the filters below are optional
-- AND t.DELIVERY_ASSIGNMENT_ID = <DELIVERY_ASSIGNMENT_ID>
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.DELIVERY_ASSIGNMENT_ID;4 parameters not filled: <catalog>, <schema>, <DELIVERY_ASSIGNMENT_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_ASSIGNMENTS.DELIVERY_DETAIL_ID = WSH_DELIVERY_DETAILS.DELIVERY_DETAIL_IDON WSH_DELIVERY_ASSIGNMENTS.DELIVERY_ID = WSH_NEW_DELIVERIES.DELIVERY_IDON WSH_DELIVERY_ASSIGNMENTS.PARENT_DELIVERY_DETAIL_ID = WSH_DELIVERY_DETAILS.DELIVERY_DETAIL_ID