Search Results ultimate_dropoff_location_id

Overview

IBE_SHIPMENT_LINES_V is an iStore (IBE) reporting view that exposes shipment line information for post-sales customer interactions in Oracle E-Business Suite. Its purpose is to present delivery detail and shipment status data from the Oracle Shipping execution layer in a flattened, item-joined form suitable for display to end customers checking order status, tracking shipments, or reviewing shipment history from within the iStore self-service interface. Because it is a view rather than a table, it is not implemented as a physical database object; it is defined at runtime and depends on the presence of the underlying Shipping objects in the instance.

The view is documented in ETRM as being based on WSH_DELIVERY_LINE_STATUS_V, with a join to MTL_SYSTEM_ITEMS_KFV. This makes it a thin presentation layer over standard Oracle Shipping status data, enriched with item description for customer-facing display.

Underlying Base Objects

The view text joins two objects:

• WSH_DELIVERY_LINE_STATUS_V — the Shipping execution status view providing delivery detail, quantities, locations, shipment method, tracking, and status attributes. Aliased as WSH in the view definition.
• MTL_SYSTEM_ITEMS_KFV — the key flexfield item view supplying the item description (MSI.DESCRIPTION). This is joined on INVENTORY_ITEM_ID and ORGANIZATION_ID, ensuring the item description is resolved in the correct inventory organization context.

The join is an equality join across both INVENTORY_ITEM_ID and ORGANIZATION_ID, so shipment lines must resolve to a valid item master record in the same organization. No additional base tables are documented as referenced by the view itself; the ETRM listing notes no independently documented base objects beyond the view definition text.

Key Columns

The view exposes shipment detail and header context in a single row per delivery detail:

• DELIVERY_DETAIL_ID, LINE_ID, HEADER_ID — identifiers for the delivery line, source line, and source header.
• DELIVERY_ID, DELIVERY_NAME, HEADER_NUMBER, LINE_NUMBER — delivery and order identification for customer display.
• INVENTORY_ITEM_ID, ITEM_DESCRIPTION — item identity and its resolved description.
• REQUESTED_QUANTITY, SHIPPED_QUANTITY, and their UOMs — ordered versus shipped quantities.
• SHIP_METHOD_CODE, TRACKING_NUMBER, WAYBILL_NUMBER — carrier and tracking detail.
• INITIAL_PICKUP_LOCATION_ID / INITIAL_PICKUP_LOCATION — origin location of the shipment.
• ULTIMATE_DROPOFF_LOCATION_ID / ULTIMATE_DROPOFF_LOCATION — the final destination location for the shipment line. This is the column most relevant to the search term ultimate_dropoff_location_id, which returns the destination location identifier paired with its descriptive name.
• DELIVERY_STATUS, DELIVERY_STATUS_MEANING, PICK_STATUS, PICK_MEANING — status codes and their translated meanings.
• DATE_SHIPPED, DATE_RECEIVED, WEIGHT, WEIGHT_UOM_CODE, REVISION, LOT_NUMBER, SERIAL_NUMBER — shipment timing and item control attributes.

Common Use Cases and Queries

Typical use cases include customer-facing shipment tracking, post-sales order status pages in iStore, and reporting on destination locations for shipped lines. A representative query retrieving shipment lines with destination location:

• SELECT header_number, line_number, item_description, shipped_quantity, date_shipped, ultimate_dropoff_location_id, ultimate_dropoff_location, tracking_number FROM ibe_shipment_lines_v WHERE header_number = :p_order_number;

To filter by destination location specifically:

• SELECT delivery_name, line_number, ultimate_dropoff_location FROM ibe_shipment_lines_v WHERE ultimate_dropoff_location_id = :p_location_id;

To report shipped versus requested quantities by delivery:

• SELECT delivery_name, item_description, requested_quantity, shipped_quantity, delivery_status_meaning FROM ibe_shipment_lines_v WHERE delivery_id = :p_delivery_id ORDER BY line_number;

Because the view depends on WSH_DELIVERY_LINE_STATUS_V and MTL_SYSTEM_ITEMS_KFV, query performance is governed by those base objects; filtering on delivery or header identifiers generally yields the most efficient execution plans.