Dynamics GP Partner Chicago, San Diego News: Integration Manager

December 22, 2017 by  Filed under: Computer 

Great Plains integrations, especially in Edi and ecommerce scenarios are very popular and in our opinion they are not overly too complex to design and implement.  If you are MS Visual Studio C#, VB .Net programmer with some SQL and XML skills, you should be able to program real time or batch mode integrations in eConnect SDK for Dynamics GP, and as such your integration could be called directly as part of your ecommerce web site instruments.  

However if you do not carry programmer in your ITdepartment, but have some SQL expertise, you do not even have to toucheConnect, as most of the job could be done in Great Plains Integration Managerdirectly, and you could schedule integration as macro, and the rest of work forEDI or ecommerce integration could be done in SQL Views.  Read this small publication as orientationsession in GP IM:


1.       Simpleintegration scenarios.  If you have text CSVor tab delimited file as integration source, then all you need to do is toestablish simple text file source and if your target has header and lines,where you have only single file, you need to look at grouping feature.  For example, if you plan to import GLtransactions – one per each day of Retail operations, natural grouping would betransaction date.  Two sources will bebased on one text file, where header will be grouped by date and transactionswill be as they are and you link header and lines by Date field


2.       AdvancedODBC over text file.  Imaging that youhave CSV or Excel file, which has several columns, staying for SOP Invoice Itemlines each column.  In our opinion, thisone is pretty challenging in creating Advanced ODBC Source and then creatingunions over the same text file, pulling specific column in first select, thenunionize it with the second column in the second select and so on.  This natural technology of building unions isunfortunately complicated by bugs in ODBC Text driver, where you cannot save Selectstatement field format in INI file.  Thework around – have driver guess on field format every integration once again


3.       AdvancedODBC over SQL View.  This is the mostadvanced scenario, when you can expose transactions from ODBC compliant DB: MSSQL Server, Oracle, Linux PHP MySQL, Microsoft Access, Lotus Notes (withrepetitive records).   Our favoritetechnique is this – create linked server in MS SQL Server 2005 ManagementStudio or SQL 2000 Enterprise Manager and then create heterogeneous, meaning cross-platformSQL View and base Advanced ODBC Source on that view.  Here you can practice with EDI (preciselyformatted SQL Select statement).  To makeyour integration more powerful, consider creation SQL DTS package, where youexpose specific day transactions set and mark them as exposed and whenintegration is accomplished with success flag, mark those transactions asintegrated


4.       VBAscripting in IM integration.  Here youhave additional alteration options in even driven scripts: Before Integration,Before Document Commit, etc.  Goodexample would be something like this – imagine you are in Collection businessand you have to issue checks to your customers with 30 days payment delay.  In Before Document commit script you canincrease check date accordingly

Speak Your Mind

Tell us what you're thinking...
and oh, if you want a pic to show with your comment, go get a gravatar!

You must be logged in to post a comment.

Prev Post:
Next Post: