Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

Manual payment only in GL with only orphan records on PM

(0) ShareShare
ReportReport
Posted on by

Hi,

Sorry in advance for any grammar issue, not native english.

I am new on this company and I am assigned to this issue. I've previously used GP as a consultant but I've never seen this issue before.

A user did tried to do manual payment during one night (he reported frecuent disconnections). The result of this is 5 journal entries on GL (GL20000) but none or part of them on PM. Checked them and those transactions only appear in tables PM10200 and PM30600.

The journals appear on the Jounal Entry Inquiry window but when I try to check the Source Document, the "Transaction history does not exist for this transaction".

So far I've been instructed to delete the orphan records on the PM tables that I mentioned earlier. So Financial users make a journal entry correcting the duplicate ones.

I want to be sure if this is the correct way.

Thanks in advance.

Javier Sandoval.

*This post is locked for comments

  • Community Member Profile Picture
    on at
    RE: Manual payment only in GL with only orphan records on PM

    Hi Victoria,

    Thank you very much!!

    Great fan, btw.

    Cheers,

    Javier S.

  • Verified answer
    Victoria Yudin Profile Picture
    22,766 on at
    RE: Manual payment only in GL with only orphan records on PM

    Hi Javier,

    Yes, this sounds like the correct fix to me. A few observations:

    • You can also run Check Links on the Purchasing series, that should remove the orphaned records in the PM tables. Check Links will also check other related tables that you might not be checking and may find other orphaned records that you don't know about yet.
    • I would investigate the "frequent disconnections" to minimize the chance of this happening on the future. For example, I often see companies using Dynamics GP over a VPN, where the GP application is installed on someone's laptop and they are working from another location, connecting over a VPN to SQL server in the office. This is a bad idea and can easily cause many data issues.
    • I would also recommend to the users that if they are experiencing "frequent disconnections", don't go posting transactions - it will usually cause a lot of work for others trying to clean this up, as you are seeing in this case. Instead, they should contact someone to help figure out why they are getting disconnected and address that.

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

Daivat Vartak – Community Spotlight

We are honored to recognize Daivat Vartak as our March 2025 Community…

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Kudos to the February Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 292,865 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 231,723 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156 Moderator

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans