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

[rfthomas <rf...@as...>]

Tim and Klaus,

The MySQL table changes appear to make sense, but we have the problem of
properly identifying the process revisions and production history.  There
are a number of areas that need to know and deal with such information.  The
following is coding of inventory could work:

<product code>_<product revision>_<routing>_<routing revision>

It would be assumed that in normal operation the latest active item would be
produced and sold.  Salesmen would for normal sales, quote <product> and the
system would automatically select the most recent active product (<product
code>_<product revision>_<routing>_<routing revision>).  Order
acknowledgements, shipping documents, work orders, etc. would normally
default to the most recent active product.

We need to be able to know the full pedigree of the parts sold.

There are times when one must produce a product to an earlier revision.  One
would need to be able to select the full product code.  One could end up
with a very large number of fully qualified product codes.

Bob Thomas



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