Search Results jai_om_oe_bond_trxs




Overview
Explore in AI Chat

Overview

The SO_PICKING_HEADERS_ALL table is a core transactional data object within the Oracle E-Business Suite Order Entry (OE) module, specifically for releases 12.1.1 and 12.2.2. It serves as the header-level record for batch picking operations. Batch picking is a warehouse fulfillment process where order lines from multiple sales orders are grouped together for efficient picking and packing. This table acts as the parent entity, grouping individual picking lines (SO_PICKING_LINES_ALL) under a single picking header for a specific batch, order, and delivery. Its primary role is to track the lifecycle and assignment of a consolidated picking task, linking the sales order management process with subsequent shipping execution.

Key Information Stored

The table's primary key is PICKING_HEADER_ID, which uniquely identifies each picking header record. As indicated by the foreign key relationships, other critical columns establish essential links to related business entities. The BATCH_ID links the header to its parent SO_PICKING_BATCHES_ALL. The ORDER_HEADER_ID provides the direct connection to the original sales order in SO_HEADERS_ALL. For logistics, the SHIP_TO_SITE_USE_ID (linked to RA_SITE_USES_ALL) defines the delivery location, and the DELIVERY_ID (linked to WSH_DELIVERIES) integrates the picking task with the Shipping Execution module. The table also tracks personnel responsible for the task via PICKED_BY_ID and PACKED_BY_ID, both referencing FND_USER. Standard Oracle EBS columns for audit, multi-org structure (ORG_ID), and control are also present.

Common Use Cases and Queries

A primary use case is generating reports on picking batch status and productivity. For instance, a query can join SO_PICKING_HEADERS_ALL with SO_PICKING_BATCHES_ALL and FND_USER to list all picking headers in a 'Released' batch, showing the assigned picker. Another common scenario is tracing the fulfillment progress of a specific sales order by joining SO_HEADERS_ALL to this table via ORDER_HEADER_ID. Technical support often queries this table to diagnose issues where order lines are not progressing to shipping, checking for missing delivery assignments or incomplete picking tasks. A sample query pattern is:

  • SELECT ph.picking_header_id, ph.batch_id, oh.order_number, ph.delivery_id, u_pick.user_name picked_by FROM so_picking_headers_all ph JOIN so_headers_all oh ON ph.order_header_id = oh.header_id LEFT JOIN fnd_user u_pick ON ph.picked_by_id = u_pick.user_id WHERE ph.batch_id = :batch_id;

Related Objects

SO_PICKING_HEADERS_ALL is central to a network of related tables. It is a child of SO_PICKING_BATCHES_ALL (via BATCH_ID) and SO_HEADERS_ALL (via ORDER_HEADER_ID). Its primary child is SO_PICKING_LINES_ALL, which holds the detailed line items to be picked. Critical integrations exist with Shipping (WSH_DELIVERIES), Customer Locations (RA_SITE_USES_ALL), and User Management (FND_USER). As per the documented foreign keys, it is also referenced by several objects for extended functionality, including SO_FREIGHT_CHARGES for freight calculation, and the JAI (Oracle India Localization) tables JAI_OM_OE_BOND_TRXS, JAI_OM_OE_GEN_TAXINV_T, and JAI_OM_WSH_LINES_ALL for tax and regulatory compliance.