Search Results oe_ship_methods_v




Overview
Explore in AI Chat

Overview

IBE_SHIP_DLVY_DTL_V is an Oracle E-Business Suite 12.1.1 / 12.2.2 reporting view owned by the APPS schema and classified under the IBE (iStore) product family. Its documented purpose is to store and expose delivery detail information, denormalizing shipment, trip, order, and item attribution into a single queryable structure. The view is used primarily for iStore order tracking and shipment status presentation, as well as for custom shipping and delivery reporting and integration extracts that require shipment method, carrier waybill, and delivery line status data at the delivery detail grain.

Users who search for the related object OE_SHIP_METHODS_V typically reach this view because OE_SHIP_METHODS_V is joined twice within its definition. In EBS, OE_SHIP_METHODS_V is the Order Management shipping method lookup view keyed by LOOKUP_TYPE = 'SHIP_METHOD'. IBE_SHIP_DLVY_DTL_V resolves a ship method code from either the trip (WSH_TRIPS.SHIP_METHOD_CODE) or the delivery detail (WSH_DELIVERY_DETAILS.SHIP_METHOD_CODE), then translates that code to a user-facing meaning via two outer joins to OE_SHIP_METHODS_V. This makes OE_SHIP_METHODS_V an implicit dependency of the IBE view and the reason both are frequently referenced together.

Underlying Base Objects

The view is defined over eleven documented base objects. Core delivery detail data comes from WSH_DELIVERY_DETAILS (aliased DD) and delivery header data from WSH_NEW_DELIVERIES (DL) and WSH_DELIVERY_ASSIGNMENTS (DA). Trip and leg routing is sourced from WSH_DELIVERY_LEGS, WSH_TRIP_STOPS, and WSH_TRIPS. Order attribution comes from OE_ORDER_HEADERS_ALL (OH). Item and unit of measure descriptions come from MTL_SYSTEM_ITEMS_VL (MSI) and MTL_UNITS_OF_MEASURE_TL (MSIT). Status decoding uses the WSH_LOOKUPS view (WL) against LOOKUP_TYPE = 'PICK_STATUS'. Ship method decoding uses two instances of OE_SHIP_METHODS_V, aliased LV1 and LV2, both constrained to LOOKUP_TYPE = 'SHIP_METHOD'.

The joins are predominantly outer joins to preserve delivery detail rows even when trip, delivery, or lookup data is absent. The view filters rows to order-management sources via DD.SOURCE_CODE = 'OE' and restricts the unit-of-measure language via MSIT.LANGUAGE = USERENV('LANG'). Delivery detail rows are matched to items by both INVENTORY_ITEM_ID and ORGANIZATION_ID.

Key Columns

Common Use Cases and Queries

Typical uses include order shipment tracking in iStore, delivery-status dashboards, and integration feeds to carriers or external tracking systems. A common query joins back to OE_SHIP_METHODS_V directly when additional ship method attributes are required:

  • Order and shipment listing: SELECT ORDER_NUMBER, DELIVERY_ID, SHIP_METHOD_CODE, SHIP_METHOD_CODE_MEANING, SHIPPED_QUANTITY, WAYBILL_NUMBER, DELIVERY_LINE_STATUS_MEANING FROM IBE_SHIP_DLVY_DTL_V WHERE ORDER_NUMBER = :p_order_number.
  • Carrier tracking extract: filter on TRACKING_NUMBER IS NOT NULL and DATE_SHIPPED within a date range.
  • Ship method validation: join SHIP_METHOD_CODE to OE_SHIP_METHODS_V.LOOKUP_CODE WHERE LOOKUP_TYPE = 'SHIP_METHOD' to reconcile codes for a specific organization.
  • Delivery line status reporting: filter on DELIVERY_LINE_STATUS_MEANING to isolate released, staged, or shipped lines.

Because ship method and status values are decoded through outer joins, consumers should expect NULL meanings when lookup setup is incomplete, and should not rely on the view for non-order sources, since DD.SOURCE_CODE is fixed to 'OE'.