Search Results date_last_printed

Overview

SO_PICKING_BATCHES is a reporting and inquiry view owned by the APPS schema in Oracle E-Business Suite, defined within the Order Entry (OE) product family. It exposes picking batch header and selection criteria information used by the Oracle Order Management picking and shipping process, commonly referred to as Pick Release. A picking batch represents a logical grouping of order lines that are released for picking against a warehouse and a set of filter criteria such as requested dates, ship method, shipment priority, and inventory item.

The view is registered in EBS Release 12.1.1 and 12.2.2 with a status of VALID. Its principal purpose is to present picking batch data in a Multi-Org secured manner, since it filters on ORG_ID using the CLIENT_INFO environment value rather than exposing all operating units simultaneously. This makes it suitable for forms, concurrent programs, reports, and custom integrations that must respect the session's current organization context.

Underlying Base Objects

SO_PICKING_BATCHES is a view defined over a single documented base object, the synonym SO_PICKING_BATCHES_ALL. The view text performs a straight projection of all columns from the underlying synonym, augmented by a WHERE clause that restricts rows to the current operating unit. The predicate derives ORG_ID from the session's CLIENT_INFO value using USERENV and SUBSTRB, comparing it against the ORG_ID column in the base object, with -99 used as the fallback when no organization is set.

Because the view is defined against the _ALL synonym, it retains the multi-org partitioning behavior of the underlying table while presenting only the rows relevant to the logged-in organization. The view does not join to any additional tables; all descriptive and transactional attributes originate from the base object itself.

Key Columns

• BATCH_ID — Primary identifier for the picking batch.
• NAME — User-visible or system-generated batch name.
• ORG_ID — Operating unit that owns the batch; drives the view's security predicate.
• WAREHOUSE_ID, SUBINVENTORY — Target warehouse and subinventory for the pick.
• BACKORDERS_ONLY_FLAG, PRINT_FLAG, EXISTING_RSVS_ONLY_FLAG — Selection and processing flags controlling batch behavior.
• SHIPMENT_PRIORITY_CODE, SHIP_METHOD_CODE, ORDER_TYPE_ID — Filter criteria used to select order lines.
• CUSTOMER_ID, SITE_USE_ID — Customer and ship-to site criteria.
• INVENTORY_ITEM_ID, ORDER_LINE_ID, HEADER_ID, SHIP_SET_NUMBER — Order line and shipment grouping references.
• DATE_REQUESTED_FROM/TO, SCHEDULED_SHIPMENT_DATE_FROM/TO — Date range criteria for line selection.
• DATE_RELEASED, DATE_CONFIRMED, DATE_COMPLETED, DATE_LAST_PRINTED — Lifecycle timestamps tracking release, confirmation, completion, and printing.
• PARTIAL_ALLOWED_FLAG, INCLUDE_PLANNED_LINES, PICK_SLIP_RULE_ID, RELEASE_SEQ_RULE_ID — Controls governing partial picks, planned lines, and rule assignment.
• DEPARTURE_ID, DELIVERY_ID — Links to outbound delivery and departure grouping.
• CONTEXT and ATTRIBUTE1–15 — Descriptive flexfield storage.
• CREATION_DATE, CREATED_BY, REQUEST_ID, PROGRAM_ID — Standard WHO and concurrent program audit columns.

Common Use Cases and Queries

Typical usage includes monitoring pick release activity, identifying batches pending print or confirmation, auditing batch criteria, and building custom shipping dashboards or integrations. A common query retrieves batches for the current organization with their status:

• SELECT batch_id, name, warehouse_id, subinventory, date_released, date_confirmed, date_completed FROM so_picking_batches WHERE date_completed IS NULL ORDER BY creation_date DESC;
• SELECT batch_id, name, shipment_priority_code, ship_method_code, date_requested_from, date_requested_to FROM so_picking_batches WHERE warehouse_id = :warehouse_id;
• SELECT batch_id, name, backorders_only_flag, existing_rsvs_only_flag, print_flag FROM so_picking_batches WHERE org_id = :org_id AND date_last_printed IS NULL;

Because the view enforces organization security automatically, queries issued from within an EBS session return only batches for the active operating unit, eliminating the need for explicit ORG_ID filtering in most reporting scenarios.