| At this time (fall of 2007) Microsoft Dynamics GP | | | | POP30110 and POP30310 - they store purchase |
| customers are actively upgrading to GP version 9.0 | | | | orders and receipts lines. Microsoft recommends |
| and initial upgrades are performed to Microsoft | | | | doing checklinks, prior to upgrade process, however |
| Dynamics GP 10.0. Version 10.0 will be in more active | | | | we saw situations, where potentially check links don't |
| upgrade mode, when Microsoft will release GP 10.0 | | | | do all the orphans cleaning job. If check links doesn't |
| Service Pack 1, as current GP 10.0 upgrade path is | | | | help, please construct the script which will give you |
| limited to 8.0 SP5 and 9.0 SP2. | | | | orphans in lines table, similar to the following: select |
| Having reasonable number of GP version updates | | | | a.* from POP10110 a left join POP10100 b on |
| performed, we would like to share experience. Lets' | | | | a.PONUMBER=b.PONUMBER where b.PONUMBER is null. |
| start with the most popular upgrade to 9.0. | | | | And again, prior to rescuing to scripting, you should |
| 1. As versions 8.0, 7.5, 6.0, and earlier are discontinued | | | | try check links approach. |
| for Microsoft Dynamics technical support, you should | | | | 3. If after check links, upgrade failed on POP tables, |
| consider this bell as strong signal to walk away from | | | | you will have to restore DYNAMICS and all |
| these older versions. Versions 7.5 and older were | | | | Companies DB to initial version and try data repair |
| available on MS SQL Server as well as on Pervasive | | | | with scripting. Then design delete scripts with your |
| SQL 2000 (former Btrieve) and Ctree. In the case | | | | DBA person. Microsoft partner should be able to |
| when you are on non-MS SQL Server DB - you will | | | | apply failed company rolling back script, so you do |
| have to undergo migration step to SQL Server based | | | | not have to start from initial version for all the |
| version. Assuming that your case is straight forward, | | | | databases, however this script is confidential. |
| let's move on and review known version upgrade | | | | 4. Other potentially problem tables. We've also seen |
| issues | | | | the problem with IV10200 table. In version 9.0 |
| 2. Purchase Order Processing tables problems. If you | | | | inventory valuation formula was revised and it now |
| are using POP module, then you must check you | | | | relies on IV10200 to higher extent. In some cases |
| Purchase Orders and Receipts work and historical | | | | this table conversion script fails and upgrading |
| tables on the subject of so-called orphan lines. These | | | | application freezes. |
| tables should be verified: POP10110, POP10310, | | | | |