CallOutOrder make a mistake of calculating LineNetAmt,When updata enterQty at detail panel using UOM conversion.
Description
Hi,All. I am Hideaki Hagiwara in Japan.
For Example
1.'Elm Tree' that is Product of GardenWorld is setting UOM Conversion.(image1.jpg) 2.Create Sales Order.and create Order Line. 3.updata enterQty at detail panel. mistake of calculating LineNetAmt(image2.jpg). 4.Of courese, CallOutOrder is calculating correctly at Single Row Layout and Grid Layout.mistak a detail panel only.
Hi Calros. Thank you for your patch quickly. I checked your patch. I think it's good.
But please check again only one sentence.
CalloutOrder.java - amt method Line:1039
int M_PriceList_ID = Env.getContextAsInt(ctx, WindowNo, mTab.getTabNo(), "M_PriceList_ID");
I think that this sentence is not need to modify. I think that sentence below is better. int M_PriceList_ID = Env.getContextAsInt(ctx, WindowNo, "M_PriceList_ID");
Carlos Ruiz
February 18, 2015 at 10:18 PM
Attaching a patch for community test purposes - this fixes the issue on sales order, but it's concerning the same issue must be found in many callouts and maybe it's worthy to check always for tabno in the Env.getContext in any callout.
Carlos Ruiz
February 18, 2015 at 10:10 PM
raised priority as it's allowing to write a data corrupted record - 2 six-pack = 2
Hi,All.
I am Hideaki Hagiwara in Japan.
For Example
1.'Elm Tree' that is Product of GardenWorld is setting UOM Conversion.(image1.jpg)
2.Create Sales Order.and create Order Line.
3.updata enterQty at detail panel. mistake of calculating LineNetAmt(image2.jpg).
4.Of courese, CallOutOrder is calculating correctly at Single Row Layout and Grid Layout.mistak a detail panel only.
May be related:
IDEMPIERE-2255: Lookup not working on Tab level, wrong context parsing, MLookup not fully implementedClosed
IDEMPIERE-2471: I can't select UOM at detail record tab, in spite of setting UOM conversion. Closed
I'm sorry for my poor English.