Hi Val,
How about the GL Transaction report within Payables? That one really is the key here, because the report is based on the same file that is about to be retrieved into Ledger. This will also tell us if there are any other transactions from AP wanting to be retrieve, such as system checks or invoices.
Also, was any consolidation performed after printing the GL Transaction report. Just wondering...
It is possible to remove the APGLBTCH file and 'start again'. However, if you are able to print the GL Transaction report (sorted by journal entry), this would give you an indication of which transactions were about to be retrieved into Ledger. This report (in conjunction with AP posting journals and revaluation journals) can help in making sure the journal entry batch you'll have to enter in Ledger isn't missing anything or duplicated.
- Make a backup of your data; I'd recommend doing all your data, using the File/Backup from either Payables or Ledger. Just in case anything unexpected happens.
- Print the GL Transaction report to paper or a Word document.
- Rename (not delete) the APGLBTCH data file that exists in your data directory. This will remove the file, and posting again in AP will recreate it.
- Do the journal entry batch in Ledger.
-------
This of course will help out this time, but the error you received could possibly happen again. Let us know about the questions at the top so that we can help determine what the cause is and prevent this from re-occuring.