Search Results wshbv_picking_batch

Overview

WSHBV_PICKING_BATCH is an Oracle E-Business Suite view owned by the APPS schema and classified under the Oracle Order Entry (OE) product family. It is documented as VALID and carries the note "- Retrofitted," indicating that it was introduced or re-pointed to preserve backward compatibility for pre-existing customizations, reports, or integrations that referenced the earlier object name after a form or table restructuring. The view presents picking batch header information — the grouping construct used by Oracle Shipping Execution to collect eligible delivery lines into a batch that will be released for picking, and ultimately drive pick slip generation.

Functionally, the view is a reporting and integration surface rather than a transactional entity. It exposes the attribute set maintained by the picking batch definition process, including release criteria, filter criteria, organizational context, and audit columns. Because the underlying table is an _ALL table with an ORG_ID column, the view is multi-org aware and returns data across operating units unless the caller restricts it. The alias mapping for the RELEASED_DATE column is of particular interest to consumers who search on that term: the view does not expose a column literally named RELEASED_DATE in the base table; instead, the column DATE_RELEASED is projected and aliased as RELEASED_DATE. This aliasing is the primary reason the view is referenced in queries using the "released_date" identifier.

Underlying Base Objects

The view is defined over a single documented base object, SO_PICKING_BATCHES_ALL, which is present in the APPS schema as a synonym. There are no joins, unions, or aggregates; the definition is a straightforward column projection, with one rename applied. Because it reads from the _ALL table directly, the view inherits row-level operating unit partitioning and any row-level security applied at the table level through the MO (Multi-Org) views or security profiles.

No filters are applied in the view text, so the view returns all batch rows visible to the querying user's organization context. This is significant for reporting: unfiltered queries against WSHBV_PICKING_BATCH can return batches from multiple operating units, and explicit ORG_ID predicates should be applied where operating-unit isolation is required.

Key Columns

• PICKING_BATCH_ID — Surrogate primary key of the batch, projected from BATCH_ID.
• NAME — User-defined batch name used for identification on shipping and picking windows.
• RELEASED_DATE — Projection and rename of DATE_RELEASED; records the timestamp at which the batch was released for picking. This is the column most frequently searched by users referencing "released_date."
• DATE_REQUESTED_FROM / DATE_REQUESTED_TO — Requested-date range filter captured when the batch was defined.
• SCHEDULED_SHIPMENT_DATE_FROM / SCHEDULED_SHIPMENT_DATE_TO — Scheduled shipment date range criteria.
• ORDER_TYPE_ID, CUSTOMER_ID, SITE_USE_ID, HEADER_ID — Order and customer selection criteria applied to the batch.
• INVENTORY_ITEM_ID, WAREHOUSE_ID, SUBINVENTORY — Item and inventory-organization scoping.
• SHIPMENT_PRIORITY_CODE, SHIP_METHOD_CODE, SHIP_SET_NUMBER — Shipping attribute filters.
• BACKORDERS_ONLY_FLAG, EXISTING_RSVS_ONLY_FLAG, PARTIAL_ALLOWED_FLAG, INCLUDE_PLANNED_LINES — Boolean process controls governing which lines are eligible.
• PICK_SLIP_RULE_ID, RELEASE_SEQ_RULE_ID — References to the picking and release sequence rules applied.
• ORG_ID — Operating unit identifier.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID.

Common Use Cases and Queries

The view is typically used to audit batch release activity, to reconcile batches against delivery and trip data, and to supply batch attributes to downstream reports or interfaces. A representative query identifying batches released within a period is:

SELECT picking_batch_id, name, released_date, warehouse_id, org_id FROM apps.wshbv_picking_batch WHERE released_date BETWEEN :p_from AND :p_to AND org_id = :p_org_id ORDER BY released_date;

Because there is no status column, release state must be inferred — a non-null RELEASED_DATE indicates the batch was released. A companion query for unreleased batches uses WHERE released_date IS NULL. Joining to WSH_DELIVERY_ASSIGNMENTS or the delivery tables on batch context supports reconciliation of released batches to actual deliveries, while joining on PICK_SLIP_RULE_ID to the shipping rule tables supports rule-usage analysis.