User manual MICROSOFT INTEGRATION MANAGER QUICK START

[. . . ] Microsoft DynamicsTM GP Integration Manager Quick Start Copyright Copyright © 2005 Microsoft Corporation. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Notwithstanding the foregoing, the licensee of the software with which this document was provided may make a reasonable number of copies of this document solely for internal use. Trademarks Microsoft, Microsoft Dynamics, and Windows are either registered trademarks or trademarks of Microsoft Corporation or its affiliates in the United States and/or other countries. [. . . ] Additionally, you can create integrations that extract data from applications and integrate it into custom XML format, or create integrations that transform XML data to the XML format you prefer. 26 INTEGRATION MANAGER QUICK START CHAPTER 4 ADDING SOURCES Understanding the source files The integration in this Quick Start guide, the GL-GJ Integration, involves importing two transactions into the General Ledger. The information for these transactions is found in two files, GLHEADER. txt and GLLINE. txt. These files are located in the Samples directory where you installed Integration Manager. The following illustrations show how the files appear in Notepad. The first line contains column names. Tab characters separate the items in each line. If you are not using the Microsoft Dynamics GP test company, or if your account format structure does not match the account structure in the sample files, the integration cannot successfully complete. It is possible to modify the structure in the text files by opening these files in Notepad. INTEGRATION MANAGER QUICK START 27 PART 2 BUILDING AN INTEGRATION The two text files actually contain the same information as the following two transactions: This information is contained in the GLHEADER. txt file. This information is contained in the GLLINE. txt file. This information is contained in the GLHEADER. txt file. This information is contained in the GLLINE. txt file. Note that the header information for both transactions is contained in the GLHEADER. txt file, and that the line items for both transactions are contained in the GLLINE. txt file. You will create two queries that retrieve the information from these two text files. These two queries are: GL Header Query This query retrieves data from the GLHEADER. txt. Refer to Chapter 5, "Creating Query Relationships, " for information about how to create relationships between the two queries that "reassembles" the information back into complete transactions. The complete transactions can then be read by Integration Manager. 28 INTEGRATION MANAGER QUICK START CHAPTER 4 ADDING SOURCES Creating the GL Header query First, you are going to add a text source that queries the data in the GLHEADER. txt file. To create the GL Header query: 1. In the Integration window, right-click Sources and, from the menu that appears, choose Add Source. 3. In the Adapters pane of the Add Source window, expand ODBC/Text by clicking the plus sign. INTEGRATION MANAGER QUICK START 29 PART 2 BUILDING AN INTEGRATION 4. Choose Text, and in the Sources pane choose Define New Text. Then, choose Open. The Properties window for the Text query opens. 5. Enter a Name and Description for the source. Name Description GL Header GL Header Query The Name should describe the type of information retrieved by the source. 30 INTEGRATION MANAGER QUICK START CHAPTER 4 ADDING SOURCES The source Description should describe the type of data contained in the source. It must be descriptive enough so other Integration Manager users can easily identify and use it. 6. Define the general properties for the query. In the General tab: · Select the source file to use for the query by clicking the Lookup (. . . ) button on the right side of the File field. Browse to the Samples location where GLHEADER. txt file is located, usually C:\Program Files\Microsoft Dynamics\ Integration Manager\Samples, and select GLHEADER. txt. As discussed earlier, the items in the GLHEADER. txt file are separated or delimited by tab characters. · Select First Row Contains Column Names. When you select this option, Integration Manager uses the names in the text file when referring to the columns. You can view these column names in the next step. INTEGRATION MANAGER QUICK START 31 PART 2 BUILDING AN INTEGRATION When you have finished, the window should look like the following illustration: 7. Choose the Columns tab to view columns from the text file. If you correctly specified the general properties, the Columns tab displays three items under Column Name, as shown in the following illustration: If three items are not listed in the Column Name list, return to the General tab and verify that you have specified the appropriate values. [. . . ] It is analogous to an XML schema, but it usually contains more information than an XML schema. Data source An ODBC data source from which you want to retrieve data. Import command A command that approximates the structure of an XML source that you select and converts it into recordsets and fields­a structure Integration Manager can use. Data type A data source setting that indicates what type of data is contained in the column of a data source. Common data types include booleans, currencies, integers and strings. Integer A data type that stores integral numeric values. It must be in the range ­32, 768 to 32, 767. Delimiter A character or characters that separate the individual data items in a text file. Commas and tab characters are often used as delimiters. Integration group A set of integrations that are performed in succession in a specified order. INTEGRATION MANAGER QUICK START 71 GLOSSARY Integration Manager engine An Integration Manager component that receives data from the source adapter, provides mapping and transformation functionality, and passes data to a destination adapter. Recordset An element that is used to map items in an integration destination. [. . . ]