[FIX] When creating a procurement from a move, respect the right UoM conversions
authorJosse Colpaert <jco@odoo.com>
Mon, 1 Dec 2014 15:05:07 +0000 (16:05 +0100)
committerJosse Colpaert <jco@odoo.com>
Tue, 2 Dec 2014 14:51:58 +0000 (15:51 +0100)
addons/stock/stock.py

index 2d49d26..254855b 100644 (file)
@@ -1848,9 +1848,9 @@ class stock_move(osv.osv):
             'company_id': move.company_id and move.company_id.id or False,
             'date_planned': move.date,
             'product_id': move.product_id.id,
-            'product_qty': move.product_qty,
+            'product_qty': move.product_uom_qty,
             'product_uom': move.product_uom.id,
-            'product_uos_qty': (move.product_uos and move.product_uos_qty) or move.product_qty,
+            'product_uos_qty': (move.product_uos and move.product_uos_qty) or move.product_uom_qty,
             'product_uos': (move.product_uos and move.product_uos.id) or move.product_uom.id,
             'location_id': move.location_id.id,
             'move_dest_id': move.id,