Hi:
We tested updating to GP 18.2 (2019) from GP 2018 R2 in a separate environment and found that the A/P Historical Aged Trial Balances display transactions from three years ago despite the fact that those transactions were "paid" and are in A/P historical tables in SQL.
Is there a script that can be run to fix the A/P apply tables?
John
Hello John,
Please see the information below from the help menu which discuss what the option Document Date and GL Posting Date does when running the report.
Select Transactions For Report Using
Mark GL Posting Date or Document Date to determine the transactions that should appear on the report. This option is available only when you’re printing the Historical Aged Trial Balance.
The posting date might be different from the document date of the entered transactions. For example, assume you enter and post a transaction with January 15, 2007, as the document date and January 20, 2007, as the posting date. If you print a trial balance with a posting date range of January 20, 2007, to January 20, 2007, the transaction would be included on the report. If you print a trial balance report with a document date range of January 20, 2007, to January 20, 2007, the transaction wouldn’t be included on the report.
I hope this helps!
Brandon Jarrett | Microsoft Support Engineer.
If choosing by document date in both versions do you get the same erroneous results? If you pick one of these erroneous documents what is the GL posting date and what is the document date?
Hi All:
Thank you, for the quick responses!
Basically, I had already gone through the usual battery of troubleshooting steps. No dice.
The only thing that had made a huge difference since then is choosing G/L Posting Date instead of Document Date for "Select Transactions for Report Using".
So, when choosing G/L Posting Date instead of Document Date, the transactions from 2017 do not appear. That's good.
When choosing Document Date, which I think is unfortunately what the client does, data from 2017 appears.
Why in the world would that be?
John
I would ask if you run the same report with the exact same parameters in GP 2018 R2 do you get the same erroneous results? When you upgraded the reports dictionary were any errors reported?
Hello John,
Thank you for your question today!
Before any scripting should be done, you should review some of the Transaction to see what the actual issue is on the data. The HATB reports looks at the Apply Record and compares it the Transaction record to determine if it is fully applied. This also looks at the apply date to determine if and when it should drop off the report.
I would also recommend that you review your Report Options you are using. Are you maybe not excluding fully applied documents on the HATB report?
Once you have determined the actual issue why these are showing on the HATB report, you can then determine how to correct it based on the data.
One last thing, as you stated this is a test upgrade. If the data is fine in the tables, you could try synchronizing your Forms and Reports as i have seen these get out of synch during an upgrade and cause odd reporting issues. I have provided the KB's below for this.
850465 How to re-create the Reports.dic file in Microsoft Dynamics GP
support.microsoft.com/.../850465
951767 How to re-create the Forms.dic file in Microsoft Dynamics GP
support.microsoft.com/.../951767
I hope this helps!
Brandon Jarrett | Microsoft Support Engineer.
#1
André Arnaud de Cal...
291,622
Super User 2024 Season 2
#2
Martin Dráb
230,354
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
