I have a client who is reporting a DIC error - "Posted transaction file out of order". I used A+ DIC on the dataset with no errors being reported and after passing the data through FixIt, the error was not corrected. This is using Ledger 8.0. Any suggestion as to the problem, or could it be DIC reporting an erroneous message?

Hi Lars,

This is technically not an erroneous message being reported by the Adagio Ledger 8.0A integrity check. The GL Posted Transactions file needs to be sorted by a good number of fields, but the WSM integrity check only looks at the sort by acct/dept/period, which is what Adagio did prior to releasing version 8.0.

To accomodate the Unpost function (a new 8.0 feature not available in Plus GL), we require the GLPST to be sorted in a particular way, by more than 3 fields, rather than 'letting it go' in previous versions. An incorrectly sorted GLPST file did not cause processing errors, but it would cause inquiry screens to not display transactions in the expected order.

So your GL database is not 'corrupt' but neither is it 'correct'. This should not influence your processing, though it is possible it will affect Unposting if the unposted batch happens to contain an out-of-order transaction.

A soon-to-be-released PTF (I don't know exactly when) of Adagio Ledger will perform the re-sorting of the GLPST file using the Rebuild function of the Adagio integrity Check.