
The standard cost rollup process is ungainly at best. So far we have a manual process to recalculate all the levels in each site. Our two factories share assemblies and materials so the costs are similar.
Does anyone on 2012 R3 have any tips, techniques or code to make the process easier and help work around problems in costing as they are found?
Thanks in advance!
Konrad
*This post is locked for comments
I have the same question (0)Nobody ever answered so I thought I would document a bit of what we did to address the problem.
The largest problems involved both identifying obsolete product and addressing the huge number of warning and hard error messages sent to the infolog during the costing. With 50k plus infolog messages just dividing up the work and trying to figure out what REALLY mattered is a difficult issue. Feeds from the CAD system with many new uncosted parts contribute greatly as well. With limited time and staff the concern is focused on what we make not have made or to be made at some time in the future.
So a partial solution was to add error logging to the roll process done by level. A new table to trap the errors and flatten the messages to yes no flags was created. Each record in the table was keyed by the costing run id, costing version, item and site. Fields from InventTable were added to help sort and determine if the warning or hard error was relevant. Likewise the last InventTrans date and creation date for the InventTable were added. Two message fields were added to trap the messages that caused the cancel.
Logic was added to test the warnings and dates to set a flags that said the errors were ok to ignore.
Finally a form was created to view the results in grid format so the items that needed attention could be addressed before the next level was costed. Various queries allow the review of items without BOMs, items without Routes, items without costs and so on to be reviewed.
One final benefit is that the added table provides a go to place for review of costing activity.
Hopefully this is helpful.
Konrad