I found that https://idempiere.atlassian.net/browse/IDEMPIERE-1530 is covering over receipt to handle corrupted qtyOrdered. But similar case is qtyResereved. Should we make same implementation for qtyReserved based on overReceipt field?
Also I noticed that reservedQty is updated in loop for LineMA, If we move this out of this loop and make one update per shipment line, it will save some sql query cost in worst case scenario.
Please advise, can I proceed to make those changes?
If over shipment make wrong update of QtyReserved then yes, we should fix it.
Preferably every commit is keep as simple as possible, i.e it is best to split bug fixing and optimization into 2 separate commit. Will make peer review a lot easier.
Hengsin,
I found that https://idempiere.atlassian.net/browse/IDEMPIERE-1530 is covering over receipt to handle corrupted qtyOrdered. But similar case is qtyResereved. Should we make same implementation for qtyReserved based on overReceipt field?
Also I noticed that reservedQty is updated in loop for LineMA, If we move this out of this loop and make one update per shipment line, it will save some sql query cost in worst case scenario.
Please advise, can I proceed to make those changes?
With Regards,
Deepak Pansheriya