|
When
your company has subsidiaries overseas, where Great Plains is not
available as localized ERP solution, you have to find an efficient way
of consolidation your financial statement and even migrate GP or Sales
transactions from third party MRP to Microsoft Dynamics GP, assuming
that you are running Great Plains in the headquarters. Here we would
like to give you some highlights on possible data ongoing import and
migration scenarios
-
SAP Business One
to GP. SAP B1 is localized not only for English and Spanish
speaking countries, but also for such regions as Brazil. In the
case of Brazil – MS Dynamics GP is not supported. We have
international client with manufacturing facility in Manaus and Sao
Paulo, Brazil. SAP Business One is implemented as local Brazilian
ERP and we have transactions export routine from SAP BO to Excel.
Then Excel file is imported into Microsoft Dynamics GP in Chicago
headquarters via Integration Manager
-
eConnect Sales
Transactions Integration. Another good cross-platform data
migration. One of our clients has Oracle based industry specific
sales system, from where transactions are moved to GP Sales Order
Processing via XML web service, which in turn calls eConnect Web
services interface. In Oracle we have scheduled routine to call our
custom web service, which does integration job – we used Visual
Stidio.Net VB and C#.Net.
-
SQL Stored
Procedures. Another popular integration scenario for GP. In this
case study we have placement agency, which uses custom CRM solution
for its temps to log time and expenses, then these transactions are
moved to GP Project Accounting to be invoiced to their clients.
Please, note that in some cases eConnect has limitations, especially
in the cases when you deal with third party GP modules or somewhat
not yet automated by eConnect, such as invoicing module
|
ALBA Partners:
GP Business Portal
Great Plains Accounting
for DOS & Windows
Microsoft CRM
SAP Business One
ALBA Products:
-
Posting Server
-
RMS-GP Integration
-
SOP Connector
-
More...
|
