Microsoft Dynamics GP is hosted in MS SQL Server 2008/2005/2000, or if your Great Plains Dynamics license is for MSDE (light version of Microsoft SQL Server 2000) or SQL Select (2005). This fact allows you to deploy your DBA and SQL data fixing skills, however please be very conservative as records in GP tables are interrelated and you potentially can cause serious damage and data integrity disruption.
Out of the box Great Plains version 10.0, 9.0, 8.0 should be considered as very stable and reliable, so we assume that if you suspect that your GP data is now corrupt and requires recovery – likely the reason is one of these three: batch posting interruption, custom external integration (including GP data conversion and migration from legacy accounting application), Dexterity customization errors. We would like to give you some guidelines on how to approach Great Plains Data corruption:
1. Restore from recent backup. Cool features of MS SQL Server 2005, 2008 and even 2000 allow you to restore Dynamics GP database up to the specific moment of time (if you are doing transaction log backup and your backup scenario is adequate to your disaster data recovery requirements). Taking into consideration the fact, that Great Plains is serving to mid-size and in some cases smaller businesses – you could consider approach, when you are restoring from full backup of the previous business day
2. Batch Recovery. Here you should ask user, who got Batch posting limbo to log off and then log in back. In logging in user should get the message about batch posting interruption with opening Batch Recovery screen. Here you have to read your options – either click fix the batch (if you do not see batch editing is required message) or go to reviewing batch transactions and editing them accordingly. If editing is required, please open the batch and print Batch Edit Report. In our experience, the most complicated batch recovery cases are – when you are posting PM Computer Checks and US Payroll Checks. If these are your cases, please read further Dynamics GP tables structure: SY00500 (in Company DB) and SY00800 (in Dynamics DB)
3. If the cases described above are not yours… Please, consider Check Links procedure: Microsoft Dynamics GP->Tools->Maintenance->Check Links. Then simply select your module and table groups, for example Financials and Account Master tables. If Check Links doesn’t do the job, try to make a further research on what is going on in your Dynamics GP records. Great Plains tables structure could be found in Tools->Resource Description->Tables, then find your table of suspicion and look at its records
4. If you feel that you need Dynamics GP consultant help, please call your Great Plains Guru, or if you do not have one, consider calling to Great Plains Resellers in your area or who are familiar with your industry. Feel free to call us: 1-866-528-0577, help@albaspectrum.com
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
