Amit Dodiya (OpenERP) has proposed merging 
lp:~openerp-dev/openobject-addons/6.0-bug-876243-ado into 
lp:openobject-addons/6.0.

Requested reviews:
  Xavier ALT (OpenERP) (xal-openerp)
  Naresh(OpenERP) (nch-openerp)
Related bugs:
  Bug #876243 in OpenERP Addons: "Cannot pay a PoS line with production lot"
  https://bugs.launchpad.net/openobject-addons/+bug/876243

For more details, see:
https://code.launchpad.net/~openerp-dev/openobject-addons/6.0-bug-876243-ado/+merge/102251

Hello,

"[FIX] Cannot pay a PoS line with production lot"

Steps to reproduce:
- Create a product with Track Incoming Lots and Track Outgoing Lots.
- Create all data needed to create a PoS Order.
- Create a new PoS Order with a client.
- Create a new line with the product previously created.
- Click on Make Payment

The following warning appear:
Error occurred while validating the field(s) prodlot_id: You must assign a 
production lot for this product

Code is back-ported from stable 6.1.

Regards,
Amit

-- 
https://code.launchpad.net/~openerp-dev/openobject-addons/6.0-bug-876243-ado/+merge/102251
Your team OpenERP R&D Team is subscribed to branch 
lp:~openerp-dev/openobject-addons/6.0-bug-876243-ado.
=== modified file 'point_of_sale/point_of_sale.py'
--- point_of_sale/point_of_sale.py	2011-06-02 05:14:55 +0000
+++ point_of_sale/point_of_sale.py	2012-04-17 08:45:22 +0000
@@ -476,7 +476,7 @@
                             'pos_line_id': line.id,
                             'state': 'waiting',
                             'location_id': location_id,
-                            'location_dest_id': stock_dest_id,
+                            'location_dest_id': order.shop_id.warehouse_id.lot_output_id.id,
                         }, context=context)
 
             wf_service = netsvc.LocalService("workflow")

_______________________________________________
Mailing list: https://launchpad.net/~openerp-dev-gtk
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~openerp-dev-gtk
More help   : https://help.launchpad.net/ListHelp

Reply via email to