Yes, because this wizard set the return move like parent of origin move, but it must be child of origin move, or not? Then int all file you must use move_history_ids instead of move_history_ids2.
Imagine that your origin move have parents, who aren't returns, this wizard checks all parents moves then the sum of parents quantity doesn't represent the consumes or returns quantity, this quantity is represented by children moves.
Hi Vinay,
Yes, because this wizard set the return move like parent of origin move, but it must be child of origin move, or not? Then int all file you must use move_history_ids instead of move_history_ids2.
Imagine that your origin move have parents, who aren't returns, this wizard checks all parents moves then the sum of parents quantity doesn't represent the consumes or returns quantity, this quantity is represented by children moves.
Test it, thanks