[AccessD] BOM - Table Structure For Handling CommonPartsInVarious Assemblies/Sub-Assemblies.

A.D.:

More info - the Assembly and Component part numbers in the Product
Structure table are FKs to the Part Master table where the Part Number is
the PK.  

The cost roll up utility calculates standard cost and the material, labor,
burden, etc. costs are stored in the part master table.  A flag is set on
any part which changes so  notice is given on the BOM report that costs may
have changed since the last cost roll up.  And the roll up is required
before running the MRP calculations.

The depth of the BOM is artificially limited to 10 levels, which has proven
to be quite enough for the small manufacturers who use E-Z-MRP.  

Is your application just for engineering support or will it be for
manufacturing support as well - kitting, phantom parts, sub-contract parts,
etc.?

HTH

Rocky

Original Message:
-----------------
From: A.D. Tejpal adtp at airtelmail.in
Date: Sat, 19 Jun 2010 10:56:06 +0530
To: accessd at databaseadvisors.com
Subject: Re: [AccessD] BOM - Table Structure For Handling
CommonPartsInVarious Assemblies/Sub-Assemblies.


    Thanks Rocky! I shall examine it further and revert back.

Best wishes,
A.D. Tejpal
------------
  ----- Original Message ----- 
  From: rockysmolin at bchacc.com 
  To: accessd at databaseadvisors.com 
  Sent: Saturday, June 19, 2010 00:44
  Subject: Re: [AccessD] BOM - Table Structure For Handling Common
PartsInVarious Assemblies/Sub-Assemblies.


  A.D>:

  I worked this out for the bill of materials module in E-Z-MRP by defining
  the record as:

  Assembly Part Number
  Component Part Number
  Quantity

  I also added Reference Info as a memo and effective and obsolete dates but
  that's not relevant to your question.

  Both Assembly and Component Part numbers are indexed duplicates OK.  With
  this scheme you can easily do both indented BOM listings and Where Used. 
  Each assembly only appears once in the table but that assembly can be the
  chiled to any numnber of higher level assemblies.

  Rocky
   

  Original Message:
  -----------------
  From: A.D. Tejpal adtp at airtelmail.in
  Date: Fri, 18 Jun 2010 23:32:18 +0530
  To: accessd at databaseadvisors.com
  Subject: [AccessD] BOM - Table Structure For Handling Common Parts
  InVarious Assemblies/Sub-Assemblies.

      Typical fields for a table having hierarchical list of assemblies and
  parts are observed to include:  ItemID, ParentID, Description, Qty

      With this arrangement, the complete hierarchical chain from each
  topmost item (having no immediate parent) downward can be worked out right
  upto the lowest part (having no child).

      In situations where a part with same ItemID is needed for more than
one
  Item chain (i.e. more than one top parent), the above table structure
might
  not prove adequate. 

      Any suggestions - while retaining its role as a self contained table ?

  Best wishes,
  A.D. Tejpal
  ------------
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com


--------------------------------------------------------------------
mail2web LIVE – Free email based on Microsoft® Exchange technology -
http://link.mail2web.com/LIVE