Great,Plains,Technical,Consult computer Great Plains Technical Consultant News: Dynamics GP Data Mig
Gone are those times when the companies and the organisations didn't need a hi-tech system to handle them. Owing to the considerable increase in the business sector and thus, an enormous increase in the complexity of the organisational struc ----------------------------------------------------------Permission is granted for the below article to forward,reprint, distribute, use for ezine, newsletter, website,offer as free bonus or part of a product for sale as longas no changes a
Plus, in our opinion data conversion recommendations or saystronger principles are applicable to other ERP and MRP systems: 1. Masterrecords migration. This is likely therequired step, where you move your GP Chart of Accounts, Customers, InventoryItems, Bills of Materials, Vendors, Employees, etc. In GP these are so-called masterrecords. The simplest way is Dynamics GPIntegration Manager. If you only need GLaccounts, you could try direct SQL Insert into GL00100 and then run Check Linkson Account Master tables cluster. In allother cases we do not recommend direct SQL insert, as it is not guaranteed thatbusiness logic required dependencies will be restored by Check Links routine 2. BeginningBalances. When you are done with masterrecords migration, we recommend you to keep historical transactions lookup inyour old accounting system: Peach Tree, MYOB, QuickBooks, or whatever it was. In this case, you launch New Year or newfiscal period in Great Plains by entering beginning balances to each GL accountin one General Ledger transaction, review and post it on the day of the firstdate in the new fiscal period. Preferredway it to start GP in production on January 1st, or whatever is yourfirst day of your Corporate ERP fiscal year 3. OpenAR, AP. We recommend you to import viaIntegration Manager unpaid AR and AP, then post them and wait for payments tobe issued (AP) or received (AR and SOP) 4. HistoricalData Conversion. We recommend you toconsider avoiding it and instead keep legacy accounting open forinquiries. If this is absolutelyimpossible, consider creating historical company in GP, closed for newtransactions and then move historical records there, here you can use SQLInsert statement. Please, never runcheck links in this historical company, as your historical data migration willlikely be inconsistent, but good for querying. Another way, which might be taken import all your historicaltransactions via Integration Manager and then post them by historicaldates. The pitfalls of this approachmight be the problems with historical data export quality and IM performance 5. Ifyou have concerns, please give us a call: 1-866-528-0577, [email protected]
Great,Plains,Technical,Consult