As part of bug 627936, Dukai Gábor added filters to the minimum stock rule scheduler so that it will only look at products that are active and can be purchased. I agree with filtering on the active flag, but we turn off the "can be purchased" flag for products that we produce, because we will never create a purchase order for them. However, we still want to generate production orders for products that we produce when they drop below the minimum quantity.
Remember that minimum stock rules are used to generate production orders as well as purchase orders.
I'm running OpenERP version 5.0.16 on Ubuntu 10.04.
See comment #3 for the steps to reproduce the bug in 6.1. Here are the steps to reproduce the bug in 5.0.16:
1. Create a sample database with the manufacturing profile. Use the default settings for everything, except the chart of accounts should be None, and the extra modules should be mrp and mrp_jit.
2. Open product PC1, and check that supply method is produce. Clear the checkbox for can be purchased and save. This marks it as a product that we always produce and never purchase.
3. Compute all schedulers. Use the default settings.
4. Count the number of production orders. I see 11 in my sample database.
5. Check the virtual stock of PC1. I see six.
6. Check the minimum stock rule's minimum and maximum quantities for PC1. I see three and five.
7. Create a sales order to Agrolait with PC1. Set the quantity high enough to drop the virtual stock below the minimum quantity. I used four.
8. Confirm the sales order.
9. Check virtual stock is below minimum quantity. I see two.
10. Compute all schedulers with the default settings.
11. Check number of production orders.
Expected result: more production orders to bring PC1's quantity above the minimum.
Actual result: no change in the number of production orders. I see 11.
12. Check virtual stock of PC1.
Expected result: the maximum quantity from the minimum stock rule. I expected five.
Actual result: no change. I see two.
Hello Don Kirkby,
I have checked your issue with latest trunk at my end, but all are working as expected.
So would you please check with the trunk version and notify us your issue is only effecting for 5.0.16 or trunk also.
Thanks and waiting for your reply!