Sage 100

Customer at 4.4 pu5 is trying to change all items to standard costing. Printed the 13-page Valuation Change Register then said yes to update. It ran for almost two hours until they ended the task. In recreating it in a test company, it says it is recalculating item history and is going through all years and periods. Why is it recalculating history? Has it always done this??

Probably only with 4.40 with the new ability to print the TB using historical or current standard costs. They do realize they can't just change their standard costs whenever they feel like it now, don't they?

Yes, but they were changing items at average TO standard. Why does it need to recalculate history - it doesn't change the cost of prior transactions - what is it updating?

Beats the heck out of me, but the motto of 4.4 and higher seems to be ""let's bloat up everything in Inventory"" - Physical Count screen now takes forever to load, conversion takes forever, renumber takes forever...

And bringing IM to the business framework was supposed to be good, yes? While there are nice features, the limitations are frustrating...

This is the perfect thread I was looking for, as I had a customer complain to me today about the recalculating item history task that runs as each item goes through the valuation change.  If there is a developer who can explain WHY the Item history recalculations take place, then I can explain to the customer why this is a necessary task for this utility.  I've been around long enough to know that way long ago changing the valuation and standard cost fields didn't have the right restrictions on them in the past and that the IM rewrite incorporated more rules (but for the better!).  When I look at what the Recalc Item History utility does when you run it on its own it updates multiple files:  

I'm sure that, for example, if you change the valuation from Average to Standard, and if there is a difference in cost between Average and Standard, then I can understand why the recalc history task goes into action.  I'm guessing that is why .. in case there is a cost change.  And possibly because the utility isn't going to check to see if there is a cost change between the old and new valuation so it just wholesale runs the recalc task on each item to ensure item history integrity in the other history data files. 

------------------------------
Jane Scanlan
Partner
Next Level Manufacturing Consulting Group
------------------------------

Original Message:
Sent: 11-30-2011 13:58
From: Therese Logeais
Subject: Customer at 4.4 pu5 is trying to change all items

And bringing IM to the business framework was supposed to be good, yes? While there are nice features, the limitations are frustrating...