Community mailing list archives

RE: functional change in v8 MRP, asking feedback from experts

Ursa Information Systems, Ray Carnes
- 08/29/2014 12:06:06

I believe we reported this as a bug and had it fixed.


It was not possible for the future stock quantity to be trusted until all manufacturing orders had been completed.


I don’t know a single customer who isn’t making something all the time, so this had unacceptable consequences for all of our customers.


If they can never know what the real future stock quantity is, they can’t operate.


I’m just quickly reading and may be wrong, but if you want the patch, let me know.




From: []
Sent: Friday, August 29, 2014 7:56 AM
To: Community
Subject: functional change in v8 MRP, asking feedback from experts


Dear community,



I don't report this as a bug because I'm not sure if there is a bug here, I'm in fact asking for feedback from the MRP expert arounds (Yes Ana that's for you).


In OpenERP/Odoo 6.1 or 7.0,

when you created a Manufacturing Order, for each bill of material component to consume it would:


1) reserve all components in an internal picking.

by default the reservation move was Stock -> Stock, but eventually you could hack it into Stock -> Some Production Location


2) remove all components from the stock by moving it to a virtual location. So for all components we had a second move: Stock -> Virtual / Production



All right, that was 6.1 or 7.0. It was complex and detailed. Eventually you could had discrepancy troubles if you had to change lot or quantity between the reservation picking and the consumed moves but you could work it out.



Now in v8,

things are simpler, for all components, it simply creates a move:

Stock -> Virtual / Production




So no more reservation picking. So if you wanted to move the components to some specific location to prepare the production, you should now set up or develop something. I tried to set up some pull route to create component reservations, but it forces passing through a procurement and a scheduler run so it seems a bit more bureaucratic and even error prone that what we had in 6.1 / 7.0.



So what do you think? It is ok to simply destroy the components now without a reservation move? Is it a simply a functional regression due to the WMS refactor? How would you go to reproduce the reservation move if you needed to?



Raphaël Valyi

Founder and consultant

+55 21 3942-2434


Post to: