I've seen a couple of post requiring data to be imported into GP but needs to be QA'ed. Example, let's say you have an e-Commerce system where orders get created and are manually entered in GP as Sales Orders. While entering in GP, the user make changes to amounts, quantities, prices, costs,etc.
Over the years, Microsoft Dynamics had been creating tools to make integration easier to manage. You can create interfaces using GP Web Services and this can reside outside GP where you can QA data before the actual import happens. The advantage? You're not using any GP license.
Another tool you can use - eConnect. A lot of GP vendors have created eConnect templates for ease-of-use and faster ROI.
You can also look at SQL Server Integration Services. This improved version of DTS is a true ETL solution for enterprises.
My 2 cents, spend more time choosing the right tool as each can have their pros and cons. Also consider creating a Staging database when you're not sure if data is reliable enough to be imported to GP.
This blog was created to help CIOs, Program leads, solution architects and administrators.
Friday, May 16, 2008
Subscribe to:
Posts (Atom)
Digital Transformation unleashed
You're the CIO/CDO sitting in your weekly update executive meeting with the CEO, CFO, COO, and others. You start the meeting with the pr...
-
The first time that you log in to Microsoft Dynamics GP 9.0, you can select to have default information that is specific to your job display...
-
Did you hear about the latest trend in databases? If not then you should read this article about NoSQL or "not only SQL". NoSQL...
-
This month Microsoft announced the availability of Dynamics GP 2013 demo which you can download here . Most of the improvements were geare...