Search Results wsh_picking_details_interface




Overview
Explore in AI Chat

Overview

WSH_PICKING_DETAILS_INTERFACE is a VALID database view owned by the APPS schema in Oracle E-Business Suite, associated with the Order Entry (OE) product family. It exposes the picking detail interface structure used to communicate pick confirmations and shipment transactions into the shipping execution and inventory transaction pipeline. The view presents a flattened, integration-oriented projection of picking line detail data, joining interface records in MTL_TRANSACTIONS_INTERFACE with sales order and picking entities so that downstream processes can validate, error-report, and post inventory transactions.

The view is particularly relevant to interface and conversion developers because it carries the full flexfield segment breakdowns for both items and locators. The search term loc_segment20 corresponds directly to the LOC_SEGMENT20 column exposed by this view, which surfaces the twentieth segment of the inventory locator (stock locator) key flexfield. Organizations that have configured a deeply structured locator flexfield rely on these segment columns to identify the exact storage location without a separate join to MTL_ITEM_LOCATIONS.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, the view resolves over the following base objects through APPS synonyms:

  • MTL_TRANSACTIONS_INTERFACE (SYNONYM) — the primary interface table supplying transaction, item, lot, revision, locator, and attribute columns.
  • SO_PICKING_LINE_DETAILS (SYNONYM) — source of picking line detail identification and quantity information.
  • SO_PICKING_LINES_ALL (SYNONYM) — header-level picking line data.
  • SO_HEADERS_ALL (SYNONYM) — sales order header context.
  • SO_LINES_ALL (SYNONYM) — sales order line context.
  • SO_ORDER_TYPES_ALL (SYNONYM) — order type classification used in transaction processing.

As reflected in the view text, the principal driving table is MTL_TRANSACTIONS_INTERFACE (aliased MTI), from which the majority of columns are projected with aliasing to present a picking-oriented interface shape.

Key Columns

Common Use Cases and Queries

Typical use cases include reconciling pending pick interface records, diagnosing errors from the transaction worker, and validating locator segment population before posting. A representative query isolating the locator segment columns is:

  • SELECT transaction_id, inventory_item, loc_segment1, loc_segment20, locator_name, shipped_quantity, process_flag, error_explanation FROM wsh_picking_details_interface WHERE process_flag = 1;

To identify records failing because of locator data, filter on error conditions while projecting the relevant segment:

  • SELECT transaction_id, locator_id, loc_segment20, error_code, error_explanation FROM wsh_picking_details_interface WHERE error_code IS NOT NULL;

These queries support operational troubleshooting and pre-conversion validation of interface data before it is consumed by the shipping and inventory transaction managers.