Dynamics Gp Partner Los Angeles Newsflash: Data Conversion

Dynamics Gp Partner Los Angeles Newsflash: Data Conversion

By:


Each ERP and MRP system typically requires certain level of historical data migration from old accounting application to newly implemented one. Being customer of new accounting application, such as Microsoft Dynamics GP, you should initially try to be conservative and avoid full-size data massage and conversion, instead try to think about moving master records and initial balances in General Ledger and have old accounting stand by for historical data inquiry. If this is not acceptable, then, please read this small publication to see what are your options and integration tools in Great Plains Dynamics:
1.Master Records: these are GL accounts, customers, vendors with addresses, employees, inventory items, bill of materials, etc. Typically every data conversion requires master records import. Please, consider either exporting master files in text tab or comma delimited format. If your legacy accounting is ODBC open, you may simply create SQL Linked Server to reach legacy master files, then read about Great Plains Integration Manager two paragraphs below
2.Open Transactions: customer and vendor invoices where payments are not yet received or checks mailed to the vendors. Normally you handle these reasonably moderate data migration in IM and then post RM and PM batches to open customer and vendor invoices for aging and applying
3.Historical transactions these are the most difficult to get imported, as you can imagine that most of your hard drive space at your legacy accounting system side is taken by all sorts of historical records. We recommend you to consider having legacy accounting application available for data lookup for several years, then you could archive it and print major reports
4.Integration Manager and its technology. IM is user friendly tool, where you should be able to setup simple integration intuitively. When you are implementing GP initially, you could get IM conversion license which is good for initial implementation time span. For those of you who are advanced in programming and software development, Integration Manager is open for such modifications as VBA scripting, name translation (where you translate vendor id for example into another vendor ID, based on names translation table, which you could prepare in Excel and import into Integration)
5.IM Performance. This is for technology folks. In GP 10.0 and to some extent in 9.0, IM was rewritten in new SDK eConnect. eConnect is in essence old Great Plains Dexterity methods reprogrammed in SQL Stored Procedures. Traditionally GP Dex was called as C Programmed shell from GP, then it was forming Dexterity cursors to do data insert, delete or update. SQL stored procedure should be a way faster if you heard old IM stories about Integration Manager being limited to ten thousand transactions per day these limitations are no longer valid with IM being now based on eConnect connectors

About the Author:
Andrew Karasev, Alba Spectrum LLC. http://www.albaspectrum.com help@albaspectrum.com 1-866-528-0577. Web portal: http://www.pegasplanet.com We are Microsoft Dynamics GP technology partner, ERP and software integrator, who serves you USA, Canada, Mexico and Latin America nationwide. Local service is available in Chicago, San Diego, Los Angeles, Houston



Article Originally Published On: http://www.articlesnatch.com


Tags: ,

|

Loading...
Related....
Videos...

Recent Software Articles

Comments

Still can't find what you are looking for? Search for it!

Loading

Site Navigation:

Copyright 2005-2011 ArticleSnatch, LLC - All Rights Reserved.
Privacy Policy | Terms of Service.