Search Results so_picking_line_details

Overview

The SO_PICKING_LINE_DETAILS table is a core transactional data object within the Oracle E-Business Suite (EBS) Order Entry (OE) module. It serves as a detailed sub-ledger for the picking and shipping execution process. For each individual picking line (SO_PICKING_LINES_ALL), this table stores granular records that track the allocation of specific inventory serial or lot numbers to fulfill an order line. Its primary role is to maintain a precise audit trail of which specific inventory items were selected, packed into which container, and assigned to which delivery and departure, thereby linking order fulfillment directly to warehouse operations and shipment planning.

Key Information Stored

The table's structure is designed to capture the detailed breakdown of a picked quantity. Its primary key, PICKING_LINE_DETAIL_ID, uniquely identifies each detail record. The most critical columns are the foreign keys that establish its operational context. The PICKING_LINE_ID links the detail to its parent picking instruction. The LOT_NUMBER and SERIAL_NUMBER columns (common in such tables, though not explicitly listed in the brief metadata) would identify the specific inventory units picked. As per the documented foreign keys, CONTAINER_ID, DELIVERY_ID, and DEPARTURE_ID are essential for tracking the item's progression through the shipping stages, connecting it to the Oracle Shipping Execution (WSH) module. Other typical columns would include the detailed QUANTITY and references to subinventory and locator.

Common Use Cases and Queries

This table is central to queries about shipment composition, lot/serial traceability, and packing verification. A common use case is generating a packing slip that lists the specific serial numbers included in a shipment. Another is tracing a recalled lot number to determine which customer orders and shipments it fulfilled. For reporting, one might join this table to delivery and order lines to analyze picking accuracy or fulfillment lead times. A typical SQL pattern involves joining to the parent picking line and order line to get a complete view:

• SELECT oel.line_number, spld.lot_number, spld.serial_number, spld.container_id FROM oe.so_picking_line_details spld JOIN oe.so_picking_lines_all spl ON spld.picking_line_id = spl.picking_line_id JOIN oe.order_lines_all oel ON spl.line_id = oel.line_id WHERE oel.header_id = :p_order_header_id;

Related Objects

SO_PICKING_LINE_DETAILS is a nexus table with defined relationships to several key EBS entities. Its primary parent is SO_PICKING_LINES_ALL, linked via PICKING_LINE_ID. It is a critical child table of the Shipping Execution module, linking to WSH_PACKED_CONTAINERS (via CONTAINER_ID), WSH_DELIVERIES (via DELIVERY_ID), and WSH_DEPARTURES (via DEPARTURE_ID). Furthermore, it acts as a parent table itself; the documented foreign key shows that SO_FREIGHT_CHARGES references SO_PICKING_LINE_DETAILS.PICKING_LINE_DETAIL_ID, indicating that freight costs can be assessed at this granular level of detail. This web of relationships underscores its integral position in the order-to-ship lifecycle.