Confirmation of chained internal package does not propagate availability
Bug #1238508 reported by
Nicolas Bessi - Camptocamp
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
lp:~camptocamp/ocb-addons/7.0-fix-1238508-nbi
- Alexandre Fayolle - camptocamp: Approve (code review, automated test)
- Holger Brunn (Therp): Approve (code review)
- Stefan Rijnhart (Opener): Approve
-
Diff: 144 lines (+104/-7)3 files modifiedstock/__openerp__.py (+1/-0)
stock/stock.py (+5/-7)
stock/test/stock_move_chain_validation.yml (+98/-0)
lp:~camptocamp/openobject-addons/7.0-fix-1238508-nbi
- Alexandre Fayolle - camptocamp (community): Approve (code review, automated test)
- OpenERP Core Team: Pending requested
-
Diff: 144 lines (+104/-7)3 files modifiedstock/__openerp__.py (+1/-0)
stock/stock.py (+5/-7)
stock/test/stock_move_chain_validation.yml (+98/-0)
| description: | updated |
| Changed in openobject-addons: | |
| status: | New → Confirmed |
Revision history for this message
| Alexandre Fayolle - camptocamp (alexandre-fayolle-c2c) wrote | #1 |
| 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.
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.