Skip to main content

Notifications

Announcements

No record found.

Finance | Project Operations, Human Resources, ...
Suggested answer

Why REMITTANCE remains in PM20100 table

Posted on by 75,730

I was pulled in to move a couple of AP documents that were fully paid but were still in the open apply table(PM20100). I deleted those records and ran check links and they moved to history. Looking back at the PM20100 there are almost 2,400 records and the KEYSOURC value in all of them is REMITTANCE. Would there be any harm in deleting them?

Categories:
  • Richard Wheeler Profile Picture
    Richard Wheeler 75,730 on at
    RE: Why REMITTANCE remains in PM20100 table

    Thanks for chiming in on this Brandon. I will wait for the final update.

  • Hokuminaria Profile Picture
    Hokuminaria 2,950 on at
    RE: Why REMITTANCE remains in PM20100 table

    Hey Richard,

    I took a look at the data and the problem appears to be the APFRMAPLYAMT and ActualApplyToAmount columns in the PM30300 table. They are 0.00. These should be the apply amounts. I believe this is the problem.

    Hira, who is the case owner of the case above should have an update for you shortly with a script to test correcting this.

    I hope this helps!

    Thank you!

    Brandon | Microsoft Support Engineer.

  • Richard Wheeler Profile Picture
    Richard Wheeler 75,730 on at
    RE: Why REMITTANCE remains in PM20100 table

    Thanks for your response Brandon. In this case there was an interruption in posting. This has resulted in the amount remaining being $1,000, which is correct, on the vendor inquiry screen but a value of $1,093.19 in the AP HATB. I have opened a case to resolve this and have sent over the results of the AllPayables script. In case you are interested the case number is 2303290030002519.

  • Hokuminaria Profile Picture
    Hokuminaria 2,950 on at
    RE: Why REMITTANCE remains in PM20100 table

    Hey Richard,

    The PM20100 is the remittance table. I know it has apply in the name but it has nothing to do with the apply records.

    This table just holds what was applied and previously applied. It is not the apply table. The apply tables are the PM10200 and PM30300. The PM20100 recrds are deleted once they are printed on the next check.

    There is no harm in deleting the records in the table. Just note, they will not print on the next check to show what was previously applied.

    The most common cause for documents not moving to history is these records. If they exist and the posting process was interrupted, it will stop them from moving to history until you delete them.

    I hope this helps!

    Thank you!

    Brandon | Microsoft Support Engineer.

  • Richard Wheeler Profile Picture
    Richard Wheeler 75,730 on at
    RE: Why REMITTANCE remains in PM20100 table

    In this case there was a posting interruption and records that should have been removed were not.  This was preventing these two invoices from moving to history. I was simply curious as to why there were almost 2,400 records with a value of REMITTANCE for KEYSOURC.

  • Suggested answer
    DAnny3211 Profile Picture
    DAnny3211 9,272 Super User 2024 Season 1 on at
    RE: Why REMITTANCE remains in PM20100 table

    hi

    Deleting records from the PM20100 table can have serious consequences and should be done with caution. The PM20100 table contains payment-related information for Accounts Payable, and deleting records from this table can cause a loss of data that may affect other modules in Dynamics GP.

    Additionally, the KEYSOURC value being REMITTANCE indicates that these records are related to payments received from a vendor, and deleting them may impact your ability to track payment history and vendor balances accurately.

    Before deleting any records, it's important to understand the reason for their existence in the PM20100 table. You may want to consult with a Dynamics GP expert or your organization's Dynamics GP support team to ensure that it is safe to delete these records.

    It's also a good practice to create a backup of your Dynamics GP database before making any significant changes, including deleting records from tables. This will allow you to restore the database in case anything goes wrong.

    DAniele

  • Suggested answer
    Joseph Markovich Profile Picture
    Joseph Markovich 3,900 on at
    RE: Why REMITTANCE remains in PM20100 table

    Hi Richard-

    Microsoft has a nice article explaining the whole reason for the records in this table.

    community.dynamics.com/.../faq-open-apply-table-pm20100-in-payables-management

    Joe

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,269 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,198 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Product updates

Dynamics 365 release plans