Results for “planned_departure_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The WSH_DELIVERIES table is the central shipping delivery entity in Oracle E-Business Suite, owned by the OE (Order Entry) schema and documented as VALID in the ETRM reference for both 12.1.1 and 12.2.2. It represents a physical shipment of goods from a warehouse or organization to a ship-to destination, consolidating one or more delivery details, picking activities, packed containers, and freight charges under a single delivery identifier. In the shipping execution flow, the delivery record is created when order lines are released for picking and is carried forward through pick confirmation, packing, manifesting, and ship confirmation. It acts as the operational anchor connecting order management, inventory, shipping, and receivables.

From a Data Vault modeling perspective, the ETRM relationship metadata classifies WSH_DELIVERIES as a hub. This classification is heuristic — mined from the foreign key structure and the singular delivery_id primary key — and suggests that WSH_DELIVERIES serves as a business-key repository whose descriptive attributes would typically be split into satellites in a formal Data Vault design.

Key Information Stored

The documented physical schema contains 76 columns. The surrogate primary key is DELIVERY_ID, enforced by the WSH_DELIVERIES_PK constraint and reinforced by the unique index WSH_DELIVERIES_U1. A second unique index, WSH_DELIVERIES_U2, identifies NAME as the business-key candidate — the user-facing delivery name or delivery number that appears on shipping documents and reports.

The most significant columns include:

• DELIVERY_ID — system-generated surrogate primary key for the delivery.
• NAME — the delivery number, the principal business key used by planners and carriers.
• ORGANIZATION_ID — the warehouse or inventory organization fulfilling the shipment.
• SOURCE_CODE — indicates whether the delivery originated from Order Management, Inventory, or another source.
• STATUS_CODE — current lifecycle state (for example, open, picked, packed, confirmed, or closed).
• CUSTOMER_ID — the ship-to customer, referencing RA_CUSTOMERS.
• ULTIMATE_SHIP_TO_ID and INTERMEDIATE_SHIP_TO_ID — the final and intermediate ship-to site uses, both referencing RA_SITE_USES_ALL.
• PLANNED_DEPARTURE_ID and ACTUAL_DEPARTURE_ID — departure records in WSH_DEPARTURES for planning and confirmation.
• DATE_CLOSED — the date the delivery was closed.
• FREIGHT_CARRIER_CODE, FREIGHT_TERMS_CODE, FOB_CODE, and CURRENCY_CODE — commercial and freight terms.
• WAYBILL, GROSS_WEIGHT, NET_WEIGHT, and VOLUME — carrier and measurement attributes, with their associated UOM code columns.

Common Use Cases and Queries

Reporting on delivery status, carrier performance, and shipment volumes is the dominant use of this table. A typical query lists open deliveries by organization and status:

• SELECT d.name, d.status_code, d.customer_id, d.freight_carrier_code FROM wsh_deliveries d WHERE d.organization_id = :org_id AND d.status_code NOT IN ('CLOSED','CANCELLED');

Detail-level reporting joins WSH_DELIVERIES to SO_LINE_DETAILS via DELIVERY_ID to reconcile ordered versus shipped quantities. Freight analysis joins to SO_FREIGHT_CHARGES on DELIVERY_ID to aggregate transportation cost per delivery, while packing analysis joins to WSH_PACKED_CONTAINERS. ASN processing uses ASN_DATE_SENT and ASN_SEQ_NUMBER to determine which deliveries have been transmitted to the customer. Weight and volume columns support load planning and manifest reporting.

Related Objects

WSH_DELIVERIES participates in a large dependency network. The most significant related objects, with join columns, include:

• WSH_DEPARTURES — referenced by PLANNED_DEPARTURE_ID and ACTUAL_DEPARTURE_ID.
• RA_CUSTOMERS — referenced by CUSTOMER_ID.
• RA_SITE_USES_ALL — referenced by ULTIMATE_SHIP_TO_ID and INTERMEDIATE_SHIP_TO_ID.
• SO_REPORT_SETS — referenced by REPORT_SET_ID.
• SO_LINE_DETAILS — references WSH_DELIVERIES.DELIVERY_ID.
• SO_PICKING_BATCHES_ALL, SO_PICKING_HEADERS_ALL, and SO_PICKING_LINE_DETAILS — all reference DELIVERY_ID.
• WSH_PACKED_CONTAINERS and WSH_INVOICE_NUMBERS — both reference DELIVERY_ID.
• SO_FREIGHT_CHARGES — references DELIVERY_ID.

Collectively, these dependencies confirm WSH_DELIVERIES as the hub of the shipping execution model, bridging order entry, inventory, transportation, and invoicing.