Search Results serial_transaction_id




Overview
Explore in AI Chat

Overview

APPS.WSH_PICK_LOT_V is a lightweight Oracle E-Business Suite view that exposes lot-level picking transaction data sourced from the material transaction lot numbers table. It is delivered under the APPS schema and is defined in the Shipping (WSH) product family, where it supports visibility into which lots were picked against shipping and move-order driven transactions. The view does not introduce new storage or business logic of its own; it is a thin projection over existing transactional data, renaming a small number of columns and injecting a literal status value.

The view is most relevant to reporting, integration, and diagnostics that require the association between a base transaction identifier, its serial transaction identifier, and the lot number involved. Because it is a simple view with no filtering predicate in its projection, it returns the full contents of the underlying table as defined, with no WHERE clause restricting rows by organization, date, or transaction type.

Underlying Base Objects

The documented source for the view is a single base object:

  • MTL_TRANSACTION_LOT_NUMBERS — referenced as a synonym. This table records the lot and serial number detail associated with material transactions in Oracle Inventory, and it is the only documented underlying object for WSH_PICK_LOT_V.

Because the view is defined over this single table without joins, it inherits the row granularity of MTL_TRANSACTION_LOT_NUMBERS: one row per lot/serial detail record attached to a transaction. The view therefore carries no existence or completeness guarantees beyond what is stored in that table, and any lot-level picking data not captured there will not appear in the view.

Key Columns

The documented view text exposes the following columns:

  • LOT_TXN_ID — aliased from TRANSACTION_ID. This is the transaction identifier for the lot transaction record, used to correlate back to the parent material transaction.
  • SERIAL_TRANSACTION_ID — the serial transaction identifier, which links the lot detail to the corresponding serial number transaction. This is the column most frequently sought by users searching the term "serial_transaction_id".
  • LOT_NUMBER — the lot number associated with the transaction detail. This identifies the specific lot that was picked or moved.
  • PICK_STATUS — a literal value, always 'PICKED', supplied by the view definition itself rather than derived from the base table.

Note that because PICK_STATUS is a constant, it conveys no genuine status information. Consumers requiring true pick confirmation status must join to the relevant transaction or shipping tables rather than relying on this column.

Common Use Cases and Queries

The primary use case is joining lot-level pick detail to serial transaction data and to the broader transaction table to reconstruct lot and serial movement. A representative query follows:

  • SELECT lot_txn_id, serial_transaction_id, lot_number FROM apps.wsh_pick_lot_v WHERE lot_number = :lot;
  • SELECT lot_txn_id, serial_transaction_id, lot_number FROM apps.wsh_pick_lot_v WHERE serial_transaction_id = :serial_txn_id;
  • SELECT v.lot_txn_id, v.serial_transaction_id, v.lot_number, t.transaction_type_name FROM apps.wsh_pick_lot_v v, apps.mtl_transaction_types t WHERE v.lot_txn_id = t.transaction_type_id;

Typical scenarios include tracing which lots were associated with a given serial transaction, validating lot/serial detail during shipping reconciliation, and building ad hoc extracts for inventory-to-shipping audits. Because the view exposes a constant PICK_STATUS and no filtering, implementers generally treat it as a convenience projection and add their own predicates and joins to reach organization, item, and transaction context. For high-volume reporting, querying MTL_TRANSACTION_LOT_NUMBERS directly may be preferable to avoid the extra view layer.