From 88889b6aa82e05c98ddb4a61e7dce97bb5823518 Mon Sep 17 00:00:00 2001 From: Goffin Simon Date: Mon, 16 Sep 2019 09:06:01 +0000 Subject: [PATCH] [FIX] mrp: operation type defined on a BOM not chosen Steps to reproduce the bug: - Create two operation types OP1, OP2 with code = mrp_manufacture - Create a BOM B with operation type = OP2 - Create a MO with B Bug: The operation type set on the MO was OP1 instead of OP2 Technically: The default value was always taken from function _get_default_picking_type opw:2070370 closes odoo/odoo#37029 X-original-commit: 3c5338dce8db7606ac2ac0101473bcafe3bd4f76 Signed-off-by: Nicolas Martinelli (nim) --- addons/mrp/models/mrp_production.py | 1 + 1 file changed, 1 insertion(+) diff --git a/addons/mrp/models/mrp_production.py b/addons/mrp/models/mrp_production.py index 015e1c24609..e3d52d95355 100644 --- a/addons/mrp/models/mrp_production.py +++ b/addons/mrp/models/mrp_production.py @@ -391,6 +391,7 @@ class MrpProduction(models.Model): def _onchange_bom_id(self): self.product_qty = self.bom_id.product_qty self.product_uom_id = self.bom_id.product_uom_id.id + self.picking_type_id = self.bom_id.picking_type_id or self.picking_type_id @api.onchange('date_planned_start') def _onchange_date_planned_start(self):