7.0 - automatic orderpoints defect

[Pierre Gault]

Product set as: MTS, no reordering rules, buy procurment method, supplier defined.
Stock is negative. (force availibilty)
Expected result: Scheduler (with automatic orderpoints checked) generates a PO to make stock back to zero.
Observed result: No PO generated. Exception: ' Not enough stock and no minimum orderpoint rule defined'

PLatform : Ubuntu 12.04
DB : PostgreSQL 9.1
Language : Python, XML

[Rifakat Husen (OpenERP) (rha-openerp)]

Hello Pierre,

Thanks for providing detail.

Yes, running scheduler with "Automatic orderpoint" enabled will only check the negative stock on any product and puts it to level zero by creating new procurement order, and this procurement order will trigger an RFQ. I have checked it and it works as expected.

Could you please check it again if you are checking the right procurement order reference because I think you might be checking another procurement order, which could be generated from other documents like sales order?

A procurement order generated due to Automatic orderpoint will have string "SCHEDULER" in field Source Document.
Thanks for checking it again at your end.

Regards,
Rifakat

[Pierre Gault (pierre-gault)]

Hello,

Thank you for your quick answer. But I do not understand why I have an exception with a SO as source document while my product is MTS.

Pierre Gault

Consultant OpenERP
Savoir-faire Linux
Tel: + 1 [phone], ext. 329
Courriel: <email address hidden>

7275 Saint-Urbain, bureau 200
Montréal, QC
H2R 2Y5

----- Original Message -----
From: "Rifakat Husen (OpenERP)" <email address hidden>
To: "pierre gault" <email address hidden>
Sent: Friday, May 2, 2014 5:42:42 AM
Subject: [Bug 1312907] Re: 7.0 - automatic orderpoints defect

Hello Pierre,

Thanks for providing detail.

Yes, running scheduler with "Automatic orderpoint" enabled will only
check the negative stock on any product and puts it to level zero by
creating new procurement order, and this procurement order will trigger
an RFQ. I have checked it and it works as expected.

Could you please check it again if you are checking the right
procurement order reference because I think you might be checking
another procurement order, which could be generated from other documents
like sales order?

A procurement order generated due to Automatic orderpoint will have string "SCHEDULER" in field Source Document.
Thanks for checking it again at your end.

Regards,
Rifakat

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1312907

Title:
  7.0 - automatic orderpoints defect

Status in OpenERP Addons (modules):
  New

Bug description:
  Product set as: MTS, no reordering rules, buy procurment method, supplier defined.
  Stock is negative. (force availibilty)
  Expected result: Scheduler (with automatic orderpoints checked) generates a PO to make stock back to zero.
  Observed result: No PO generated. Exception: ' Not enough stock and no minimum orderpoint rule defined'

  PLatform : Ubuntu 12.04
  DB : PostgreSQL 9.1
  Language : Python, XML

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

[Denis Durepos (djdurepos)]

For an example, please see attached images of the procurement exception, product configuration and related reservation (from the outgoing stock move created by the SO). As mentioned by Pierre, the expected behaviour is that an RFQ be created (this works in a blank database with only the test data), however none is created.

Is it possible that the scheduler gets hung up on other procurement exceptions that are intentionally "misconfigured" (i.e. no supplier defined so that they cannot generate RFQs) and does not end up processing the automatic orderpoints correctly?

[Denis Durepos (djdurepos)]

Any chance we can get some movement on this issue? This is a crippling problem that was supposed to be absent in v7. We need a resolution.

[nivels GmbH (nivels)]

dear support,

I do have exactly the same issues now - the scheduler worked fine until last week - now the scheduler is not creating the draft purchase orders anymore.

I installed an old codebase to see if the problem is based on a new version - but without success. So I'm guessing as well like Denis,
that the scheduler does not run through - that it gets blocked because one product is not configured correctly? (it worked before...)

Thanks for prioritizing this issue - customer production is on hold

[Denis Durepos (djdurepos)]

Any advancement on this issue? This is a critical problem for us as purchasers have to manually check inventory. Very disappointing to see what an OpenERP Enterprise support contract is NOT getting us in terms of bugfixes.