Search Results initial_pickup_location_id




Overview
Explore in AI Chat

Overview

APPS.WSH_DLVY_SHIP_FROM_TO_V is a reporting and integration view in Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2 that exposes ship-from and ship-to location information for standard outbound deliveries. It is part of the Warehouse Management (WSH) module and is primarily intended for use by external systems, reporting tools, and interface programs that need a flattened, query-friendly projection of delivery header data combined with its associated origin and destination locations, without joining directly against the transactional delivery tables.

The view is defined specifically for deliveries with a standard delivery type and an outbound or internal outbound shipment direction, which makes it suitable for logistics, transportation planning, and shipment tracking scenarios where only customer-facing or internal outbound movements are relevant.

Underlying Base Objects

According to the ETRM documentation, this view is defined over a single referenced base object: the synonym WSH_NEW_DELIVERIES, which resolves to the underlying WSH_NEW_DELIVERIES table in the APPS schema. No additional joins or external tables are included.

Because the view selects only from WSH_NEW_DELIVERIES, it acts as a lightweight filter over that table. It restricts the result set with two predicates: NVL(SHIPMENT_DIRECTION, 'O') IN ('O', 'IO'), limiting output to standard outbound and internal outbound shipments, and DELIVERY_TYPE = 'STANDARD', excluding other delivery types. This narrows the view to conventional outbound deliveries and excludes special or non-standard movement types.

Key Columns

The view exposes a set of delivery header attributes and aliased location identifiers. Note that several columns are populated with explicit NULL placeholders (TO_CHAR(NULL) or TO_NUMBER(NULL)) so that the view's column structure matches a consolidated ship-from/ship-to reporting contract shared with related views such as container-level or line-level views.

  • delivery_id — Primary identifier of the delivery from WSH_NEW_DELIVERIES.
  • delivery_name — Business-facing name of the delivery (aliased from NAME).
  • container_flag — Always NULL in this view; exists for structural consistency.
  • delivery_detail_id — Always NULL; used in other views that expand delivery lines.
  • container_name — Always NULL; used for container-level reporting contexts.
  • organization_id — Always NULL; relevant in item/inventory-level views.
  • inventory_item_id — Always NULL; used where item detail is required.
  • ship_from_location_id — Aliased from INITIAL_PICKUP_LOCATION_ID. This is the column most relevant to the user's search term initial_pickup_location_id, representing the location from which the delivery initially departs.
  • ship_to_location_id — Aliased from ULTIMATE_DROPOFF_LOCATION_ID. Represents the final destination of the delivery.

Common Use Cases and Queries

This view is typically used to report on planned or actual ship-from and ship-to locations for standard outbound deliveries. A common scenario is feeding a transportation or carrier interface with origin and destination details, or reporting shipment routes by delivery.

Because the view already filters for outbound standard deliveries, queries do not need to repeat those predicates:

SELECT delivery_id,
       delivery_name,
       ship_from_location_id,
       ship_to_location_id
  FROM apps.wsh_dlvy_ship_from_to_v
 WHERE ship_from_location_id = :p_location_id
 ORDER BY delivery_name;

For delivery-level routing reports, the view can be joined to WSH_NEW_DELIVERIES or to location tables (such as HR_LOCATIONS or WSH_LOCATION_ASSOCIATIONS) on ship_from_location_id and ship_to_location_id to resolve human-readable address details. Because the view does not expose line, item, or organization context, it should be regarded as a header-level convenience view rather than a substitute for detailed shipment line reporting.