Search Results ship_status_code

Overview

IBE_SHIP_DETAIL_V is an APPS-owned database view in the Oracle E-Business Suite iStore (IBE) module. It presents a consolidated, denormalized picture of the shipping lifecycle for order lines, bridging sales order data in Oracle Order Management with delivery and transportation data in Oracle Shipping Execution (WSH). For the ETRM 12.1.1 and 12.2.2 releases, the view is documented as VALID and is a core object used by iStore shipping pages and related reporting.

The view is particularly significant for users searching on ship_status. Although the view does not expose a column literally named SHIP_STATUS, the shipping status information is available through the DL.STATUS_CODE column and its decoded meaning WL.MEANING, derived from the WSH_LOOKUPS lookup type DELIVERY_STATUS. This is the field that displays shipment status on iStore order tracking pages. The view also carries line-level flow status (OL.FLOW_STATUS_CODE, decoded as LINE_STATUS) and ship method descriptions, allowing a single query to return order, delivery, and transportation context.

Underlying Base Objects

IBE_SHIP_DETAIL_V is defined over a join of the following documented base objects:

• OE_ORDER_LINES_ALL — order line header, line, shipment, component, and service identifiers.
• WSH_DELIVERY_DETAILS — delivery detail rows, shipped and requested quantities, and ship method.
• WSH_NEW_DELIVERIES — delivery header, waybill, initial pickup date, and delivery status code.
• WSH_DELIVERY_ASSIGNMENTS — links delivery details to deliveries.
• WSH_DELIVERY_LEGS, WSH_TRIP_STOPS, WSH_TRIPS — transportation legs, trip stops, and trips providing actual departure date and trip ship method.
• MTL_SYSTEM_ITEMS_VL — item description and concatenated segments.
• MTL_UNITS_OF_MEASURE_TL — units of measure descriptions for shipped quantity.
• OE_LOOKUPS, WSH_LOOKUPS, OE_SHIP_METHODS_V — lookup and ship method meaning lookups.
• OE_PROFILE — package supplying the OE_ORGANIZATION_ID profile value used to resolve the inventory item.

Most joins use outer joins (+), so order lines without a delivery still appear, which suits iStore display of partially shipped orders.

Key Columns

• DELIVERY_ID, DELIVERY_DETAIL_ID — delivery and delivery-detail identifiers.
• HEADER_ID, LINE_ID, LINE_NUMBER — sales order header and line identifiers.
• STATUS_CODE / WL.MEANING — delivery status code and its decoded meaning, effectively the ship status exposed to iStore.
• SHIP_METHOD_CODE / SHIP_METHOD_CODE_MEANING — ship method from the trip or delivery detail, with lookup meaning.
• SHIPPED_QUANTITY, REQUESTED_QUANTITY, REQUESTED_QUANTITY_UOM, SHIPPED_QUANTITY_UOM_DESC — quantities and units.
• TRACKING_NUMBER, WAYBILL_NUMBER, DATE_SHIPPED — carrier tracking, waybill, and actual departure date.
• FLOW_STATUS_CODE / LINE_STATUS — line-level flow status and its meaning.
• INITIAL_PICKUP_DATE, LINE_CATEGORY_CODE — pickup date and line category.

Common Use Cases and Queries

Typical scenarios include iStore order-status displays, shipment tracking for customers, and shipping reports that reconcile ordered versus shipped quantities. To locate shipment status by order line:

SELECT line_number, status_code, meaning, tracking_number, waybill_number, date_shipped FROM apps.ibe_ship_detail_v WHERE header_id = :p_header_id;

To filter by ship status:

SELECT line_id, shipped_quantity, meaning FROM apps.ibe_ship_detail_v WHERE status_code = :p_status AND line_id = :p_line_id;

These queries leverage the DELIVERY_STATUS lookup meaning as the effective ship_status field for iStore functionality.