[6.1][mrp_subproduct] makes no finished product in production order
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Odoo Addons (MOVED TO GITHUB) |
Fix Released
|
Low
|
OpenERP Publisher's Warranty Team |
Bug Description
1.-Steps to reproduce the issue you have observed.
having a production order with a list of materials that have assigned subproduct with production quantity X. to finished production in the "production and consumption" but giving a smaller amount as X / 2. no brand becomes the subproduct and inconsistency
production order:
product: [SHE100] Estante de 100cm qyt: 10.00
subproduct in BOM :
Producto UdM del producto Cantidad producto Tipo de cantidad
[SPAN100] Repisa Unidad 0.003 variable
Wizard: produce
Modo: "consume & produce"
Qty: 10.00
2.-The result you observed.
Warning!
You are going to produce total 10.0 quantities of "[SPAN100] Shelf Panel".
But you can only produce up to total 0.03 quantities.
3.-to produce
4.-The result you expected
Ubuntu. 12.04, Python 2.7.2+
openerp- addons :6979
openerp- server : 4265
NOTE: Attached VIDEO with Explain.
Also in: http://
Related branches
- Acsone OpenErp Team: Pending requested
-
Diff: 14 lines (+2/-2)1 file modifiedmrp/mrp.py (+2/-2)
description: | updated |
Changed in openobject-addons: | |
status: | New → Confirmed |
importance: | Undecided → Low |
assignee: | nobody → OpenERP Publisher's Warranty Team (openerp-opw) |
I experienced the same kind of problems with mrp_subproducts, so I started an investigation why and foremost where this occurs.
It turns out that the 'problem' is being generated by the warningmessage in mrp.py in the mrp-module at the following line: osv(_(' Warning! '), _('You are going to consume total %s quantities of "%s".\nBut you can only consume up to total %s quantities.') % (qty, prod_name, qty_avail))
raise osv.except_
I put a hashtag (#) at the beginning of this line, did a restart of the OpenERP server and an update of the MRP-module and my problem was and is fixed.
This may be a very crude way to fix this bug, but for me it is essential because with this particular customer I really need to use subproducts.
I would like to see this bug fixed by using a different statement in stead of "raise osv.except_osv", because, as a user, I would like to get the warningmessage but I also want to be able to continue or stop (break), whichever I would like to choose.