Sage 100

v2016 Std PU2 - Client is irritated that lines are displaying in inventory valuation when there is zero on hand and zero value displaying. I thought perhaps it was a linger lot value of a extended decimal value but the culprit turns out to be a small value in the total warehouse value field in the IM_itemwarehouse table. Of course, this value is not accessible via VI. Can this field be hacked in the data dictionary and if so, can someone explain the hack? I just need it for short while to import a zero value. TIA

Jeff - Fyi - be careful 1) File -> Run -> Syzcon 2) call ""*dict/maint 3) browse to the IM folder -> browse to IM_ItemWarehouse and select 4) click on the 'Data Elements' tab 5) Under Data Elements, scroll down to 'TotalWarehouseValue' and double click 6) On the Element Description dialogue box, click the 'Custom Info' button - 7) On the 'Data Elements Descriptions' dialogue box, uncheck 'Read Only' 8 ) click Accept and back out - the field should now be available in VI Good Luck! - Randy

Also, as I am sure you are aware, your import of zero values only addresses the symptom. Not that it does not need corrected, but the underlying problem is still there. i.e. how does this value not tie correctly with valuation?

What file should I back up first.

Yes, I do realize that the code will not be modified to remedy this on a long term basis. This is very similar to lots not disappearing when the quantity is zero but there are a few tenths of a cent in value remaining. Really, there should be a period end process that reads through the two files for zero quantities with value remaining and zero that field out.

I am wondering if the problem is not even more general than that... If they do not tie when they should be zero, how can we trust them when they shouldn't be zero... I hate these kinds of problems. Backup ... looks like providex.ddf is the only file really modified, but I recommend zipping up all the providex.* files in the Mas90 folder just to be safe.