Search Results wshbv_deliveries




Overview
Explore in AI Chat

Overview

WSHBV_DELIVERIES is an APPS-owned database view in the Oracle E-Business Suite Shipping Execution (WSH) module, valid in both 12.1.1 and 12.2.2. It presents a consolidated, secured projection of delivery information sourced primarily from WSH_NEW_DELIVERIES, with supplementary address references resolved from WSH_LOCATIONS. The view materializes a single row per outbound (or outbound/internal order) delivery and exposes the header-level attributes required for shipment reporting, carrier-facing documents, and integration feeds.

The "BV" naming convention indicates a business view, a class of WSH objects intended for direct consumption by reports, BI Publisher templates, and external interfaces. Because it joins locations and applies security predicates, the view provides denormalized access to ship-to, drop-off, and FOB addresses without requiring consumers to reconstruct the underlying location joins. The view carries a WITH READ ONLY clause, confirming it is intended strictly for query, not as an update target.

Underlying Base Objects

The documented ETRM metadata identifies two referenced base objects: WSH_NEW_DELIVERIES (SYNONYM) and WSH_LOCATIONS (SYNONYM). WSH_NEW_DELIVERIES is the primary delivery header table and supplies nearly all exposed columns. WSH_LOCATIONS is joined five times (aliases LOC, LOC1, LOC2, LOC3, LOC4) to resolve distinct delivery location roles:

The WHERE clause also filters on '_SEC:WND.ORGANIZATION_ID' IS NOT NULL (organization-level security) and restricts SHIPMENT_DIRECTION to 'O' or 'IO', excluding inbound-only deliveries.

Key Columns

Regarding the user's search term, GROSS_WEIGHT is exposed directly from WSH_NEW_DELIVERIES, accompanied by WEIGHT_UOM_CODE and the parallel NET_WEIGHT. Volume measures appear as VOLUME and VOLUME_UOM_CODE. These are the primary columns for carrier rating, manifesting, and weight-based freight calculation.

Identification and status columns include DELIVERY_ID, NAME, ORGANIZATION_ID, and DELIVERY_TYPE, along with audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN). Status is surfaced through a lookup-translation construct (_LA:STATUS_CODE:WSH_LOOKUPS:DELIVERY_STATUS:MEANING), returning the descriptive delivery status. Similarly translated columns supply SHIP_METHOD, FOB, and the YES/NO meanings for PLANNED_FLAG and ACCEPTANCE_FLAG. Additional functional columns include WAYBILL, CARRIER_ID, FREIGHT_TERMS_CODE, CURRENCY_CODE, LOADING_SEQUENCE, LOADING_ORDER_FLAG, NUMBER_OF_LPN, CONFIRM_DATE, ACKNOWLEDGED_BY, ACCEPTED_BY, ACCEPTED_DATE, CONFIRMED_BY, and ASN_DATE_SENT. Transportation and trade fields (PORT_OF_DISCHARGE, PORT_OF_LOADING, BOOKING_NUMBER, SERVICE_CONTRACT, COD_AMOUNT, COD_CURRENCY_CODE, COD_REMIT_TO, COD_CHARGE_PAID_BY, BILL_FREIGHT_TO, CARRIED_BY, DOCK_CODE) are also exposed.

Common Use Cases and Queries

Typical scenarios include shipment weight/volume reporting, carrier manifest and ASN extracts, delivery status dashboards, and COD or freight-terms analysis. Organization security imposed by the view makes it safe to expose in shared reporting layers.

Example: retrieve deliveries with gross weight for a given organization.

  • SELECT delivery_id, name, gross_weight, weight_uom_code, net_weight, volume, volume_uom_code
    FROM apps.wshbv_deliveries
    WHERE organization_id = :org_id
    ORDER BY name;

Example: identify deliveries with an outstanding or missing ASN transmission.

  • SELECT delivery_id, name, waybill, carrier_id, asn_date_sent, confirm_date
    FROM apps.wshbv_deliveries
    WHERE asn_date_sent IS NULL AND confirm_date IS NOT NULL;

Example: aggregate weight by carrier for freight analysis.

  • SELECT carrier_id, SUM(gross_weight) total_gross_weight, weight_uom_code
    FROM apps.wshbv_deliveries
    GROUP BY carrier_id, weight_uom_code;

Because all columns originate from the delivery header and its location references, joins to WSH_DELIVERY_DETAILS or WSH_DELIVERY_ASSIGNMENTS are required to obtain line- or LPN-level granularity.