Results for “ship_from_location_id”

50+ results




Overview
Explore in AI Chat

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

Overview

WSH_DLVY_SHIP_FROM_TO_V is a Shipping Execution (WSH) view owned by the APPS schema. It presents a consolidated "ship-from / ship-to" perspective of delivery records so that shipping, order management, and integration processes can resolve the origin and destination locations associated with a delivery without navigating the full delivery data model. The view is documented as VALID in Oracle E-Business Suite 12.1.1 and 12.2.2 and is part of the standard ETRM-referenced WSH object inventory.

Functionally, the view flattens the header-level delivery record into a location-oriented projection: it maps the delivery's initial pickup location to a SHIP_FROM_LOCATION_ID and its ultimate dropoff location to a SHIP_TO_LOCATION_ID. It is therefore suited to reporting, extracts, and integration interfaces in which the question is "from where and to where is this delivery moving?" rather than "which container or line items are on it." The view deliberately returns the delivery grain only and suppresses detail-level attributes, as reflected by its NULL-cast placeholder columns.

Underlying Base Objects

The view is defined over a single documented base object, WSH_NEW_DELIVERIES, accessed through a synonym in the APPS schema. No additional joins, lookup tables, or location master references are included in the view text; location identifiers surface directly from the delivery header columns. The documented definition is:

The WHERE clause restricts results to outbound and internal-outbound delivery directions. Because SHIPMENT_DIRECTION is wrapped in NVL with a default of 'O', records with a NULL direction are treated as outbound and are included. Inbound-only deliveries are excluded, which is consistent with the view's intended outbound logistics reporting role.

Key Columns

  • DELIVERY_ID — Primary identifier of the delivery, sourced directly from WSH_NEW_DELIVERIES. Joins back to the delivery header.
  • DELIVERY_NAME — The delivery name (aliased from NAME), the human-readable delivery number used for display and search.
  • SHIP_FROM_LOCATION_ID — Aliased from INITIAL_PICKUP_LOCATION_ID; the location from which the delivery originates.
  • SHIP_TO_LOCATION_ID — Aliased from ULTIMATE_DROPOFF_LOCATION_ID; the final destination location for the delivery.
  • CONTAINER_FLAG, DELIVERY_DETAIL_ID, CONTAINER_NAME, ORGANIZATION_ID, INVENTORY_ITEM_ID — Placeholder columns cast as NULL (TO_CHAR(NULL) / TO_NUMBER(NULL)). They exist to preserve a stable, container/detail-compatible column signature for consumers such as LOVs, flexfield-backed queries, or union-style consumers, while this view itself supplies only header-level data.

The presence of the NULL placeholder columns indicates that WSH_DLVY_SHIP_FROM_TO_V is one member of a family of shipping views sharing a common column list, with sibling views populating the container- and item-level attributes.

Common Use Cases and Queries

Typical uses include location-based shipping reports, carrier and route analysis, and integration extracts that push ship-from/ship-to pairs into external transportation or WMS systems. A representative query:

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

Because the view returns one row per outbound or internal-outbound delivery and performs no container or item expansion, it is efficient for header-level joins. Analysts commonly join DELIVERY_ID back to WSH_NEW_DELIVERIES or WSH_DELIVERY_ASSIGNMENTS to enrich results with status, carrier, or trip information that the view does not expose.