Just had a break through in developing the BOM structure for making a hamburger. (I’ll work on the MRP related stuff later).
Several tables:
Assemblies- Listed by Part Number. Which has a portal to related records in:
Usages- Where are parts used. Sorted by Assembly Number (which has to be unique, except when an Assembly overrides that), and is the Part Number in “Assemblies”. Many usages go into a single Assmebly. Each usage is really a part number. Quantity used gets stored here. The same Part Number can show up multiple times, and the same Assembly Number This then relates to:
Part Numbers- Lists each unique part number. This is where the description and Unit of Measure are stored. This is related to:
Part Costing- Lists out the part number, an effective and expiration date for the record, and a price per unit. If I did not have changing prices over time, I could eliminate the Effective and Expiration Dates, and make each Part Number unique. This is related to:
Assemblies 2- Really, just another way of looking at the previous Assemblies table, but here Assembly Number is directly related to the part number. If I didn’t do this, the Part Costing table would only give raw material costs. By doing this, an Assembly Number will add up it’s associated costs, and plug that straight into it’s Part Costing record.
Problems: Creating a new assembly isn’t yet performing new record creation in the Part Costing or Part Number tables, but I’m sure I’ll get there. If I manually create that record, and fill in the right Part Number, it fills in the rest correctly.
I’m pretty stoked about this….
2 Responses to Hamburger Helper