INVTOTRX - Serial Numbers Chosen when Creating Move Orders Get Replaced at Allocate Step

(Doc ID 1563778.1)

Last updated on DECEMBER 19, 2017

Applies to:

Oracle Inventory Management - Version 12.1.3 and later
Information in this document applies to any platform.
Form: INVTOMAI.fmb - Transact Move Orders
Form: INVTOTRX.fmb - Move Orders (Create Move Orders)
Form: INVSDOIO.fmb - Define Organization Parameters


When allocating Requisition move orders in Transact Move Orders form (INVTOTRX), the serial number(s) entered by the user in the lines tab of the Create Move Orders form (INVTOMAI) is (are) ignored. The system is allocating other serial number(s).

-- Expectation
Expect the system to automatically allocate the serial numbers chosen by the user in Create Move Orders form.

-- Steps
The issue can be replicated at will per the below steps:
1. Create a one line Requisition move order with Transaction Type=Move Order Transfer
In Lines tab, enter one line for a serial controlled item with Quantity=1
In Source tab:
Enter the Subinventory
Press TAB key
Enter a serial number in "Serial From" and "Serial To" fields

2. Get the move order approved.

3. Go to Transact Move Orders form
Query the above move order

In Transact Move Orders window:
Check the Select check box
Click Allocate
Allocations field is now showing 'Single'
Click View/Update Allocations

In Transact Move Order Line Allocations window:
Click Lot/Serial

In Serial Entry window:
See the serial number shown in "Start Serial Number" and "End Serial Number" fields is different than the one chosen when creating the move order. That one got ignored.

-- Workaround
Override the serial numbers allocated by the system manually. (in Transact Move Orders form)

-- Business impact
Due to this issue, inaccurate serial numbers are getting moved by users which is leading to the inability to operate properly.
When allocating and transacting, users may not notice that the allocated serial number is different from the chosen one. Hence they may not apply the workaround.
Moreover the workaround is introducing an additional delay (manual step) in the processing.


 The problem started to occur after upgrading from to 12.1.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms