Microsoft Dynamics GP ERP application, formerly known as Great Plains Dynamics and eEnterprise is in our opinion good fit to the variety of business types: wholesale, retail, services, discrete manufacturing, healthcare, placement & recruiting, field services, pharmaceutical and research firms, shipping and receiving, logistics and warehouse management, and this list is not complete list, feel free to check your case study with us.
As this Corporate ERP and MRP application is dedicated to mid-size business, you may find it difficult to implement, especially when your current Dynamics GP Reseller is small CPA oriented organization and they probably do not have advanced technical expertise in such Dynamics GP related technologies as Great Plains Dexterity customizations and programming, eConnect ecommerce integration coding, Integration Manager advanced ODBC queries and ongoing integrations mapping and scheduling, barcoding and barcode scanners programming and upload to GP, advanced reporting, such as Crystal Reports based on complex SQL Server Stored procedures and Views. Let's review typical implementation failure directions:
1. GP Data Conversion. If you are very sensitive to historical data conversion, especially in General Ledger, let's say for current open fiscal year 2009, and if you are migrating from QuickBooks, or other small business accounting package, then you need to come through several test GL transactions monthly imports in Dynamics GP Integration Manager, likely in Test company images, before you are comfortable to plug in and perform production company GL data conversion. This exercise is typically done via exporting GL transactions from QB to comma delimited file, then this file is imported into custom table in SQL Server company database, then you create two SQL Views to fit GL transaction Header and Lines. Then, you create advanced ODBC Queries in IM and try your integration. Here you should expect reasonable number of iterations, as such dismaying problems as missing account in GL are normal. You should not expect every Dynamics GP VAR to carry expertise for such reasonably complex exercise. And if you got this Corporate ERP failure scenario, do not give up, ask for second opinion. The other pitfalls with GP historical data conversion are related to the attempt of SQL programmers to move data directly to GP Open and Historical tables, this is not recommended. Instead, you should consider moving transactions in Integration Manager (or via eConnect routine) to Work GP batches, and then post these batches into history with appropriate dates
2. Unsuccessful GP Customizations. This may happen, when your Dynamics GP Partner is trying to expose you to their Dexterity developers learning curve. Dex is semi proprietary programming tool, which theoretically is unlimited with Great Plains modifications and new business logic creation. In fact, traditional Add-ons are programmed in Dexterity. However, at the same time Dex requires several years of programming experience, prior to Dexterity developer could begin to participate in reliable project coding. If you are facing GP Dexterity modification project, please check first with your Dynamics GP Technology Partner on the level of their Dex developers expertise
3. GP Data Integration failures. Here we are talking about failed Barcode, eCommerce eConnect integrations. Again, you might be too demanding to your generically selected Dynamics GP consultants
4. eConnect programming limbo. DP ecommerce SDK eConnect is reasonably friendly to Microsoft Visual Studio C# or VB programmer, however it still requires some exposure to GP architecture. You should understand the fact that eConnect works with master records, such as Customer, Vendor, Employee, GL Account, and Work Transactions and Batches. eConnect doesn't have batch posting functionality, if you are looking for that, consider Alba Spectrum Posting Server
5. Dynamics GP Upgrade and Service Pack dependency. If you got Great Plains implementation or version update problem, you should be conservative and stay away from the opinions that new service pack will resolve all your problems. GP patch application and upgrade should be planned. Here you have to review your Dynamics GP system. Do you have Dynamics ISV add-ons modules? Do you have modified reports? In you have ongoing or real time legacy business system integration, you should probably consider version upgrade in test environment to see if you can remap your integration and it works with new Dynamics GP versions (current version is GP 10.0)
6. EDI Integration. Electronic Document Interchange is often considered as something very complex and as such that it requires EDI mapping add-on. In our opinion, if you are not ready to invest in luxury EDI mapping solution for GP, you can do simple SQL EDI file reading or SQL formatted Select statement export
7. Failing Crystal Reporting. Here you may expect the problem of rows duplication and incorrect summary. These problems are typically attributed to deploying CR design wizards, or in other words to learning curve of Crystal Report designer
8. Great Plains Accounting for DOS, Windows and Mac support. This archaic Corporate ERP application was also designed and supported by Great Plains Software and after GPS was acquired by Microsoft (Business Solutions), GPA support was retired in the year 2000. We are happy to give you USA nationwide Great Plains Accounting support service. Please, respect our consultants training and experience level as we have to support you, having GPA technical support archived database in hand only and we cannot redirect your question to Microsoft Business Solutions a s this Small Business Corporate ERP is no longer supported
9. Intellisol Advanced POP migration to Great Plains PO. At the end of the 20th century Great Plains Consultants were lifetime observing how long time Great Plains ISV began and finished its failure: Intellisol Software from Australia, who even paid for transferring their office to Fargo, ND. If you are still deploying Intellisol APOP, please consider to come through migration tool on Great Plains version 7.5
10. For Dynamics GP country side businesses. If you are facing technology issues, such as Customization, Integration, Reporting, Upgrade, we should be able to help you via web session, plus if necessary by visiting you to establish good relations
11. How to get help? Please call us: 1-866-528-0577, 1-630-961-5918, help@albaspectrum.com We speak English, Spanish, Portuguese, Chinese, Russian. Feel free to call us to get second opinion to recover your failed Dynamics GP Great Plains installation and implementation
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
