Re: [WebERP-developers] BOMs.php Location Defaults

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

Exson,

To implement a BOM header is straight forward.  We can until the resources
become available, leave the BOM table the same and add a BOMHeader table. 
Initially such would be used to provide static information that would be the
default for the BOM table (BOMDetail) and used mainly in BOMs.php.

Moving forwards, we need to put together a proposal to be reviewed of
integrating concepts of traceability and revision control into WebERP. 
Currently, we can not readily determine which devices in the field contain
items from batches or serialized items.  There are times when a batch of
material has defects and all items made utilizing such needs to be isolated. 
Examples would be faulty semi-conductors and material not conforming to
material specifications, i.e. bad melt.  We will investigate if there is
sufficient information in the data base to answer such queries.

We would like to differentiate product variations but still be able to use a
minimal product code for quoting, shipping and invoice; but
manufacture/purchase to a specific product revision.

We recognize that there is a lot of capability and information in WebERP. 
Some of the items can possibly be accomplished by user discipline, proper
set-up of the database, and well documented process.

Bob Thomas 



--
View this message in context: http://weberp-accounting.1478800.n4.nabble.com/BOMs-php-Location-Defaults-tp4657663p4657667.html
Sent from the web-ERP-developers mailing list archive at Nabble.com.