credativ team mailing list archive

["Olivier Dony \(OpenERP\)" <988232@xxxxxxxxxxxxxxxxxx>]

Hello,

This is the expected behavior, the procurement of MTS goods is triggered by orderpoints (also known as "minimum stock rules"), and by design a minimum stock rule cannot fire again until the previous item has been properly validated (or cancelled).
If the min. stock rule was allowed to fire repeatedly it would do so every time the scheduler runs until the product comes back in stock, creating many duplicate RfQs.
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. They should include a security extra quantity so that the stock cannot be depleted before the purchase manager is able to confirm the RfQ created by the min. stock rule.

Running the scheduler manually after creating a MO (as you describe) is
very much a MTO-like behavior. If you are working with MTS you should
start by configuring proper min. stock rules (i.e. don't simply tick the
"automatic order point" option of the scheduler), and make sure the
minimum and maximum quantities are properly sized for your needs,
including a sufficient extra quantity to cover the time it takes for the
RfQ to be validated and delivered by the supplier when the min. stock
rule fires.

I hope this helps...


PS: this is by no means a "Security Vulnerability", please do not tick that option when reporting a normal bug (you'll likely delay the answer, as only the security team can see those bugs)

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

** Visibility changed to: Public

** This bug is no longer flagged as a security vulnerability

-- 
You received this bug notification because you are a member of credativ,
which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/988232

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

Status in OpenERP Addons (modules):
  Invalid

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