[6.1][7.0][trunk][stock] Return a product must drop backorder data

Bug #1234678 reported by Yann Papouin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Odoo Addons (MOVED TO GITHUB)
Confirmed
Low
OpenERP R&D Addons Team 2
OpenERP Community Backports (Addons)
Status tracked in 7.0
6.1
Fix Released
Medium
Yann Papouin
7.0
Fix Released
Medium
Yann Papouin

Bug Description

The backorder_id field must be set to False when creating the new return picking

in "stock_return_picking.py"
new_picking = pick_obj.copy(cr, uid, pick.id, {'name':'%s-%s-return' % (new_pick_name, pick.name),

otherwise it will use the backorder_id of the original picking object -> invalid

Fix for 6.1, 7.0, trunk is necessary

Related branches

Changed in ocb-addons:
assignee: nobody → Yann Papouin (yann-papouin)
Changed in ocb-addons:
status: New → Fix Committed
Revision history for this message
Amit Parik (amit-parik) wrote :

Hello Yann,

I have checked this issue and its working fine, I have seen new return product created with the blank back order.

I have prepare a video for this, Would you please have a look on it.

Thank you!

Revision history for this message
Amit Parik (amit-parik) wrote :
Changed in openobject-addons:
status: New → Incomplete
Revision history for this message
Yann Papouin (yann-papouin) wrote :

Amit, that's normal that the backorder is empty as the original backorder (OUT/0002 in your video) is also empty (see screenshot attached).

If you want to reproduce:
You receive products with a quantity of 10 x PCE in OUT/00008:
- Change quantity to receive only 5 x PCE
- A new picking is created with quantity of 5 x PCE and a backorder is created (OUT/00009)
- Now receive remaining 5 x PCE
- Finally return products from the picking that contains a backorder
- You will see that that the returned picking has the same backorder

Changed in openobject-addons:
status: Incomplete → New
Revision history for this message
Amit Parik (amit-parik) wrote :

Hello Yann,

Thanks for the detailed explanation!
Faced the same issue.

Changed in openobject-addons:
assignee: nobody → OpenERP R&D Addons Team 2 (openerp-dev-addons2)
importance: Undecided → Low
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.