Search Results picker_name

Overview

WSHFV_PICK_HEADER is a reporting view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 associated with the Oracle Order Entry (OE) module. It presents picking header information drawn from the shipping and order entry tables, exposing a denormalized, human-readable snapshot of pick confirmation and packing activity within the warehouse. The view joins picking header records to delivery, batch, order, organization, ship-to, and person reference data, resolving surrogate identifiers into descriptive attributes such as batch name, order number, organization code, ship-to location, and picker/packer display names.

The ETRM metadata classifies this object as "Retrofitted" and notes that it is "Not implemented in this database," meaning that in the documented instance the view was not created. Nevertheless, the retired view text is preserved and provides the authoritative definition. Because it exposes the sometimes-elusive MIDDLE_NAMES attribute of person records, WSHFV_PICK_HEADER is frequently encountered in searches relating to middle name data, as the concatenated PICKER_NAME and PACKER_NAME columns incorporate it.

Underlying Base Objects

The view is defined over the following base tables using outer joins (denoted by the (+) operator):

• SO_PICKING_HEADERS_ALL SPH — the driving picking header table.
• WSH_DELIVERIES WDL — joined on DELIVERY_ID to supply the delivery name.
• SO_PICKING_BATCHES SPB — joined on BATCH_ID to supply the batch name.
• SO_HEADERS_ALL SH — joined on ORDER_HEADER_ID to supply the order number.
• MTL_PARAMETERS ORG — joined on WAREHOUSE_ID to supply the organization code.
• RA_SITE_USES SU — joined on SHIP_TO_SITE_USE_ID to supply the ship-to location.
• PER_PEOPLE_X FU1 and FU2 — joined on PICKED_BY_ID and PACKED_BY_ID respectively to supply picker and packer names.
• HR_ORGANIZATION_UNITS HOU — joined on ORG_ID to supply the operating unit name.

The ETRM 12.2.2 metadata documents no referenced base objects, but the preserved view text identifies the joined tables listed above. All joins except the primary picking header source are outer joins, so header rows are returned even where related descriptive data is absent.

Key Columns

The view exposes the picking header primary key and audit columns, plus numerous descriptive attributes:

• PICKING_HEADER_ID — unique identifier of the picking header record.
• BATCH_ID / BATCH_NAME — the picking batch and its descriptive name.
• ORDER_HEADER_ID / ORDER_NUMBER — the originating sales order header and number.
• WAREHOUSE_ID / ORGANIZATION_CODE — the warehouse organization and its code.
• SHIP_TO_SITE_USE_ID / SHIP_TO — the ship-to site use and resolved location.
• STATUS_CODE — the picking header status.
• PICKED_BY_ID / PICKER_NAME — the picker identifier and a 50-character concatenation of last name, middle names, and first name.
• PACKED_BY_ID / PACKER_NAME — the packer identifier and corresponding concatenated name.
• DATE_RELEASED, DATE_SHIPPED, DATE_CONFIRMED — released, shipped, and confirmed dates.
• DELIVERY_ID / DELIVERY_NAME — the delivery and its name.
• ORG_ID / ORG_NAME — the operating unit and its name.

The PICKER_NAME and PACKER_NAME columns are constructed with SUBSTR(... LAST_NAME || ', ' || MIDDLE_NAMES || ' ' || FIRST_NAME, 1, 50), which is why middle name data is embedded within this view.

Common Use Cases and Queries

This view is used primarily for operational reporting and integration that requires readable picking, packing, and shipping detail without performing multi-table joins manually.

A representative query retrieving picking activity with names and order context:

• SELECT ORDER_NUMBER, ORGANIZATION_CODE, BATCH_NAME, PICKER_NAME, PACKER_NAME, DATE_SHIPPED FROM WSHFV_PICK_HEADER WHERE STATUS_CODE IS NOT NULL ORDER BY DATE_SHIPPED DESC;

Another common scenario filters by warehouse and date range to produce a picking manifest:

• SELECT PICKING_HEADER_ID, ORDER_NUMBER, ORGANIZATION_CODE, SHIP_TO, BATCH_NAME, CONFIRMED_DATE FROM WSHFV_PICK_HEADER WHERE ORGANIZATION_CODE = :warehouse AND CONFIRMED_DATE BETWEEN :start_date AND :end_date;

Because the view resolves PICKER_NAME and PACKER_NAME from PER_PEOPLE_X, it is also referenced when reporting the personnel responsible for picking and packing, including their middle names as concatenated within the display name.