Search Results wsh_delivery_details_n2

Overview

WSH.WSH_DELIVERY_DETAILS is the central shipping execution table in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It stores individual delivery lines and license plate numbers (LPNs) that flow through the Warehouse Management (WSH) shipping process. Every pick, pack, ship, and manifest transaction performed in the Shipping Transactions workbench — and its HTML replacement in 12.2 — originates from or updates a row in this table. Its documented role is summarized simply: "WSH_DELIVERY_DETAILS has delivery lines and LPNs."

In Release 12.2.x the table is documented with 210 columns and resides in the WSH schema under tablespace APPS_TS_TX_DATA. It is a large, high-transaction-volume object that bridges Order Management, Inventory, Purchasing/Receiving, and Transportation modules. The heuristic Data Vault classification of this object is hub-leaning, which suggests it behaves primarily as a business entity hub anchored by a stable surrogate key rather than a pure transactional link.

Key Information Stored

The table is uniquely identified by the surrogate primary key DELIVERY_DETAIL_ID, enforced by unique index WSH_DELIVERY_DETAILS_U1. This is the single documented business-key candidate. The most operationally significant columns include:

• SOURCE_CODE, SOURCE_HEADER_ID, SOURCE_LINE_ID — identify the originating document (for example an order or move order) and its header/line.
• INVENTORY_ITEM_ID, ORGANIZATION_ID — the item and the warehouse from which it ships.
• RELEASED_STATUS — drives the workflow state used by the Shipping Transactions form.
• REQUESTED_QUANTITY, SHIPPED_QUANTITY, DELIVERED_QUANTITY — the core quantity triad tracking demand versus actuals.
• SHIP_FROM_LOCATION_ID, SHIP_TO_LOCATION_ID, DELIVER_TO_LOCATION_ID — the party location chain.
• LPN_ID, CONTAINER_NAME, CONTAINER_FLAG — support LPN and container packing hierarchy.
• DATE_SCHEDULED, EARLIEST_PICKUP_DATE, LATEST_PICKUP_DATE — scheduling and pickup windows.
• INV_INTERFACED_FLAG, OE_INTERFACED_FLAG — indicate whether inventory and order management interfaces have been processed.
• SPLIT_FROM_DELIVERY_DETAIL_ID — self-referencing pointer to a parent line when a delivery line is split.
• Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, etc.) provide auditability.

Common Use Cases and Queries

Typical use cases include open shipping-line reporting, pick confirmation auditing, and reconciliation of shipped versus requested quantities. A representative query to list unreleased lines for a specific warehouse is:

• SELECT delivery_detail_id, source_header_number, inventory_item_id, requested_quantity, released_status FROM wsh.wsh_delivery_details WHERE organization_id = :org_id AND released_status = 'R';

Joining to WSH_DELIVERY_ASSIGNMENTS exposes the delivery-to-line mapping for manifest reporting, while joins to WSH_DEL_DETAILS_INTERFACE reveal interface stages. Indexes WSH_DELIVERY_DETAILS_N2 (SOURCE_HEADER_ID), N8 (RELEASED_STATUS, ORGANIZATION_ID), and N9 (INVENTORY_ITEM_ID, ORGANIZATION_ID, SHIP_FROM_LOCATION_ID, RELEASED_STATUS) support these access paths.

Related Objects

The table participates in extensive referential relationships. The most significant include:

• WSH_DELIVERY_ASSIGNMENTS — maps delivery_detail_id to delivery assignments.
• WSH_DEL_DETAILS_INTERFACE and WSH_DEL_ASSGN_INTERFACE — staging tables feeding this table.
• WSH_EXCEPTIONS and WSH_FREIGHT_COSTS — transactional satellites keyed by delivery_detail_id.
• WSH_PICKING_BATCHES — picking association.
• MTL_CUSTOMER_ITEMS, HZ_PARTIES, and MTL_MOVEMENT_STATISTICS — master and movement references via CUSTOMER_ITEM_ID, PARTY_ID, and MOVEMENT_ID.
• JAI_OM_* and OKE_K_DELIVERABLES_B — downstream consumers, including India localizations and service deliverables.