Search Results so_picking_batches_view_v

Overview

SO_PICKING_BATCHES_VIEW_V is a reporting view in the Oracle E-Business Suite Order Entry (OE) module that consolidates picking, batch, shipping, and ship-to address information into a single denormalized result set. In release 12.1.1 and 12.2.2 this view serves as a convenient read-only interface for pick-slip confirmation and shipping reports, decoupling report logic from the underlying normalized picking schema. The ETRM metadata records the object with an implementation note of "Not implemented in this database," indicating it was delivered as a seeded view definition rather than as a physical object instantiated in every environment; consumers must verify its presence before relying on it.

Its principal value lies in joining picking header, batch, pick-slip, warehouse, customer, and address data so that a single query yields the batch name, completion status, warehouse code, ship-to party, and formatted shipping address. The DATE_RELEASED column, sourced from SO_PICKING_HEADERS, is frequently the target of user searches because it represents the moment a picking header was released to the warehouse floor.

Underlying Base Objects

The view is defined over multiple base tables joined through outer and inner joins. The core driving table is SO_PICKING_HEADERS (aliased SPH), which is joined to SO_PICKING_LINES (SPL) and SO_PICKING_LINE_DETAILS (SPLD) via PICKING_HEADER_ID and PICKING_LINE_ID respectively. The batch context is supplied by SO_PICKING_BATCHES (PB) through an outer join on BATCH_ID, and the originating order is referenced through SO_HEADERS (SH) on ORDER_HEADER_ID.

• SO_PICKING_HEADERS — primary source of DATE_RELEASED, DATE_SHIPPED, WAYBILL_NUM, SHIP_METHOD_CODE, WEIGHT, and NUMBER_OF_BOXES.
• SO_PICKING_BATCHES — supplies the BATCH name and DATE_COMPLETED used to derive COMPLETE_FLAG.
• SO_PICKING_LINES and SO_PICKING_LINE_DETAILS — provide PICK_SLIP_NUMBER.
• RA_SITE_USES, RA_ADDRESSES, RA_CUSTOMERS, RA_CONTACTS, RA_PHONES — outer-joined for ship-to location, address lines, customer name, contact, and primary phone.
• MTL_PARAMETERS — resolves WAREHOUSE_ID to ORGANIZATION_CODE.
• ORG_FREIGHT — outer-joined on the SO_ORGANIZATION_ID profile and ship method code.

Key Columns

ROW_ID uniquely identifies the picking header row. DATE_RELEASED records when the pick was released; DATE_SHIPPED records actual shipment. PICK_SLIP_NUMBER links the header to the printed pick slip, while BATCH carries the batch name and COMPLETE_FLAG (Y/N) reflects whether DATE_COMPLETED is populated. WAREHOUSE exposes the inventory organization code, and SHIP_TO, CUSTOMER_NAME, SHIP_ADDRESS1/2, SHIP_CONTACT, and SHIP_PHONE_ID present the destination in reporting-ready form. Audit columns CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY are carried from the header.

Common Use Cases and Queries

Typical uses include pick-release audits, batch completion tracking, and shipping manifests. To analyze release timing by batch and warehouse:

• SELECT batch, warehouse, pick_slip_number, date_released, date_shipped FROM so_picking_batches_view_v WHERE date_released >= :p_from_date ORDER BY date_released;
• SELECT batch, complete_flag, COUNT(*) FROM so_picking_batches_view_v GROUP BY batch, complete_flag;
• SELECT pick_slip_number, customer_name, ship_address1, ship_address2, ship_contact FROM so_picking_batches_view_v WHERE date_shipped IS NULL;

Because the view embeds outer joins with (+) syntax, queries filtering on optional columns such as BATCH or SHIP_TO should account for nulls. Performance is best when restricting on PICKING_HEADER_ID or DATE_RELEASED.