| Microsoft Dynamics GP or former ERP name Great | | | | 3. Clearing transactions and history. The |
| Plains Dynamics or eEnterprise is very popular mid-size | | | | goal is to just leave master records: GL accounts, |
| corporate ERP, which also fits smaller businesses, | | | | customers, vendors, inventory items. In tools, |
| where Small Business Financials is targeted. If your | | | | maintenance select clear data and in each series |
| business came under the restructuring and you are | | | | select transactions, summaries and history files. |
| opening new legal name and want to start over in the | | | | When you are done with this delete SYS00500 table, |
| new company, however you would like to preserve | | | | which contains unposted batches. Now go to tools, |
| your customers and vendors and most of your GL | | | | and by series (purchasing, sales, inventory) run |
| account, then you should read this small publication to | | | | reconcile – you will recalculate customer, vendors, |
| get oriented. Let’s begin with company creation | | | | items summaries and balances. Next step is check |
| routine: | | | | links, select financial, purchasing, sales and inventory |
| | | | | series files |
| 1. Creating New company. You perform | | | | |
| this in Great Plains Utilities. Dynamics GP new | | | | 4. Removing inactive accounts. If you |
| company creation should take from five to fifteen | | | | have a list of the accounts to keep, you can create |
| minutes, depending on the performance of your | | | | simple SQL delete statement, where you will join |
| server. If you would like to avoid problems, follow all | | | | accounts to keep table and GL00100. Then remove |
| the way through the creation and do not try to stop | | | | orphan accounts, joined by account index in GL00105 |
| the process | | | | table (accounts index master). If you have |
| | | | | multicurrency accounts, remove them the same way |
| 2. Load new company database with your | | | | in MC00200 table. Then, run check links on financial |
| old company backup. This should be done in | | | | |
| Microsoft SQL Server Management Studio (MS SQL | | | | 5. Company ID update script. We can not |
| Server 2005) or in SQL Enterprise Manager (MS SQL | | | | include this script in this small publication, you can find it |
| Server 2000). You typically load backup from device, | | | | on GP customer or partner source. And now you |
| select file, and then in options check force restore | | | | are ready to go live with new company |
| over existing database. Don’t forget to change | | | | |
| file name and path, before you click restore button | | | | 6. FRx reports. |
| | | | | |