Integration Manager in GP
Integration Manager provides you with a safe and easy way of integrating data between business applications. Integrating data involves extracting data from source applications or databases and bringing the data into a destination. You can integrate data from external business databases, e-commerce solutions, or other data file types into the Microsoft Dynamics GP application.
Sources, destinations, and destination mappings needs to be defined while creation of Integration. Sources include the data to integrate into a destination, such as text files or ODBC databases. A destination indicates where to integrate your source data within Microsoft Dynamics GP, such as General Journal or Payables Transaction. The destination mapping indicates where each item from your source data goes in the destination, such as which fields the source values will be integrated into.
A source indicates where the information to be integrated comes from. In Integration Manager, a source can be anything from a comma- or tab-delimited file, or a database such as an Open Database Connectivity source (ODBC). Sources exist independently of the source adapters.
Source adapters connect to sources, and filter and extract data. The data is passed on to the Integration Manager engine for processing.
Integration Manager engine
Working with the source adapter and destination adapter, the Integration Manager engine helps you map and integrate the source data into the destination.
A destination indicates where to integrate the processed information. A destination can be an application or database. Destinations exist independently of the destination adapters. Microsoft Dynamics GP is an example of a destination.
Destination adapters validate data before integrating it to the destination application, database, or file. If you do not have a destination adapter installed, you won’t be able to select a destination.
Destination mappings define how source data is mapped to the destination. Typically, the information comes from the source you specified, but it also can come from a constant value or default value in the destination. The integration mapping includes several rules you can use when creating a destination mapping.
A query is a request for information. In Integration Manager, queries are used to refer specifically to requests for information from a text file or ODBC source. You can create several queries when using ODBC/text as your source.
When you specify more than one ODBC/text source, you create several queries, as well. You need to create a query relationship between these queries. This relationship tells Integration Manager how the queries work together during the integration.
Overview of building and running an integration
- Create an integration that contains the source and destination information. You can either define a new integration or use an existing integration.
- Add a source, which indicates where information for the integration originates.
- Create query relationships (if necessary). If you are using more than one text or ODBC source to provide information for the integration, you need to create relationships between the source queries.
- Select the destination for the extracted source information.
- Create destination mappings which indicate where each item in the integration destination originates.
- Save the integration. You should save the integration periodically as you build it.
- Run the integration to bring data into your selected destination.
- Examine the integration results after the integration has finished running.