products in MTO are not the only one concerned by this. Any stock.move with the move_dest_id column filled in will trigger the filling of move_history_ids when the action_done method is called. This means that if there are any chained moves in the processing of a shippment, it will not be possible to process returns in the final outgoing move.
Examples of configurations generating this situation:
* if a stock.location has a chained location with a chaining type different from "automatic"
* if the stock_location addon is used to configure push or pull flows
* mrp also generates moves with move_dest_id set
I'm changing the title of the bug report to reflect this.
Additional information:
products in MTO are not the only one concerned by this. Any stock.move with the move_dest_id column filled in will trigger the filling of move_history_ids when the action_done method is called. This means that if there are any chained moves in the processing of a shippment, it will not be possible to process returns in the final outgoing move.
Examples of configurations generating this situation:
* if a stock.location has a chained location with a chaining type different from "automatic"
* if the stock_location addon is used to configure push or pull flows
* mrp also generates moves with move_dest_id set
I'm changing the title of the bug report to reflect this.