If this gets screwed up you get duplicate PM_Key errors.The fix is easy enough, run checklinks on Payables and increase the next voucher number in Payables setup.
But we ran into a scenario where this kept recurring and it seemed to be related to an integration but we couldn’t pin it down. We sent the details off to Microsoft and they figured it out.
GP manages the next voucher and econnect also manages the next number. What seems to have been happening is:
- A user would reserve an voucher number in AP
- An econnect based integration would bring in more than 1,000 payables transactions.
- The user would discard their voucher and release the voucher number
- GP would then reset the next voucher number to the discarded voucher resulting in duplicate PM Keys and our error.
Microsoft doesn’t have a great fix, don’t run large econnect integrations while processing AP or keep AP integrations below 1,000 records.
We chose to manage AP voucher numbers ourselves via econnect and not use the econnect process to get the next voucher number.