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:
- PM10000 Transaction work
- PM10300 Payment Work.
- PM10400 Manual Payment work.
- PM20000 Transaction Open.
- PM30200 Transaction History.
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.
https://support.microsoft.com/en-us/help/852064/how-to-continue-a-check-run-that-was-interrupted-in-payables-managemen
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.
- PM00400 - You will want to look at the DCSTATUS to determine where the Key Record sees the document should be in.
- 1 = Work
- 2 = Open
- 3 = History.
- Once you determine this, you can see what transaction tables have a record for the transactions in the batch. You can use a statement like the following:
- Transaction Batch.
select * from PM10000 where bachnumb = 'Batch name here'
select * from PM20000 where bachnumb = 'Batch name here'
select * from PM30200 where bachnumb = 'Batch name here'
- Check Batch
select * from PM10300 where bachnumb = 'Batch name here'
select * from PM10400 where bachnumb = 'Batch name here'
select * from PM20000 where bachnumb = 'Batch name here'
select * from PM30200 where bachnumb = 'Batch name here'
- This should tell you where the duplicate is. Once you determine which record is the duplicate, you can remove that from SQL and then remove the batch if there are no other transaction in the batch.
- If there are additional transactions in the batch, each one will need to be reviewed.
- You will also want to verify that these transactions updated your GL. Also your Bank Rec if it is a Check Run.
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
