Search Results manual_wv




Overview
Explore in AI Chat

Overview

APPS.WSH_SS_SHIPMENT_V is a Shipping Execution (WSH) view owned by the APPS schema and identified in FND Design Data as WSH.WSH_SS_SHIPMENT_V. It presents shipment-level information — deliveries, document numbers, carrier and service details, weight and volume attributes, and shipment descriptive flexfields — in a denormalized, report-friendly structure. Its status is VALID. ETRM classifies the view type as Internal and carries an explicit Oracle warning: the object is for Oracle Internal Use Only and is not supported for direct customer access except from standard Oracle Applications programs. Consequently, the view should be treated as a reporting and integration surface to be read only, never updated, and understood to be subject to change without notice. Custom development that references it directly assumes upgrade risk.

Underlying Base Objects

The documented dependency list shows the view drawing on both shipping tables and shared reference objects. Shipping-side objects include WSH_NEW_DELIVERIES, WSH_SHIPMENT_BATCHES, WSH_TRANSACTIONS_HISTORY, WSH_LOCATIONS, WSH_CARRIER_SERVICES, and the WSH_CARRIERS_V view. Organization and master data come from MTL_PARAMETERS, ORG_ORGANIZATION_DEFINITIONS, and HR_LOCATIONS_ALL_TL. Customer and site information is resolved through HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, and HZ_PARTY_SITES. Security and localization support are provided by HR_SECURITY and HR_GENERAL packages, which enforce organization-level access and derive descriptive location text. The joins across WSH_NEW_DELIVERIES (delivery header), WSH_LOCATIONS and HR_LOCATIONS_ALL_TL (ship-from/to addresses), and the HZ tables (ship-to customer sites) explain why a single view can return address, carrier, and weight/volume detail without additional lookups.

Key Columns

Common Use Cases and Queries

Typical uses include shipment reporting, carrier performance analysis, weight/volume audit, and integration extracts where the caller runs with APPS privileges. A frequent query is identifying shipments whose weight or volume was manually overridden, which is exactly the "manual_wv" search pattern:

  • SELECT delivery_id, document_number, carrier, gross_weight, net_weight, volume, manual_wv FROM apps.wsh_ss_shipment_v WHERE manual_wv = 'Y';
  • SELECT organization_code, ship_method, service_level, COUNT(*) FROM apps.wsh_ss_shipment_v GROUP BY organization_code, ship_method, service_level;
  • SELECT delivery_id, ship_from_location, ship_to_location, carrier, initial_pickup_date, ultimate_dropoff_date FROM apps.wsh_ss_shipment_v WHERE creation_date >= TRUNC(SYSDATE) - 30;

Because of the Oracle Internal Use Only restriction, any such query should be encapsulated in a custom view or wrapper that can be repointed after an upgrade, and access should be limited to privileged reporting accounts. This preserves compatibility across EBS 12.1.1 and 12.2.2 while protecting against changes to the underlying definition.