Andrew Karasev

Microsoft Dynamics GP 10.0 Implementation - traditional ERP approach

Great Plains, as it was formerly known, became part of Microsoft Dynamics family of ERP products in September 2005 together with Navision, Solomon, Axapta and MS CRM.  Interesting enough – the association of Dynamics with former name of Great Plains Software Dynamics – this MRP was predecessor of Microsoft Great Plains.  Nowadays ERP implementation has several phases

Let’s briefly review them one-by-one:

1. Business Processes mapping.  First question is selection of the next ERP.  If Microsoft Dynamics GP fits to your current business processes and has good room for future improvement either with GP standard set of modules or with GP third party extensions, or even custom programming, modification, integration and reporting.  If these questions are answered to the favor of GP capabilities, let’s go to the next phase.  Typically BP mapping is done by MBS partner in your area, who will be your official VAR of records with Microsoft
2. License purchasing.  Microsoft Business Solutions sells GP licenses via certified GP partner network.  You can either call Microsoft directly or select your local, regional or global GP partner, based on your organization market positioning and size.  It is important to say, that in US GP customers are required to be in good standing with so-called annual enhancement program, which usually is from 16 to 25% of GP list price.  The lower end will give you free new version reg key and CDs, the high end will give you unlimited number of cases with Microsoft Business Solutions technical support
3. Data Conversion and “massage”.  Typical scenario is the one, where you switch from legacy accounting system to GP.  Data migration has several levels of complexity, the easier way you choose – the better.  The simplest way to convert your legacy ERP data is master records migration and GL beginning balances entry.  Master records are typically referred as General Ledger accounts, customers, vendors, employees, etc.  If you think that you need historical transactions to be migrated – think about the migration cost, as it is not an easy routine.  GP developers will need to analyze your legacy database, export your historical ERP data in chosen modules, massage it and then deploy either GP Integration Manager or direct SQL scripting to bring data to newly installed and configured Great Plains
4. User Training.  It is typically done in parallel with data conversion.  ERP user training is typically performed by your MBS partner and it is usually customized to your business processes
5. Going live.  Good and recommended scenario is when you maintain one month two ERP in parallel – legacy and new GP
6. Ongoing support.  As it typically happens, you will discover new horizons and needs: reporting, new ideas on custom programming, data integration with your other databases and ERP components to name a few

Article Tags: Microsoft Dynamics

Source: Free Articles from ArticlesFactory.com

ABOUT THE AUTHOR