openerp-india team mailing list archive

["Amit Parik \(OpenERP\)" <amp@xxxxxxxxxxx>]

Hello Jordg,

We can't put the restriction like this. Because it will stop the other
functionality.

Minimum Order (Stock) rule are working like this. First talking about
the minimum qty, So whenever your stock goes to below this qty then it
will create the procurement for the required qty + maximum qty. Because
After running the scheduler in your stock the qty should be available as
your max qty of your order rule.

For that you are correct if your max aty =0 then it will work like make
to order  but not fully cause on make to order didn't check the stock of
your location and create the PO/MO for related qty. And if your maximum
and minimum qty is zero then it will create the Procurement for
satisfied your required qty not more that's it.

So we can allow the minimum and maximum qty is zero on order rule it
will never affects any where. Additionally in most of ht eral scenario
the minimum qty is zero. So your constraint will break this
functionality.

Not about your availability point, In current OpenERP availability
things are working like this. This is not specially for that particulate
order rule Because on confirm button of MO/SO we have check the
qty(virtual) of product. After run the procurement/scheduler your qty
will satisfied but we can't check this automatically. You have to do
action on "Force Reservation" or "Check availability" button then after
your move will available.

Hope this clear now.

So this is not a bug and I am closing it.

Thanks for the reporting!

** Changed in: openobject-addons
       Status: New => Invalid

-- 
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/1065772

Title:
  Stock Orderpoint min=0 and max=0

Status in OpenERP Addons (modules):
  Invalid

Bug description:
  If your product is setup as make_to_stock, buy and you set a Minimum Stock Rule for Min=0 and Max=0.
  The above is effectively make_to_order configuration.

  Run schedular
  In the case some qty of the above product is required for Manufacturing and we need to buy some to fulfil the MO requirements.
  Request for Quotation is created by schedular
  Confirm purchase order
  Recieve item into stock
  Check stock levels. These are correct.
  Run schedular
  Check MO for product avaliability - Not Avaliable

  This is a subtle bug that the user will not be able to solve, and will
  take some time for a technical person to identify the configuration
  error.

  One solution is to add _sql_contraints that prevent this situation from occuring in the first place
  class stock_warehouse_orderpoint(osv.osv):
      _sql_constraints = [
          ('qty_multiple_check', 'CHECK( qty_multiple > 0 )', 'Qty Multiple must be greater than zero.'),
  +        ('mix_qty_ge_zero_check', 'CHECK( product_min_qty >= 0 )', 'Min Quantity must be greater than or equal to zero.'),
  +        ('max_qty_gt_zero_check', 'CHECK( product_max_qty > 0 )', 'Max Quantity must be greater than zero.'),
      ]

  Thanks

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