Results for “so_picking_batches_all”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

SO_PICKING_BATCHES_ALL is an Order Entry (OE) table in Oracle E-Business Suite that stores released order batches generated during the pick-release process. It represents the header-level record of a picking batch — the grouping construct by which orders, order lines, or shipping sets are selected, released, and ultimately organized into pick slips and deliveries. Each row captures the release criteria, status dates, and organizational context used to define and track the batch through the warehouse execution lifecycle.

The table resides in the OE schema and is fully valid in both EBS 12.1.1 and 12.2.2. Its documented physical schema contains 61 columns. Based on the foreign key structure — which shows this table referencing multiple parent entities (customers, deliveries, pick slip rules, release sequence rules, headers) while being referenced by SO_PICKING_HEADERS_ALL — the heuristic Data Vault classification is satellite-leaning. As a modeling suggestion, this implies the table functions primarily as a descriptive attribute store for a central business key (the batch), extending data drawn from surrounding hubs and links rather than acting as an independent hub.

Key Information Stored

The surrogate primary key is BATCH_ID, enforced by the constraint SO_PICKING_BATCHES_PK. Two unique indexes define business-key candidates: SO_PICKING_BATCHES_U1 (BATCH_ID) and SO_PICKING_BATCHES_U2 (NAME). The NAME column therefore carries a natural uniqueness constraint, making it the principal user-facing batch identifier.

• BATCH_ID — Surrogate primary key uniquely identifying each released batch.
• NAME — Business-key batch name; uniquely constrained via SO_PICKING_BATCHES_U2.
• ORG_ID — Operating unit context for multi-org partitioning.
• CUSTOMER_ID / SITE_USE_ID — Customer and ship-to site defining release scope.
• HEADER_ID / ORDER_TYPE_ID / ORDER_LINE_ID — Order header, order type, and order line selection criteria.
• INVENTORY_ITEM_ID / GROUP_ID / SHIP_SET_NUMBER — Item, item group, and shipping set criteria.
• WAREHOUSE_ID / SUBINVENTORY — Warehouse and subinventory targeting the batch.
• DATE_RELEASED / DATE_UNRELEASED / DATE_CONFIRMED / DATE_COMPLETED — Lifecycle timestamps for release, unrelease, pick confirmation, and completion.
• DEPARTURE_ID / DELIVERY_ID — Links to WSH_DEPARTURES and WSH_DELIVERIES for carrier and delivery integration.
• PICK_SLIP_RULE_ID / RELEASE_SEQ_RULE_ID — Rule references governing pick slip generation and release sequencing.
• PRINT_FLAG / ERROR_REPORT_FLAG / BACKORDERS_ONLY_FLAG — Control and status indicators for batch processing.
• AUTOCREATE_DELIVERY_FLAG / PARTIAL_ALLOWED_FLAG / INCLUDE_PLANNED_LINES — Delivery and release behavior flags.

Common Use Cases and Queries

The principal use case is operational visibility into pick-release activity — identifying which batches were released, when, and under what criteria. Reporting typically joins the batch to its child pick headers and to the referenced order and delivery entities.

To list released batches for an operating unit:

• SELECT BATCH_ID, NAME, DATE_RELEASED, DATE_COMPLETED FROM SO_PICKING_BATCHES_ALL WHERE ORG_ID = :org_id ORDER BY DATE_RELEASED DESC;

To trace a batch to its pick headers and orders:

• SELECT b.NAME, h.PICKING_HEADER_ID, b.HEADER_ID FROM SO_PICKING_BATCHES_ALL b, SO_PICKING_HEADERS_ALL h WHERE h.BATCH_ID = b.BATCH_ID;

Additional scenarios include monitoring unreleased or stalled batches (DATE_RELEASED populated, DATE_UNRELEASED populated), auditing batch completion performance, and reconciling batches against delivery and departure records for shipping analysis.

Related Objects

The following objects are most significant to SO_PICKING_BATCHES_ALL, joined on the documented foreign key columns:

• SO_PICKING_HEADERS_ALL — Child table referencing BATCH_ID; holds individual pick headers belonging to a batch.
• SO_HEADERS_ALL — Order header referenced via HEADER_ID.
• WSH_DELIVERIES — Delivery referenced via DELIVERY_ID.
• WSH_DEPARTURES — Departure referenced via DEPARTURE_ID.
• WSH_PICK_SLIP_RULES — Pick slip rule referenced via PICK_SLIP_RULE_ID.
• WSH_RELEASE_SEQ_RULES — Release sequence rule referenced via RELEASE_SEQ_RULE_ID.
• RA_CUSTOMERS and RA_SITE_USES_ALL — Customer and site use referenced via CUSTOMER_ID and SITE_USE_ID.
• SO_ORDER_TYPES_115_ALL — Order type referenced via ORDER_TYPE_ID.
• SO_ITEM_GROUPS — Item group referenced via GROUP_ID.

These relationships position SO_PICKING_BATCHES_ALL at the intersection of order management and warehouse shipping execution, supporting both OE and WSH-integrated reporting.