| |
Microsoft RMS Integration & customization - overview for Consultant
By Andrew Karasev
Microsoft RMS (Retail Management System) is former SMS QuickSell and QuickSell2000 - retail management and point of sale application, which has headquarters solutions and is now owned and marketed by Microsoft subdivision - Microsoft Business Solutions. Microsoft followed its traditional pattern in building its business application products base - it simply purchased several software development companies to make this happen: Great Plains Software, Navision Software (primarily European market), SMS. Due to the fact of high acquisition activity - all these products turned up to be poorly integrated. Microsoft is resolving integration issue by moving all its application to MS SQL Server platform or exposing them to BizTalk Server (like in the case of Microsoft CRM - Microsoft Great Plains integration). When we are talking to Microsoft RMS - the most typical customization for US market would be the one with Microsoft Great Plains. In its off-the-shelf version RMS is integrated on GL and POP level with multiple restrictions:
· Transaction level should be low - because it is cursor-based integration, initiated by pressing the button (you got to wait while all your daily POS batches are transferred to Great Plains GL)
· Restriction to one company in Great Pains - again, you initiate it by hand and target it to one company at the time
· We could continue the list of restrictions…
Microsoft understands the problem and currently is in the research mode to select the ISV contractor to write or pick existing third party integration and recommend it as Microsoft-approved solution.
The nature of RMS - you have pretty high Inventory count control in Store Operation Manager and Headquarters applications and so from Great Plains side you don't count your inventory and pretty much want your check books to balance as well as have proper GL accounts distribution, based on your Items / Departments matching in Microsoft RMS.
This makes it natural to choose integration on Accounts Receivable level, when you move to Great Plains AR transaction and then post them there.
Another way is - to move transactions to Sales Order Processing (SOP) - in this case you can synchronize Inventories in RMS and Great Plains (in our opinion - this is too luxury solution).
We could help you with tuning AR integration, maintained by Alba Spectrum Technologies. It is written as a collection of SQL Stored procedures, called from Dexterity interface with stores-to-companies mapping without restriction to the number of companies/stores.
Microsoft RMS Customization. Recently (October 2004), Microsoft Business Solutions released RMS customization guide, primarily targeted to Microsoft Business Solutions partner, so you should check with your MBS Var if they provide Microsoft RMS customization. The technologies behind might be native RMS object call (when you can have discounting routine called for example), COM objects or external application, plus you could open specific web page.
Give us a call if you need help: 1-630-961-5918 or 1-866-528-0577, help@albaspectrum.com
About the Author
Andrew Karasev is consultant and CTO in Alba Spectrum Technologies ( http://www.albaspectrum.com ) - Microsoft Business Solutions partner, serving clients in Illinois, California, New York, Florida, Georgia, Arizona, Colorado, Texas, Minnesota, Virginia, Washington, UK, Canada, Australia. He is Microsoft Great Plains certified master, Great Plains Dexterity, Microsoft CRM SDK C#.Net, Crystal Repots developer. You can reach Andrew: akarasev@albaspectrum.com
Article Source: http://www.simplysearch4it.com/article/1100.html
| If you wish to add the above article to your website or newsletters then please include the "Article Source: http://www.simplysearch4it.com/article/1100.html" as shown above and make it hyperlinked. |
| Some other articles by Andrew Karasev | |
| |
|
