Search Results oebv_shipment_lines

Overview

The OEBV_SHIPMENT_LINES view is a read-only reporting object within the Oracle E-Business Suite Order Entry (OE) module. It presents shipment-level detail for sales order lines, combining scheduling, reservation, shipping, and container attributes into a single denormalized projection intended for reporting, inquiry, and downstream integration use. In the 12.1.1 and 12.2.2 releases, the view is defined with the WITH READ ONLY clause, confirming that it is not exposed for insert, update, or delete operations through the view itself. The ETRM metadata notes the object as "Not implemented in this database," meaning its presence depends on the specific instance configuration; where instantiated, the OE schema owns it.

The view serves the classic EBS reporting pattern of hiding code-to-meaning translation behind pseudo-columns prefixed with _LA: (lookup attributes) and _DF: (descriptive flexfield), allowing Report Builder, OBIEE, and custom SQL to surface user-facing labels without repetitive lookup joins.

Underlying Base Objects

The view is defined over two documented base tables joined on LINE_ID:

• SO_LINE_DETAILS DETAIL — supplies shipment detail attributes such as quantity, unit of measure, scheduling dates, subinventory, delivery and departure identifiers, and the container item references.
• SO_LINES_ALL LINE — supplies line-level attributes including ship-to site use, ship-to contact, and terms.

The join condition is DETAIL.LINE_ID = LINE.LINE_ID. No additional base objects are documented in the ETRM extract. The aliases DETAIL and LINE are preserved in the select list and drive the output column naming.

Key Columns

• QUANTITY_SHIPPED and UOM_CODE — shipped quantity and its unit of measure.
• MASTER_CONTAINER_ITEM_ID and DETAIL_CONTAINER_ITEM_ID — the master and detail container item identifiers, central to packing and container shipment configurations. The user search term "master_container_item_id" maps directly to this column.
• INVENTORY_ITEM_ID, CUSTOMER_ITEM_ID, WAREHOUSE_ID, SUBINVENTORY — item and stocking location context.
• SHIPMENT_LINE_ID and SALES_ORDER_LINE_ID — primary and foreign keys linking back to detail and line records.
• DELIVERY_ID and DEPARTURE_ID — delivery and departure references used in shipping execution.
• SCHEDULED_DATE and LATEST_ACCEPTABLE_DATE — scheduling constraints.
• _LA:* columns — lookup-derived meanings for REQUIRED_FOR_REVENUE_FLAG, SCHEDULE_STATUS_CODE, INCLUDED_ITEM_FLAG, SHIPPABLE_FLAG, TRANSACTABLE_FLAG, RESERVABALE_FLAG, SHIPMENT_PRIORITY_CODE, SHIP_METHOD_CODE, and DEMAND_CLASS_CODE.
• _DF — the SO_LINE_DETAILS descriptive flexfield context value.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard WHO audit columns.

Common Use Cases and Queries

Typical uses include shipment reporting, container/inventory reconciliation, and integration extracts. Example: retrieve container shipments for a sales order.

SELECT MASTER_CONTAINER_ITEM_ID,
       DETAIL_CONTAINER_ITEM_ID,
       QUANTITY_SHIPPED,
       UOM_CODE,
       SUBINVENTORY
FROM   OEBV_SHIPMENT_LINES
WHERE  SALES_ORDER_LINE_ID = :p_line_id;

Another common pattern filters by shippable or reservable status using the lookup columns, or joins INVENTORY_ITEM_ID to MTL_SYSTEM_ITEMS_B for descriptions. Because the view is read-only and unindexed itself, queries filtering on SALES_ORDER_LINE_ID or DELIVERY_ID perform best when the underlying base tables carry appropriate indexes.