Great Plains Ecommerce Partner: Dynamics Gp Integration Overview

In 2009 the actual question is your Dynamics GP or Great Plains ERP version.  If you are on Dynamics GP 10.0 or 9.0, then you can enjoy deploying eConnect or eConnect Runtime to program ecommerce integration directly in your Microsoft Visual Studio C# or VB.Net projects.  There is some chance, however, that if you are reading these lines – you are on older Great Plains Dynamics GP version: 8.0, 7.5, 7.0, 6.0, 5.5, 5.0 or earlier or even on Great Plains on Pervasive SQL Server or Ctree.  In old Great Plains Dynamics you have to program Microsoft SQL Server Stored Procedures or automate Great Plains Integration Manager Integration to work every 10 minutes or so.  Let’s review the scenarios.  Again, real life could be more complex, and there you need to call our office to get your case reviewed:

1.       eConnect.  This Software Development Kit, or in essence stack of interface calling technologies, based on SQL encrypted stored procedures, is available to you if you are on Dynamics GP 10.0 and also with some restrictions if you are on Great Plains Dynamics GP 9.0.  If you are on older Dynamics GP versions, econnect was in progress of being developed at the time, and it is up to you to try to deploy it – we recommend you to upgrade to Dynamics GP 10.0 and then work on eConnect integration programming

2.       SQL Stored Procedures Approach.  If eConnect is not an option for you, this means that you are on historical Dynamics GP Great Plains version, then you should consider direct SQL scripting to develop your ecommerce integration.  This job is really hard and prone to multiple data integrity errors and probes.  If you are experienced MS SQL Server DBA and you feel like you are ready to learn new MRP and ERP application, Microsoft Dynamics GP – including its data flow scenarios, and your job is secured for the next few years, then go ahead and try SQL Stored Procedures programming to accomplish Dynamics GP Great Plains integration project

3.       Pervasive SQL and Ctree.  These are really archaic versions, and if you have to commit to those older Great Plains platforms, please consider creative solutions, such as importing data to Great Plains tables via Microsoft SQL Server linked server constructions.  If you are doing direct Great Plains data repair, use Microsoft Access with ODBC connection to GP tables via linked tables technique

Source by Andrew Karasev