Notifications
Announcements
No record found.
After deploying the SSRS reports in GP18.02.1060, the SQL Server Reporting Services Reports Deployment Status report shows that the version number is 12.00.1295 for the modules including Purchase Order Processing. Is the SSRS report version number correct? What is the explanation for not increasing the SSRS reports version number with the GP version number?
We want to use the Historical Received Not Invoiced report, which was not correct in GP2015 per Microsoft. Has this report been fixed and is accurate in GP 18.02.1060?
Thank you,
Li and Olga
Hi Li & Olga,
Wehre do you get this version number 12.00.1295 for the deployed SSRS reports ? I do know that the internal SSRS report version haven't changed in a while, and I think this is because Microsoft hadn't updated the definitions of those reports in a while..
EDIT: I guess you pulled the report version info from the DYNAMICS..syDeployedReports table ? as on my brand new 18.2 setup it shows the same version 12.00.1295, as it has for a long time (even on my GP 2015 & 2016 setups).
PS: what makes you believe that the POP report is not working ?
PPS: there are actually 12 deployed reports that show a version more recent than 12.00.1295.. According to this, the above mentioned report has been updated last time on GP 2015 (14.00.618)
Hi Beat,
Thank you for sharing your insight again with us.
You are right the Historical Received Not Invoice (HRNI) report has version of 14.00.618. As of April 2018, the SSRS HRNI report has a know bug according to the following link:
community.dynamics.com/.../877690
If the version is still at 12.xx or 14:xx for the SSRS reports, I am not sure if they have been updated beyond GP2015. Maybe in GP18.2 the backend data source for the SSRS NRNI report has been updated but The report (template) itself has not?
you're correct..
I would guess that based on the other forum post the underlying SP for this report had been fixed in some 2018R2 release or service pack.
When opening this report in SSRS Report Builder 3.0, the underlying datasource is a stored proc called 'seeHistReceivednotInvoiced' . This SP is over 750 lines long (when properly formatted) and there is not a single comment in it to indicate what the historical changes are (which Microsoft may track separately from the code).
The only way to know would be to pull the same SP from an older GP instance prior to 2018R2 and compare the 2 source codes.
Thank you for pointing out the stored procedure (SP) name. I scripted the SP from GP2015 14.00.1230 and GP18.2.1060 into files. Then compared the two files. As far as I can see, the only difference was
“P.POSTATUS not in (5,6)’ and pol.POLNESTA not in (5,6)”
had been changed to
“p.POSTATUS not in (6) and pol.POLNESTA not in (6)”.
’p’ referes to POP10100 and ‘pol’ is POP10110. Status ‘5’ is ‘closed’ and ‘6’ is ‘canceled’.
My accountant still think this SSRS report differs from her expected GL number. I am not sure if the discrepancy is caused by the data, or there is still incorrect logic in the SSRS report. It is hard to say without spending time going through the data.
Thank you for helping us understand this SSRS report better.
Li
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.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Martin Dráb 664 Most Valuable Professional
André Arnaud de Cal... 522 Super User 2025 Season 2
Sohaib Cheema 303 User Group Leader
