Comment 3 for bug 1312907

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?