Microsoft Dynamics GP Corporate ERP, formerly known also as Great Plains Dynamics, eEnterprise (please note that Great Plains Accounting for DOS, Windows and Mac is different legacy ERP application), is designed for mid-size businesses and it has plenty of functionality and the whole stack of technologies: Dexterity, MS SQL Server, MS Office Integration, SSRS, Integration Manager, eConnect, etc
Having said that - we would like you to expect certain level of commitment to implementation project from your management, including IT department. Also, sometimes you may be exposed to the situation when your Dynamics GP Partner is sort of introducing new Great Plains Consultant, or simply doesn't have sufficient expertise in your industry or project scale might be too challenging. In other words, combinations of factors, and if you are reading these lines, you probably are trying to understand how to recover your investment into Dynamics GP licenses and move on to the second opinion and Great Plains Implementation recovery. Let's try to analyze the most typical scenarios of Dynamics GP project failures and how to get out of there:
1. Failures scenarios. Probably the most often is the one, when you are forcing 100% data conversion to GP from your legacy Corporate ERP (Oracle Financials, Lawson, Epicor, QuickBooks, Accpac, MYOB, etc) - please, know that moving transactions to Dynamics GP Open and Historical tables: Sales Invoices, Purchase Orders, GL Transactions, Payroll, Customer Payments, etc., if you are not doing it via GP Integration Manager, but instead trying direct SQL insertion, is source of huge data validation and following corruption problems. Second scenario is when you are trying to customize GP screens and business logic too heavily, or use too many Dynamics GP ISV add-ons (they might conflict to each other if you toss too many into implementation). The third scenario is when you are trying to build too complex eConnect or Integration Manager integration and move transactions to GP in real time or in scheduled batch processing - here you are rather in the trap of your Dynamics GP Reseller learning curve, as IM and eConnect are extremely powerful, but they require Great Plains Partner commitment to the technologies. The fourth most typical case if when your Dynamics GP consultant is not too familiar with GP module (Manufacturing, Project Accounting, Field Services, Grant Management, Analytical Accounting, Multicurrency, etc), required for your industry. Next scenario is when you are doing old Great Plains Dynamics version upgrade and it fails due to such archaic GP add-ons as Intellisol APOP and Project Accounting - APOP has migration tool to Great Plains Purchase Order Processing module, however Intellisol Project Accounting should be considered to be redeployed on GP Project Accounting module, where object match requires discussions and decisions
2. The way out. We assume that you already tried to discuss the options with your local Great Plains Dynamics GP VAR, and now you should look for better expertise USA nationwide. You new provider could likely have satellite office in your state or business metro, but in our opinion this is not critical, as remote training, support is very simple via web sessions and phone conferences and if visit onsite is required - travel is reasonably cheap in the United States. If your problem is failed data conversion, feel free to get second opinion from the Dynamics GP Partner with GP Software Development Factory. If your problem is ecommerce, or barcode real time or batch mode integration, we are here to help you
3. Dynamics GP Implementation in International Environment. If you are multinational firm with offices overseas, please note that GP is localized officially for English Speaking countries, Quebec in French and Spanish Latin America (with some restrictions). If your subsidiary is located in Unicode compliant language country (China, Korea, Japan, Thailand, etc) - Great Plains Dexterity doesn't support Unicode at this time (and likely will never support). Plus local tax legislation compliance is very important, if you are in such region as Brazil, we do not really recommend you to force your Brazilian Portuguese speaking employees to implement GP, as Brazilian tax code is complex. Better approach is to deploy Corporate ERP coming from another brand name, SAP Business One for example, or stay with local ERP legacy application and try to consolidate it to your Corporate ERP Great Plains
4. How to get help? Please, feel free to call us: 1-866-528-0577, outside of USA: 1-630-961-5918 or email us help@albaspectrum.com We are very technical and real Dynamics GP Dexterity, SAP Business One SDK programming gurus. We have Great Plains Software Development Factory and could support unlimited Dynamics GP Customization and Programming needs. Plus we speak English, Chinese, Spanish, Portuguese, Russian, and not only as native speaking sales folks, but as real technical consultants. If you prefer skype: albaspectrum
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
