Confirmation of chained internal package does not propagate availability

Bug #1238508 reported by Nicolas Bessi - Camptocamp
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Odoo Addons (MOVED TO GITHUB)
Confirmed
Medium
OpenERP R&D Addons Team 2
OpenERP Community Backports (Addons)
Status tracked in 7.0
7.0
Fix Committed
Medium
OpenERP Community Backports

Bug Description

Using the demo set up modified to chained internal location to out location in manual mode.

If you make a sales order for a stockable product and with procure method set to make to stock.

When you confirm the sales order you have two related pickings:
- one (internal) picking that goes from internal location to out location.
- one picking that goes from out location to customer location.

If you split one stock move, you will have two stock move that have the same move_dest_id (destination move).

When you deliver the internal picking the outgoing (to customer) picking is not set as available.

Regards

Nicolas

Related branches

Changed in openobject-addons:
status: New → Confirmed
Revision history for this message
Alexandre Fayolle - camptocamp (alexandre-fayolle-c2c) wrote :

To be more precise in the bug description, the problem occurs when several moves have the same move_dest_id (which happens when a move is split into different production lots, e.g. with the product_serial community addon on which we are working), and then all moves are processed.

The problem does not happen if the moves are processed one by one.

Amit Parik (amit-parik)
Changed in openobject-addons:
assignee: nobody → OpenERP R&D Addons Team 2 (openerp-dev-addons2)
importance: Undecided → Medium
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.