Search Results so_picking_batches_all




Overview
Explore in AI Chat

Overview

The SO_PICKING_BATCHES_ALL table is a core data repository within the Oracle E-Business Suite Order Entry (OE) module. It serves as the master table for storing records of released order batches, which are logical groupings of sales orders created during the Order-to-Cash cycle to facilitate coordinated picking and shipping activities. This table is central to the batch picking and release functionality, enabling warehouse operations to process multiple orders as a single unit for efficiency. As an "ALL" table, it is a multi-organization structure, storing data for all operating units accessible to a responsibility, with data segregation managed via the ORG_ID column.

Key Information Stored

The table's primary identifier is the BATCH_ID, which is enforced by the SO_PICKING_BATCHES_PK primary key. A unique key (SO_PICKING_BATCHES_UK1) also exists on the NAME column, ensuring batch names are unique. The table's structure is defined by its critical foreign key relationships, which link the batch to other essential entities in the supply chain. Key columns include BATCH_ID, NAME, and foreign keys such as DELIVERY_ID (linking to WSH_DELIVERIES), DEPARTURE_ID (linking to WSH_DEPARTURES), and PICK_SLIP_RULE_ID (linking to WSH_PICK_SLIP_RULES). It also maintains references to the originating sales order (HEADER_ID in SO_HEADERS_ALL), customer (CUSTOMER_ID in RA_CUSTOMERS), ship-to site (SITE_USE_ID in RA_SITE_USES_ALL), order type (ORDER_TYPE_ID), and a grouping identifier (GROUP_ID in SO_ITEM_GROUPS).

Common Use Cases and Queries

This table is primarily queried for operational reporting, process tracking, and data validation in shipping and fulfillment. Common scenarios include tracking the status of all picking batches for a specific warehouse, identifying batches associated with a particular delivery, or auditing batch creation over a date range. A typical query might join with shipping tables to list batch details:

  • SELECT spb.name AS batch_name, spb.batch_id, wd.delivery_id FROM oe.so_picking_batches_all spb, wsh_deliveries wd WHERE spb.delivery_id = wd.delivery_id AND spb.org_id = :p_org_id;

Another common use case involves troubleshooting the release process by examining batches that have not been successfully converted into deliveries or pick slips. Analysts may also run queries to reconcile the number of lines or orders contained within a batch against the source sales orders.

Related Objects

SO_PICKING_BATCHES_ALL has extensive relationships with key tables across the Order Management and Shipping Execution modules. As per the metadata, it is a parent to SO_PICKING_HEADERS_ALL via the BATCH_ID foreign key. It is a child to numerous critical tables, including:

  • WSH_DEPARTURES and WSH_DELIVERIES (Shipping Execution)
  • WSH_PICK_SLIP_RULES and WSH_RELEASE_SEQ_RULES (Release Rules)
  • RA_CUSTOMERS and RA_SITE_USES_ALL (Trading Community Architecture)
  • SO_HEADERS_ALL and SO_ORDER_TYPES_115_ALL (Order Management)
  • SO_ITEM_GROUPS (Order Management grouping)

This network of relationships underscores the table's role as a pivotal junction between the order release, warehouse picking, and outbound shipping processes.