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
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
In field listings, K marks a primary-key field.

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 →

Fields

6 fields · 1 key

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_ASSIGNMENTSon 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
-- ============================================================
-- 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 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>'  -- the column incremental BICC extracts key on
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

  • 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 & Deliveriestables →

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.