Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / Reconcile to GL - Rece...
Microsoft Dynamics GP (Archived)

Reconcile to GL - Receivables Management

(0) ShareShare
ReportReport
Posted on by Community Member Microsoft Employee

Hi:

One of my customers is trying to run the Reconcile to GL feature of GP 10.0 to reconcile Receivables and they are having the following message:

I ran a trace using SQL Profiler and when the message appears was in the following process:

glGetRMTransactions.

this is a Dynamics Stored procedure (very long one) that get the RM transactions into temporary tables to do the reconciliation. It seems that there is something duplicated in the data for the date range that I selected. So far we determine which is the date range and the information of the index : TRXSORCE,DOCNMBR,RMDTYPAL,CUSTNUMBR.  the problem is that I can not run the stored procedure alone to review the data.  I need some guide here, please help!!!

 Here is the stored procedure (a link for a text file, it is too long to paste it here):

http://jumbofiles.com/juqhv2y92rhk

 

*This post is locked for comments

  • Verified answer
    Community Member Profile Picture
    Community Member Microsoft Employee on at
    Re: Reconcile to GL - Receivables Management

    I found out what was happening. We have 3 debit memo transactions without Batch Source nor Batch No, they were void. I checked the distributions and there are two sets of of distributions one set with date 01/04/2011 and second set with date 01/11/2011. I delete both sets and the message disappears.

    Jesus

  • Verified answer
    Community Member Profile Picture
    Community Member Microsoft Employee on at
    Re: Reconcile to GL - Receivables Management

    You have some data corruption in eithre the RM Transaction Open or RM History tables.

    I would query those tables and order the results by the fields you identify above to soo if there is any blank / missing data.

    If you could narrow down the error to a very short date range, then you could filter the query to transaction in this date range and look for duplicates.

    I'm pretty sure there are scripts available on customer/partnersource that will find duplicates. Search for them and see what you can find.

    Ian.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,280 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,214 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans