Since changeset 4d228a081908 we no longer set the effective date of a move when it is assigned. However, currently we still check if there’s an assigned move in a period before we allow to close it:
http://hg.tryton.org/modules/stock/file/tip/period.py#l126
I’m thinking that maybe the check is not correct. I see several possibilities but maybe this is the one that convinces me the most:
Check for any move that is not in ‘done’ or ‘cancel’ state and has effective_date set to a date within the period to be closed. If there’s one, we raise a warning (not an error) and let the user decide if she still wants to close the period.
Opinions?