Search Results wsh_dlvb_ship_from_to_v

Overview

WSH_DLVB_SHIP_FROM_TO_V is a reporting view owned by the APPS schema within the Oracle Shipping Execution (WSH) module. It exposes a reduced projection of delivery detail records that carry ship-from and ship-to location information, along with container and item context. The view is classified as VALID in the ETRM metadata for Oracle E-Business Suite 12.1.1 and 12.2.2, and it is intended for read-only consumption by reports, concurrent programs, and external integrations that require a compact, denormalized view of shipping detail location data.

The defining characteristic of this view is its use of a filter on the LINE_DIRECTION column of WSH_DELIVERY_DETAILS. Only rows whose LINE_DIRECTION is 'O' (Outbound) or 'IO' (Internal Order / Internal Sales Order) are returned. Rows with a NULL LINE_DIRECTION are treated as 'O' by the NVL expression, ensuring that legacy detail records are not silently excluded.

Underlying Base Objects

The view is defined over a single base object, WSH_DELIVERY_DETAILS, referenced through a synonym. WSH_DELIVERY_DETAILS is the core transaction table for shipping execution, storing one row per deliverable line, container, or inventory unit associated with a delivery. Because the dependency is limited to this one table, the view introduces no joins and therefore no risk of row multiplication.

The projection is notable for two columns that are deliberately returned as typed NULLs: DELIVERY_ID is cast with TO_NUMBER(NULL) and DELIVERY_NAME with TO_CHAR(NULL). Neither the delivery header identifier nor the delivery name is physically populated by this view, even though the base table carries a delivery association. This design indicates that the view is intended as a component of a larger UNION ALL construct — a common pattern in Shipping Execution where several direction-specific or role-specific views are combined into a single interface view such as WSH_DLVR_SHIP_FROM_TO_V or a similar shipping inquiry form.

Key Columns

• DELIVERY_ID — Declared as TO_NUMBER(NULL); always NULL in this view. Placeholder for union compatibility.
• DELIVERY_NAME — Declared as TO_CHAR(NULL); always NULL in this view. Placeholder for union compatibility.
• CONTAINER_FLAG — Indicates whether the detail row represents a container rather than a standalone item.
• DELIVERY_DETAIL_ID — Primary key of the underlying WSH_DELIVERY_DETAILS row; the join key back to the base table.
• CONTAINER_NAME — Name of the container (LICN) associated with the detail, when applicable.
• ORGANIZATION_ID — Inventory organization that owns the item being shipped.
• INVENTORY_ITEM_ID — Inventory item identifier for the shipped material.
• SHIP_FROM_LOCATION_ID — Location identifier from which the material is shipped.
• SHIP_TO_LOCATION_ID — Location identifier to which the material is shipped.

Common Use Cases and Queries

The view is typically queried when a report or interface needs ship-from and ship-to location pairs for outbound and internal order lines, without the overhead of joining to delivery header tables. A representative query retrieving location data for a specific organization follows:

SELECT delivery_detail_id, container_name, inventory_item_id, ship_from_location_id, ship_to_location_id FROM apps.wsh_dlvb_ship_from_to_v WHERE organization_id = :p_org_id AND ship_from_location_id IS NOT NULL;

A second common pattern resolves location identifiers to their descriptive names by joining to HR_LOCATIONS_ALL, which is useful in shipping label and manifest reporting:

SELECT v.delivery_detail_id, v.container_name, f.location_code ship_from_code, t.location_code ship_to_code FROM apps.wsh_dlvb_ship_from_to_v v, hr_locations_all f, hr_locations_all t WHERE v.ship_from_location_id = f.location_id AND v.ship_to_location_id = t.location_id(+) AND v.inventory_item_id = :p_item_id;

Because DELIVERY_ID and DELIVERY_NAME are always NULL, consumers must obtain delivery header context by joining WSH_DELIVERY_DETAILS to WSH_DELIVERY_ASSIGNMENTS and WSH_NEW_DELIVERIES using DELIVERY_DETAIL_ID. The view is best treated as a direction-filtered, header-free projection suited to location-centric reporting rather than to full delivery inquiry.