Search Results pick_slip_number




Overview
Explore in AI Chat

Overview

APPS.WSH_SRS_PICK_SLIP_V is a lightweight Oracle EBS database view whose sole exposed column is PICK_SLIP_NUMBER. It provides a consolidated, de-duplicated list of pick slip numbers that exist across the three principal pick-slip-bearing transaction tables in Oracle Warehouse Management and Oracle Inventory. The view is defined as a three-way UNION (not UNION ALL) of pick slip numbers drawn from the temporary material transaction interface, the historical material transaction table, and the move-order (transaction request) line table. Because UNION strips duplicates, a given pick slip number appears at most once even when several transactions or request lines reference it.

Functionally, the view acts as a master pick slip number lookup — an existence list rather than a transactional detail source. It carries no quantities, item information, dates, or status codes; it answers only the question "does a pick slip number exist, and where can it be found?" Typical consumption patterns include value-set style validation, LOV population, integration reconciliation, and reporting filters that must restrict a query to valid pick slip numbers without joining all three transactional tables individually.

Underlying Base Objects

Per the documented view text, the view is defined over three synonyms:

  • MTL_MATERIAL_TRANSACTIONS_TEMP — the material transaction open interface table. Rows are contributed when PICK_SLIP_NUMBER is not null and NVL(TRANSACTION_QUANTITY,0) > 0, i.e. pending or unprocessed positively-quantified transactions.
  • MTL_MATERIAL_TRANSACTIONS — the posted transaction history table. The corresponding branch carries an INDEX(m) hint and selects rows where PICK_SLIP_NUMBER is not null and NVL(TRANSACTION_QUANTITY,0) < 0, capturing completed issue-type transactions.
  • MTL_TXN_REQUEST_LINES — the move order line table, accessed with an INDEX(r) hint, contributing pick slip numbers from move order lines regardless of quantity sign.

Because the referenced objects are synonyms owned by APPS, the view resolves to the underlying base tables through standard EBS synonym chains. The UNION set operator enforces distinctness across all three sources.

Key Columns

The view projects a single column:

  • PICK_SLIP_NUMBER — the pick slip identifier assigned during picking, corresponding to the PICK_SLIP_NUMBER column that exists on each of the three base objects. It is the only column available for selection, filtering, joining, or sorting from this view.

No trailing or system columns are exposed. Consequently, all filtering must be performed on PICK_SLIP_NUMBER itself; attributes such as organization, item, quantity, transaction date, or transaction type must be retrieved by joining back to the originating base tables.

Common Use Cases and Queries

The most frequent usage is existence validation or LOV enumeration for the pick slip number field:

  • Validating a user-entered or integrated pick slip number before processing returns, corrections, or reconciliations.
  • Populating a pick slip selection list in a custom concurrent program or OAF/Forms page.
  • Reconciling pick slip numbers referenced in external systems or interfaces against those known to EBS.
  • Constraining a detail report to only pick slips that actually exist in transaction or move order data.

Illustrative queries:

  • SELECT pick_slip_number FROM apps.wsh_srs_pick_slip_v WHERE pick_slip_number = :p_pick_slip;
  • SELECT pick_slip_number FROM apps.wsh_srs_pick_slip_v ORDER BY pick_slip_number;
  • Join back to history for detail: SELECT m.transaction_id, m.inventory_item_id, m.transaction_quantity FROM mtl_material_transactions m WHERE m.pick_slip_number IN (SELECT pick_slip_number FROM apps.wsh_srs_pick_slip_v);

Because each branch of the union may scan large transactional tables, queries against this view should always be bound by a specific PICK_SLIP_NUMBER predicate whenever possible, and appropriate indexes on the base tables should be verified.