Microsoft Dynamics GP is successor of very popular mid-size and small business ERP and MRP application: Great Plains Dynamics and eEnterprise. Great Plains Dynamics Standard was in its time available on Pervasive SQL and Ctree DB platforms for the following versions: 7.5, 7.0, 6.0, 5.5, 5.0, 4.0 and earlier
The same versions of Great Plains Professional (known also as GP eEnterprise for versions 6.0, 7.0 and 7.5) were available for Microsoft SQL Server 2000, 7 or 6.5. If you are running your corporate ERP application on older Dynamics GP version, there should be respected reasons to stay with the version and probably now is a bit tough budget, which doesn’t allow to consider version upgrade and migration to Microsoft SQL Server 2008 or 2005 platforms. This small publication reviews typical services for older Great Plains versions:
1. Location Translation. This is when you are moving Great Plains on Ctree or Pervasive SQL / Btrieve to new Windows Server. On each user workstation you should translate the path from original (where Great Plains was installed likely in late 1990th) to new path (where you just moved your Dynamics folder with all the company folders in it). Location translation sometimes is complicated by the fact, that historically your Dynamics was translated multiple times and you now have no clue on how to clean up all these historical debris
2. US and Canadian Payroll Tax Update for Dynamics GP 8.0, 7.5, 6.0, 5.5, 5.0. if you are on Microsoft SQL Server 2000, 7.0 or even on Pervasive SQL 2000 or Ctree, with some restrictions you can still be up-to-date with your Payroll module State/provincial and local municipalities tax rates. Restrictions should be understood – Missouri for example changed tax calculation formulae in 2008, where Dynamics.DIC Dexterity code was updated in Microsoft Dynamics GP 10.0 and 9.0 service packs. These changes may happen in the future as well, but for the rest of us – it is probably fair to say that Tax rates are changing, but tax codes and formulas are staying conservatively
3. Great Plains Dynamics Standard on Pervasive SQL 2000 and Ctree data repair. Our favorite technique is Microsoft Access (as you normally do not expect Microsoft SQL Server 2000 Enterprise Manager or Microsoft SQL Server 2005 Management Studio to be installed on such networks). In MS Access you will need to familiarize yourself with ODBC linked tables approach
Dexterity Customization for Dynamics GP Evaluation Level Paper
When you are developer it is always a good idea to read technical manuals. But if you was just assigned to the IT team to decide if Dexterity is the right tool to customize your ERP application then first you need something which is in style of ‘easy reading papers’ or FAQ
Planning Dynamics GP Customization in Large Corporation
If you are reading this page then chances are high that you were not able to find ISV add-on and need customization project. Let’s talk about planning, quality assurance and future event such as version updates.
Dynamics GP Invoice Logo Attributed to Specific Company or Crossing the Borders of Three SOP Forms
Initial Great Plains Dynamics architecture had three SOP Invoice forms: Long, Short and Blank. Modern GP is popular in scenarios where you have more than three companies under one business entity umbrella
