Thanks for your good explanation.
You are right according to comment #3 both have the same behavior but in current system both way have not same behavior becasue we need to set the stock move of procurement order field as a "one2many" instead of "many2one".Because procurement order should check all the stock moves according to split.Right now it is not possbile because stock move field is "many2one".
According your scenario after spliting 2 move generated.
-> First Case
[1] for qty = 70/done
[2] for qty= 130/available
-> Second Case
[1] for qty = 70/available
[2] for qty= 130/done
so in the stock move of procurement order always set the move for qty=70 becasue it is the first move.According to Second case it's work perfect becasue move is "available" state for qty=70.In the First case move is "done" for qty=70 so procurement come in "done" state.
Currently its not feasible because Its many affects.So currently setting this bug as wishlist.
Hello Patrick,
Thanks for your good explanation.
You are right according to comment #3 both have the same behavior but in current system both way have not same behavior becasue we need to set the stock move of procurement order field as a "one2many" instead of "many2one".Because procurement order should check all the stock moves according to split.Right now it is not possbile because stock move field is "many2one".
According your scenario after spliting 2 move generated.
-> First Case
[1] for qty = 70/done
[2] for qty= 130/available
-> Second Case
[1] for qty = 70/available
[2] for qty= 130/done
so in the stock move of procurement order always set the move for qty=70 becasue it is the first move.According to Second case it's work perfect becasue move is "available" state for qty=70.In the First case move is "done" for qty=70 so procurement come in "done" state.
Currently its not feasible because Its many affects.So currently setting this bug as wishlist.
Thanks.