Sage 100

v2016 PU5 - In addition to the program leaving rounding values which you have to adjust quantities in then out, it appears that the same thing is happening in the item warehouse table. Client has about 60 records with zero QOH but having a warehouse value. Has anyone else experienced this? It could be the result of have a utility written which cleaned up my item cost table by zeroing out the cost if there were no QOH's but I neglected to look at the item warehouse table for similar issues. The end result is that I have zero qty and value lines printing on the inventory valuation report even though the parameter do not print zero cost lines is turned. A nagging problem that is pissing the client off. Thoughts?

I have an end user that regularly has several items that have an extension amount without a quantity on the inventory valuation report. The way I correct it is using a VI import to IM Transaction Entry. Export the relevant items to a file with item code. In VI assign a quantity = 1 and a cost of .01 and import to transaction entry and update. You then have a quantity on the valuation report. VI import again with a quantity = -1 and the cost equal to the new extension amount. I am reasonably sure @ChuckPeddy posted about this same issue a few months ago.

Since it sounds like they've already bypassed GL (with the previous utility), for 60 records, I'd probably DFDM the value away. For more, I would do a a script to set TotalWarehouseValue=0 where Qtys=0. Or to really live dangerously, you can modify the valuation report (what could go wrong?!?)

https://90minds-com.socialcast.com/messages/33991494

@JeffSchwenk you should use the Inventory Utility: Balance Inventory Quantity and Cost to clean up these stranded costs, and then Recalculate Item History after that. Until Sage permanently remedies this from happening, this utility is the best one to ensure that there is a good audit trail and that all needed files are updated.

@JaneScanlan - Report went from 27 pages to 14 pages, but there are still some zero lines appearing which indicate there is still some rogue $ in itemwarehouse with 0 QOH's... Getting closer.

From the release notes 2017.2:

That was also in the v2016 update. Not sure how it exactly impacts this client. maybe inventory transactions have been the root of their sorrow...

The fix won't correct existing problems in the inventory files, only (hopefully) stop it from happening again.