Search Results pick_slip_number




Overview
Explore in AI Chat

Overview

The WSH_SRS_PICK_SLIP_V view is a Shipping Execution (WSH) database object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented status is VALID. The view presents a consolidated, de-duplicated list of pick slip numbers that exist across the material transaction and move order request data model. Rather than storing data itself, the view is a UNION-based query that surfaces the PICK_SLIP_NUMBER attribute from three independent base objects, returning a single column of distinct pick slip identifiers.

Users searching for "skp july slip" are most likely attempting to locate pick slip records associated with a specific pick slip number or a particular transaction period. Because the view exposes only the pick slip number — not the transaction date or organization — it functions primarily as a lookup or validation construct rather than a full reporting source. In EBS reporting and integration contexts, it is typically used to confirm that a given pick slip number exists somewhere in the shipping supply chain before joining to transactional detail tables.

Underlying Base Objects

The ETRM 12.2.2 metadata documents the following referenced base objects, each accessed through a public synonym in the APPS schema:

  • MTL_MATERIAL_TRANSACTIONS_TEMP (synonym) — staging area for pending material transactions. The view selects positive-quantity rows, i.e. transactions with NVL(TRANSACTION_QUANTITY,0) > 0.
  • MTL_MATERIAL_TRANSACTIONS (synonym) — the completed transaction ledger. The view selects negative-quantity rows (< 0), with an index hint on the M alias, representing issues or reversals tied to a pick slip.
  • MTL_TXN_REQUEST_LINES (synonym) — move order request lines. The view selects any row with a non-null pick slip number, using an index hint on the R alias, which covers move order driven picks that have not yet been transacted.

The three result sets are combined with UNION, which both merges the columns and eliminates duplicate pick slip numbers, producing the consolidated list. This design reflects the fact that pick slip numbers are generated and referenced at several points in the shipping lifecycle: at move order release, during pending staging transactions, and at final transaction posting.

Key Columns

The view exposes a single documented column:

  • PICK_SLIP_NUMBER — the alphanumeric identifier assigned to a pick slip. This is the value used on the printed pick slip document and as the linkage key across shipping tables. In the view it appears once per distinct value because of the UNION set operation.

Because only this column is projected, no quantity, date, organization, or item attributes are available directly from the view. Any such detail must be obtained by joining back to the base tables.

Common Use Cases and Queries

A typical use is confirming that a pick slip number exists before further processing, for example validating a July pick slip reference supplied by a user or inbound interface. A representative query would select the pick slip numbers matching a pattern:

  • SELECT PICK_SLIP_NUMBER FROM APPS.WSH_SRS_PICK_SLIP_V WHERE PICK_SLIP_NUMBER LIKE 'JUL%';
  • SELECT DISTINCT PICK_SLIP_NUMBER FROM APPS.WSH_SRS_PICK_SLIP_V ORDER BY PICK_SLIP_NUMBER;

The view is also used as a driver set when reconciling pick slips against delivered or invoiced shipments, and as a lightweight existence filter in integration programs that must determine whether a pick slip originated from move order release, staging, or posted transactions. Because the base objects are large transaction tables, queries should always restrict PICK_SLIP_NUMBER rather than performing unrestricted full scans.