A payables batch is stuck in batch recovery. When attempting to recover we get the message:
A save operation on Table PM_Transaction_Open has created a duplicate key.
Please advise.
Thanks
A payables batch is stuck in batch recovery. When attempting to recover we get the message:
A save operation on Table PM_Transaction_Open has created a duplicate key.
Please advise.
Thanks
Hello Nrpacct,
My name is Brandon. I am a support Engineer on the Microsoft GP Team and will address your question.
This error tells us you have a duplicated in the PM Open Table. When we get a duplicate error, what it refers to is there is record in more than one of our Transaction Tables. These tables are:
GP expects a record in only one of these tables.
Now, depending if this was a Transaction or a Check batch will determine what tables you need to look at.
If this was a Check batch, you should be able to clean up the issue with the following KB. If the problematic batch is a check batch, please try the KB below in test and determine if it resolves your issue.
If it was an invoice batch, you will need to review all the tables for the transaction to see where they sit and remove the duplicate record with SQL. Below is a brief overview of the table you will need to review.
We have additional scripting that can help us locate the duplicates if you would like to create a support case and have us take a look. We might be able to address multiple transactions in the batch as well if the batch has multiple transactions and duplicated.
I hope this helps!
Brandon Jarrett | Microsoft Support Engineer
As suggested this will require SSMS. Here is what you can try first:
1) Backup company database
2) In SSMS DELETE PM00400
3) IN GP Maintenance Check Links -> Purchasing insert Payables History and Payables Transaction Logical tables
4) Try to recover batch now
Do this while no one else is in GP. Let us know if this works. If not, then are other steps to correct this.
Unfortunately, this is not something that can be resolved thru forums. Someone needs to remote connect to your SQL server and fix that. If you can allow remote connection, I can assist. Just message me directly.
André Arnaud de Cal...
291,791
Super User 2024 Season 2
Martin Dráb
230,488
Most Valuable Professional
nmaenpaa
101,156