Microsoft Dynamics GP, formerly popular under Great Plains eEnterprise and Dynamics name, this ERP, MRP, Warehouse and Supply Chain Management application requires certain experience and often your industry knowledge.  Having said that, we expect that some of the local Dynamics GP implementations leave you under impression that your chosen Dynamics GP Reseller was in learning curve mode.  If you feel, that you need second opinion and would like to try guru level Great Plains consultant s and developers, in this small publication we offer Great Plains technology and implementation highlights:

1. Great Plains Architecture.  Dynamics GP is MS SQL Server based application.  If you tried it on MS SQL Server 2008 and Windows 2008 Server, chances are high that you got some issues with bullet proof security and you had to enable SQL port 1433, plus additional directory and shares level rights to your Windows users, especially if you are maintaining centralized Report.dic.  Also, you should have some understanding on Great Plains Dexterity architecture – chunks, dictionaries, Dynamics.set and Dex.ini files.  Most of the Dynamics GP ISV add-ons are coded in Dexterity, as Dex allows you seamless integration with GP user interface and it also creates custom tables in SQL Server company or Dynamics databases

2. Dynamics GP Data Conversion.  If you are migrating from legacy accounting, especially large accounting package: Oracle, PeopleSoft, SAP – often due to downsizing, you might be in the trap of over budgeting in Great Plains Data migration.  You should make a pause at some point and reconsider Data Massage and conversion strategy.  Large Corporate ERP applications carry huge amount of historical data and you should accommodate yourself and your IT management to the idea of limiting data conversion to GP and do not convert “All” history, but only something that is absolutely required.  If you are facing your legacy Corporate ERP access termination, please consider exporting “History” from your legacy ERP and importing it into MS SQL Server tables for potential future inquiry only and do not try to move Everything into Dynamics GP tables.  New Corporate ERP data conversion requires special philosophy and expectations management

3. Dynamics GP Customizations.  Here you also have to consider reasonable balance – try to review available core modules and see if your unique business logic could be implemented procedurally in existing GP functionality.  If you have too many exceptions and standard logic doesn’t fit, you might be trying to save too much on new Corporate ERP software licenses – try to think about Corporate ERP for larger organization, Microsoft Dynamics AX Axapta for example

4. Dynamics GP version upgrade.  Here you also have to do your homework.  Microsoft Business Solutions tries to release new version of it s Dynamics products every two years.  However if you try to upgrade your one-step-behind version of Dynamics GP immediately – you may be at risk to be placed in Beta testing clientele pool.  And to our knowledge a lot of quick fixes and known issues are patched the next few month or first half a year of new version life

5. Dynamics GP and Industry knowledge.  Here you have to try to avoid risk of Dynamics GP consultant not being familiar with your industry niche requirements.  It is important in GP modules selection as well as in user training, business processes mapping and data conversion

6. Local versus Regional or even Nationwide Dynamics GP support.  If your organization is located in rural area and your business model is very traditional: wholesale or retail, simple service, healthcare, manufacturing, you may prefer to appeal to local Dynamics GP Reseller, who will do basic initial service in selling your Dynamics GP licenses, installing the system with CPA type of user training.  However if you are claiming to be industry leader in high-tech, or pioneer in future business models, you may think of reviewing your Dynamics GP implementation case with Nationwide Dynamics GP partner, who typically carries Great Plains Dexterity Software Development Factory and reasonable pool of Master level Dynamics GP Certified Consultants

7. Please, feel free to call us: 1-866-528-0577, help@albaspectrum.com

Andrew Karasev, Alba Spectrum, help@albaspectrum.com http://www.albaspectrum.com 1-866-528-0577. Please visit our info portal Pegas Planet: http://www.pegasplanet.com Local Service in Chicago, Atlanta, San Diego, Los Angeles, Orange County, Houston. We also have SAP Business One Software Development Factory and SB1 Technical Support Call Center, serving USA country side businesses and internationally: Canada, Brazil. Illinois practice: Naperville, Aurora, Plainfield, Marseilles, Ottawa, DeKalb, Springfield, Oakbrook, Glenn Ellyn, Wheaton, Bolingbrook, Romeoville, Lisle, Melrose Park, Brookfield. San Diego and LA practice: Rancho Bernardo, Oceanside, Poway, Long Beach, Irvine, Mission Viejo, San Marcos, Carlsbad, La Jolla, Escondido. Houston Practice: Dallas, Galveston, Sugar Land, Pearland, Katy, Pasadena, Rosenberg, League City, Galena Park

Article Source:http://www.articlesbase.com/software-articles/dynamics-gp-partner-san-diego-chicago-great-plains-implementation-recovery-997973.html

Related posts