Comment 6 for bug 915481

Revision history for this message
Amit Parik (amit-parik) wrote :

Hello Dmitrijs,

I have clearly analysed this issue, But I think all are working correct as per the behaviour.

Now, I explain you the current behaviour of 6.1 trunk according to your scenario.

First Ravish was described you the SO to PO cycle and your behaviour for MO to PO. There is no difference in SO to PO or MO to PO scenario for created PO because the main thing is, here we have consider the quantity of PO. So that doesn't matter the PO created from SO or MO.

Yes, you are right. We are used a arithmetic rounding for this (Product UoM 's rounding precision as well as for all rounding).

You can see that we have used different value for rounding precision field for different 'Product UoM Category' like for kg and gm we have used 0.010 and for PC we have used 1.00 value. Because for unit type of categories, I don't think the product 's quantity going in to decimal value. As well as this field is changeable, So we can change this easily as per our requirement.

According to your scenario, If you want the PO for 1.111 PC quantity then you have to change your product UoM's rounding precision as 0.001 then and then only it will satisfied your scenario.

I have attached a video for this whcih is described the solution of your configuration as well as described that we have used different rounding precision for different product UoM category.

Now comes your another two problem.

#Ceiling Rounding..

You have suggested that we have to use 'Ceiling Rounding' instead of 'Arithmetic Rounding'. Below some example of Ceiling Rounding.
'Ceiling(0.00) = 0
'Ceiling(0.10) = 1
'Ceiling(0.20) = 1
.
.
'Ceiling(0.90) = 1
'Ceiling(1.00) = 1
'Ceiling(1.10) = 2

But As per my 'Opinion' the 'Arithmetic Rounding' is proper for this because we have used everywhere this same rounding functionality. But may be your suggestion is good because If we used a Ceiling Rounding then always satisfied our required product.

#Why used "Rounding Precision" in "Product UoM"?

Ans:- Currently quantity rounding is consider based on Rounding Precision field of "Product UoM" object because different UoM have different rounding as I described above. If our product UoM id PCS then there is no possibility that our product goes into decimal quantity, I mean it never possible If I Purchase or Sale 1.12 or 1.5 PCS in real scenario.

If our product UoM is in KG or Liter then it's possible, that's why we have consider different 'Rounding Precision' for different UoM.

So as per my "Opinion' this place is better for satisfy the quantity rounding that's why current behaviour is good.

Finally it's not a bug rather than your suggestion that's why I am setting it as a "Wishlist"

For last two point I am consider it as an "Opinion" because mainly for Ceiling Rounding point we need a more discussion then and then only we can look this issue on future.

@Experts: Would you please share your views on this.

Thanks and more suggestions are welcomed!