Re: [WebERP-developers] Bug? MRP for WO at reqdate instead of startdate

[opto <bu...@op...>]

well -   possible answers:

1) 
Using WO required date for MRP PO clearly is a bug - even the manual says
the items should be procured for WO start date. I will change that file in
the next days

2) currently, any item can be only once per BOM. If it is used in two places
at different times, I have to enter 2 required and the earliest time and
procure both parts for that date (in the current implementation)

3) the current MRP implementation prevents the use of weberp in the
electronics industry (actually, you can find a similiar complaint about
openerp in their forum). Part lists for electronic assemblies typically have
component counts higher than 1 (like I need two resistors of 1 kiloohm
value), and the CAD numbers them like R1, R7 to indicate their position n
the circuit diagram. For clarity, it would be nice to reflect that in the
BOM's, but after a short look at the code, this would need more serious
consideration whether the current mrp.php needs to be changed.

4) BOM's need a few custom fields to be usable in daily work (same for
workorders).
First, the BOM will correspond to a product number, will have a revision,
documents, a staging URL, etc.
Here, the current BOMs miss some mapping possibility to the actual
engineering documents related to the BOM. You find that in other ERP/MRP
software, and it should not be too difficult to add.

just some more thoughts on the manufacturing implementation,

Klaus
 

--
View this message in context: http://weberp-accounting.1478800.n4.nabble.com/Bug-MRP-for-WO-at-reqdate-instead-of-startdate-tp4651206p4655124.html
Sent from the web-ERP-developers mailing list archive at Nabble.com.