Microsoft Great Plains Dynamics GP Integration With MS RMS - Highlights For Consultant

This was long lasting issue and demand from the ERPoriginated as in GP as well as in RMS in counterpart
market - to integrate back end accounting with retailapplication. Here, serial/lot number is complication from
management application.GP side, so again be sure that you don not use lots
At this moment MS RMS version is not a concern, itand serials in Great Plains. In GP inventory transfers
should be easily adaptable for new RMS releases.are created in history, so you do not need to post
Integration works as the set on MS SQL Serverthemo Sales Order Processing/SOP. Integration can
stored procedures, custom tables, triggers and views.work as with orders as well as with invoices.
In RMS it pulls data from HQ database as well asPayments are deposits. You will have to post SOP
updates data in HQ, by creating RMS worksheets,batches (or transfer orders to invoices). Return logic is
these worksheets are automatically marked asincorporatedo Customers synchronization. Two ways
approved and then RMS process them internally.- from GP to RMS and from RMS to GPo Inventory
Please be aware that integration is powerful and so,Items. Items are created in GP. The purpose of this
complex - it requires our professional consultants to beintegration is to control RMS financial results as well as
involved in its implementationo Purchase Receipts. Youautomate new items creation in GP plus print barcode
receive in GP, integration moves purchase receipts intolabels at GP sideo GP-RMS stores mapping.
RMS. Please be sure that you have the same itemIntegration allows you to control several stores from
numbers in Great Plains and in RMS. Additionalone GP company as well as allows you to have
restriction - items should not be serial or lot numbercomplex mapping: one gp company to one store, one
tracked in GPo RMS and GP Inventory transferGP company site to one store, etc.
synchronization. Integration synchronizes transfers