Comment 3 for bug 798890

I didn't really consider either 1 or 2 issues, as I completely understand why the procurement can be in the state it was (confirmed and past scheduled date) and I wasn't reporting those. As for #3 - yes, agreed, but it's separate from my issue.

#4 is definitely a bug and not a code improvement. Specifically, the fact that it will never break out of the while loop under the conditions I mentioned is an issue. The result it a pegged CPU and, if the scheduler is catching up on Open ERP startup, the server will not start properly.