User accidentally chose wrong bank for manual check entry. Checks are all entries of hand-written checks, not printed - 127 entries.
Can't copy batch to one with another bank. Could import a MC batch, but can't export one.

What would you suggest as the best way to create the file to import from the batch already there?
Client has Gridview and Crystal Reports for Adagio.

you can also e-mail me today at mrobbins@hickoryfirst.com

Hi Kate,

Because batches are stored in two separate data files (header and detail), GridView would not be the appropriate choice here. Crystal Reports for Adagio would be a logical choice.

As long as you are using Adagio Payables 6.8B, then import manual checks is available. My recommendation is to create a report using the APB68 tables (specific to open batches) and use both the Header and Detail tables (Details is the driving table). Put all the required Header fields to the left, and all Detail fields to the right. You can choose to use the 'H' and 'D' labels but this is not required. Remember to that you don't have to include all fields - you can set default values in the import process for fields that will be the same value for all checks (ie the bank code).

Hide the report header and page header sections. Export this report to an Excel file. You may have to look at the imported file to remove blank columns.

In Adagio Payables, create a template where the selected fields match those you included in your report. Set default values for any required fields you did not put in your report. You can also make the Header Character and Detail Character fields defaulted because you are using an Excel format. Set the format of the import to Excel in the template, and select the option for 'header fields on every record'. You can also choose 'verify before importing' if you wish.

Good luck!

Where do I get APB68 tables?

I find AP61A, APW65, APW68 but none of these works completely for all the fields.

Hi Kate,

Firstly, you should get the latest PTF for Adagio Payables; if not then you may not have the most up to date file that Crystal Reports for Adagio uses when APGLOB is the database selector.

When this is all set up correct, you should see tables called APB68 that only contain the batch files. If using APGLOB doesn't load these tables for you, does using ADAGIO.SSI as the database selector?

Check your report tables drive and within QRASP look for the table file QRTAPB68.QRW. If you do not have it, then that explains why it doesn't appear as a selection. This table is installed by Adagio Payables.

You should be able to use the AP61A table for reporting on batches (this is the table geared towards the Accpac Plus AP file layout, without the 'Adagio-only' data files).

QRTAPB68.QRW was installed in QRASP and in Softrak\System\QRASP\AP as part of the AP6.8B install but the tables are still not available.

I tried using your sample report but can't locate the tables it needs to run.

So I am trying it with AP61A tables, but with the P2IRSSI.cfg file added in Winnt\Crystal.

Tried various imports. The best I can do is Cash Invoice batches with details listed but missing the amounts and GL Accounts/Departments, and Payment batches with details showing 0 dollars and status of deleted. If I apply any detail in a payment transaction, I can save the transaction and go back in and apply the correct details. The process of saving seems to correct the "deleted" status.

Hi Kate,

Even though I sent you a new P2IRSSI.CFG file, it may not have been copied to the correct place, thus not fixing the problem you are having with using APGLOB as the database selector within Crystal, and recognizing the Batch tables.

Under Windows 2000 and XP, sometimes the system wants to look at C:\Documents and Settings\{user}\windows\crystal for this file, and sometimes it will look directly at C:\windows\crystal. This is completely Windows environment. Note that Adagio installation will put files in the correct place, but simply saving a sent file might not go to the right place.

Get the newest Adagio PTFs, as if the one for Payables doesn't install the newest P2IRSSI file, then I believe newer ones will (ie Order Entry). This file is common for all Adagio applications in working with Crystal Reports for Adagio.

For others reading this, we found that the problem with Crystal Reports not loading the AP batch tables was because there was a problem with the APGLOB.DAT data file. On other databases, using APGLOB as the database selector allowed all tables to be loaded.

For others reading this post, the reason why the imported batches did not apply correctly to the invoices was that the import template was defaulting the H and D record characters. I expected this to be OK, but it turns out it was not. When the H and D characters were added to the import file and template, the batch imported successfully with the payments properly applied.