A fix for this bug (rev 7253) has been committed for 6.1 back-ported from 7.0
[MERGE] OPW 577110: stock.move: only auto-validate next move if there are no other pending upstream moves Backport of 7.0 fix at revision 8023 [email protected] ** Changed in: openobject-addons Status: Expired => Fix Released -- You received this bug notification because you are a member of OpenERP Indian Team, which is subscribed to OpenERP Addons. https://bugs.launchpad.net/bugs/1160927 Title: [6.1][7.0][trunk][stock] Move destination and action_done bug Status in OpenERP Addons (modules): Fix Released Bug description: This bug can be observed when the fix for following bug is applied: https://bugs.launchpad.net/openobject-addons/+bug/1137541: [6.1][7.0][trunk][stock] Move destination and partial picking When doing a partial picking, a new move is created when the quantity quantity received/sent is lesser than the expected one. For eg: You are waiting for 10xPCE, you received 6xPCE: A: stock.move with 10xPCE -> state ASSIGNED after the partial picking, it gives: A: stock.move with 4xPCE -> state ASSIGNED B: stock.move with 6xPCE -> state DONE But if you take a look "stock_move.action_done", you will see that a force_assign is done on the destination move and this is a wrong thing to because 6xPCE != 10xPCE if move.move_dest_id.state in ('waiting', 'confirmed'): self.force_assign(cr, uid, [move.move_dest_id.id], context=context) This part of code was Ok before because the move_dest_id was not copied in the newly create move. Fix proposal: Replace "force_assign" with "check_assign" AND doing it AFTER the move state is set to done. see screenshot attached To manage notifications about this bug go to: https://bugs.launchpad.net/openobject-addons/+bug/1160927/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~openerp-india Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-india More help : https://help.launchpad.net/ListHelp
