>>Hi I am posting this again as I hadn't got a response, as I had posted on a Saturday maybe it was a wrong day <g>.
>>
>>Hi all
>>
>>I have this requirement for an inventory system and the following is the rough master data structure I have in mind:
>>
>>Items Master where iParentItemsID is for maintaining a tree structure of item heirarchcy. Item in say nos., having no secondary units, can be purchased or sold on say kgs. thus the yItemWeight
>>iID
>>iParentItemsID
>>cDesc
>>yOpStock
>>yItemWeight
>>Secondary Units Master to maintain breakup of the Items Opening Stock in say for eg. packs; 10gms Pack, 50gms Pack, 1kg Pack. cConversion is / or * to convert it back to the Main Items Stock
>>iID
>>iItemMastersID
>>cSecondaryUnit
>>yOpStock
>>yConversionQty
>>cConversion
>>BOM Master this will maintain Bill of Material for each item. iItemID uses the Items Master above. cAddLess is required as in a production there is less of the actual BOM items but add of Scrap etc.
>>iID
>>iItemMastersID
>>iItemID
>>yQty
>>cAddLess
>>Now there is stil one requirement is Godown-wise stocks primary (which is a club of secondary units) and secondary units. This was still not clear how to implement as there are 2 places where there is a opening stock qty.
>>
>>In short I need:
>>- Item Heirarchy
>
>This should tell you "which item contains which other item", right? Since this is a many-to-many relationship, you will need a separate table, which you might call ItemComponents, or ItemComposition, or something similar.
>
>Minimum fields:
>
>Parent (an item)
>Child (an item contained in Parent)
>Quantity

Actually we are talking about the same thing in diff. lang. <g> We call it Bill Of Material (BOM) here. For item heirarchy I have iParentsID in the Items Master itself. This Items Master is supposed to maintain the hierarchy by having iParentsID and another table BOM Master will again call Items Master for item codes as iItemID and it's qty.

>
>>- Multiple Units qty.
>
>Can't you convert to a single unit?

Yes they are finally converted to the main unit, but stocks are supposed to be maintained seperately also. I had thought about this as item heriarchy using it directly into the Items Master but it will so happen that the user will want to know about all item stocks for items hainvg say a packing of 1 kgs. So I thought a seperate DBF child to Items Master might do the job.

>
>>- BOM
>
>What does this TLA mean?

see above

>
>>- Godown-wise stock
>
>Can you explain what this is about?

Love to. This unit has a total stock say 500 units of those 100 units are at a suburb unit and 300 at another and so on. Also to complete the whole specs, out of these stock of 500 there are packing of them say in 1 set, 5 sets and 10 sets packs (again distributed in proportion to then units lying with each suburb units) thus the Secondary Units master. As each set has a BOM thus the BOM Master.

Now Godown wise stock has something similar but I have run out of steam literally with the specs <g>.