I'm reopening this bug for two reasons:
First, the proposed solution was pushed only to v6.1 but not to v6.0, 7.0 or trunk
Second the proposed solution is wrong: the inventory-related stock moves are first created with the wrong date, and then tinkered but any automatic processing (chained move, accounting entry...) is made with the wrong date.
A clean solution is to pass the date as a context entry, and change stock.move.action_done() to take that date instead of the current date.
I'm reopening this bug for two reasons:
First, the proposed solution was pushed only to v6.1 but not to v6.0, 7.0 or trunk
Second the proposed solution is wrong: the inventory-related stock moves are first created with the wrong date, and then tinkered but any automatic processing (chained move, accounting entry...) is made with the wrong date.
A clean solution is to pass the date as a context entry, and change stock.move. action_ done() to take that date instead of the current date.
Lionel Sausin.