Cross Project Transaction Created during Subinventory Transfer Without Project/Task
Last updated on AUGUST 21, 2016
Applies to:Oracle Warehouse Management - Version 18.104.22.168 to 12.1.3 [Release 11.5.10 to 12.1]
Information in this document applies to any platform.
On : 22.214.171.124 and 12.1 version, Materials Management
We have noticed that subinventory transfer transactions cause cross project costings.
This is happening when a subinventory transfer is done for a non-serialized item (in which case a project number needs to be entered during the transaction) and then followed by a subinventory transfer for a serialized item.
System should not perform project transfer
The issue can be reproduced at will with the following steps:
1. Navigate in MSCA to Warehousing\Inventory\Transfers\Sub Transfer
Enter transfer for non-serialized item. Note that the project and task are amongst the fields to enter.
Now perform transfer for serial controlled item
Enter Item, revision and serial no (note that Project and task as well as subinventory and locator are being retrieved automatically). Project = <value>; task = <value>.
Enter quantity and to sub and locator.
Now check the material transactions:
The subinventory & locator and Transfer Subinventory & locator look okay. The correct project and task are being displayed.
However when you check the project/task and To Project/Task in the 'Transaction ID' tab these are not correct for the second transaction. The project number of the 1st is being cached and this is taken over in the second transaction
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