Microsoft Dynamics GP ERP is typically deployed in mid-size organizations, or if it is in the smaller firm, then likely that business processes are relatively complex, and this was potentially one of the reasons Great Plains was evaluated and chosen. As modern MRP and ERP applications, Dynamics GP is relatively intuitive, especially considering role-oriented pages with tight integration with Microsoft Office and Sharepoint. However it is still mid-size ERP and as such precise user training is needed:
1. Classroom training. This type of training is recommended for general GP features, such as screens navigation, Explorer and Smart List, Batch processing concept. If you have large AR and AP departments, then you may decide to use formal training prior to scheduling precise business oriented training. Please, note that one of the disadvantages of this type of training is very weak connection to GP user specific transactions entry procedures. Class room training could be purchased from specialized training organizations.
2. Precise user oriented training. This training, to be efficient, should be delivered by your serving Dynamics GP consultant, who preferably was involved in your GP selection and implementation process. This training is usually oriented for user groups. If you have AR clerks, you may consider the training, where you want to review Sales Order Processing batch verification and posting procedure, then if required SOP approval cycle, AR aging reporting. This group also may need special Smart List report to be built to control work SOP Invoices, for example. Special attention should be given to FRx financial reporting - training should include reports design and running.
3. Great Plains Training for IT department. If you carry MS SQL DBA in staff, you should consider portion of technical support to be assigned to this person, as you should save substantially in reduction of consulting and external support fees. DBA typically needs training in the following areas: GP DB and sometimes tables structure to run simple scripts, such as Batch unlocking, user deletion from Activity table, recommended GP DB support plans, new workstation installation, customization rollout to the users, FRx installation and support.
4. Training via remote support and web sessions. Your Great Plains trainer or consultant may serve you from nationwide support center via web session. This is especially works for US country side businesses, where local Great Plains Resellers support is limited.
Great Plains Dynamics Upgrade Notes
If your organization deploys GP Dynamics or eEnterprise ERP versions 7.5, 7.0, 6.0, 5.5, 5.0 or 4.0 you should consider upgrade scenarios, plus you should also consider reenrollment into Microsoft Business Solutions annual enhancement program to get license keys to newest versions, such as 10.0, 9.0 and 8.0. Let's review the history of Great Plains Software Dynamics MRP application to give you the idea where Microsoft Dynamics stays nowadays, October 2007:
1. Microsoft Great Plains Business Solutions, when Microsoft purchased Great Plains Software, it is really the history now as it is back to the beginning of 21st Century, it created special subdivision, based in Fargo, ND to support from there new Microsoft ERP marketplace. Former GPS leader Doug Burgum became MBS CEO to lead Microsoft MRP expansion. Later on Microsoft acquired Navision Software, Denmark based ERP development company, and as doing so MS became the owner of Navision, and Axapta. Navision had and as of now has great positions in European ERP market. Axapta as Microsoft Dynamics AX is now promoted for large enterprises.
2. Great Plains Dexterity evolution. Microsoft has .Net platform, where such programming languages as C# and VB play substantial role, being tightly integrated with Windows .Net object model. However Great Plains eEnterprise and Dynamics had their own proprietary scripting language and IDE - Great Plains Dexterity: DYNAMICS.DIC, DEX_ROW_ID, Dynamics.set, Dex.ini - these are Dex architecture components.
3. Version Update Technology. We should be laconic as article genre dictates. If you are on legacy DB platform, such as Ctree/Faircom or Pervasive SQL/Btrieve you should be prepared to migrate to Microsoft SQL Server DB platform. If you are on GPA (Great Plains Accounting) for DOS or Windows, you should consider migration to GP with some software price to be paid.
4. GP version 10.0 upgrade specifics. At this time GP 10.0 upgrade path requires specific service packs for version 9.0 and 8.0 to applied first.
5. Customization upgrade. Great Plains Dynamics had Dexterity customizations, where you have to have source code containing DYNAMICS.DIC or EXTRACT.DIC - these dictionaries should be submitted to your GP development partner - Dexterity has Sanscript programming language and old version scripts need to be analyzed and upgraded by GP Dexterity developer.
6. Reporting Upgrade: if you have ReportWriter modified reports (more likely SOP Invoice, POP Purchase Order), Crystal Reports, Microsoft SQL Server Reporting Services (SRS) - upgrade analysis is recommended, as you may encounter problems (GP typically alters and extends tables structures to adopt newly added logic).
No comments:
Post a Comment