WSH_DELIVERY_ASSIGNMENTS
Product: WSHtransactionThe assignment bridge between shipment lines and deliveries — also the carrier of the packing hierarchy through its parent-detail pointer; a line reaches its delivery only through this table
DELIVERY_ID is NULL while a line is unassigned — an inner join to deliveries silently drops not-yet-assigned lines. Respect ACTIVE_FLAG. The packing hierarchy is expressed here via PARENT_DELIVERY_DETAIL_ID even though details no longer carry container flags.
What the badges mean
- Product: EGP
- Product: the Oracle product family that owns the object — the short code Oracle's Tables and Views documentation lists as the object owner. Fusion is SaaS, so this isn't a database schema; there's no SQL path to the tables at all (see the quirks guide).
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
- BU-striped (ORG_ID)
- Rows are scoped to a business unit. The column is still named
ORG_ID, but in Fusion it means business unit, not the EBS operating unit — treat any migrated “operating unit” filter as suspect (see the quirks guide). - Per inventory org
- Rows are scoped to an inventory organization via
ORGANIZATION_ID— always pair it withINVENTORY_ITEM_IDon item-level joins (see the quirks guide). - Set / ledger / named-BU striped
- Some tables stripe by a named column instead of
ORG_ID: reference data set (SET_ID— see the quirks guide), ledger (LEDGER_IDon the GL journal tables), or a named business-unit column (PRC_BU_ID/REQ_BU_IDin procurement). The table page’s partition line names the column, and the generated SQL anchors on it — never treat these tables as unpartitioned. - 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. - Date-effective
- This is an
_Ftable — one row per entity per effectivity window, withEFFECTIVE_START_DATEandEFFECTIVE_END_DATEpart of the key. Join without a window filter and every fact multiplies by history (see the quirks guide). - View
- This is a documented convenience view, not a physical table. Extract through the BICC data store that fronts its base objects instead of assuming the view lands as-is.
Structural facts — how the table is partitioned, not a trap by itself
Join & extract hazards — verify before you rely on this
Extract access
The delivered surfaces that reach this table — the BICC extract data store (PVO) for bulk extraction and the OTBI subject areas for real-time queries. There is no SQL path to the SaaS database.
- FscmTopModelAM.ScmExtractAM.WshBiccExtractAM.DeliveryLineAssignmentExtractPVO
Shipment Line Assignments data store — keyed on DeliveryLineAssignmentPEODeliveryAssignmentId, with documented link attributes for the line and delivery keys.
Oracle data-store documentation (opens in new tab)
Fields
6 fields · 1 key
6 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | DELIVERY_ASSIGNMENT_ID | Surrogate key of the assignment | NUMBER | Key |
| 2 | DELIVERY_ID | The delivery the line is assigned to — NULL while unassigned, so LEFT JOIN | NUMBER | |
| 3 | DELIVERY_DETAIL_ID | The shipment line being assigned | NUMBER | |
| 4 | PARENT_DELIVERY_ID | Parent delivery, when nested | NUMBER | |
| 5 | PARENT_DELIVERY_DETAIL_ID | The container/LPN row this line is packed under — the packing hierarchy lives here | NUMBER | |
| 6 | ACTIVE_FLAG | Whether this assignment is currently active | VARCHAR2 |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the BICC-landed copy of WSH_DELIVERY_ASSIGNMENTS on Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark (the column incremental BICC extracts key on) are already in place. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.
4 parameters not filled: <catalog>, <schema>, <DELIVERY_ASSIGNMENT_ID>, <watermark>
-- ============================================================
-- Table : WSH_DELIVERY_ASSIGNMENTS — The assignment bridge between shipment lines and deliveries — also the carrier of the packing hierarchy through its parent-detail pointer; a line 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 Fusion Cloud data landed in your lakehouse by a BICC extract — there is no SQL path to the SaaS database. Column names follow Oracle's table documentation — if your landed data still carries PVO attribute headers, map names first; see quirks #pvo-drift. 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_ID AS "The delivery the line is assigned to — NULL while unassigned, so LEFT JOIN",
t.DELIVERY_DETAIL_ID AS "The shipment line being assigned",
t.PARENT_DELIVERY_ID AS "Parent delivery, when nested",
t.PARENT_DELIVERY_DETAIL_ID AS "The container/LPN row this line is packed under — the packing hierarchy lives here",
t.ACTIVE_FLAG AS "Whether this assignment is currently active"
FROM <catalog>.<schema>.WSH_DELIVERY_ASSIGNMENTS t
WHERE
1 = 1 -- no automatic partition anchor on this table; the filters below are optional
-- AND t.DELIVERY_ASSIGNMENT_ID = <DELIVERY_ASSIGNMENT_ID>
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- the column incremental BICC extracts key on
ORDER BY t.DELIVERY_ASSIGNMENT_ID;Verified September 2026 · docs release 26C
Column names differ in BICC extracts — see PVO header drift.
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_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
More Shipping & Deliveries tables
- WSH_DELIVERY_DETAILSThe atomic shipment line — one row per shippable unit of demand, tracking the source order line, item, warehouse, and the requested/picked/shipped quantity lifecycle through pick, stage, and ship confirm
- WSH_NEW_DELIVERIESThe delivery (shipment) header — a named grouping of shipment lines shipped together, carrying the ship-confirm and actual ship/delivery dates, carrier, ship method, waybill, and weight/volume rollups