This is unfortuantely one of the great failings of BOM and WO in Sage 100 ERP.  Not sure if this will ever be addressed. You MIGHT be able to do something with UDFs but I have not played around with it.

That is a bummer. No extended solutions of which you're aware either, eh?

Using UDF's might be problematic. I'd might have to script out some of that in order to make it all work right. I'll have to think that one through more, though.

Thanks for your feedback.

Lou

You can actually build something but it will take some work. Note that the ItemLotSerialTransactionHistory filie can be linked to the BOM ProductionHistory files linking the Production Number to the Entry Number. However the Entry Number in the Inventory table will have a P in front so you will need to use a formula. You could build an Access database that pulls all data into tables and then strips out the P and then builds a single data source table with all the information. This would give you what you need.

That makes perfect sense. My biggest fear, though, is that some of those tables are not on framework yet and if Sage suddenly switches them over, I'll have to redo the work during an upgrade. Not that it will be hugely problematic because the underlying logic wouldn't change.

Still thinking this through. Thanks for the heads up on the serial transaction history file. Since it already exists, I won't have to sandwich the info into some I/M file.

Lou

Here is your issue. The BOM production history table does not give you all of the serial numbers of the parent item, just the first one if you produce more than one item. To get all the serial numbers in the run you need the ItemLotSerialTransactionHistory table. By linking this with the BOM tables you should be able to get the data. Now you have not mentioned if you want a report or some sort of dataset that you can query.

Your concerns about the framework are unfounded if you are on Sage 100 ERP 2013 as both Inventory and BOM are on the framework. Nothing will change in the future.

Base line requirement demands a dataset I can query. After that, reports are incidental, even if I have to write them in Access or. . . .

I could have sworn that IM and BoM were still on the old file structures but it's been a very long time since I slogged around in them. Your comment is good news to me; makes it easier to work with. Thanks for the heads up.

I greatly appreciate your thoughts on this. I'll keep you posted on how this goes.

Lou

Hi Lou, did you ever find a solution for this?  I am looking for something similar.  Thanks!  

Never did but have not looked at the new Production Manager. that might have something

Unless you are doing a production entry for each serial #, there is no way to know which serial component goes with each serial # produced.  The data simply doesn't exist.