Search Results detail_item

Overview

APPS.WSHBV_DELIVERY_DETAILS is a business view (the "BV" suffix denotes Business View) in Oracle E-Business Suite that exposes delivery detail information from the Shipping Execution module in a denormalized, user-friendly form. It presents the core records of WSH_DELIVERY_DETAILS together with translated lookup meanings and resolved key flexfield values, so that reporting and integration clients can consume readable descriptions rather than raw codes. Each row corresponds to a single delivery detail — the lowest-level shipping line that identifies the item, quantity, source order line, and shipping attributes associated with a delivery. The view is widely used for order management and shipping reporting, shipping manifests, WMS and carrier integrations, and downstream data extracts. It is available in both 12.1.1 and 12.2.2, with the documented ETRM metadata reflecting the 12.2.2 definition.

Underlying Base Objects

The documented referenced base objects are MTL_CUSTOMER_ITEMS, MTL_ITEM_LOCATIONS, MTL_SYSTEM_ITEMS, WSH_DELIVERY_DETAILS, and WSH_LOCATIONS, all accessed through APPS synonyms. WSH_DELIVERY_DETAILS supplies the primary attributes of the view, including the delivery_detail_id, source document identifiers, quantities, and shipping characteristics. WSH_LOCATIONS is joined multiple times to resolve the source, ship-to, deliver-to, and intermediate ship-to location identifiers. MTL_SYSTEM_ITEMS and MTL_CUSTOMER_ITEMS provide item and customer-item context, while MTL_ITEM_LOCATIONS resolves locator and subinventory information. The view also embeds inline lookup translations — for example the ship model complete flag, customer requested lot flag, ship method code, freight terms, shipment priority, FOB code, and departure planning required flag — using FND_LOOKUPS, FND_LOOKUP_VALUES_VL, and AR_LOOKUPS, and it incorporates a key flexfield reference (_KF:INV:MTLL:MIL) for the material locator flexfield.

Key Columns

• DELIVERY_DETAIL_ID — primary identifier of the delivery detail; the join key to other shipping tables.
• SOURCE_CODE, SOURCE_HEADER_ID, SOURCE_LINE_ID — identify the originating document (for example, an order or transfer) and its header and line.
• CUST_PO_NUMBER — the customer purchase order reference carried on the detail.
• ITEM_DESCRIPTION — descriptive item text; the search term cust_item relates to customer item context exposed through MTL_CUSTOMER_ITEMS and the CUSTOMER_ID column.
• ORGANIZATION_ID, SUBINVENTORY, LOCATOR_ID, REVISION, LOT_NUMBER, SERIAL_NUMBER — inventory and lot/serial attribution.
• REQUESTED_QUANTITY, SHIPPED_QUANTITY, DELIVERED_QUANTITY, CANCELLED_QUANTITY, SRC_REQUESTED_QUANTITY — quantity tracking across the shipping lifecycle, with corresponding UOM columns.
• DATE_REQUESTED, DATE_SCHEDULED, LOAD_SEQ_NUMBER — scheduling and load sequencing data.
• SHIP_METHOD_CODE, CARRIER_ID, FREIGHT_TERMS_CODE, SHIPMENT_PRIORITY_CODE, FOB_CODE — shipping and freight attributes, several exposed with translated meanings.
• RELEASED_STATUS, MVT_STAT_STATUS, OE_INTERFACED_FLAG — status and processing indicators.

Common Use Cases and Queries

Typical scenarios include order-to-shipment reconciliation, delivery backlog reporting, and preparing data for carrier or WMS interfaces. The following query lists open delivery details for a given organization, including translated ship method:

• SELECT delivery_detail_id, source_code, source_line_id, item_description, requested_quantity, shipped_quantity, ship_method_code, released_status FROM apps.wshbv_delivery_details WHERE organization_id = :org_id AND released_status NOT IN ('Y','C');
• SELECT d.delivery_detail_id, d.cust_po_number, d.customer_id, d.item_description, d.date_scheduled FROM apps.wshbv_delivery_details d WHERE d.date_scheduled BETWEEN :start_date AND :end_date ORDER BY d.date_scheduled;
• SELECT d.delivery_detail_id, d.source_line_id, d.lot_number, d.serial_number, d.subinventory, d.locator_id FROM apps.wshbv_delivery_details d WHERE d.source_code = 'OE';

Because the view is one of the primary reporting interfaces for shipping execution, it should be treated as read-only and joined carefully on DELIVERY_DETAIL_ID and SOURCE_LINE_ID to avoid row multiplication.