Search Results serial_txn_temp_id
Overview
APPS.WSH_PICK_SERIAL_TEMP_V is an internal Oracle E-Business Suite view owned by the APPS schema, with FND design data registered under the WSH (Shipping Execution) product. The view is documented as VALID and is classified as an "Internal" view type. It exposes a narrow projection of serial number data used during the picking and pick-confirmation flow in Oracle Shipping Execution, presenting temporary serial capture records together with the vendor serial number and the current pick status of each record.
Because the object is flagged "Oracle Internal Use Only," Oracle Corporation does not support direct access to it except through standard Oracle Applications programs. Its principal role is therefore not as a public reporting interface, but as a supporting view consumed by Shipping Execution logic that stages serialized material movements before they are confirmed. The most frequently searched column, SERIAL_TXN_TEMP_ID, is the sole numeric key surfaced by the view and identifies the temporary serial transaction record being processed.
Underlying Base Objects
The documented metadata states that APPS.WSH_PICK_SERIAL_TEMP_V references MTL_SERIAL_NUMBERS_TEMP, resolved through a SYNONYM. MTL_SERIAL_NUMBERS_TEMP is the Inventory temporary serial number table used to hold serial numbers that have been entered but not yet committed to the permanent serial number tables. The view is a simple, read-oriented projection over that single base object: it selects the transaction identifier, the vendor-supplied serial value, and a status flag.
Documentation confirms that WSH_PICK_SERIAL_TEMP_V is not referenced by any other database object. It sits at the top of the dependency tree, meaning changes to MTL_SERIAL_NUMBERS_TEMP — columns, datatypes, or validation — flow directly into the view with no intermediate layer. This also means the view cannot be relied upon as a stable interface across patches, since the underlying temporary table is itself an internal structure.
Key Columns
- SERIAL_TXN_TEMP_ID (NUMBER) — The primary identifier exposed by the view. It corresponds to the temporary serial transaction row, allowing a given staged serial record to be joined back to its originating picking or transaction context. Users searching for "serial_txn_temp_id" are typically attempting to correlate this identifier with the pick transaction that produced it.
- VENDOR_SERIAL_NUMBER (VARCHAR2, 30) — The serial number value as supplied, typically the external or vendor-provided serial string captured during receiving or inspection. A 30-character limit applies.
- PICK_STATUS (CHAR) — A single-character status indicator describing the pick state of the temporary serial record, allowing consumers to distinguish records that are pending, selected, or already processed within the picking flow.
No mandatory columns are documented, and no additional descriptive columns such as inventory item, organization, or lot are surfaced. Any enrichment of these records must be obtained by joining back to the base temporary table or to other Shipping Execution and Inventory objects using SERIAL_TXN_TEMP_ID.
Common Use Cases and Queries
Typical use is diagnostic: confirming which temporary serial records exist for a picking cycle, verifying that a vendor serial number was captured correctly, and tracking whether a staged serial has progressed past picking. Because the view is internal, production code should not depend on it, and any query should be treated as read-only troubleshooting.
Listing all staged serials with their status:
SELECT serial_txn_temp_id, vendor_serial_number, pick_status FROM apps.wsh_pick_serial_temp_v;
Locating a specific temporary transaction by identifier:
SELECT serial_txn_temp_id, vendor_serial_number, pick_status FROM apps.wsh_pick_serial_temp_v WHERE serial_txn_temp_id = :temp_id;
Finding records by vendor serial value, which is useful when a user reports a duplicate or missing serial during pick confirmation:
SELECT serial_txn_temp_id, pick_status FROM apps.wsh_pick_serial_temp_v WHERE vendor_serial_number = :serial_number;
Because the view exposes only three columns and is built over a temporary table, results are transient and reflect only uncommitted staging data. For historical or audited serialized movement reporting, the permanent inventory and shipping tables should be queried instead.
-
VIEW: APPS.WSH_PICK_SERIAL_TEMP_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:WSH.WSH_PICK_SERIAL_TEMP_V, object_name:WSH_PICK_SERIAL_TEMP_V, status:VALID,
-
View: WSH_PICK_SERIAL_TEMP_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:WSH.WSH_PICK_SERIAL_TEMP_V, object_name:WSH_PICK_SERIAL_TEMP_V, status:VALID, product: WSH - Shipping Execution , implementation_dba_data: APPS.WSH_PICK_SERIAL_TEMP_V ,
-
View: WSH_PICK_SERIAL_TEMP_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:WSH.WSH_PICK_SERIAL_TEMP_V, object_name:WSH_PICK_SERIAL_TEMP_V, status:VALID, product: WSH - Shipping Execution , implementation_dba_data: APPS.WSH_PICK_SERIAL_TEMP_V ,
-
VIEW: APPS.WSH_PICK_SERIAL_TEMP_V
12.1.1
-
VIEW: APPS.WSH_PICK_SERIAL_TEMP_V
12.2.2
-
VIEW: APPS.WSH_PICK_SERIAL_TEMP_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:WSH.WSH_PICK_SERIAL_TEMP_V, object_name:WSH_PICK_SERIAL_TEMP_V, status:VALID,
-
PACKAGE: APPS.INV_TRANSFER_ORDER_PVT
12.1.1
-
PACKAGE: APPS.INV_TRANSFER_ORDER_PVT
12.2.2
-
APPS.INV_TXN_MANAGER_PUB SQL Statements
12.1.1
-
APPS.INV_TXN_MANAGER_PUB SQL Statements
12.2.2
-
APPS.INV_TXN_MANAGER_PUB dependencies on MTL_TRANSACTION_LOTS_INTERFACE
12.2.2
-
APPS.INV_TXN_MANAGER_PUB dependencies on MTL_TRANSACTION_LOTS_INTERFACE
12.1.1
-
PACKAGE BODY: APPS.INV_TXN_MANAGER_PUB
12.1.1
-
PACKAGE BODY: APPS.INV_TXN_MANAGER_PUB
12.2.2
-
APPS.INV_TXN_MANAGER_GRP SQL Statements
12.1.1
-
APPS.INV_TXN_MANAGER_GRP SQL Statements
12.2.2
-
PACKAGE BODY: APPS.INV_TXN_MANAGER_GRP
12.1.1
-
PACKAGE BODY: APPS.INV_TXN_MANAGER_GRP
12.2.2
-
PACKAGE BODY: APPS.INV_TRANSFER_ORDER_PVT
12.1.1
-
PACKAGE BODY: APPS.INV_TRANSFER_ORDER_PVT
12.2.2
-
eTRM - WSH Tables and Views
12.2.2
description: Stores hierarchy for zones. Each region component of a zone has a record in this table. ,
-
eTRM - WSH Tables and Views
12.1.1
description: Stores hierarchy for zones. Each region component of a zone has a record in this table. ,