[6.0] mrp MO : wrong stock moves to production

Bug #740047 reported by Jacques-Etienne Baudoux
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Odoo Addons (MOVED TO GITHUB)
Fix Committed
Medium
OpenERP Publisher's Warranty Team

Bug Description

When you create a MO (manufacturing order) with raw materials in location A and a product to consume in location B (filled by 'confirm production'), you are forced to create manually an internal move from A to B (otherwise you have to 'force reservation'). That's correct. However, the move generated by the 'start production' is from A to production instead of from B to production -> BUG. You consume from B, not from A.
The side effect is that the stock level in A is decreased twice and the stock level in B always increases.

Related branches

Changed in openobject-addons:
importance: Undecided → High
status: New → Confirmed
description: updated
Revision history for this message
Jacques-Etienne Baudoux (jbaudoux) wrote :
Revision history for this message
qdp (OpenERP) (qdp) wrote :

as explained on bug https://bugs.launchpad.net/openobject-addons/+bug/740056, for us this flow is working fine. Please test again with an updated version of trunk and provide more information if you still don't think it's the case.

Thanks for the contribution

Changed in openobject-addons:
status: Confirmed → Invalid
importance: High → Medium
Revision history for this message
Steffi Frank (Bremskerl, DE) (steffi-frank) wrote :

Hi

I send you some screenshots.... Did you tested with batch handled component?

Revision history for this message
Steffi Frank (Bremskerl, DE) (steffi-frank) wrote :
Revision history for this message
qdp (OpenERP) (qdp) wrote :

ok i found and fixed the problem: it was occurring only when there was a production lot on the product to consume move.

Thanks for the explanation Steffi: it's fixed in trunk in revision 4612.
Quentin

Changed in openobject-addons:
status: Invalid → Fix Released
Changed in openobject-addons:
assignee: nobody → OpenERP Publisher's Warranty Team (openerp-opw)
Revision history for this message
Jay Vora (Serpent Consulting Services) (jayvora) wrote :

Thanks Steffi and Quentin,

It has been fixed by revision 4505 <email address hidden> in stable 6.0.2.

Changed in openobject-addons:
milestone: none → 6.0.3
Revision history for this message
Jacques-Etienne Baudoux (jbaudoux) wrote :

If location A = location B, you do not have to create a move from A to B. Please review the fix.

Changed in openobject-addons:
status: Fix Released → Confirmed
Changed in openobject-addons:
status: Confirmed → In Progress
Revision history for this message
Jay Vora (Serpent Consulting Services) (jayvora) wrote :

Hello Jacques-Etienne Baudoux (OpenERP) ,

We investigated a little more into it and it seems a quite reasonable behavior to have items' moves into the same location internally.

Please let me know more.

Thanks.

Changed in openobject-addons:
status: In Progress → Confirmed
Revision history for this message
Jay Vora (Serpent Consulting Services) (jayvora) wrote :

Hello Jacques-Etienne Baudoux (OpenERP),

Can we have an update over this?

Thanks.

Changed in openobject-addons:
status: Confirmed → In Progress
Revision history for this message
Riken Bhorania (OpenERP) (rch-openerp) wrote :

Hello Jacques-Etienne Baudoux (OpenERP),

Thanks for reporting.

According to your comment #7, we are agree that such stock move should not be created.

This issue is fixed in https://code.launchpad.net/~openerp-dev/openobject-addons/6.0-bug-740047-rch branch.

It will be merged soon in stable v6.

Thanks.

Changed in openobject-addons:
status: In Progress → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.