Skip to content
Fusion Reference

WSH_DELIVERY_ASSIGNMENTS

Product: WSHtransaction

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

Notes

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.

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

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 with INVENTORY_ITEM_ID on 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_ID on the GL journal tables), or a named business-unit column (PRC_BU_ID / REQ_BU_ID in 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 LANGUAGE column (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to one LANGUAGE or a join multiplies rows.

Join & extract hazards — verify before you rely on this

Date-effective
This is an _F table — one row per entity per effectivity window, with EFFECTIVE_START_DATE and EFFECTIVE_END_DATE part 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.
In field listings, the Key chip marks a key field — a member of the documented primary key or of a documented unique index.

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.

Table fields: position, field name, description, data type, and flags. 6 fields.
#FieldDescriptionTypeFlags
1DELIVERY_ASSIGNMENT_IDSurrogate key of the assignmentNUMBER
Key
2DELIVERY_IDThe delivery the line is assigned to — NULL while unassigned, so LEFT JOINNUMBER
3DELIVERY_DETAIL_IDThe shipment line being assignedNUMBER
4PARENT_DELIVERY_IDParent delivery, when nestedNUMBER
5PARENT_DELIVERY_DETAIL_IDThe container/LPN row this line is packed under — the packing hierarchy lives hereNUMBER
6ACTIVE_FLAGWhether this assignment is currently activeVARCHAR2

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.

Query parameters

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

  • WSH_DELIVERY_ASSIGNMENTSWSH_DELIVERY_DETAILSforeign key · N:1
    ON WSH_DELIVERY_ASSIGNMENTS.DELIVERY_DETAIL_ID = WSH_DELIVERY_DETAILS.DELIVERY_DETAIL_ID
  • WSH_DELIVERY_ASSIGNMENTSWSH_NEW_DELIVERIESforeign key · N:1
    ON WSH_DELIVERY_ASSIGNMENTS.DELIVERY_ID = WSH_NEW_DELIVERIES.DELIVERY_ID
  • WSH_DELIVERY_ASSIGNMENTSWSH_DELIVERY_DETAILSforeign key · N:1
    ON WSH_DELIVERY_ASSIGNMENTS.PARENT_DELIVERY_DETAIL_ID = WSH_DELIVERY_DETAILS.DELIVERY_DETAIL_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 Fusion Cloud Applications are registered trademarks of Oracle and/or its affiliates.