Hi Board! Looking good, like the upgrade!

 

My FMS13 app logs product coming off the end of our production line. We have a simple BOM table, with Parent_Stockcode, BOM_Level_Stockcode, Quantity, UOM, price.

 

Each record belongs to a Parent stockcode as a child. Many childs build up the BOM list. The BOM list is added to by selecting a Child Stock Code from a 'Products' table and entering the details.

 

Up to now, I have just summed the total BOM cost and when a complete product comes off the line, FM grabs the latest BOM cost from that SUM and copies it into a static text field. So the cost at that point is recorded.

 

What I'd like to do  now is attach the complete list of BOM details to each product. So we can look at the cost over a period of time. BOM's change and quantities change because of yeild of materials at the beginning.

 

I want some advise to see if I'm doing it 'correctly' or sensibly, at least.

I have a COUNT field which goes to the related BOM table and finds how many lines of BOM there are. It grabs a timecode $, sets the product Serial Number as a $, then moves into a LOOP - which goes to the first line of an on-Layout Portal of associated BOM's, copies the Child Stockcode details, then moves to the BOM_Logging table on the layout and copies those details across, associating that first line of the standard BOM, with the individual Parent product. It dumps the Var's, setting them as "", then the loop starts again after adding a 1 to a COUNT $.

Then it goes to Line 2 of the BOM, copies that, pastes it into the Product BOM_Logging table and so on.

When $Count=$BOM_Line_Total_COUNT, the script exits.

I am currently running this script through all of last years and this years products to associate our output with BOM.

 

Is copying from a Portal into another Portal in this way, line by line, the right approach? It is taking days to go through 200K records, but running the script on one record seems to be fairly quick. Is there a better way? Should I set all of the BOM details into $'s first, then move to the BOM_Logging table and paste them, or is moving from one portal to another and back not a problem?

This is a logging operation and doesn't need to provide any sort of 'MRP' viability of manufacture, as perhaps a more complicated BOM system might.

Thank you for your help.

The script is running very quickly today....

 

So I guess my question is somewhat moot. Perhaps it is not very elegant,  but it works.

Should I be using 'Repeating Variables'? I'm not sure how they work or if this would be a correct application thereof.

Thanks!