Target Date Mismatch Error
Years ago you could go down to the local post office and see the FBI's ten-most-wanted posters which were always titled "Be on the Look-out for:"; well we don't have 'ten', but here are three QuickBooks errors we are requesting that you 'look out for' and 'report' if you see them.
One such problem is: LVL_ERROR--Error: Verify Item: Item history Item Latest Target Date mismatch error. Item ID 117, expected value: 01/01/1901, found value: 05/22/2003. According to Intuit's Technical Support website (excerpt shown in the 'title illustration' for this article) they are “working to resolve this issue”. If you have experienced errors of this nature that prevent your QuickBooks file from completing the verify routine or back-up, please let us know by posting a comment to this article.
Another relatively new error is associated with the QuickBooks Enterprise Advanced Inventory "Row, Shelf or Bin" feature. When running a Verify, QuickBooks detects errors which report in the QBWin.log file as Error: Verify Target: Bin Location Does Not Belong to Site. While Technical Support has a routine for possible resolution of this error, that involves having to 'disable' the "Track Bin Locations within Inventory Sites (row, shelf or bin)" feature, they do not indicate any specific causes for this type of error. Once again, if you have experienced errors of this nature in your QuickBooks file, please let us know by posting a comment to this article.
An increasing number of users are also reporting Advanced Inventory errors in QuickBooks Enterprise that specify "Sum of item on item site table not match quantity on hand stored at item history table". Obviously whoever wrote this script for the reporting routine had some grammar issues having left out 'does' (table 'does' not match). Regardless of this grammar problem, the error occurs when the sum of the quantity of an item recorded in the item site table is not equal to the quantity on hand stored in the item 'parent' table. Intuit's Technical Support says this 'issue has been resolved in the latest release for QuickBooks Enterprise 13.0' however they don't specify which 'release' that is, and in fact that resolution was reported prior to the most recent release update. The problem is that I am seeing files with this problem submitted to me with increasing frequency, having seen three or four of these within just the last couple of weeks. So, if you have experienced these errors in your QuickBooks file, it would be very helpful if you would post a reply comment to this article.
We at Intuitive Accountant will strive to keep you aware of data file issues which are new, increasing in frequency, or which may pose substantial risks. Your assistance in providing valuable information as to variations or frequency of these errors can assist in researching potential resolutions.