c2c-oerpscenario team mailing list archive

["vra \(openerp\)" <535401@xxxxxxxxxxxxxxxxxx>]

** Also affects: openobject-addons/5.0
   Importance: Undecided
       Status: New

** Also affects: openobject-addons/trunk
   Importance: Undecided
       Status: New

** Changed in: openobject-addons/trunk
   Importance: Undecided => Low

** Changed in: openobject-addons/trunk
       Status: New => Confirmed

** Changed in: openobject-addons/trunk
     Assignee: (unassigned) => OpenERP R&D Addons Team 2 (openerp-dev-addons2)

-- 
Production orders ignore chained location at destination
https://bugs.launchpad.net/bugs/535401
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.

Status in OpenObject Addons Modules: Confirmed
Status in OpenObject Addons 5.0 series: New
Status in OpenObject Addons trunk series: Confirmed

Bug description:
This bug is very similar to bug lp:428873, but with production orders instead of purchase orders. I have tested it on the 5.0.7 tagged revision.

I will create a merge proposal with a failing unit test and a proposed fix.

Steps to reproduce with the demo data:
1. Create a new location "Holding" that is chained to the "Workshop" location. That is, any stock moves to "Holding" should generate another move from "Holding" to "Workshop". The move type doesn't matter.
2. Create a production order for PC1 with Holding as the destination location. Quantity is 1.
3. Look at the virtual stock of PC1 in the Holding location.
Expected behaviour: virtual stock should be 0 because the stock should be moved on to the Workshop location.
Actual behaviour: virtual stock is 1.

Analysis:
The fix for lp:428873 seems like it can apply here as well: just add a call to stock_move.action_confirm() in mrp_production.action_confirm(). One thing I'm not sure of is why lp:428873 adds a call to stock_move.force_assign().