Hello Jignesh, I've tested with fresh trunk today and the problem is still here :(
The issue doesn't directly come from purchase_requisition : if I change the PO of the procurement manually, the behavior is the same. The procurement seems linked to the initial PO workflow. -- You received this bug notification because you are a member of C2C OERPScenario, which is subscribed to OpenERP Project Group. https://bugs.launchpad.net/bugs/891616 Title: purchase_requisition: procurement is cancelled when first PO is cancelled Status in OpenERP Addons (modules): Confirmed Bug description: Steps to reproduce the issue: 0) Create product X, make to order, purchase requisition checked, 2 suppliers (supplier1, supplier2) 1) Confirm sale order for one X 2) Run scheduler => a requisition with one PO for supplier1 is created 3) Open requisition, select exclusive type and add a PO for supplier2 4) Confirm supplier2 PO Observed result: First PO is cancelled and procurement is cancelled Expected result: First PO is cancelled and procurement is running OpenERP version: 6.0.3 I don't find in the code where this cancellation occurs. Even if I remove "visible" links between the procurement and the first PO (procurement_order.purchase_id and purchase_order_line.move_dest_id), the procurement is cancelled. The state of procurement's stock move doesn't change (keeps unavailable), it's OK, but the Suppliers->Stock move hasn't move_dest_id filled (consequence of the bug ?). So, the procurement and the moves chain are broken. To manage notifications about this bug go to: https://bugs.launchpad.net/openobject-addons/+bug/891616/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~c2c-oerpscenario Post to : [email protected] Unsubscribe : https://launchpad.net/~c2c-oerpscenario More help : https://help.launchpad.net/ListHelp
