(1888PressRelease)
August 07, 2007 - Microsoft Great Plains, current version in 10 historically had very robust integration tool – Great Plains Integration Manager (IM). GP customers historically deployed IM since earlier 1990th up to today and this tool should be utilized in the future. IM integration design is often end-user routine, however is some cases you will need IM to be given professional consultant touch. Let’s come through few examples
1. GL transaction import, one source. This is classical IM design task, however if your case is complicated, where you have to cancel to integrate specific lines without real data (comments lines in text file and things like that), then you will need to deploy VBA scripting in the IM events handler – in this case ‘Before Document’ event
2. ODBC data sources. Especially when you have data to be integrated sitting in SQL Server tables, where you need stored procedures to preprocess integration dataset and send it to GP. This type of assignment requires strong SQL scripting, knowledge of GP tables and IM linking
3. Translation technology. IM allows you to deploy translation table. The typical scenario is something like that – you have to integrate payments on behalf of your customers to the bank (which is your GP customer). Or similar, but reverse scenario in AP – typical to collection management business. You can further advance translation rules with VBA scripting, if required
Alba Spectrum Group, http://www.albaspectrum.com help ( @ ) albaspectrum dot com 1-866-528-0577, 1-630-961-5918, serving GP client in USA nationwide and Canada. Local service is available in Chicago area: Naperville, Warrenville, Oakbrook, Lisle, Downers Grove, Romeoville, Aurora, Hinsdale, Joliet, Plainfield, Morris, Orland Park, Lombard, Elgin, Crystal Lake, in Houston: Richmond, Sugar Land, Rosenberg, Katy, Galveston. Nationwide service: California, New York, Ontario, Quebec, Florida, Arizona, Iowa, Indiana, Kansas, Wisconsin, Minnesota, Washington, Nevada, Utah, Louisiana, Texas, Illinois
###
