Search Results ui_location_code

Overview

The view WMS_WP_WWB_LINES_V is an Oracle E-Business Suite Applications (APPS) database object residing in the Warehouse Management (WMS) product family. It is a reporting and integration view that consolidates wave planning line information with associated outbound shipment, delivery, order, and item attributes. The view exposes a denormalized, query-friendly projection of line-level details used by the Wave Planning Workbench (WWB) within Oracle Warehouse Management. Because it joins data drawn from Order Management, Shipping Execution, and Inventory, it serves as a single source for line-level wave and delivery reporting without requiring consumers to reconstruct the join graph themselves.

The view is classified as VALID in the 12.1.1 / 12.2.2 data dictionary and is owned by the APPS schema. Its SELECT statement incorporates a USE_NL(MSIV) hint and a DISTINCT qualifier, indicating that it is intended to return unique line rows joined through nested loops against the item master view. Notably, the view repeatedly references WSH_LOCATIONS to resolve multiple ship-to, deliver-to, and contact identifiers into their UI_LOCATION_CODE descriptions.

Underlying Base Objects

The documented ETRM metadata lists the objects over which this view is defined. These span several EBS modules:

• Shipping Execution: WSH_DELIVERY_DETAILS, WSH_DELIVERY_ASSIGNMENTS, WSH_DELIVERY_LEGS, WSH_NEW_DELIVERIES, WSH_TRIP_STOPS, WSH_CARRIERS, and WSH_LOCATIONS.
• Warehouse Management: WMS_WP_WAVE_LINES, WMS_WP_WAVE_HEADERS_VL, WMS_LICENSE_PLATE_NUMBERS, and the WMS_WAVE_PLANNING_PVT package.
• Order Management: OE_ORDER_LINES_ALL.
• Inventory: MTL_SYSTEM_ITEMS_KFV, MTL_ITEM_LOCATIONS_KFV, and MTL_PARAMETERS.
• Trading Community / Parties: HZ_CUST_ACCOUNTS, HZ_PARTIES, and HZ_PARTY_SITES.

The heavy reliance on WSH_LOCATIONS is central to the view's design. Each of the many location-related columns (deliver-to, ship-to, contacts, and intermediate stops) is resolved through a scalar subquery against WSH_LOCATIONS keyed on WSH_LOCATION_ID. Because the user search term was wsh_locations, this view is a principal consumer of that table, translating numeric location identifiers into human-readable location codes for reporting and downstream integration.

Key Columns

The view exposes a broad set of line- and delivery-level attributes. Important columns include:

• ORDER_NUMBER — derived from WDD.SOURCE_HEADER_NUMBER, the originating order or wave header reference.
• DELIVER_TO / SHIP_TO / DELIVER_TO_LOCATION — location codes resolved from WSH_LOCATIONS via the respective location IDs.
• LINE_SHIP_TO_CONTACT / DELIVER_TO_CONTACT — contact location codes resolved from WSH_LOCATIONS.
• DELIVERY — the delivery name from WSH_NEW_DELIVERIES.
• ITEM and ITEM_DESCRIPTION — concatenated item segments from MTL_SYSTEM_ITEMS_KFV and the item description.
• REQUESTED_QTY, SHIPPED_QTY, DELIVERED_QUANTITY — quantities at the requested, shipped, and delivered stages.
• PLANNED_FILL_RATE, RELEASE_FILL_RATE, PICK_FILL_RATE — wave planning fill metrics from WMS_WP_WAVE_LINES.
• CARRIER — freight code from WSH_CARRIERS.
• MODE_OF_TRANSPORT, FOB_CODE, FREIGHT_TERMS_CODE — transportation attributes.
• GROSS_WEIGHT, NET_WEIGHT, MAXIMUM_LOAD_WEIGHT, MAXIMUM_VOLUME — weight and volume metrics used in load planning.
• ORGANIZATION_CODE — the warehouse organization code from MTL_PARAMETERS.

Common Use Cases and Queries

This view is typically queried for wave planning dashboards, delivery line reporting, and location-resolution integrations. A representative query follows:

• Reporting all lines for a given delivery or order, including resolved ship-to and deliver-to location codes.
• Analyzing pick, release, and planned fill rates across wave lines to identify shortfalls.
• Extracting weight and volume data for load planning or carrier tendering.

Sample SQL:

SELECT order_number, delivery, item, requested_qty,
       shipped_qty, ship_to, deliver_to_location,
       pick_fill_rate, mode_of_transport, organization_code
  FROM apps.wms_wp_wwb_lines_v
 WHERE delivery = :p_delivery
 ORDER BY order_number;

Because the view resolves many identifiers through WSH_LOCATIONS, it is well suited to integrations that require readable location codes rather than internal IDs, eliminating the need for the calling application to join WSH_LOCATIONS independently.