Dynamics Community Forum Thread Details

A save operation on table "PM_Transaction_Open' has created a duplicate key

We are using ver 9.0. A single invoice in a payables batch was posted . The
batch did not appear to post and said go to batch recovery. In batch
recovery the status showed as Posting Interrupted and said "A save operation
on table "PM_Transaction_Open' has created a duplicate key ". Running batch
recovery did not work. Check links was then run and then when batch recovery
was run a Payables Transaction Posting Journal was automatically printed.
The posting journal says "This transaction already has been posted. This
transaction contains errors. It won't be posted " The transaction appears to
be correct and the proper entries have been posted to the GL and the AP
Vendor.

The batch could not be deleted or posted. Eventually we tried to edit the
batch by changing the invoice # and the amount of the transaction to 0. When
this was done the batch could then be posted.

Now however when you do an inquiry on the vendor it gives an error "The stored procedure
createSQLTmpTable returned the following results: DBMS: 2627, Great Plains 0.

Any suggestions as to what should be done next ??

Hi Suresh,

Please note that Microsoft does not support GP 9.0 anymore.

With regard to the error that you are receiving ,this error is caused by a duplicate transaction existing in more than one table (WORK, OPEN & HISTORY) and is usually caused by a posting interruption.

The situation is discussed in the following blog articles.

blogs.msdn.com/.../identifying-duplicate-transactions.aspx

blogs.msdn.com/.../the-stored-procedure-createsqltmptable-returned-the-following-results-dbms-12-exceptions.aspx

After creating a backup of the company data, use the script from the first blog article to identify the duplicate transactions and check what the correct state for the transaction is... unposted (WORK), posted (OPEN), Fully applied (HISTORY) and then you can use SQL to directly remove the duplicate records.

Quick Links