I am experiencing an issue with Adagio 9.2A. We did a Year End and the batch numbers for Invoices and Manual Checks do not restart from 1.

Invoice Batches start from #2 and Manual Checks start from #3.

I did a Data Integrity on a back done before the year end and tried the process again Test Data and I got the same result.

Any assistance would be appreciated.

Dwaine:

Which version did you upgrade from?

There was an issue, many years ago, with orphan batch files being skipped but I thought that Softrak had added a process to the data integrity check that cleaned them up.

Someone who is very familiar with Adagio databases needs to take a look for orphan batch files and remove them. Your Adagio dealer should be bale to help you out.

Thanks for your reply. I think since data conversions to versions 8 and 9 we don't see the batchs in the Data anymore.

You can still see them in AP 9.2A. They'll be gone in AP 9.2B.

If Payables goes to create a batch, and the batch is already there, then the batch number is skipped.

Hi Dwaine,

You're right that the 9.x upgrade to some modules changed the batch structure in a way that meant you did not see individual files for the various batch types any longer but this did not happen for AP. I believe the AP move to 9.x was mainly to do with its Cloud readiness and the batch structure changes are coming later.

In the pre-year end backup, look for API0001?.xxx, APC0001?.xxx and APC0002?.xxx (where the I = Invoice batches, the C = Manual Check batches, the xxx = your specific data selector and the ? could be D, H or I. If you see them, give me a call and I'll give you the procedure to correct depending on how much work you've done since and how important the sequencing is to you.

Best, Pete

I thought the file conversion was across the board of modules, so Douglas you were initially correct about the orphan batch files; thank you.

From within the company Data Set I was able to remove the orphan batch files since Pete was able to help me identify them (I noticed the date modified on the files were old as well).

So I went through the following process:
Restored from backup,
Removed the orphan files
Did a Data Integrity (which was error free)
Created New Batches

End Result: Number sequence was correct.

Issue Resolved. . .

Thank you very much everyone!