c2c-oerpscenario team mailing list archive
-
c2c-oerpscenario team
-
Mailing list archive
-
Message #26960
[Bug 794412] Re: delivery order with back order is 100% picked
Hello,
I have checked in sale.The procurement order has gone into the done
state even when one move is still left to be done.I modified the
condition and checked that delivered(boolean) should become True on the
basis of (procurement.order = done AND stock.move = done).But the
test_state() of sale.order which gets triggered on procurement.order
model, wont get called for the move which is yet to be done.
I think the check_move_done() method on procurement.order should check
not only the original move assigned on procurement but all the move(s)
associated with the original move.
So I request community team to check this bug.
Thanks,
mtr
** Changed in: openobject-addons
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/794412
Title:
delivery order with back order is 100% picked
Status in OpenERP Modules (addons):
Confirmed
Bug description:
Hey,
When we do a partial picking for a delivery order, if we pick the corresponding original stock.move (the one which is linked to procurement.order), the procurement.order workflow terminates and the picking status of sale order is set to 100%.
This is simply caused by the
procurement>action_check_finished>check_move_done function which check
the end of procurement.order workflow by looking only at original
stock.move, not taking care of back order stock moves.
Here is how to reproduce the bug:
Create a Sale Order, with one order line (CPU1 - 10) from stock. Validate.
In Delivery Order, split the stock move by assigning a production lot > prodlot: A, qty: 3
Process the Delivery Order, and put 0 as a quantity for the prodlot A.
A back order is created for prodlot A.
The other 7 CPU1 are Done.
Go to Sale Order, it is 100% picked. Procurement.order is Done.
We want the picking state to take into account back orders, and
therefore the procurement.order should not be Done until all related
stock.moves are Done (or cancel).
I use openerp 6.0.2. The behavior should be the same on the trunk
version, as the check_move_done function is still the same.
A proposal of correction, taking into account the moves linked to sale
order lines instead of moves linked to procurement order is linked as
attachment. The case where no sale order is involved (from order point
?) should be analyzed.
Best,
Patrick
To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-addons/+bug/794412/+subscriptions
References