Since the Service Pack to IC 8.1C (110713), the Item Valuation Report is giving us an error.

"Error Floating point overflow occured when attempting to append record to I/C Valuation Report Temp File".

See .jpg attached.

Hi, Susan,

Have you checked to ensure that data passes integrity? If not, please do.

I notice that you are printing a backdated Summary report. Do you receive the same error (or another) when printing a Detail report or when using today's date.

Also, I only see one of the two print window tabs in your screenshot. Are there any values in the Sort by and Location from/to range fields (other than 'blank' thru Z's) on the Sort by/Ranges tab? If so, what happens if you change the range values to, say, another item or location or to the complete range?

Integrity check runs through without errors.

The error only occurs when I date it back to March 31, 2011 which is the last day of our last fiscal year. After the error, the report completes, however, it's showing almost $20,000 in residual costs, that I know for sure was not there as of March 31, 2011.

Sort by item number starting at first and ending at the last item.

After day end today, I checked the Inventory balance in Ledger and compared it to the Item Valuation Report. Ledger was up $1.14. Yeah!

Then I dated the Item Valuation Report back to July 31 and compared it to the Inventory balance in Ledger on July 31 and Ledger is down over $29,000.

Then I dated the Item Valuation Report back to June 30 and compared it to the Inventory balance in Ledger on June 30 and Ledger is down over $16,000.

Then I dated the Item Valuation Report back to May 31 and compared it to the Inventory balance in Ledger on May 31 and Ledger is up over $21,000.

Then I dated the Item Valuation Report back to April 30 and compared it to the Inventory balance in Ledger on April 30 and it crashed "Error Floating point overflow occured when attempting to append record to I/C Valuation Report Temp File".

I tried dating the Item Valuation Report back further (i.e. March 31) but it also crashes.

I was hoping for a fix to the problem of not being able to back date the Item Valuation report. Without back dating, it makes it very difficult to balance IC to Ledger and provide the accountant with a report to show they balance as of year end. There seems to be ongoing major problems with this report related to back dating. As it stands now, I don't think anyone should attempt to back date the Item Valuation report if they are wanting accurate results. There are also some crazy residuals reported with back dating that don't make any sense.

Please let me know if this is being looked at and if and when it will be fixed.

Can someone at Softrak let me know if you acknowledge that back dating IC Item Valuation is not working and let me know when to expect a fix?

Susan:

While I can't say positively that it's not broken (this report has been a major thorn ever since the date cut off was introduced) I have not yet found a problem with the current release in testing similar to what you describe.

Can you replicate the problem in sample data?

Softrak can't fix what they can't confirm is broken. Likely this problem is specific to your database or how you use Adagio. Unfortunaltely tracking such a unique problem down is virtually impossible in any forum.

Hi, Susan,

There are no known problems with the report at this time.

It doesn't even almost work when back dating on mine. Back date to the last day of the previous month and I get 2 pages of residuals that are not actually there. Also the balance is way off from Ledger. Did anyone try it and if so, did it balance with Ledger?

What sample data can I use to test this? The sample data in IC and Ledger both say the fiscal year is 2007 when you open it in Ledger and there are a number of batches to retrieve and post. To test this, I need some current data where the day end has been done and all batches retrieved and posted in Ledger.