openerp-india team mailing list archive

[Don Kirkby <939790@xxxxxxxxxxxxxxxxxx>]

I tried my scenario on the trunk version, Amit, and the fix for bug
627936 was slightly more restricted there than in 5.0. It only added
filters to the automatic orderpoint, not minimum stock rules. I think
it's still a bug, though. Shouldn't automatic orderpoints generate
manufacturing orders as well as purchase orders?

Make the following changes to my scenario for the trunk version:
- In step 1, install mrp and sale modules.
- In step 4, clear the Ready state filter on the Manufacturing Orders screen to see all manufacturing orders. I see nine.
- In step 5, I see quantity available of 14.
- In step 6, delete the minimum stock rule.
- In step 7, drop the quantity below zero. I used 15.
- In steps 3 and 10, check the automatic orderpoint checkbox.
- In step 12, I expect to see the quantity available back at zero, but there is no change.

-- 
You received this bug notification because you are a member of OpenERP
Indian Team, which is subscribed to OpenERP Addons.
https://bugs.launchpad.net/bugs/939790

Title:
  Minimum stock rules only applied to products you purchase

Status in OpenERP Addons (modules):
  Incomplete

Bug description:
  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.

  Here are the steps to reproduce the bug:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-addons/+bug/939790/+subscriptions