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

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

Manual Payment missing after crash

(0) ShareShare
ReportReport
Posted on by

Hi,

One of our users was entering a Manual Payment in the Purchasing module. She had already hit the Apply button and chosen a vendor invoice to apply the payment to, but she had not yet hit the Post button. At that point the system crashed, so her process was interrupted. Now the vendor invoice shows a $0.00 unapplied amount remaining, as if it has been paid in full, but we can find no record of the manual payment anywhere else. It does not show up in Transactions By Vendor or Transaction By Document inquiry. It also does not show up when clicking the "Apply" button on the invoice.

Looking in the SQL database, we see that the Manual Payment is not in any of the following tables:
PM20000, PM30200, PM00400

However it is in:
PM10200 and PM20100

I have already tried running "Check Links" on the Payables Transaction Logical File and Payable History Logical File. This removed some distribution records related to the missing payment from PM00100, but didn't help the problem beyond that. I also tried running Reconcile on the vendor in question, no luck.

Anyone have any suggestions on how we can either re-create the missing Manual Payment info, or safely remove the orphaned Apply info so that we can create a new payment and apply it to this invoice?

Thanks,

Benjamin

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Community Member Profile Picture
    on at

    A quick fix would be to search for the applied document, and set its CURTRXAM back to what it should be. This field is the unapplied amount, once this is reset you will be able to enter a new payment and apply it. (I am assuming that the invoice is still in the Open table). Yes, you will still have orphaned apply records...these could be deleted once both transactions have moved to history. I assume from your text above that you are comfortable working in SQL to achieve the above. Backups of course first! This may not be your final resolution, but will get you started.

  • Verified answer
    Community Member Profile Picture
    on at

    Thanks Ian. Between your comments, and the suggestions from Leslie Vail here and here, I was able to get this back to normal. I ended up manually deleting the orphaned records from PM10200 and PM20100, then adjusting the CURTRXAM in PM20000 as you suggested.

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

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
Dan Liebl Profile Picture

Dan Liebl 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans