After doing upgrades, all DIC came back with no errors. I started to do my daily work, but could not go past trying to create a batch. Once I select new after selecting invoices in AP, an error message comes up.

Error Message: Error adding record to Payables Batch Control, record already exists.

I am at batch number 8865 however when I say OK to the error message it comes back with another error message stating that it cannot write to a low numbered batch like 18.

Error Message: Error writing to the batch 18

I executed the HotFix thinking that that would help but that didn't work.

Can anyone help?

Hi Ishana,

The Payables 9.2A upgrade did not change the batches structure, thus nothing was converted in this area. We are not aware of any problems with batches, so I wonder if this problem may have pre-existed the conversion.

The values for the Next Batch numbers for each batch type are stored in the Company Profile. To investigate, you could point GridView at the data and the Payables 9.2A Company Profile table, and the fields for 'Next Inv Batch #', 'Next Manual Check #', and 'Next Adj Batch #'. If you find that these values already exist in the Payables batch control file, then the data is out of sync. Attempting to create a new batch would give the reported error because the 'Next batch #' is already in the control file and should not be in a normal data set.

Has Year End Processing been done, and was there an expectation that batch and posting numbers should have been reset to 1 and the batch control files cleared? If so, maybe the batch control file was locked on the server and not cleared.

Did you/they have to restore data from a backup? If so, was previous data cleared out before the restoration was performed? Not clearing out old data prior to a restore is a common reason for data being out of sync.

You'll need to determine the state of the data versus what it is expected to be before resolution suggestions can be made. Perhaps files need to be cleared/removed/restored. Perhaps GridView Read/Write is necessary to edit the Next Batch numbers. And so on.

The problem did not exist pre upgrade. Period ends are done but not year end because they did not want duplicate batch numbers in history. No data was restored pre or post upgrade.

I will check the grid view reports as suggested and see if what you are saying exists and then I will get back to you.

Hi Ishana

This is almost always corrupt data - the batch control file.

Run Data Integrity and let us know if Rebuild fixes the problem. Sometimes it does, but not always.

Steve

Hi Steve,

A DIC was done but it returned with no errors.

The company had never done a year end, once I did this I was able to create a batch. I couldn't replicate the problem and had to go to collect a back up as their's was too large to be emailed.

Thanks for all the help.