Search Results source_location_id




Overview
Explore in AI Chat

Overview

The APPS.WSHBV_DELIVERIES view is a business view (BV) in Oracle E-Business Suite that exposes delivery header information from the Oracle Shipping (WSH) module. It is owned by the APPS schema and is defined as a read-only view, as indicated by the WITH READ ONLY clause in its definition. The view presents a denormalized, reporting-friendly picture of delivery records by joining the core deliveries table, WSH_NEW_DELIVERIES, with the location table, WSH_LOCATIONS, on multiple occasions. Its purpose is to provide a stable, presentation-layer interface for delivery data that can be queried by reports, concurrent programs, and integration components without requiring callers to reconstruct the underlying join logic. Because several descriptive attributes are exposed through lookup labels (for example status, planned flag, shipment method, FOB code, and acceptance flag), the view delivers human-readable meanings alongside raw codes.

Underlying Base Objects

WSHBV_DELIVERIES is defined over two referenced base objects, both accessed through synonyms in the APPS schema:

  • WSH_NEW_DELIVERIES (alias WND) — the driving table containing the delivery header record, including identifiers, weights, dates, carrier references, and shipment classification.
  • WSH_LOCATIONS (aliases LOC, LOC1, LOC2, LOC3, LOC4) — joined five times against distinct delivery location foreign keys: the ultimate dropoff location, intermediate ship-to location, pooled ship-to location, initial pickup location, and FOB location.

The joins follow an outer-join pattern. The ultimate dropoff and initial pickup joins are mandatory, while the intermediate ship-to, pooled ship-to, and FOB joins are outer joins ((+)) because those attributes may be null. The view further filters the results so that only deliveries for the calling user's organization (via the security predicate _SEC:WND.ORGANIZATION_ID) and whose shipment direction is outbound or internal outbound (NVL(SHIPMENT_DIRECTION,'O') IN ('O','IO')) are returned.

Key Columns

Common Use Cases and Queries

This view is typically used for delivery reporting, status dashboards, and integrations that need delivery header data without coding the underlying joins. A common query lists deliveries with their status meaning and source locations for a given organization:

SELECT delivery_id, name, status_code, source_location_id,
       confirm_date, carrier_id, waybill
  FROM apps.wshbv_deliveries
 WHERE organization_id = :org_id
 ORDER BY creation_date DESC;

Because READ ONLY, the view supports SELECT access only and cannot be used as a DML target. Reports can also filter on confirm or ASN dates for shipping performance tracking, and integrations can resolve the multiple SOURCE_LOCATION_ID columns to determine the correct pickup, ship-to, or dropoff location depending on the delivery role required.