Search Results earliest_ship_date




Overview
Explore in AI Chat

Overview

The OE_DELIVERY_LINES_V view is a shipping interface construct in Oracle E-Business Suite Order Management (ONT). It presents order line and shipment detail in a flattened form intended to feed downstream shipping execution and departure planning processes. The view exposes a single row per order line shipment combination, joining header-level context from OE_ORDER_HEADERS_ALL with line-level attributes from OE_ORDER_LINES_ALL, and enriching item information from MTL_SYSTEM_ITEMS and container data from MTL_CUSTOMER_ITEMS. The description states its purpose precisely: it is for interfacing the lines to shipping, for departure planning.

Because it consolidates scheduling, freight, address, quantity, and container attributes into one projection, OE_DELIVERY_LINES_V is frequently used as a reporting source for transportation planning, load building, and shipment prioritization. It is not a transactional table; it is a read-only projection over the live order tables, so its contents always reflect the current state of the underlying order lines.

For users searching on "earliest_ship_date," it is important to note that this view does not expose a column named EARLIEST_SHIP_DATE. The closest scheduling attribute available from the view is SCHEDULE_SHIP_DATE, which represents the currently scheduled ship date for the line shipment. The earliest ship date concept is typically derived from schedule or requested-date logic in other scheduling views and tables, and is not a native column of this view.

Underlying Base Objects

The view is owned by APPS and is defined over the following documented objects:

The joins are keyed on the order header and line identifiers, with item and container enrichment layered on top, producing the denormalized projection required by shipping integration.

Key Columns

The LINE_NUMBER column is noteworthy because it is not a raw column. It concatenates LINE_NUMBER, SHIPMENT_NUMBER, and, where present, OPTION_NUMBER, COMPONENT_NUMBER, and SERVICE_NUMBER using conditional DECODE logic to build a fully qualified line reference. Other significant columns include:

Common Use Cases and Queries

The view supports departure planning reports, shipping interface extracts, and freight prioritization queries. A representative query returning scheduled shipments by order follows:

SELECT ORDER_NUMBER, LINE_NUMBER, SCHEDULE_SHIP_DATE, ORDERED_QUANTITY, SHIPPING_METHOD_CODE
FROM APPS.OE_DELIVERY_LINES_V
WHERE ORG_ID = :p_org_id
AND SCHEDULE_SHIP_DATE BETWEEN :p_from_date AND :p_to_date
ORDER BY SCHEDULE_SHIP_DATE, ORDER_NUMBER;

To identify lines awaiting shipping interface, filter on the interface flag:

SELECT ORDER_NUMBER, LINE_NUMBER, DEP_PLAN_REQUIRED_FLAG, SHIPPING_INTERFACED_FLAG
FROM APPS.OE_DELIVERY_LINES_V
WHERE SHIPPING_INTERFACED_FLAG = 'N';

When a user requires the earliest ship date, the practical approach is to query SCHEDULE_SHIP_DATE from this view or to consult scheduling-specific views that expose earliest acceptable date logic, since OE_DELIVERY_LINES_V itself exposes only the scheduled ship date for the line shipment.