Search Results item_primary_uom_code

Overview

WSH_PICK_SLIP_V is a shipping execution view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It consolidates pick slip line information by combining three distinct sources: temporary material transactions, completed material transactions, and move order transaction request lines. The view presents a unified, normalized picture of pick slip activity across unpicked, picked, and move-order-driven states, exposing subinventory and locator information for both the source (FROM) and destination (TO) sides of a move.

Its principal reporting role is to provide a single query point for pick slip detail without requiring report authors to union the underlying tables manually. Because it spans temporary staging rows and finalized transaction rows, it is commonly used for integration and reconciliation, particularly where the orchestration of material movement between subinventories must be tracked. Users searching on TRANSFER_SUBINVENTORY are typically interested in the destination subinventory for a pick-driven transfer, which the view surfaces through the TO_SUBINVENTORY column.

Underlying Base Objects

The view is defined over three documented base objects, each referenced as a synonym from APPS:

• MTL_MATERIAL_TRANSACTIONS_TEMP — supplies rows where pick slip transactions are staged but not yet finalized. These contribute an 'UNPICKED' LINE_STATUS and are filtered on PICK_SLIP_NUMBER IS NOT NULL and an absolute transaction quantity greater than zero.
• MTL_MATERIAL_TRANSACTIONS — supplies finalized pick transactions, filtered on PICK_SLIP_NUMBER IS NOT NULL and a negative transaction quantity, and flagged with a 'PICKED' LINE_STATUS.
• MTL_TXN_REQUEST_LINES — supplies move order lines associated with pick slips, also flagged 'PICKED', with a NULL transaction identifier since no inventory transaction has yet been posted.

The three branches are combined with UNION ALL, preserving row identity and producing a LINE_STATUS discriminator that distinguishes staged from completed movement.

Key Columns

• FROM_SUBINVENTORY / FROM_LOCATOR_ID — originating subinventory and locator for the pick.
• TO_SUBINVENTORY / TO_LOCATOR_ID — destination subinventory and locator, derived from TRANSFER_SUBINVENTORY and TRANSFER_TO_LOCATION (or TRANSFER_LOCATOR_ID) in the transaction tables, and from TO_SUBINVENTORY_CODE / TO_LOCATOR_ID in move order lines.
• PRIMARY_QTY — absolute primary quantity moved, exposed as PRIMARY_QTY (or PRIMARY_QUANTITY in the move order branch).
• PICK_SLIP_NUMBER — the linkage key across all three sources and the mandatory filter for every branch.
• DETAILING_DATE — creation date for unpicked rows, transaction date for transactions, and pick slip date for move orders.
• MOVE_ORDER_LINE_ID — the move order line driving the pick.
• LINE_STATUS — either 'UNPICKED' or 'PICKED', indicating the stage of the pick.
• TRANSACTION_ID — transaction identifier, or TO_NUMBER(NULL) for move order lines.
• ITEM_PRIMARY_UOM_CODE, SECONDARY_QUANTITY, SECONDARY_UOM_CODE — unit of measure and secondary quantity attributes.

Common Use Cases and Queries

Typical scenarios include open pick slip reporting, reconciliation of staged versus posted picks, and transfer subinventory analysis for move orders and staging moves.

SELECT PICK_SLIP_NUMBER, FROM_SUBINVENTORY, TO_SUBINVENTORY,
       PRIMARY_QTY, LINE_STATUS, DETAILING_DATE
FROM   APPS.WSH_PICK_SLIP_V
WHERE  PICK_SLIP_NUMBER = :pick_slip_number;

To isolate transfers into a specific destination subinventory, filter on TRANSFER_SUBINVENTORY-derived output:

SELECT PICK_SLIP_NUMBER, FROM_SUBINVENTORY, TO_SUBINVENTORY,
       PRIMARY_QTY, LINE_STATUS
FROM   APPS.WSH_PICK_SLIP_V
WHERE  TO_SUBINVENTORY = :transfer_subinventory
AND    LINE_STATUS = 'PICKED';

Reconciliation between unpicked and picked activity for a given move order line can be achieved by grouping on MOVE_ORDER_LINE_ID and LINE_STATUS.