Minimum stock rule + Compute Schedulers + Chained Locations creatings two stock moves

[dev.data.dev]

Setup internal chain locations. Stock arrives to a internal location then move to another internal location.

After creating a Minimum stock rule for a product.
I run compute scheduler.

It then creates two stock moves to the internal locations and doubling stock.

I applied the the bugfix #812678(https://bugs.launchpad.net/openobject-addons/+bug/812678) and it did not help my problem.

Thanks

[Amit Parik (amit-parik)]

Hello,

This problem not only exist on stable 6.0 but I have faced the same problem on trunk.

I have tried the following scenario for the subcontracting process using chain location and faced the wrong stock move when I run the scheduler.

I have also tried the lp:~openerp-dev/openobject-addons/6.0-opw-51081-rha this branch but faced the another problem which is
UnboundLocalError: local variable 'order_point_warehouse_id' referenced before assignment and also it gives the wrong stock move.

I have used following scenario.
I have create a one *chain location* 'Subcontract' , Location type ='Supplier', Chained Location Type = 'Fixed' and assigned it to 'Stock ' and Chaining type ='Manual'

I have created one product name "test" and create a Procurement(Stock) rule for this product as follow.
location : Subcontract , minimum qty : 5, maximum qty : 15.

After that I have run the Schedulers It creates a RFQ for that product with 15 qty and I have received the product.
So now whole process is done then after I have seen the stock move which is wrong I have attached the screen-shot for same.

Please check the attached screen-shot at the one stock move for Subcontract to stock is correct cause here I have set the Chaining type ='Manual' to stock So I have to Manually done it.

Now about the remaining stock move 1) same as above subcontract to stock for same qty I don't think it's correct stock move Cause if I have done it Manually then It will double the stock which the same issue as reported on lp:812678.

Additionally I get the one more move with waiting availability it's subcontract to subcontract, here I have done whole the process so as my Opinion this move should be on done state.

Currently I am assigning this for the trunk cause lp:812678 is still doesn't fixed and it's effecting our whole stock part.

Correct me If I missed something.

Thank you!

[Amit Parik (amit-parik)]

You mean for "Make to stock" correct?

Whenever the procurement method is "Make to stock" then we have to define the "Minimum Stock rule".
And this problem only faced when we run the scheduler with "Order Point" true.

Thank you!

[dev.data.dev (dev-data-dev)]

Yes I ment 'Make to stock'.

All the above you have mention is correct.