Recreating Dynamics GP PM Historical Trial Balance Report in Crystal

Feb 24
09:47

2010

Andrew Karasev

Andrew Karasev

  • Share this article on Facebook
  • Share this article on Twitter
  • Share this article on Linkedin

We already released several small publications, where the progress of business logic replication was reported. As you may already realized - Great Plains Report Writer print outs are sort of difficult to export to Excel.

mediaimage
Crystal Reports at the same time are perfect in data export and reformatting.  The challenge of Historical Aging reports (both in Accounts Payable and Accounts Receivable modules) is complex business logic,Recreating Dynamics GP PM Historical Trial Balance Report in Crystal Articles which should be replicated in SQL Stored Procedure - it is very difficult to replicate this procedure without deep exposure to GP technical consulting and certifications in Dexterity and Dex source code programming.  At this point we are ready to announce good progress in AP Historical Trial Balance report replication:
1. Why Dynamics GP doesn't export Historical Aging report to Excel?  This question could be well addressed to Microsoft Business Solutions, as Great Plains Small Business Financials 9.0 or earlier versions was tuned to export this report directly to Excel, and customers, who migrated away from SBF to Microsoft Dynamics GP 10.0 reported disappointment about the lack of this feature in high-end Dynamics 
2. What are the challenges in SQL Stored Procedure, which is the base for Historical Trial Balance?  Consider several scenarios.  First - imagine you had historically Vendor invoice, which you decided to void few days after targeted aging date (in report).  This record, when voided will be sent to RM30200 table (as you may know, all PM transactions go there when they are completely applied or in our case voided).  If you would try to just do this small business logic passage in Crystal Report data expert wizard - please let us know and we will present you small pocket aquarium as the prize if you have success.  Second scenario - PM30200 (History document header), PM30300 (history apply to) tables have various fields with questionable meaning : DOCDATE, DATE1, GLPOSTDT, ApplyToGLPostDate, ApplyFromGLPostDate.  In suh situation, if you do not have access to Microsoft Dexterity source code programming - you may decide to give up
3. Product versus Solution.  If add-on is not ready to be implemented with clear instructions, we think that that product is still in the Solution phase
4. Please feel free to call us 1-866-528-0577, help@albaspectrum.com