Smart questions
Smart answers
Smart people
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Member Login

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips now!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

Join Tek-Tips
*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

LINK TO THIS FORUM!

Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.
Just copy and paste the
code below into your site.

Partner With Us!

"Best Of Breed" Forums Add Stickiness To Your Site
Partner Button
(Download This Button Today!)

Feedback

"...It is good to know that there are groups such as this willing to share knowledge in this money driven economy..."

Geography

Where in the world do Tek-Tips members come from?
Borvik (Programmer)
1 May 12 11:13
I'm trying to determine HOW to solve the problem - though I've managed to identify what the problem is (down to the trx).

We are receiving the error "Cannot insert duplicate key row in object 'dbo.RM30101' with unique index AK4RM30101'."  Followed by: "The stored procedure rmPaidTransactionRemoval returned the following results: DBMS: 2601, Microsoft Dynamics GP: 0."

Based on the index AK4RM30101 (RMDTYPAL, DOCNUMBR) I figured it was a duplicate document number.

Running:

CODE

SELECT a.rmdtypal, a.docnumbr, b.rmdtypal, b.docnumbr
FROM RM20101 a
  INNER JOIN RM30101 b ON (a.rmdtypal = b.rmdtypal) AND (a.docnumbr = b.docnumbr)
Yielded just a single result (the duplicates).

Pulling all the fields for those documents, from their respective tables I found that BOTH are supposed to be valid.

Searching only suggested I modify the document number with a suffix, though event after I did that I was still unable to pull up the document in RM20101 in Cash Receipts Entry because it was "posted".

More searching suggested something to do with RM00401 and DCSTATUS (0: Reserved, 1: Work, 2: Open, 3: History), and it is showing a value of 2.

The customer numbers on these are different as are the method of payments, dates, and values.

How should I go about fixing this error?
Borvik (Programmer)
3 May 12 10:36
Any ideas? Anyone?
VictoriaYudin (IS/IT--Management)
4 May 12 8:35
I have never run into this issue before...from what you are describing, you have two transactions with the same doc type and doc number, which should never happen in GP.  Fixing this will most likely involve changing the doc number for one of these in all the related tables, which could be a lot.  The hard part of that will be that it's not called RMDTYPAL and DOCNUMBR in all those tables.  If you have support available from Microsoft, I would recommend talking to GP Support about the best way to fix this.  

Victoria Yudin
Dynamics GP MVP 2005 - 2012
Use Crystal Reports and SSRS with GP:
http://www.GPReportsViewer.com/gpreports.html
blog: http://victoriayudin.com

Borvik (Programmer)
8 May 12 9:41
No, unfortunately we don't have support from Microsoft. Just the most basic stuff to get us the software updates.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close