Great Plains Data Import: Dynamics GP Integration

Jan 27
08:18

2009

Andrew Karasev

Andrew Karasev

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

Microsoft Dynamics GP or former Great Plains has several methods in importing data

mediaimage

In this small publication we would like to give you initial highlights and after getting this help you should be able to find additional info in GP user manuals,Great Plains Data Import: Dynamics GP Integration  Articles Customer Source Knowledge database or request it through your Dynamics GP Partner or reseller

 

1.       Dynamics GP Integration Manager.  This tool is user friendly and allows you to import majority of GP master objects: accounts, customers, vendors, employees, addresses; work transactions: sales invoice, purchase order, payroll transaction to give you the idea.  In IM you should come through several steps to design integration: setup source or sources (if more than one – you should link them into one set following SQL rules), select destination (like SOP Entry – target object) and then tune destination mapping.  If you are programmer, you would also like to review IM VBA scripting chapters in IM manual.  IM accepts tab, csv as well as custom character delimited text files plus via ODBC and Advanced ODBC you can import or integrate everything that is ODBC compliant: Microsoft SQL Server, mySQL, Oracle, DB2, SyBase, Lotus Notes Domino, Microsoft Access, Microsoft Excel, FoxPro and so on and so on.  ODBC integration should work in most of the EDI (Electronic Document Interchange) scenarios, where you pull data into Dynamics GP

 

2.       eConnect.  For those of you who are looking into more technically challenging projects: real time, ecommerce, scheduled integration, and if you are comfortable with Microsoft Visual Studio C# or VB .Net programming with XML and SQL elements, please consider eConnect.  This SDK was initially designed for ecommerce web programmers to integrate ecommerce website with Dynamics GP back office

 

3.       SQL insert statements.  If you are SQL DBA or very experienced programmer, we understand the desire to push records directly to Dynamics GP SQL tables.  However, you will face the challenge of meeting very complex business logic and its reflection in data flow.  Plus all this work was already completed by eConnect developers, where end technology is SQL Server encrypted stored procedures.  So, this approach of direct SQL scripting might only be recommended if your GP import task is absolutely simple (when you have to populate one table only, for example)

 

4.       SQL DTS packages.  Here you could consider complex scenarios, when you are exporting data from cross-platform database, calling eConnect based application to move data to GP and then mark the data as imported in your source DB.  Call your Dynamics GP technical consultant for further details