A save operation on table 'RM_OPEN' has created a duplicate key.

(0) Share

Report

Posted on by Romryan

To All,

Am having a receivable batch that cannot post.When you click post the batch progresses but at some point its stops and throws the batch to recovery window.

When I click more information before going to recovery window I can see the error "A save operation on table 'RM_OPEN' has created a duplicate key.".

The batch in the recovered window is rendered as posting interrupted.

I did my update sy00500 set mkdtopst=0,bchsttus=0 where bachnumb='yyyyyyyy' so that I can recover it.

I checked the transaction in the batch and I realized that some invoices had duplications in (RM10301 and RM20101) .I checked all the duplicates and I realized that they were all posted to GL (GL20000) so I went to table RM10301 and I cleared the duplicates since the had hit RM20101 and GL20000 and then run the reconcile to batches,debtor information and outstanding documents to all debtors.

I was left with my batch having only the transactions that had not posted.

When I try to post them the same error and batch is thrown to recovery again.

I went on and transferred transaction to a new batch and nothing changed.

Before I delete RM00401 and run check links to rebuild the table,is there anything I can do?

Kindly help.

RomRyan

*This post is locked for comments

I have the same question (0)

All responses (8)

Answers (0)

Romryan on at

Like (0)

Report

Any help please?

Was this reply helpful? Yes No
Jothi Krishnan N 1,895 on at

Like (0)

Report

Just giving some directions to identify the cause...

After clearing the duplicates, print the Batch Edit List and see if there is any error. If nothing, then...

Run the below script and then copy the result and run it again to see if you can find a duplicate entry somewhere. modify and/or add additional conditions as needed.

select 'select * from ' + object_name(object_id) + ' where docnumbr =''enter the Error Doc number here'' ' from sys.columns where name ='docnumbr'

Or

Move only one problem document to another new batch ( it will be easy to analyze the SQL trace)

Run SQL Profiler for SP Statement Starting/Completed and SP Starting/Completed and then either print Batch Edit list or just post the batch . Now note down all the tables traced and query those tables to see if you can find any duplicate entry.

Was this reply helpful? Yes No
Jothi Krishnan N 1,895 on at

Like (0)

Report

You can add the condition { object_name(object_id) like 'RM%' } to restrict it to RM tables only.

Was this reply helpful? Yes No
Maria Carrero 150 on at

Like (0)

Report

Hi,

Are you sure the documents in RM20101 are in GL20000 and these are not in RM10301?

If a document is in the 3 tables, you should delete from RM10301.

If the document is RM10301 and RM20101, but not in GL200000, you should delete in RM20101.

Was this reply helpful? Yes No
Suggested answer

Mahmoud Saadi 32,738 on at

Like (1)

Report

Get this resolved from the root, check David's article on Identifying Duplicate Transactions which results with duplicate key error.

Let us know if you need any further assistance,

Was this reply helpful? Yes No
Romryan on at

Like (0)

Report

I had Identified the duplicates and I removed them from the batches and I was left with the only documents in rm10301 and that are not in both gl20000 and rm20101.But this batch continues to give the same error.

Was this reply helpful? Yes No
Bill Campbell 12 on at

Like (0)

Report

Sorry, pretty simple question at this time in the analysis. But,

Do you have print of the Edit List - before you attempt to post?

If you print - even to screen - be sure to review for any errors in the data.

Also, you say that it only kicks the error when you post - if you move all the 'good' transactions to a differently named batch - does that make any difference?

Sorry to come so late to the thread and ask some similar questions, but I just wanted to see if anything made more sense to you.

Was this reply helpful? Yes No
Romryan on at

Like (0)

Report

Thanks Bill Campbell for your contribution.I am sorry I had not stated that I separated the local currency transactions from the foreign ones and I managed to post the local currency ones.But the foreign currency transactions are stubborn.When I print the edit list there are no errors everything seems to be okay.The server has been exuding slow response due to being bombarded by many resource consuming applications gp,mr,srss,smartconnect,IM and a third party payroll system until we migrated and dedicated GP to its own server.We though the batch posting issues came as a result of slow response from the server.Now batch issues are no more but I haven't been able to post this receivable batch.

Was this reply helpful? Yes No