Search Results line_set_id




Overview
Explore in AI Chat

Overview

OE_DELIVERY_LINES_V is a reporting and integration view owned by the APPS schema in Oracle Order Management (ONT). Its documented purpose is to interface order lines to shipping for departure planning. In practice, the view flattens the shipment-level detail of sales order lines into a single denormalized row that downstream shipping, warehouse, and transportation processes can consume without navigating the parent-child hierarchy of OE_ORDER_LINES_ALL.

Because departure planning must resolve which lines are eligible to ship, from which warehouse, in what quantity, and by what date, the view exposes a broad projection of order, schedule, address, and container attributes. It also carries the SHIPPING_INTERFACED_FLAG and DEP_PLAN_REQUIRED_FLAG columns, which allow external planners and shipping execution programs to select only those lines that have not yet been handed off and which genuinely require departure planning.

The view exists in both Oracle EBS 12.1.1 and 12.2.2 and is documented as VALID in the ETRM repository. Note that the identifier line_set_id, which often prompts interest in shipment grouping logic, is not among the documented columns; related grouping semantics are represented instead through SHIP_SET_ID and ARRIVAL_SET_ID.

Underlying Base Objects

ETRM documents the following referenced objects for the 12.2.2 definition:

The view therefore sits directly on top of the order headers and lines tables, joining the transaction type and item master for descriptive enrichment, and joining customer items for container configuration.

Key Columns

The view concatenates the line, shipment, option, component, and service numbers into a composite LINE_NUMBER using dot delimiters, which uniquely identifies a shipment line within a model or kit configuration. This composite key is the single most important identifier for reporting because it visually encodes the ATO or PTO structure.

Common Use Cases and Queries

The most frequent use is a departure planning extract. A planner filters lines that still require planning and have not yet been interfaced, ordered by scheduled ship date.

SELECT order_number, line_number, description, ordered_quantity, schedule_ship_date
FROM oe_delivery_lines_v
WHERE dep_plan_required_flag = 'Y'
AND shipping_interfaced_flag = 'N'
AND org_id = :p_org_id
ORDER BY schedule_ship_date, order_number;

A second common pattern is shipment set analysis. Because the view exposes SHIP_SET_ID and ARRIVAL_SET_ID, planners can group lines that must ship together:

SELECT ship_set_id, order_number, line_number, ship_from_org_id, shipping_quantity
FROM oe_delivery_lines_v
WHERE ship_set_id IS NOT NULL
AND ship_to_org_id = :p_ship_to;

A third use is container and model interrogation, where MASTER_CONTAINER_ITEM_ID or TOP_MODEL_LINE_ID is joined back to MTL_SYSTEM_ITEMS to describe configured shipping units. Queries that filter on line_set_id will fail against this view; shipment grouping must instead be expressed through SHIP_SET_ID, ARRIVAL_SET_ID, or the composite LINE_NUMBER, which is the documented mechanism this view provides for line-level identification during shipping interface and departure planning.