openerp-india team mailing list archive

["Chris Halls \(credativ\)" <halls@xxxxxxxxxx>]

Hi Olivier

> Minimum stock rules are *not* meant to be used for MTO-like behavior, but should be carefully configured to match the 
> raw material requirements of the company, fine-tuned to provide a sufficient stock on hand quantity at all times.

Thanks for your comments. We are looking for MTS-like behaviour, not
MTO.

Imagine a product is normally sold from stock in quantities of maybe
5-10. So the product is set up as MTS with a minimum stock level of 100.
This fits in with the 'finely tuned' levels as you suggest above.

However, we might occasionally also receive larger orders.

Say we have 100 units in stock. We receive 2 separate orders for 250
units and 300 units. We'll need to procure additional units to meet this
demand.

We don't want to use MTO generally for the product, because smaller
orders should be supplied from stock. We don't want to have to train the
sales staff to remember MTS/MTO rules ('When ordering product X you have
to set MTO if you order more than 100. When ordering product Y you have
to set to MTO if ordering more than 50'). That might work for a few
products but not for a company with a large number of products.

The person doing the purchasing does not need to know the details of the
stock rules or individual sales order. They just need to know that we
need an extra 450 units. The current behaviour would give an RFQ for the
first order, but not the second. So the purchaser will order too few
items.

So from the above explanation, is it clear to you that neither minimum
stock rules, nor MTO, would solve this case?

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

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

Title:
  Scheduler don't create a second RfQ for the same part

Status in OpenERP Addons (modules):
  New

Bug description:
  we faced a new issue in MTS. Scenario: create MO with raw material A
  (not available), confirm it, run scheduler (creates RfQ - do not
  confirm it!). Create a second MO with same raw material and confirm
  it, run scheduler. Scheduler does NOT create another RfQ unless you
  confirm the first one... Conesequence: You will not be notyfied about
  the whole qty needs to be purchased.

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