Announcements
I have an AP check fully applied to 5 regular AP invoices (not from POP). A user tried to void the check which is dated about 2 years ago but not yet reconciled. When they hit process they get the DBMS 2627 error. Once that happens, one of the invoices is copied from PM30200 to PM20000 (exists in both tables). The distribution record is moved from PM30600 to PM10100 (no longer exists in history). All the other information for check and invoices appears to stay in the history tables. I do get the duplicate error when using the Transaction by Vendor Inquiry window since the one invoice is in open and history. When I look at the check and drill back into the apply window, the voucher number is showing for this particular invoice but not the document number. Running checklinks brings that document number back but everything else stays as is.
I have run checklinks on the entire Purchasing series. I have cleaned out activity tables and restarted SQL. I have deleted and re-created the PM Keys table. I remove the extra record in the PM20000 table, copy the distributions back to history, delete the distributions from open, and run checklinks again. Of course, I no longer get the duplicate key error in the inquiry window but as soon as I try to void the payment, it all goes back to what is described above. I tried looking through each table in open and history to make sure it wasn't in open and was in history.
Anything else to try? Accounting wants to void the check rather than create offsetting transactions because they are worried about audit issues.
Thank you
I looked at the PM00400 table. The document status is history until I try to void the check applied to it. It then changes to open. After I delete the duplicate record from the PM20000 table and run checklinks, the document status goes back to history.
I did notice what looks like a duplicate voucher number for the payment being voided in the PM00400 table. I had to log off so I will check that out.
If this doesn't help me, then I will recommend accounting purchase a support case. I do not think they have any.
Thank you
Hey Stefanie,
If this continues to happen for a vendor, I recommend that a support case be created so we can dive into it.
Some of the troubleshooting steps.
For the void issue itself, the data will need to be reviewed to determine what needs to be changed to correct the duplicate. This is not something we can do in a forum question and would require a support case to request the data for the problem transaction for review.
There could also be stuck record in the void temp tables that might be causing this. I can't tell for sure without seeing the data. The whole solution relies on where the data sits.
If you would like us to look, please create a support case. We can likely have the duplicate error cleaned up in a matter of moments once we can see the data.
I hope this helps!
Thank you!
Brandon | Microsoft Support Engineer.
Hi Brandon,
Yes, I followed or attempted to follow, the instructions about finding duplicates. I did mention that I found a duplicate and removed it but it keeps happening with this vendor. It has actually happened on more than one document for this vendor. I also deleted and recreated the PM Keys table (PM00400) after removing the duplicate. I will check the document status in that table for this one transaction. Last night I also logged into the test company. The same transactions existed there and I was able to successfully void the check. Intercompany is enable and setup for the live company but not the test company. These transactions did not have intercompany though.
I have actually run a script to find all tables that had the voucher number column. I then checked all those tables (work, open, history) for this voucher. I didn't do any searches for the check that is being voided. Oh, I also checked the Apply to in the Open and History apply tables.
I feel like I was thorough but I am obviously missing something. I am wondering if I should move the data from test to live. I took a backup before voiding the check in test.
Hey Stefanie,
The DMBS 2627 means you have a duplicate. To correct this, you need to determine which transaction line is duplicated and remove the one that does not match the document status that the PM00400 believe the document is in. If the Distributions are duplicated as well those need to be removed as well from the table they should not be in.
Once you have cleaned up the duplicates, (Duplciate means a record in more than one transaction table for the transaction. It does not mean two of the same documents) then you should be able to void the document without issue.
If you would like assistance with this, please create a support request so we can see the data and provide steps to clear up the duplicates.
Below is the transaction flow for payables.
I hope this helps!
Brandon | Microsoft Support Engineer
André Arnaud de Cal... 291,359 Super User 2024 Season 2
Martin Dráb 230,370 Most Valuable Professional
nmaenpaa 101,156