Hi SPISLGAL,

When printing the Item Valuation report with a date earlier than today, the report relies on transactions being in the history file. Essentially in your case, if you printed the report as of Sept 30, 2008, the report would take the current valuation and subtract out all historical transactions with a date later than Sept 30 to arrive at the total. If any of the historical transactions are missing, this could result with an incorrect back-dated valuation.

If you preview the IC Transaction History report for a particular date range (say Sept 1-30/2008, or Oct 1-31/2008), you can select the 'GL Summary' option to see the GL activity for all transactions during that month. Compare this against the Net Changes in the GL for that period and see if you find differences.

Perhaps also print a Source Journal report in Ledger for that period and all IC-related source codes to see if this matches the IC History amounts.

Deleting items could have ramifications but I can't say for sure, as it depends on the state of the data and what else has happened.

Adagio does allow deleting items that don't have any quantities or costs, but it is typically inadvisable to do so when the item could exist in IC History or other application data that integrates to IC, such as OrderEntry, Invoices or SalesAnalysis. In has been suggested elsewhere on this forum that a better way is to use the Adagio IC Toolkit (a separate program from Dakota Software) to merge all items together (that would be deleted) into a single item record. This would have the benefit of not deleting anything and also cleaning up the item list.

Do you (or anyone else reading this thread) have any suggestions as to what the correct behaviour of the Delete Items function should have, and what other preventions are in place? Should there be a search in all other integrated databases like OE, SA, IN and other to ensure it doesn't exist, no matter slow that would be? Other thoughts, such as removing the Delete button?