Microsoft Great Plains 10.0 and 9.0 Upgrade - Technical Notes

By: Andrew Karasev

At this time (fall of 2007) Microsoft Dynamics GP customers are actively upgrading to GP version 9.0 and initial upgrades are performed to Microsoft Dynamics GP 10.0. Version 10.0 will be in more active upgrade mode, when Microsoft will release GP 10.0 Service Pack 1, as current GP 10.0 upgrade path is limited to 8.0 SP5 and 9.0 SP2. Having reasonable number of GP version updates performed, we would like to share experience. Lets' start with the most popular upgrade to 9.0.

1.As versions 8.0, 7.5, 6.0, and earlier are discontinued for Microsoft Dynamics technical support, you should consider this bell as strong signal to walk away from these older versions. Versions 7.5 and older were available on MS SQL Server as well as on Pervasive SQL 2000 (former Btrieve) and Ctree. In the case when you are on non-MS SQL Server DB - you will have to undergo migration step to SQL Server based version. Assuming that your case is straight forward, let's move on and review known version upgrade issues

2.Purchase Order Processing tables problems. If you are using POP module, then you must check you Purchase Orders and Receipts work and historical tables on the subject of so-called orphan lines. These tables should be verified: POP10110, POP10310, POP30110 and POP30310 - they store purchase orders and receipts lines. Microsoft recommends doing checklinks, prior to upgrade process, however we saw situations, where potentially check links don't do all the orphans cleaning job. If check links doesn't help, please construct the script which will give you orphans in lines table, similar to the following: select a.* from POP10110 a left join POP10100 b on a.PONUMBER=b.PONUMBER where b.PONUMBER is null. And again, prior to rescuing to scripting, you should try check links approach.

3.If after check links, upgrade failed on POP tables, you will have to restore DYNAMICS and all Companies DB to initial version and try data repair with scripting. Then design delete scripts with your DBA person. Microsoft partner should be able to apply failed company rolling back script, so you do not have to start from initial version for all the databases, however this script is confidential.

4.Other potentially problem tables. We've also seen the problem with IV10200 table. In version 9.0 inventory valuation formula was revised and it now relies on IV10200 to higher extent. In some cases this table conversion script fails and upgrading application freezes. The remedy is roll back to initial version, be sure that you did check links

If you like us to help you with GP upgrade, integration, software licenses, reporting, please give us a call

Microsoft
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 
 • 

» More on Microsoft