|
|
 |
|
Day end critical error - cannot create AP or JC batchIn most ACCPAC Plus batch systems, including Accounts Payable and Job Costing, there are three elements or components controlling batch creation - the global file, batch control file and the physical batch files. If these three for some reason go out of sync any attempt to create a batch, by IR or from within the system itself, will probably result in a critical error. The files could be out of sync because of file corruption but more often this happens when data is restored without deleting the old or corrupted data first. For example, AP Invoice batches have been created up to batch 250. For some reason the user decides to restore a backup of AP where the last invoice batch created was 248. The batch control which was restored has record of batches up to 248 and the global file says that the next batch to be created is 249 but the files for batches 249 and 250 already exist in the data set. When a day-end is now run in IR it will look in the AP global file and based on the data IR will attempt to create batch 249. This will result in a critical error. To correct, restore the data before the day end was run. Check the batch control file in AP (or JC) and then check that only the files recorded and shown as open in these systems actually exist in the data set. The batch files for AP invoice batches are named API nnnnH.DAT (batch header) and API nnnnD.DAT (batch detail) where nnnn is the batch number. In job costing the file is JCCT nnnn. Delete any files which should not be there.
|
|
|
