[AccessD] BOM - Table Structure For Handling Common Parts InVarious Assemblies/Sub-Assemblies.

rockysmolin at bchacc.com rockysmolin at bchacc.com
Fri Jun 18 14:14:16 CDT 2010


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


--------------------------------------------------------------------
myhosting.com - Premium Microsoft® Windows® and Linux web and application
hosting - http://link.myhosting.com/myhosting






More information about the AccessD mailing list