In order to enable custom integration you need to have this license - which costs $750 for Great Plains Standard. Microsoft Business Solutions Great Plains has I'd say end user integration tool - Great Plains Integration manager. Integration Manager itself uses OLE functionality to validate text or ODBC integration files data through Great Plains forms behind the scenes. Continuum could deploy Great Plains Dynamics macros, recorded to switch companies. However there are Microsoft Great Plains maestros who could make magic things happen.
It has Dexterity interface in Great Plains, does integration to single company at the time. This integration is maintained by Microsoft Business Solutions and allows you to synchronize SOP and Customers in Great Plains with Microsoft CRM Quotes and Orders. However you can have successful bridge between non-Microsoft ERP and Great Plains. If your company is ISV and implements eCommerce product, integrating to Great Plains - you would rather prefer set of open and simple stored procedures, moving data to and retrieving from Microsoft Great Plains Sales Order Processing (SOP) module. Here we need to mention interesting thing, The product, created and dedicated to eCommerce developers - Great Plains eConnect is often considered as a bit expensive and licensing-restricting solution.
Since then Great Plains Dynamics/eEnterprise integration techniques use Microsoft technologies. Great Plains Dexterity integration with Great Plains process server. In this short FAQ style article we would like to introduce you - software developer, programmer, database administrator into Microsoft Great Plains Integration tools and options. This integration technique uses SQL stored procedures and views to pull data from your legacy or third party application and push it into Great Plains. It was initially created for eCommerce application integration to Great Plains.
We see more and more requests for Great Plains integrations with web eCommerce applications, industry specific databases. Microsoft Business Solutions Great Plains is very popular ERP/MRP applications in the USA, Canada, UK, Australia, New Zealand, Middle East, South Africa, Latin America. These are the restrictions of Great Plains architecture and to resolve the issue you need set of custom stored procedures. The dilemma for the programmer is - should I know all the details of Great Plains table structure model and document workflow - or probably purchase the set of SQL stored procs to help me. The plans are the plans, but the realities of Microsoft Great Plains customization signals that Dexterity will stay another 5-7 years as IDE.
VBA Scripting - Launch Great Plains Integration Manager, open your integration, right click->Properties, switch tab to scripts, open Before Document script. Now your vendors from integration file will be replaced with real vendors from Great Plains. Great Plains Integration Manager scripting and translation - overview for programmer, software developer, database administrator, IT specialist. Microsoft Business Solutions main middle market ERP application - Microsoft Great Plains has multiple integration options. Microsoft Great Plains Integration Manager.
Great Plains Integration Manager - if the sales volume is very low, say 100 transactions per day - then you can do data export from RMS and import it into Great Plains via Integration Manager.
There is the product on the market, which is integration on the Receivables Management level from RMS to Great Plains, written by Daniel Sionov and Andrew Karasev and maintained by the alliance between LightEdge Solutions (www. It was initially created for eCommerce application integration to Great Plains. We do understand the need for midsize and large retail companies, structured as clubs and selling on account to their members to have more adequate integration when you can synchronize your Sales information and have robust Great Plains reporting. At this time MBS has RMS integration on the General Ledger and Purchase Order level into Great Plains out of the box.
In the case when you use Microsoft RMS Store Operations and Headquarters - you should consider seamless integration of your daily transactions into Microsoft Great Plains Sales Order Processing (SOP) or Receivables Management (RM) modules. Microsoft Business Solutions Great Plains is ERP platform, ready for third party modules additions and customizations, plus being SQL Server-based system it opens you wide spectrum of integration options and tools. If you have only one Great Plains Company - you can deploy RMS->GP integration utility, coming to you with RMS purchase and support CDs. This text file should be forwarded to your supplier and in Great Plains POP you set flags for POs being sent to your vendor. In both cases - Great Plains and RMS compliance reporting should be realized in Crystal Reports and the best way and design style is creating SQL views and stored procedures and basing report on these views and procs.
Seamless integration into Great Plains interface - Great Plains Project Accounting is Dexterity-written module, so it is in Dexterity interface and security model. Simple budgeting and project tracking - if this is your goal - consider it, especially if you already have Great Plains implemented in your company.
It is very simple and intuitive - if you are certified accountant and know the GAAP on project accounting - you should be able to understand all the data flow and distribution in GL - Great Plains Project Accounting is following the rules. The long story of Great Plains Software Project Accounting - it was originally created by MatchData, which was bought by Great Plains in late 1990-th and renamed into Great Plains Project Accounting. Great Plains Project accounting future is uncertain - it will not ( according to rumors in Microsoft) become the base for one of the Microsoft suites.
We do understand the need for midsize and large retail companies, structured as clubs and selling on account to their members to have more adequate integration when you can synchronize your Sales information and have robust Great Plains reporting. It is for integration into one Great Plains company only. So, if you have to reconcile checkbooks / Bank Reconciliation module in Great Plains - you can not do it with standard integration. This integration is currently available for Great Plains version 7. It was initially created for eCommerce application integration to Great Plains.
Great Plains Integration Manager - this is rather end-user tool - it is very intuitive, it validates 100% of business logic, brings in/updates master records (accounts, employees, customers, vendors. It was initially created for eCommerce application integration to Great Plains. Looks like Microsoft Great Plains becomes more and more popular, partly because of Microsoft muscles behind it. You need to know Great Plains tables structure and data flow. Launch Great Plains and go to Tools->Resource Description->Tables.
It was initially created for eCommerce application integration to Great Plains. Great Plains Integration Manager - this is rather end-user tool - it is very intuitive, it validates 100% of business logic, brings in/updates master records (accounts, employees, customers, vendors. Launch Great Plains and go to Tools->Resource Description->Tables. Looks like Microsoft Great Plains becomes more and more popular, partly because of Microsoft muscles behind it. You need to know Great Plains tables structure and data flow.
This integration could work as nightly SQL routine and bring all the daily sales transactions from RMS stores or Headquarters to mapped Great Plains companies. This might be done as SQL routine or Great Plains Dexterity customization. Microsoft Great Plains fits to majority of horizontals and retail business is good fit as well. These campaigns are automated in RMS and Great Plains, however promotion scenarios might be not the same. Great Plains or RMS and then synchronize via stored procedures.
Microsoft Business Solutions Great Plains might be considered as ERP platform, ready for customization and integration. This tool should be considered as the way to move your very unique custom sales logic into Microsoft Great Plains - if you decide to stick to outside customization (like eCommerce for example. Andrew is a Great Plains specialist in Alba Spectrum Technologies ( http. Dexterity is programming language of Great Plains. Highlights for Great Plains implementation.
If you have something else, besides Microsoft CRM and Great Plains, then you might need the integration. Great Plains is integrated with MS CRM on the level of Sales Order Processing module (SOP. Great Plains is good ERP solution for majority midsize business and fits to variety of business niches. Currently, Microsoft Business Solutions has MS CRM integrated with Microsoft Great Plains. Andrew is Great Plains specialist in Alba Spectrum Technologies ( http.
So as you see - logic is present and structured, but it is not friendly to the developer, who never seen and worked with Great Plains Dynamics. But these legacy Great Plains Dexterity names do not help eCommerce developer - only probably as the reference on which table works with specific screen. Great plains was designed to first serve mid-size businesses and then with the availability of third party modules - the intention was to compete on corporate ERP market with Oracle, PeopleSoft, SAP and others big players. This tool covers a lot of Great Plains objects creation and retrieving functionality, however it does have restrictions, because it was not intended as replacement to Great Plains Dexterity shell. Andrew is Great Plains specialist in Alba Spectrum Technologies ( http.
|