Dynamics GP Integration Manager in Data Imports

Jan 18
08:28

2011

Andrew Karasev

Andrew Karasev

  • Share this article on Facebook
  • Share this article on Twitter
  • Share this article on Linkedin

There is an option for new GP customer to purchase IM module for initial data conversion only. We’ll try to describe you data migration scenarios and how Integration Manager does the job.

mediaimage

For those of you who needs ongoing data import from external systems,Dynamics GP Integration Manager in Data Imports Articles such as Text Files, ODBC compliant databases (good names would be Oracle, Microsoft Access, FoxPro, Pervasive SQL, Ctree, MySQL, Lotus).  Let’s review the details:

1. Who do I setup the integration?  IM is user friendly tool, and at the same time it is pretty advanced and would give some challenge to your VB programmers, if you plan to deploy custom data migration logic.  You start with one or several queries, normally for the document with several detail lines you need at least two queries: one for the document header and the second for the lines.  Two queries do not necessary mean two source tables.  IM has samples and we recommend you to look at GL transaction from one source sample integration, where you should be able to get the idea on how to group records into one document header and then link this query with the second one from the same file, where you have line details.  The second step is to specify query destination, Sales Transaction Entry for example and map queries fields with the destination ones.  In our opinion, if you have structured text files as the sources, end user can do the integration setup with minimal training.  However, if you are planning to process more complex text files (such as reports coming out of your legacy application in reporting style, prepared for human reading – space lines, date on the page, header, etc.), where you need preprocessing in Advanced ODBC queries – you would rather hire professional IM designer

2. Advanced ODBC.  This query type allows you to cross text file limitation and connect to ODBC compliant database, where the query could be based on the table, or even SQL View.  If you are planning to join MS SQL Server table with cross-platform tables in Oracle for example, one of the ways would be to create in MS SQL Server custom view, which joins Microsoft and Oracle tables internally and gives the output for the query.  In our opinion such an approach is very elegant, as you may test and tune your data export logic directly in MS SQL Server View and test it quality prior to launching the Integration Setup

3. VBA Scripts.  Integration tool provides several events for your custom VBA event handlers.  Please, review VBA programming manual coming on the installation DVD.  Good example might be ‘Before Integration’ handler, where you may decide to set several global variables, such as document date, taken from the header of the text report file

4. Initial Data Conversions.  We recommend you to apply conservative judgment in deciding on the initial data migration scope, as it is much easier to keep old accounting system just for data queries and import into the new one only master records and GL beginning balances.  If this approach doesn’t work for you, try do discuss every conversion step in its feasibility and expected budget with your consulting team.  As even if theoretically it is possible to migrate “everything”, but practical realization of that possibility might be unexpectedly expensive

5. Ongoing Migrations.  Popular examples, where you may expect these are eCommerce Shopping Cart move to SOP Invoice with Customer Deposit in the form of Credit Card prepayment, EDI (Electronic Document Interchange) where you are trying to keep lower profile and do not purchase expensive full featured EDI integration module, various Manufacturing, Inventory Customer Service integrations from custom applications (often programmed in MS Access, VB, PHP/MySQL)

6. For further information, please call us 1-866-304-3265 or email help@efaru.com