I've re-examined the code in v7:
- the quantities are computed for the date specified on the inventory ("to_date=inv.date")
- the moves are written at the date the inventory is confirmed ("now").
So the behavior is indeed not consistent and buggy, so I'm confirming again.
According to Quentin's comments, I think the consistent solution for the standard would be to :
- compute the quantities up to now
- keep the stock moves up dated "now".
Quentin do you agree please ?
This would of course impose real-time inventory management in OpenERP, which is impossible for some businesses like Hugh Turner emphasized.
I've re-examined the code in v7: inv.date" )
- the quantities are computed for the date specified on the inventory ("to_date=
- the moves are written at the date the inventory is confirmed ("now").
So the behavior is indeed not consistent and buggy, so I'm confirming again.
According to Quentin's comments, I think the consistent solution for the standard would be to :
- compute the quantities up to now
- keep the stock moves up dated "now".
Quentin do you agree please ?
This would of course impose real-time inventory management in OpenERP, which is impossible for some businesses like Hugh Turner emphasized.