[ad_1]
Microsoft Dynamics project was first known as Microsoft Project Green, and got its current name in September 2005. Currently Microsoft Dynamics combines family of former Microsoft Business Solutions ERP and CRM products, Great Plains, Microsoft CRM, Axapta, Navision, Solomon . The idea of former Project Green was to create several Microsoft Suites: Financial, HR, Production, Supply Chain (SCM) at the base of ERP products, where they would presumably take the best core for each suite from one of MBS ERPs. Microsoft Dynamics seems to emphasize interfaces unification and merge, so you should not be confused if all of a sudden instead of GP database you must switch to say Axapta database for SCM. Obviously the first phase of Microsoft Dynamics each product: GP, NAV, AX, CRM, SL has its own integration methods and tools. Let’s consider Microsoft Dynamics GP 9.0 integration tools in this small article
o Microsoft Dynamics GP Integration Manager. It is an end-user tool and as a user you should feel free to experiment. You should understand that Integration Manager is redesigning phase when instead of using GP workstation or so-called fat client as OLE server and used behind the scenes forms data entry and update food – it will be used more eConnect, which is repeated data entry logic in SQL stored procedure level and this is definitely way faster and more efficient. Some glitches – the Integration Manager is switching from OLE to eConnect – VBA scripting will not be available, too, so you should redesign the old merger if you use a lot of custom integration logic of VBA scripting
o Microsoft Dexterity. We want to say dexterity Avoid integration logic, you can use custom Dex forms initialize integration parameters and then pass them to SQL stored procedures, eConnect, etc. The reason for avoicing dexterity – complex to create Dex integration is similar to the above complex to create a stored procedure. Meanwhile, Dex is cursor-driven language and SQL can use aggregation and more efficiency
o eConnect. It was initially designed for eCommerce web developers to enable them to use Microsoft Great Plains as support for ecommerce applications. So – the answer is normal – it is a good tool to create GP objects, such as Customer, Product, Sales Order or invoice. Later eConnect logic took over almost every item in Microsoft Dynamics GP. eConnect has some limitations, however – it was designed to take care of creation and were updating the so-called work, such as the Sales Order, the sales order transfer to the account and invoice posted to the duty GP operators – in case if you need to send it automatically, eConnect extensions
o SQL stored procedures. We do not recommend that you use DTS directly, for data validation is pretty sensitive and you have to simulate it in the code more flexible stored procedure. Also stored procedure may be the way to go, when the integration is very simple and straightforward and it is not feasible to pay for eConnect or Integration Manager. As developers / programmers what you need to do is enter the trade you expect to integrate the GP test environment and see how they go to SQL tables. In GP you Dynamics (or system) database and many companies databases, you integration is generally hits its database only. The typical tables for integrations: SOP10100 – Sales Haus, SOP10200 – Sales Lines, RM00101 – customer master, RM00102 – Customer Address Master, PM00200 – Vendor Master etc.
Please do not hesitate to call or email us: USA / Canada: 1-866-528-0577, 1-630-961-5918, Europe: +44 20 8123 2580, +45 36 96 55 20, Mexico 52-55-535-04027 help @ albaspectrum.com
[ad_2]