Software informational articles

Microsoft rms ? great plains integration ? overview for it specialist - software


Microsoft Great Plains and Microsoft Retail Management Approach (Microsoft RMS) are in receipt of new marketplace share due to the Microsoft brawny marketing campaign. Both products: Microsoft Great Plains and Microsoft RMS are advent from the same Microsoft division - Microsoft Big business Solutions (MBS), in spite of this due to the fact that both crop were bought by Microsoft from assorted vendors, the integration among the two is not an easy thing. At this time MBS has RMS integration on the Broad Ledger and Buy Order level into Great Plains out of the box. This integration has some advancements in contrast to old product: QuickSell, but it is still GL and PO only. We do absorb the need for midsize and large retail companies, structured as clubs and advertising on checking account to their members to have more ample integration when you can make tally your Sales in a row and have robust Great Plains reporting. There is the effect on the market, which is integration on the Receivables Management level from RMS to Great Plains, on paper by Daniel Sionov and Andrew Karasev and maintained by the alliance connecting LightEdge Solutions (www. lightedge. com) and Alba Spectrum Technologies (www. albaspectrum. com). In Alba Spectrum Technologies we in fact do coding and artifact tuning for certain client needs.

If you are developer you can end up with your own custom solution, we would like to give you directions.

1. Great Plains Integration Boss - if the sales capacity 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. This is fairly end-user tool - it is very intuitive, it validates 100% of commerce logic, brings in/updates master report (accounts, employees, customers, vendors. etc. ) brings in transactions into work tables. The limitation of Integration Director - it does use GP windows at the back of the scenes exclusive of viewing them - so it is fairly slow - you can bring 100 account - but when you are conversation about thousands - it is not a good option. By the way you can agenda Integration Boss with VBA.

2. eConnect - You can construct VB. Net appliance which will be pulling info from RMS and then uses eConnect to move it to Great Plains. eConnect is kind of Software Change Kit with samples in VB. Net. Clearly the change background be supposed to be Visual Studio. Net. eConnect will allow you to integrate master account - such as new customers, vendors, employees, etc. , plus you can bring transactions into so called Great Plains work tables (eConnect doesn't allow you to bring open or past report - you need to post work account in Great Plains, the same limitation applies to Integration Administrator above) eConnect is fairly for ongoing integration. It was at the outset bent for eCommerce appliance integration to Great Plains.

3. SQL Stored Procedures. The consequence we've mentioned above is assembly of stored procs. Evidently you have bottomless check and promise with SQL queries. You need to know Retail Management Coordination Command center and Great Plains tables arrangement and data flow. Launch Great Plains and go to Tools->Resource Description->Tables. Find the table in the accurate series. If you are looking for the customers - it must be RM00101 - client master file. If you need chronological Sales Order Doling out credentials - they are in SOP30200 - Sales Chronicle Heading file, etc. Do not alteration free tables - do not construct new fields, etc. Also you need to appreciate that each GP table has DEX_ROW_ID - individuality column. From time to time it is good idea to use inbound/outbound XML in the parameters - then you can position web advantage as a center party among two systems. RMS tables arrangement is self explanatory.

4. Data Transformation Military (DTS) - Good tool for importing your third party data into performance tables in GP - then you can pull them in using any stored procs of Integration Manager. You can also install this tool for EDI export/import.

5. Great Plains Adroitness Custom Screens. You can coin the window, which will have integration settings in it - RMS store ID matching GP Band database, etc. At times users choose to have seamlessly integrated into GP boundary custom screens - for parameters settings and initiating integration. Adroitness is a good option, conversely commit to memory - it is all the time advance to conceive new custom broadcast versus customizing obtainable one - due to the expectations upgrade issues. Also - Agility is in phasing our by Microsoft Affair Solutions.

6. Modifier/VBA custom buttons on the offered screens - choice to Adroitness is you are comfortable with VBA and ADO. Happy integrating! if you want us to do the job or use our effect - give us a call 1-866-528-0577! help@albaspectrum. com

Andrew Karasev is Chief Know-how Executive in Alba Spectrum Technologies - USA all over the country Microsoft CRM, Microsoft Great Plains customization company, based in Chicago, Boston, San Francisco, San Diego, Los Angeles, Houston, Atlanta, New York, and Miami and having locations in manifold states and worldwide (www. albaspectrum. com), he is Dexterity, SQL, VB/C#. Net, Precious stone Gossip and Microsoft CRM SDK developer.

Developed by:
home | site map © 2018