Sage 100

Before I call Sage to ask them this vague question, I thought I'd bother you guys first. I have a client on 4.50.4 that runs the *UTL - Balance Inventory Quantity and Cost at least once a month and has tons of items that show up...many times, the same items over and over. These are typically FIFO raw materials that are components of BMs, and as they are entered in as Production Entries, they show as BI transactions just fine in history, but it appears that the IM_ItemCost table is not getting updated. Here's the kicker...I cannot duplicate the problem on my machine with their data. Has anyone else encountered this as a recurring issue with a customer before, and if so, was is data-related or environmental (bad workstation connection, etc.)?

What version is your machine running? I thought they had problems with that utility that wasn't resolved until a later PU in v4.5. Maybe you have the corrected version and they don't!

They are on PU5 and I am on PU3, so unless it was broken again in 4 or 5, I'm not sure why. I will look through the release notes again but focus on the utility instead of the BM notes.

I have two customers on 4.50 that have experienced cost table records that either never updated or went missing. I have still not found the cause. It appeared to correlate to the SP. I updated them to the latest SP and have not heard any more, until this week...

Great...so it's still happening on PU7?

I would use extreme caution when using this utility in the later releases as I don't believe that it takes into account the IM_TransactionHistory (IM5) QOH which is typically what the QOH is balanced to. First thing I would do is to run the replace embedded io script for CI, IM, SO and then the other modules for the production company. The balancing utiity is not using the same process as in the pre-migration program which does include the IM5 (TransactionHistory).Pick an item that keeps going OOB and run the 3 inventory reports (Stock Status, Valuation and Detail Transaction) for that item and whs. Hopefully all three reports will have the same ending value, depending on the outcome the older process of correcting the OOB condition may need to be used. From theree, Verify that there are no other installations of MAS90 in the current installation path, files improperly renamed (""copy of mas_abc"" or ""oldIM_ItemCost.m4p""), if present remove them from the shared path or store in a zip file. Next in troubleshooting, if there are any Mods or customizations in this install, temporarily disable them and see if the same results are recieved. Disabling the customizations and mods will affect all users and all companies so plan accordingly. When these things occur that cannot be replicated in another install with the same data I like to rule out possible causes starting with the least invasive. Hope this additional input helps lead you to a resolve.

Thank you for the detailed response Joan. I will look into these suggestions next.