This was a lasting problem and demand for the ERP market: to integrate back-end accounting with the retail management application.
At this time, the MS RMS version is not a concern, it should be easily adaptable for new versions of RMS. The integration works as the set of MS SQL Server stored procedures, custom tables, triggers and views. In RMS, it extracts data from the HQ database and updates it in HQ, when creating RMS worksheets, these worksheets are automatically marked as approved and then RMS processes them internally. Keep in mind that integration is powerful and therefore complex: it requires our professional consultants to participate in its implementation
o Purchase receipts. You will receive in GP, the integration moves the purchase receipts to RMS. Make sure you have the same item numbers in Great Plains and in RMS. Additional restriction: items must not be followed by the serial or lot number in GP
o Synchronization of RMS and GP inventory transfer. The integration synchronizes transfers originated in both GP and RMS in the counterpart application. Here, the serial / lot number is a complication by GP, so again be sure not to use lots and series in Great Plains. In GP, inventory transfers are created in the history, so it is not necessary to publish them
o Sales order processing / SOP. Integration can work with both orders and invoices. Payments are deposits. You must post SOP lots (or transfer orders to invoices). The return logic is incorporated
o Customer synchronization. Two ways: from GP to RMS and from RMS to GP
o Inventory items. Articles are created in GP. The purpose of this integration is to control the financial results of RMS, as well as automate the creation of new items in GP plus print barcode labels on the GP side
o GP-RMS stores mapping. The integration allows you to control several stores of a GP company, as well as allows you to have a complex mapping: a GP company to a store, a GP company site to a store, etc.