Merge lp:~openerp-dev/openobject-addons/7.0-opw-586594-acl into lp:openobject-addons/7.0
Status: | Needs review |
---|---|
Proposed branch: | lp:~openerp-dev/openobject-addons/7.0-opw-586594-acl |
Merge into: | lp:openobject-addons/7.0 |
Diff against target: |
121 lines (+22/-19) 5 files modified
mrp/mrp.py (+13/-11) mrp/procurement.py (+1/-1) mrp/report/price.py (+1/-1) mrp/stock.py (+6/-5) mrp/wizard/change_production_qty.py (+1/-1) |
To merge this branch: | bzr merge lp:~openerp-dev/openobject-addons/7.0-opw-586594-acl |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
OpenERP R&D Team | Pending | ||
Review via email: mp+150551@code.launchpad.net |
Description of the change
When creating a sale order with lines having phantom BoM, the first BoM for the corresponding product was always found.
It now takes care of properties to select the right BoM.
Steps to reproduce :
1. In Settings > Manufacturing, we have selected the tickbox: Allow several bill of materials per products using properties
2. In the Manufacturing module > Products > Bill of Materials there are 2 BOM’s called ‘HDD on Demand’. I have edited them both to be BOM Type: Sets / Phantoms
3. In Manufacturing > Properties, I created 2 new Properties: one called HDD1 x1 and the other called HDD2 x4
4. In the 1st ‘HDD on Demand’ I loaded Property HDD1 x1 and in the 2nd ‘HDD on Demand’ we loaded HDD2 x4
5. In each BOM ‘HDD on Demand’ I added an extra line for ease of identification
6. Then I go to the Sales module > Sales Orders to create a quotation using any Customer. When I come to add a product line, I Create Product ‘HDD on Demand’ and select a Property, look for hdd, the 1st one being: HDD1 x1. Save & Close. Confirm the Order. View the Delivery Order and I see the 2 lines on Property HDD x1
7. If I create another order and create Product ‘HDD on Demand’ and select Property, look for hdd and select the 2nd one being: HDD2 x4. Save and Close. Confirm the Order. View the Delivery Order, I see the 2 lines from HDD1 x2 displayed. In other words, the Property selection is not picking any subsequent Properties selected other than the 1st Property.
Unmerged revisions
- 8765. By Anaël Closson (openerp)
-
[FIX] mrp : Phantom BoM can be chosen according sale order line properties
Before this patch, BoM was incorrectly chosen : for 2 BoM bound to properties for a single product,
the first BoM found was used each time the product was added to a sale order; the property had no impact.
Now, the right BoM is used according the property used in the sale order line.