Decimalization Occuring On Pick Releases (12.1 and above)
Last updated on MAY 04, 2017
Applies to:Oracle Warehouse Management - Version 12.2.3 and later
Information in this document applies to any platform.
On : 12.1.3 version, Pick Release Process
We are seeing a recurring issue where if a pick release occurs for any item more than a certain amount then the system splits the line into 2 decimalized pick tasks. This seems to be related to the UNIT of MEASURE (UOM) conversion for boxes/pallets/crate and happens when the request is to pick over that quantity or if the pick release has to split the line between multiple locations.
Expect that quantities will be split in 2, non-decimalized pick tasks.
The issue can be reproduced at will with the following steps:
1. I create a sales order and include an item that had a UoM conversion saved against it.
2. I then place the order for more than 1 box quantity worth of units (say a box qty was 36, if i place the order for 60 units the issue will occur).
3. I then book the order and resolve any issues that might prevent pick release.
4. I then release the sales order using OM>Shipping>Release Sales Orders>Release Sales Orders. I can select to auto pick confirm or not, the issue happens either way.
When the pick release is complete, the quantity has been split in to two lines, both are decimalized.
The issue has the following business impact:
Issue is affecting many areas of our R12 testing. Shipping, Order Management, Finance and Inter-company are all affected by this and it is preventing us from moving forward with the testing. This happens every time more than a box quantity is ordered. It doe snot happen on small quantities. In order to correct the issue we have been going in to the related pick release and changing the required quantities to full quantities. This does allow picking but is not a solution to the issue. The decimalization prevents auto pick release from occurring as fractional picking is not allowed. In telnet we are able to load but not drop the pick quantity if left as a decimal. You can then no longer do anything with the order. Adding the extra steps to resolve the decimalization is not an acceptable way round this issue as on inter-company orders we often have hundreds of lines which would make this totally unworkable.
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