openerp-india team mailing list archive
-
openerp-india team
-
Mailing list archive
-
Message #01640
[Bug 891616] Re: purchase_requisition: procurement is cancelled when first PO is cancelled
After some debugging, I found a solution :
1) When procurement.purchase_id changes (by user action or through
purchase_requisition), update wkf_workitem.subflow_id with the
wkf_instance.id of the new selected PO.
2) In purchase.requisition.partner wizard.create_order(), set
purchase_order_line.move_dest_id with the same value as
procurement.move_id in order to build a good move chain after PO
confirmation.
I hope it will help !
Thanks
--
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/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
References