Search Results initial_pickup_location

Overview

APPS.WSH_DELIVERY_LINE_STATUS_V is a Shipping Execution (WSH) view that presents delivery detail lines together with their associated delivery header, pick, and shipment status information. It is registered in FND Design Data as WSH.WSH_DELIVERY_LINE_STATUS_V and carries a status of VALID in the EBS 12.1.1 and 12.2.2 environments. The view consolidates line-level fulfillment data — ordered, shipped, and requested quantities, item and lot/serial identity, and shipping attributes — into a single reporting structure.

The object is flagged with an Oracle Internal Use Only warning: Oracle does not support direct access to applications data through this view except from standard Oracle Applications programs. This classification does not preclude read-only querying for reporting or integration purposes, but it does mean that the column set and internal logic are not a committed public interface and may change across patch levels. The most frequently searched column, DELIVERY_STATUS_MEANING, is the user-facing description of the delivery state, resolved through the WSH lookup layer rather than being stored directly on the delivery row.

Underlying Base Objects

The view is defined over a small set of documented dependencies that supply both transactional and descriptive data:

• WSH_DELIVERY_ASSIGNMENTS_V — links delivery details to delivery headers, providing delivery-level identity and status context.
• WSH_DELIVERY_DETAILS — the core shipping line table supplying item, quantity, revision, lot, serial, and shipment attributes.
• WSH_NEW_DELIVERIES — the delivery header entity that carries the delivery name, status code, and organization.
• WSH_LOCATIONS — resolves the initial pickup and ultimate dropoff location identifiers to descriptive location values.
• WSH_LOOKUPS — the lookup source used to translate coded values such as the delivery status into the DELIVERY_STATUS_MEANING description.
• WSH_SERIAL_NUMBERS — supplies serial number detail associated with the delivery line.

The join pattern follows the standard WSH hierarchy: delivery header to assignment to delivery detail, with lookup, location, and serial objects outer-joined to enrich the line-level row.

Key Columns

• DELIVERY_DETAIL_ID — primary identifier of the delivery detail line; the grain of the view.
• DELIVERY_ID, DELIVERY_NAME — the parent delivery header key and user-visible delivery number.
• DELIVERY_STATUS, DELIVERY_STATUS_MEANING — the coded delivery status and its translated meaning, the column most commonly sought by users searching "delivery_status_meaning".
• PICK_STATUS, PICK_MEANING — pick status code and description for the line.
• SOURCE_CODE, SOURCE_LINE_ID, SOURCE_HEADER_ID, HEADER_NUMBER, LINE_NUMBER — identify the originating order or release that drove the delivery line.
• INVENTORY_ITEM_ID, REVISION, LOT_NUMBER, SERIAL_NUMBER, TO_SERIAL_NUMBER — item and lot/serial identity for the shipped material.
• REQUESTED_QUANTITY, SHIPPED_QUANTITY and the corresponding _UOM and secondary quantity (_2) columns — ordered versus actually shipped quantities in both primary and secondary units of measure.
• SHIP_METHOD_CODE, TRACKING_NUMBER, WAYBILL, DATE_SHIPPED, DATE_RECEIVED — carrier, tracking, and shipment timing data.
• ORGANIZATION_ID, INITIAL_PICKUP_LOCATION, ULTIMATE_DROPOFF_LOCATION, WEIGHT, CURRENCY_CODE — organizational, geographic, and weight context.

Common Use Cases and Queries

Typical uses include shipment status dashboards, open delivery line reports, order-to-shipment reconciliations, and integration extracts that must publish delivery status descriptions rather than internal codes. A representative query retrieving line status by delivery is:

• SELECT delivery_name, delivery_status, delivery_status_meaning, line_number, inventory_item_id, requested_quantity, shipped_quantity, date_shipped FROM apps.wsh_delivery_line_status_v WHERE delivery_status_meaning IS NOT NULL ORDER BY delivery_name, line_number;
• SELECT delivery_name, delivery_status_meaning, COUNT(*) FROM apps.wsh_delivery_line_status_v GROUP BY delivery_name, delivery_status_meaning; — used for status distribution reporting.
• SELECT line_number, inventory_item_id, lot_number, serial_number, shipped_quantity, shipped_quantity_uom, tracking_number FROM apps.wsh_delivery_line_status_v WHERE source_header_id = :p_order_header_id; — used to trace delivered material back to a sales order.

Because the view is an internal-use object, queries should be treated as read-only and validated after each application patch or upgrade.