Odoo Addons (MOVED TO GITHUB)

Bug #427733
Comment #2

Comment 2 for bug 427733

Revision history for this message

Olivier Dony (Odoo) (odo-openerp) wrote on 2010-03-29:

After checking carefully the bug description and the comments, it seems that what you describe is the expected behavior in this particular configuration.

Let me explain:

1. The purchase order for which you see a planned date you do not expect is created by the order point/min stock rule. The purpose of the minimum stock rule is to replenish the stock asap when the virtual stock is below the minimum (this can lead to a PO date in the past due to the company' security 'purchase lead time' - we could improve that and include it in the planning, but that would only move the PO to today).
If you do not want it to trigger yet, then you should make sure that the virtual stock does not drop yet.

2. The virtual stock level has dropped because the production order has been confirmed, and thus has created a corresponding procurement for the raw material it needs. If you do not want this happen yet, then make sure that the production order is not created yet.

3. The production order has been created and confirmed because the original procurement order coming from the sale order has been confirmed already. This happens by default if JIT is installed (that's the point of JIT obviously) or if you run the schedulers and the procurement is within the 'scheduler range' set on the company (80 days by default)

So it seems to me that every part of the system is doing what it should. If you do not want step 3 to occur then do not install mrp-jit *and* ensure that the 'scheduler range' on the company is sufficiently small (less than 28-30 days in your examples) so it does not trigger your procurement yet.

I will close this bug as invalid, so you have 2 options:
- if I misunderstood your report, please reopen this bug and add more info or a more detailed testcase, such as an XML test
- if you think you would like the system to behave differently, feel free to open another bug (wishlist) or a blueprint to describe it (but please keep in mind the above rules and the separate roles of each part of the system)

After checking carefully the bug description and the comments, it seems that what you describe is the expected behavior in this particular configuration.

Let me explain:

1. The purchase order for which you see a planned date you do not expect is created by the order point/min stock rule. The purpose of the minimum stock rule is to replenish the stock asap when the virtual stock is below the minimum (this can lead to a PO date in the past due to the company' security 'purchase lead time' - we could improve that and include it in the planning, but that would only move the PO to today). 
If you do not want it to trigger yet, then you should make sure that the virtual stock does not drop yet.

I will close this bug as invalid, so you have 2 options:
 - if I misunderstood your report, please reopen this bug and add more info or a more detailed testcase, such as an XML test
 - if you think you would like the system to behave differently, feel free to open another bug (wishlist) or a blueprint to describe it (but please keep in mind the above rules and the separate roles of each part of the system)