web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / current amount not equ...
Microsoft Dynamics GP (Archived)

current amount not equal to zero in rm30101

(0) ShareShare
ReportReport
Posted on by Saif Esmail Mohammed 215

Hi Everyone,

I've removed the paid receivable documents last year and recently i found that one of the documents that has been removed is having a balance amount in rm30101 while all GP is not supposed to move the documents unless they're fully paid!! because of this issue i'm having a wrong balance in the HTAB report.

My question is:

1) Under what situation a partially applied debit document can be removed from rm20101 to rm30101 while using the "Remove Paid Documents" utitlity?

2) How do i correct the issue? (updating the tables from backent should be the last option).

Regards,

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Saif Esmail Mohammed Profile Picture
    Saif Esmail Mohammed 215 on at
    RE: current amount not equal to zero in rm30101

    Hi Everyone,

    Thanks a lot for your kind help. I've verified the records in the DB and they seems to look like any other record (not corrupted). I had tried check links and reconciliation earlier but no luck.

    Finally I had to do it from back end by transferring the records from

    RM30101 to  RM20101 and from RM30301 to RM10101 then i applied the amount and removed it back via the "remove paid transaction" utility.

    Thanks again.

    Regards,

  • Suggested answer
    sandipdjadhav Profile Picture
    sandipdjadhav 18,306 on at
    RE: current amount not equal to zero in rm30101

    Saif,

    Have you run checklink and reconciliation? It may rectify this issue.

    Thanks

    Sandip

  • Suggested answer
    Tristan Clores Profile Picture
    Tristan Clores 2,812 on at
    RE: current amount not equal to zero in rm30101

    Hi Saif,

    Interruptions at the time the Paid Transaction Removal routine can be the possible cause of this or the transaction in question is corrupted already - hence the reason it moved to the RM30101.

    I recommend checking the RM20201 and RM30201 for any apply information on the transaction in question.  Sum up the apply amounts.

    Aside from using SQL, you can try the RM Transaction Unapply tool from PSTL to move the transaction from HIST to OPEN.

    Please let me know if you have further questions.

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

News and Announcements

Join experts in person to explore low code and AI agents at the Power Platform Community Conference sponsored by Microsoft

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

Congratulations to the September Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans