Community mailing list archives
Re: functional change in v8 MRP, asking feedback from expertsby
Dear Raphael,If a company has a long manufacturing time it is very useful to know how many parts are committed to orders in process. If I understand it correctly, the internal picking can be used to reduce the virtual stock to take account of those components and thus give how many components are available for new orders. If the process is only 1 stage this will not be possible?Regards,
<IMG style="HEIGHT: 57px; WIDTH: 206px" border=0 hspace=0 alt="" src="cid:663282315@29082014-27D1" width=836 align=left height=134>
Tel: 01327 857788
From: firstname.lastname@example.org [mailto:email@example.com]
Sent: 29 August 2014 16:01
Subject: functional change in v8 MRP, asking feedback from expertsDear 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 Location2) remove all components from the stock by moving it to a virtual location. So for all components we had a second move: Stock -> Virtual / ProductionAll 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 / ProductionSo 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?
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4745 / Virus Database: 4015/8119 - Release Date: 08/29/14