The reality of the modern Corporate ERP application is the every few years new version is released, then historical version has several additional years to stay supported.
Then older version support is terminated by its development company and you either upgrade to the version supported in time or seek alternative ways to support your obsolete ERP system. Now we are in earlier 2011, GP version 2010 was released just before Microsoft Convergence trade show in Atlanta, in April of 2010. Previous version 10.0 is still supported directly by Microsoft Business Solutions, however mainstream support for version 9.0 is about to expire. Let’s review the typical questions, timing and the options for those of you who decided to stick to the older system:
1. First question: why would we really care about being upgraded, we are happy with what we have? This is legitimate question and we understand your points. However consider several facts about ERP life cycle. First of all – new version has new features, which could be useful. Second, it is compatible with all the new trends in the computer technology – it is probably wiser to follow the IT industry trends, where your hardware, software and IT workforce are manageable. Third, your functional and technical consulting partner has to manage its own talents, train new support technicians, programmers – the training is only available on the current version, meaning that the pool of old consultants is shrinking. Forth, Microsoft Business Solutions has a schedule to support several releases at the time, when support expires – the only option is to seek third party consulting advise
2. When the time to upgrade comes? Some firms want to be case study stadiums, meaning that they would like to rush into the new release as soon as it hits the market. We usually advise to wait few months until the first or even the second service packs are released and all the bugs are fixed respectively. If you are trying to save as much as possible and probably take some risk, try the strategy, where you skip one version and then do update, say every five years
3. Where are we with GP 2010/11.0? Well, as we already mentioned it was released in April 2010 and Service Pack 1 was released on September 23, 2010. Now, in our opinion it is time to launch the update, especially for those of you who is still on 9.0
4. What to expect in 2010/11.0? First of all, as you might be aware, in 10.0 new security model was introduced, where it is rather role based, versus form, report, table oriented in the older releases. There are good improvements in the Distribution set of modules: SOP, POP, Inventory Control. Microsoft Management Reporter is introduced as the transitional replacement to the older Corporate Financial Reporting on the FRx platform. Plus, in our opinion the Microsoft Dynamics project is on the way to make its family members user interface, among them AX, GP, NAV, SL, more universal and recognizable by the end user. Microsoft Workflow, Metrics, Office Stack integration is catching up
5. What to do if we have Dexterity, eConnect, Web Services, Modifier with VBA, Report Writer or Integration Manager custom application? Well, altered ERP logic probably is something that gives you competitive advantage, but at the same time it requires maintenance budget. Consider contacting your original Dexterity programming organization, they should review the Sanscript code and make required changes to make it compliant to the new release
6. We are on Great Plains 7.5, 7.0, 6.0, 5.5, 5.0 on Pervasive SQL 2000/Btrieve or Ctree. Plus we are deploying Intellisol Advanced Purchase Order Processing. Are we still good to move all the way up to 2010? The answer is ‘Yes’, but expect several steps. First of all Intellisol Advanced POP had migration tool for 7.5 and even 8.0. Migration path was discussed in our earlier blogs, plus it is available if you contact your VAR – they should have access to the procedure on Partner Source. One of the important things – you should be current in Annual Enhancement program to have access to the reg key for the new release
7. Great Plains Accounting for DOS, Windows or Mac 9.5, 9.2. Here you have the option to migrate to Dynamics GP with substantial discount on the modules owned. Chances are high that your situation is resembling the downsizing, where you might decide to migrate away to QuickBooks, Peach Tree, SAP Business One or similar small business accounting package
8. Small Business Financials 9.0, 8.0 or Small Business Manager 7.5, 7.0. With version 9.0 Microsoft terminated this product line and it recommends you to migrate to GP 9.0, 10.0 and 2010. There are some contradictions in the recommendation, as you are small business and expect low software license and maintenance cost, so discuss the option with Microsoft or your Reseller
9. Version Upgrade technology. It is done in GP Utilities. As the first step it installs new user interface, then it launches SQL objects update: SQL and token stored procedures (with _z prefix), required table modification (it in fact copies them into Temp DB, alters table structure and then moves all the records back into the altered table). Of course, this process is open to all kind of data inconsistency show stoppers, where your consultant has to call Microsoft tech support team or search knowledge base in order to resume migration procedure
10. International Projects. If you are working for multinational corporation, there are more things to take into consideration. First of all, be sure that you are familiar with Corporate ERP localization concept. Microsoft is repositioning its Dynamics ERP platforms on the international Corporate ERP and small business accounting application market. If you were deploying Great Plains in one of the continental Europe countries, you may face the necessity to redeploy it on Dynamics AX or NAV platform. If you are downsizing, consider SAP Business One or such local ERP products as 1S Bukhgalteria in Russia or Microsiga in Brazil
11. For further information, please call us 1-866-304-3265 or email help@efaru.com
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
