Microsoft Great Plains Implementation Checklist

Microsoft Dynamics GP and former Great Plains are popular ERP products They should be evaluated in two ways: from the perspective of generic MRP and specific accounting applications (technical platforms, historical attempts to automate specific verticals and horizontals for specific industries, database platform,etc.). We will first review the general ERP application implementation check list, and then go into detail:

Data conversion and manipulation. ERP upgrades are characterized by a variety of scenarios. For example, you can use a simple approach to enter the initial balances. Or, you can take a more sophisticated approach and convert historical data.

o Modules selection. Microsoft Dynamics GP’s specific processes should be considered in the decision-making process. GP can be used for general accounting such as GL (general ledger), AR (accounting payable), AP (accounting receivable), INV, FDA POP SOP discrete manufacturing field service non-profit government organizations

Platform Technology. Here, we can see rapid and very successful evolution. Great Plains Software Dynamics used to be GPS Dexterity. Microsoft is now moving the ERP to MS Office and enabling GP to MS Visual Studio via tools such as Extender, eConnect or even Microsoft CRM SDK Development and Microsoft CRM Integration module with Great Plains.

o Integration Scenarios. eConnect, the most important player, is GP Integration Manager. This module is also under improvement of performance (deploying more eConnect technology and logic). Consider integration options through MS SQL Server Stored Procedures. Legacy MS Dexterity is also capable of doing the job. You should however consider the fate of Dexterity as well as the availability and cost for Dex programmers.

Microsoft Dynamics GP Pool If you are planning to implement GP at your company, then you will need to select a Microsoft Dynamics GP VAR.

Leave a Reply

Your email address will not be published. Required fields are marked *