Microsoft Dynamics GP ERP and MRP application should fit to the majority of businesses in USA, Canada, Spanish speaking South America, UK, Australia, New Zealand, South East Asia. However this is not a tiny software application and requires professionally handled Sales cycle, Modules Selection, Integration and data conversion mapping, potential custom add-ons programming or existing Dynamics GP ISV add-on purchasing and deployment.
If your Great Plains Implementation failed the first time, it is probably due to inefficient communication between your original initial Dynamics GP Partner. Sometimes your initial Dynamics GP VAR underestimates your challenging required business processes automations, where they may lack required in-depth Dynamics GP programming expertise. If by whatever reason you got false start with Great Plains Dynamics implementation, user training, custom integration, please consider to ask for second opinion and see if you can recover, as it is always unpleasant to go for second investment into another Corporate ERP or MRP platform. In this small publication we would like to give you Dynamics GP implementation recovery highlights:
1. Great Plains Integrations with Legacy Systems, such as non Microsoft based various Sales Order Processing systems: Oracle, PHP/MySQL, Linux. In other cases you could find the problem with Electronic Document Interchange or EDI mapping in Dynamics GP. If you are facing required Text Reports/Exports from Legacy DB preprocessing needs, prior to import these documents with Great Plains Integration Manager module. Dynamics GP Integration problems are one of the most common implementation impediments, and you should not always blame your Great Plains VAR for “failing”, as GP integration coding is not required expertise for Great Plains Reseller
2. Dynamics GP Customizations. Typical failing scenario is when you asked your Great Plains Partner to spec Dexterity customization for your firm and they went over budget with multiple bugs and required data fixes. And again, Dexterity programming is something optional for Microsoft Certified Partner, or even for Microsoft Gold Certified Partner. Dex programming departments are typically found in Dynamics GP Source Code Partners, who specializes in Dex software development and who are often subcontracted by regular Dynamics GP partners
3. Great Plains Reports. This is also very typical problem, especially if you are forcing your Great Plains VAR to design complex Crystal Report, where you would like to see data from several GP modules, something like Sales commission report, based on the Sold and Paid Invoices (SOP Module) with delivered Orders (Purchase Order Processing), popular complex Bill of Lading or Consignment scenarios
4. Consider to give us a call: 1-866-528-0577, help@albaspectrum.com We specialize in Dynamics GP implementation recovery, complex Dexterity customizations, Integration Manager, eConnect, ecommerce integration with GP, advanced Great Plains Reporting
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
