By Toddac-Oracle on Jan 07, 2016
In a normal Inventory transaction, the rounding is taken care of immediately, so rounding does not usually cause confusion. If for example, you entered a quantity .000006 in a Miscellaneous Receipt, then the system will round the quantity to .00001. The system rounds using the "ROUND" function to 5 decimals. As a result, 1 through 4 will round down and 5 thru 9 will round up. If for example we try to receive .000004, this would round down to 0 which is not a valid transaction quantity and would raise an error.
Here is an example in Inventory where the application rounds down. The user had entered the Quantity of .000004 (six decimal places) and received the following message:
Here is an example where the system rounds down to 0 and raises an error:
In WIP, the examples can be more complicated. The WIP forms often will help the user avoid issues. For example, you would not be able to issue .000004 because it would round to 0 in inventory. The WIP Completion and Issue forms should stop the user from entering this quantity. The user though could enter .000005 and greater as this rounds up to .00001, not zero. If we build a job for .000006. We assemble the job and look at the Inventory transactions. In Inventory, we see the assembly quantity .000006 rounded to .00001.
Would you like to see this changed? You have the power by voting in the long standing Idea (Enhancement Request) where you can discuss and vote on an enhancement: https://community.oracle.com/ideas/2485.
Rounding is something you may want to be aware of in EBS. You can find more information in documents:
Inventory and Work in Process Round Decimal Quantities Differently (Doc ID 793356.1)
What is the Restriction of Decimal Precision for Receiving Forms in 11.5.10 and R12? (Doc ID 736699.1)