Search Results so_line_details

Overview

The SO_LINE_DETAILS table is a core data object within the Oracle E-Business Suite (EBS) Order Entry (OE) module, specifically in versions 12.1.1 and 12.2.2. It serves as the primary repository for order line schedule details, which are the discrete, schedulable units of an order line. While the SO_LINES_ALL table defines the ordered item and quantity, the SO_LINE_DETAILS table manages the breakdown of that quantity into individual shipments or fulfillments over time. Each record represents a specific schedule for a portion of the line quantity, including its requested and scheduled ship dates, quantities, and fulfillment status. This table is fundamental to the order promising, shipping, and fulfillment processes, enabling complex order management scenarios like partial shipments and back-to-back orders.

Key Information Stored

The table's primary key is the unique identifier LINE_DETAIL_ID. Its most critical column is LINE_ID, which is a foreign key to the SO_LINES_ALL table, linking each schedule detail to its parent order line. Other essential columns typically include REQUESTED_QUANTITY, SCHEDULED_QUANTITY, REQUESTED_SHIP_DATE, and SCHEDULED_SHIP_DATE, which define the fulfillment plan. Status tracking is managed through columns like OPEN_FLAG and CANCELLED_FLAG. Crucially, the table holds foreign keys for integration with other modules: DELIVERY_ID links to WSH_DELIVERIES in Shipping Execution, and COMPONENT_SEQUENCE_ID links to BOM structures (BOM_INVENTORY_COMPONENTS, BOM_BILL_OF_MATERIALs) for configured items, supporting pick-to-order and assemble-to-order flows.

Common Use Cases and Queries

A primary use case is generating a shipment schedule report for a specific order. A typical query would join SO_LINE_DETAILS to SO_LINES_ALL and OE_ORDER_HEADERS_ALL to list all schedule lines, their quantities, and dates. Another common scenario is identifying open, schedulable details for order promising or pick release, often filtered by OPEN_FLAG='Y' and a future SCHEDULED_SHIP_DATE. For back-to-back orders, queries often join SO_LINE_DETAILS to purchase order lines via the OE_LINK_LINES interface table. A sample pattern to find details awaiting shipment for a given order number is:

• SELECT h.order_number, l.line_number, d.scheduled_ship_date, d.requested_quantity FROM oe_order_headers_all h, so_lines_all l, so_line_details d WHERE h.header_id = l.header_id AND l.line_id = d.line_id AND d.open_flag = 'Y' AND h.order_number = :p_order_num ORDER BY d.scheduled_ship_date;

Related Objects

SO_LINE_DETAILS is centrally connected to several key EBS tables, as documented by its foreign key constraints. Its primary relationship is with the SO_LINES_ALL table via the LINE_ID column, establishing the parent-child link to the order line. For shipping execution, it relates to WSH_DELIVERIES (DELIVERY_ID) and WSH_DEPARTURES (SO_LINE_DETAILS_DEPARTURE_ID). For products with configurations, it integrates with the Bills of Material module through BOM_INVENTORY_COMPONENTS and BOM_BILL_OF_MATERIALS using the COMPONENT_SEQUENCE_ID. These relationships are critical for processes like pick slip generation, shipment confirmation, and component requirement planning.