- The problem was down to corruption where the PO was on both the work and open tables;
- There was more than just two POs;
- The problem also affected receipts.
Rather than trying to identify the problems manually, I wrote a SQL script which would identify all POs and Receipts which were on both the Work and Open tables:
CREATE TABLE #POCHECK( PONUMBER VARCHAR(20) ,POPRCTNM VARCHAR(20) ,CHCKDGIT INT ,DCSTATUS INT ) GO INSERT INTO #POCHECK (PONUMBER,POPRCTNM,CHCKDGIT,DCSTATUS) --VALUES (SELECT PONUMBER,'',1,1 FROM POP10100) GO INSERT INTO #POCHECK (PONUMBER,POPRCTNM,CHCKDGIT,DCSTATUS) --VALUES (SELECT PONUMBER,'',1,3 FROM POP30100) GO INSERT INTO #POCHECK (PONUMBER,POPRCTNM,CHCKDGIT,DCSTATUS) --VALUES (SELECT '',POPRCTNM,1,1 FROM POP10300) GO INSERT INTO #POCHECK (PONUMBER,POPRCTNM,CHCKDGIT,DCSTATUS) --VALUES (SELECT '',POPRCTNM,1,3 FROM POP30300) GO SELECT PONUMBER ,POPRCTNM ,SUM(CHCKDGIT) AS DCCOUNT FROM #POCHECK GROUP BY PONUMBER,POPRCTNM HAVING SUM(CHCKDGIT) > 1 GO DROP TABLE #POCHECK GO
After we used the script to identify the corrupt orders, it was a case of going through the returned records and correcting errors.
In the previous two posts, I stepped through the installation and configuration of SSRS. To deploy the Microsoft Dynamics GP SSRS reports to the SSRS server there is one last piece of configuration which needs to be completed.
There is a setting in the web.config file which needs to be added for the reports to deploy successfully. I have previously blogged about that setting here. The only change in the path will be the version number in the folder name will be higher.
Once you have completed that step you can then move onto deploying the SSRS reports in Dynamics GP; this post was written on Dynamics GP 2010 R2, but the process for deploying them is the same in Dynamics GP 2015.
In the learn something new everyday category, the first Dexterity game was written back in 1999 by David Musgrave of Winthrop Development Consultants.
David has full details of the game and a link to the download on his new blog
I was just browsing the Packt Publishing website (as you do) and found that there is a new book about Microsoft Dynamics GP being released next month.
Real-world Business Intelligence with Microsoft Dynamics GP by Dynamics GP MVPs Belinda Allen and Mark Polino:
In the last post, I stepped through the installation of SSRS. As I mentioned in that post, I prefer to do the configuration separately, as I have had problems with the automatic configuration.
To configure SSRS, launch Reporting Services Configuration Manager from the Windows Start screen.
The first window launched is the Reporting Services Configuration Connection one; ensure the Server Name is correct and that the Report Server Instance is the one to be configured and click Connect:
Part of the reason for posting this, is that I have had a few conversations with prospects looking to move to a new ERP who have asked about the future of Dynamics GP and quoting competitors who have talked about doubts of its long term longevity.
This is all FUD (fear, uncertainty and doubt) relating back to the Project Green of 2007/2008 which was a plan to Microsoft to unify their ERPs into one product. It is also a plan that was abandoned back in 2008, but the fact it existed at one point is still used being used by competitors to try to blacken the name and future of Dynamics GP.
As you can see from the roadmap, above, there are plans for fairly rapid releases of Dynamics GP which include much new functionality (including a rewritten Web Client in HTML5 after the 2015 R2 release).
The Convergence conference also saw an announcement that Microsoft Dynamics GP 2015 R2 was due in late May or early June. As the RTM came out at the start of December 2014, this would align with the discussed 6 month release schedule.
Microsoft will soon be releasing details on the new features available in Microsoft Dynamics GP 2015 R2, so keep an eye out for that.