Search Results departure_name




Overview
Explore in AI Chat

Overview

APPS.WSH_PACKED_CONTAINERS_DPW_V is a reporting view in the Oracle E-Business Suite Shipping Execution module. It presents packed container information at the delivery and departure level, joining container records to their parent deliveries and, where available, to the planned departure for that delivery. The view is designed to satisfy outbound logistics reporting requirements in which container contents must be linked back to the shipment's departure schedule. This is particularly relevant to Oracle EBS 12.1.1 and 12.2.2 environments, where the WSH schema provides the foundational tables for delivery, departure, and container data.

The view's primary role is to expose a denormalized, query-friendly projection of packed containers, enriched with descriptive attributes such as the departure name, delivery name, container item description, and unit of measure. Because it surfaces DERPARTURE_NAME (aliased from WDP.NAME), it directly answers one of the most common shipping reports: which departure each packed container is associated with.

Underlying Base Objects

The view is owned by APPS and is defined over four base objects, referenced in the ETRM metadata as synonyms: WSH_PACKED_CONTAINERS, WSH_DELIVERIES, WSH_DEPARTURES, and MTL_SYSTEM_ITEMS.

  • WSH_PACKED_CONTAINERS (WPC) — The driving table, supplying the container_id, delivery_id, container_inventory_item_id, and quantity.
  • WSH_DELIVERIES (WDL) — Joined on WPC.DELIVERY_ID = WDL.DELIVERY_ID, providing the delivery name and the planned departure reference.
  • WSH_DEPARTURES (WDP) — Joined via an outer join (WDP.DEPARTURE_ID (+) = WDL.PLANNED_DEPARTURE_ID) to supply the departure name.
  • MTL_SYSTEM_ITEMS (MSI) — Joined on inventory_item_id and organization_id to provide the container item description and primary unit of measure.

The outer-join condition on WSH_DEPARTURES ensures that deliveries without an assigned planned departure are still returned, with departure_name and departure_id appearing as null.

Key Columns

  • CONTAINER_ID — Primary identifier of the packed container record.
  • DEPARTURE_ID — Derived from WDL.PLANNED_DEPARTURE_ID; identifies the planned departure for the delivery.
  • DEPARTURE_NAME — The departure name from WSH_DEPARTURES.NAME; the column users typically search for.
  • DELIVERY_ID / DELIVERY_NAME — The delivery identifier and its descriptive name.
  • CONTAINER_INVENTORY_ITEM_ID / CONTAINER_DESCRIPTION — The container's inventory item and its description from MTL_SYSTEM_ITEMS.
  • QUANTITY — The packed quantity within the container.
  • UOM_CODE — The primary unit of measure of the container item.

Common Use Cases and Queries

Typical usage includes container manifest reporting, departure-level loading summaries, and reconciliation of packed quantities against planned shipments. The following query returns all containers assigned to a specific departure:

SELECT container_id, departure_name, delivery_name,
       container_description, quantity, uom_code
  FROM apps.wsh_packed_containers_dpw_v
 WHERE departure_name = :p_departure_name;

To list deliveries lacking a planned departure, filter on a null departure:

SELECT delivery_name, container_description, quantity
  FROM apps.wsh_packed_containers_dpw_v
 WHERE departure_id IS NULL;

Aggregated departure volumes can be produced with a GROUP BY:

SELECT departure_name, SUM(quantity) total_packed
  FROM apps.wsh_packed_containers_dpw_v
 GROUP BY departure_name;

Because the view resides in the APPS schema, custom reporting and integrations should reference it as APPS.WSH_PACKED_CONTAINERS_DPW_V and observe standard EBS security and grants.