If you have Dynamics GP Great Plains implemented in your organization, and especially if you are on old version of Great Plains Dynamics or even GPA for DOS or Windows – now it is time, considering current recession, to think about getting reasonable support
In our opinion, the best support for GP system, which is already in production and which requires just an occasional maintenance: data repair, integration, version upgrade, possible customization – is remote support from nationwide call center and Great Plains Dexterity Software Development Factory. In this small publication we would like to describe typical support scenarios:
1. Adding new Great Plains Company. This work is typically done in Dynamics GP Utilities, however there are steps, which should be done in Microsoft SQL queries. When you create new company, it is common practice to transfer such objects, as chart of accounts, vendors, customers, employees, multicurrency setting, user access. Great Plains Consultant typically back up your old company, restores it into newly created company and then cleans all transactions and summaries for accounts, customers, vendors. These tasks should be done by Dynamics GP consultant and we do not recommend you to do them internally
2. Changing Chart of Accounts. As time goes, you may decide to change your account segments for current and historical transactions. This is possible, however it is again SQL precise query. To give you some technology background – each Great Plains account has integer index value, and when you record GL transaction – you are not recording the full account, but rather just the index. This is why you can theoretically change account segment values for historical transaction without compromising data integrity
3. Great Plains batch recovery. In GP you have batch recovery window, where you can unlock the batch, stuck in Posting (when GP user workstation crashed, for example). However there are scenarios, when you need SQL data repair and surgery – especially when you are selecting AP checks and trying to print them with the crash
4. Dynamics GP Version Upgrade. Current version 10.0 as well as earlier versions: 9.0, 8.0, 7.5, 7.0, 6.0. 5.5, 5.0, 4.0, GPA for DOS: 9.5, 9.2, 9.1 – are Service Pack sensitive and it is not a good idea to try to upgrade Great Plains Dynamics from just CD
5. FRx support. Typical FRx support cases are Sysdata folder security rights, incorrect DSN in FRx Systdata and on your local workstation, corrupt GL indexes, incorrect IO data folder, etc. All these problems could be resolved remotely via web session
6. Moving Great Plains System to new server. Here you have special procedure and SQL scripts to accomplish the job, according to Microsoft Business Solutions recommendations
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
