Hi gang,

I have searched the forum to find solutions to the following questions and can't seem to find anything similar:

GL: Adagio Ledger 9. A (140221):
DIC returned: Fiscal calendar 2013- setting for Prior Year Is Incorrect.
Fiscal calendar ••• 1error(s) found

AP: Adagio Payables 8. F (130826)
Matching record for Vendor VllOO transaction N SEP07VISA found but not matched to existing transaction

Matching record for Vendor 12677 transaction N Matching record for Vendor VllOO transactionIN Matching record for Vendor VllOO transaction N Matching record for Vendor VllOO transaction N Checking Matching Records....• 4 error(s) found


535 found but not matched to existing transaction. DEC1405 found but not matched to existing transaction. DEC2205 found but not matched to existing transaction. DEC2264 found but not matched to existing transaction.

Vendor N0120 transactionIN N02475216 computed balance -2,264.54 does not match stored balance 0.00
Vendor N0120 transactionIN N02475216 computed home balance -2,264.54 does not match stored home balance 0.00 Vendor N0120 balance outstanding Is 3,045.48 calculatedIs 780.94
Vendor N0120 home currency balance Is 3,045.48 calculatedIs 780.94 Checking Transactions ....•. 4 error{s) found

Vendor BElOO history transactionIN 90985494 computed balance 1,364.90 does not match stored balance o.oo
Vendor BElOO history transactionIN 90985495 computed balance -1,364.90 does not match stored balance 0.00 Vendor N0120 history transaction N N01927902 computed balance 1,456.46 does not match stored balance 0.00

Is there a hot fix I've missed?

Dawn:

There is a more current Hot Fix for Payables but it only fixes an EFT issue with CIBC.

I've never seen your GL problem before but the AP issue is common enough, typically due to a faulty network.

Back up your database and run the DIC and Rebuild functions. You may need to run DIC and Rebuild several times to clear all of the errors. Before going back to work after a successful rebuild you should check your data to make sure that the results of the rebuild are appropriate.

Hi,
so the client advises that their particular DIC error popped up back in 2012 and is on the forum under the subject heading: "Data Integrity Error - rebuild fixed incorrectly" so since the upgrade to the newer A/P, the errors that were reported in 2012 (and fixed back in 2012) have now reappeared only in the reverse. Their concern is that they may continue to manifest every time there is an upgrade.
Repair, Rebuild, or Re-enter mock data to fix vendor history?