IMQuick Start

Microsoft Dynamics™ GP
Integration Manager Quick Start

Copyright Copyright © 2005 Microsoft Corporation. All rights reserved.
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. FairCom and c-tree Plus are trademarks of FairCom Corporation and are
registered in the United States and other countries.
The names of actual companies and products mentioned herein may be trademarks or
registered marks - in the United States and/or other countries - of their respective owners.
Unless otherwise noted, the example companies, organizations, products, domain names,
e-mail addresses, logos, people, places, and events depicted herein are fictitious. No
association with any real company, organization, product, domain name, e-mail address,
logo, person, place, or event is intended or should be inferred.
Intellectual property Microsoft may have patents, patent applications, trademarks, copyrights, or other
intellectual property rights covering subject matter in this document. Except as expressly
provided in any written license agreement from Microsoft, the furnishing of this document
does not give you any license to these patents, trademarks, copyrights, or other intellectual
property.
Warranty disclaimer Microsoft Corporation disclaims any warranty regarding the sample code contained in this
documentation, including the warranties of merchantability and fitness for a particular
purpose.
Limitation of liability The content of this document is furnished for informational use only, is subject to change
without notice, and should not be construed as a commitment by Microsoft Corporation.
Microsoft Corporation assumes no responsibility or liability for any errors or inaccuracies
that may appear in this manual. Neither Microsoft Corporation nor anyone else who has
been involved in the creation, production or delivery of this documentation shall be liable
for any indirect, incidental, special, exemplary or consequential damages, including but not
limited to any loss of anticipated profit or benefits, resulting from the use of this
documentation or sample code.
License agreement Use of this product is covered by a license agreement provided with the software product. If
you have any questions, please call the Microsoft Dynamics GP Customer Assistance
Department at 800-456-0025 (in the U.S. or Canada) or +1-701-281-6500.
Publication date October 2005

Contents
Introduction ................................................................................................................................. 2
What’s in this manual .................................................................................................................. 3
Prerequisites .................................................................................................................................. 4
Symbols and conventions............................................................................................................ 4
Resources available from the Help menu ................................................................................. 5
Printable manuals ......................................................................................................................... 5
Send us your documentation comments................................................................................... 6
Part 1: Getting Started ................................................................................................. 8

Chapter 1: Starting Integration Manager....................................................... 9
Starting Integration Manager...................................................................................................... 9
Getting around the main window............................................................................................ 10
Understanding the Integration Manager toolbar................................................................... 11
Using the shortcut keys ............................................................................................................. 12
Understanding the Integration Manager menus ................................................................... 13
Chapter 2: Understanding the Terminology ............................................. 17

Source ........................................................................................................................................... 17
Source adapters ........................................................................................................................... 17
Integration Manager engine...................................................................................................... 17
Destination................................................................................................................................... 18
Destination adapters .................................................................................................................. 18
Destination mappings ................................................................................................................ 18
Query ............................................................................................................................................ 18
Query relationship...................................................................................................................... 18
Part 2: Building an Integration ...................................................................... 20

Chapter 3: Creating Integrations ........................................................................ 21
Creating a new integration........................................................................................................ 21
Removing duplicate sources ..................................................................................................... 23
I N T EG R A T I O N M A N A G E R Q U I C K S T A R T i
C O N T E N T S
Chapter 4: Adding Sources ....................................................................................... 25

Understanding sources.............................................................................................................. 25
Understanding the source files ................................................................................................ 27
Creating the GL Header query................................................................................................. 29
Previewing source data ............................................................................................................. 33
Creating the GL Line query ...................................................................................................... 34
Chapter 5: Creating Query Relationships .................................................... 39

Relationship guidelines............................................................................................................. 39
Creating relationships ............................................................................................................... 39
Chapter 6: Adding a Destination ......................................................................... 43

Understanding destinations ..................................................................................................... 43
Adding the Microsoft Dynamics GP destination .................................................................. 44
Chapter 7: Mapping Source Data to the Destination ....................... 47

Understanding the Mapping window .................................................................................... 47
Mapping fields............................................................................................................................ 49
Mapping line items for the transaction................................................................................... 52
Setting options for the General Journal destination.............................................................. 56
Part 3: Running an Integration....................................................................... 60

Chapter 8: Running the Integration .................................................................. 61
Preparing to run the integration .............................................................................................. 61
Running the integration ............................................................................................................ 64
Chapter 9: Verifying the Results.......................................................................... 67

Verifying the integration results .............................................................................................. 67
What to do next .......................................................................................................................... 69
Glossary ......................................................................................................................................... 71
Index ................................................................................................................................................... 75
ii I N T E G R A TI O N M A N A G E R Q U I C K S T A R T
INTRODUCTION
Introduction
Integration Manager is a tool designed to help you move data quickly and
easily between applications—without the need for custom programming or
extensive knowledge of application databases.
In the Ingegration Manager Quick Start guide, you use simple tab-
delimited text files as a data source and Microsoft Dynamics™ GP as the
destination, but Integration Manager does not limit you to this kind of
integration. You can combine its many source and destination adapters to
create integrations that meet your needs. No matter which combination of
sources and destinations you eventually use, the steps to building and
running integrations are basically the same.
Basic steps for creating integrations

Step 1 Open a new integration.
Step 2 Add a source.
Step 3 Set source properties or establish query relationships, depending on
which source adapter you are using.
Step 4 Add a destination (and provide destination settings if the adapter requires
them).
Step 5 Map the source data to the destination.
Step 6 Run the integration.
Whether you’ve used other integration tools or you’re new to integration

technology, use this manual to familiarize yourself with Integration
Manager, the integration tool that puts information at your
fingertips—checked, verified, and ready-to-use.
This introduction includes the following information:
• What’s in this manual

• Prerequisites
• Symbols and conventions
• Resources available from the Help menu
• Printable manuals
• Send us your documentation comments
2 IN T E G R A TI O N M A N A G E R Q U I C K S T A R T
IN TRO DUCT IO N
What’s in this manual

This manual is a hands-on learning tool to help you become familiar with
Integration Manager. If you have used other data integration tools, use this
manual to understand how Integration Manager handles integrations.
Specifically, this manual shows you how to create an integration that
extracts data from an ODBC/Text source and integrates it into Microsoft
Dynamics GP. Some features described in this documentation are optional
and can be purchased through your Microsoft Dynamics GP partner.
To view information about the release of Integration Manager that you’re

using and which adapters are installed, choose Help > About Integration
Manager.
The manual is divided into the following parts:
• Part 1, Getting Started, explains how to start Integration Manager and

discusses the terminology used in the integration process.
• Part 2, Building an Integration, describes the steps used to create an

integration that extracts data from an ODBC/Text source and integrates
it into the General Ledger for Microsoft Dynamics GP. By working
through the steps, you gain a basic understanding of Integration
Manager.
• Part 3, Running an Integration, explains how to prepare to run the

integration as well as how to run it and verify the results.
After you are familiar with the steps presented in this manual, you can
continue to the Integration Manager User’s Guide which provides detailed
information about Integration Manager and the adapters.
I N T EG R A T I O N M A N A G E R Q U I C K S T A R T 3
I N T R O D U C T I O N
Prerequisites
This manual assumes you are familiar with the Microsoft Dynamics GP
family of financial applications. Knowledge of integration products and
experience working with data in tabular format is helpful, but it is not
essential to perform the tasks discussed in this manual.
This manual assumes you are using the Microsoft Dynamics GP test company. If
you are not using the test company, the sample data files may not be in the correct
format and may not work with your company without modification. You can
modify the structure in the text files by opening these files in Notepad.
Also, this manual assumes Integration Manager is already installed.

Because the tasks are arranged in sequential order, it’s important that you
perform the tasks in the order they are presented.
This manual uses the sample files GLHEADER.txt and GLLINE.txt. Before
you begin, make sure these files exist in the Samples folder, usually
C:\Program Files\Microsoft Dynamics\Integration Manager\Samples. If
you cannot locate the Sample files at this location, browse to the location
where Integration Manager was installed. If you cannot find these files,
contact your system administrator or Product Support.
General Ledger is included in the Microsoft Dynamics GP product. This manual

uses the term General Ledger to more fully describe the integration source and
destination.
Symbols and conventions

For definitions of unfamiliar terms, see the glossary in the manual or refer
to the glossary in Help.
Symbol Description
The light bulb symbol indicates helpful tips, shortcuts and
suggestions.
The warning symbol indicates situations you should be

especially aware of when completing tasks.
IN TRO DUCT IO N
This manual uses the following conventions to refer to sections, navigation

and other information.
Convention Description
Creating a batch Italicized type indicates the name of a section or procedure.
File >> Print or File > The (>>) or (>) symbol indicates a sequence of actions, such as
Print selecting items from a menu or toolbar, or pressing buttons in
a window. This example directs you to go to the File menu and
choose Print.
TAB or ENTER All capital letters indicate a key or a key sequence.
Resources available from the Help menu

The Integration Manager Help menu gives you access to user assistance
resources on your computer.
Contents
Opens the Help file for Integration Manager, and displays the main
“contents” topic. To browse a more detailed table of contents, click the
Contents tab above the Help navigation pane.
To find information in Help by using the index or full-text search, click the
appropriate tab above the navigation pane, and type the keyword to find.
Index
Opens the Help file for Integration Manager, with the Index tab active. To
find information about a window that’s not currently displayed, type the
name of the window, and click Display.
About this window

Displays overview information about the current window. To view related
topics and descriptions of the fields, buttons, and menus for the window,
choose the appropriate link in the topic. You also can press F1 to display
Help about the current window.
Printable manuals
The Integration Manager manuals are available in Adobe Acrobat .pdf
format, which you can print or view. The default installation folder for the
documentation is C:\Program Files\Microsoft Dynamics\Integration
Manager\Help\Documentation.
I N T R O D U C T I O N
Send us your documentation comments

We welcome comments regarding the usefulness of the Microsoft Dynamics
GP documentation. If you have specific suggestions or find any errors in
this manual, send your comments by e-mail to the following address:
bizdoc@microsoft.com.
To send comments about specific topics from within Help, click the
Documentation Feedback link, which is located at the bottom of each Help
topic.
Note: By offering any suggestions to Microsoft, you give Microsoft full permission
to use them freely.
PART 1: GETTING STARTED
Part 1: Getting Started
This part explains how to start Integration Manager and discusses the basic
terminology used in the integration process.
The information is divided into the following chapters:
• Chapter 1, “Starting Integration Manager,” describes how to start

Integration Manager, discusses the Integration Manager main window,
and introduces the menu commands and toolbar buttons.
• Chapter 2, “Understanding the Terminology,” introduces the

terminology used in Integration Manager.
Before you use Integration Manager, review the information in this part of
the manual. Understanding the basics of integrations makes learning the
product easier.
Chapter 1: Starting Integration Manager
As soon as you have installed Integration Manager, you can begin using it.
This chapter describes how to start Integration Manager and describes the
components that make up the Integration Manager main window.
This chapter includes the following information:
• Starting Integration Manager

• Getting around the main window
• Understanding the Integration Manager toolbar
• Using the shortcut keys
• Understanding the Integration Manager menus
Starting Integration Manager

You can start Integration Manager from the Start menu or from within
Microsoft Dynamics GP.
To start Integration Manager:

1. From the task bar, choose Start, choose Programs, and then choose
Microsoft Dynamics.
2. From the Integration Manager program group, choose Integration

Manager.
PA RT 1 G E TT I N G S T A R T ED
The main Integration Manager workspace opens.
– Or –
You also can start Integration Manager from within Microsoft

Dynamics GP. From the Tools menu, choose Integrate, and then choose
Integration Manager.
Buttons in the window become available only after you choose to create
a new integration or open an existing one.
If the Integration Manager registration window opens, you need to either

register Integration Manager or contact the Customer Assistance Department
for registration keys. You have the ability to sample some adapters without
registration keys; integrations, however, can be run only when Integration
Manager is registered.
You’re now ready to familiarize yourself with the features of Integration

Manager.
Getting around the main window

You perform all Integration Manager tasks in the main workspace. From
this workspace, you can access the following:
The Toolbar The Integration Manager toolbar consists of buttons for

commonly used commands in Integration Manager.
10 I N T E G R A TI O N M A N A G E R Q U I C K S T A R T
C H A P T E R 1 S TA R T IN G IN T E G R AT IO N M A N AG E R
The Menus The menus include the commands available in

Understanding the Integration Manager toolbar

The Integration Manager toolbar appears in the upper portion of the main
window. Each button that appears on the toolbar represents an action you
can perform in Integration Manager. The following table lists the buttons in
the toolbar:
Button Description
Creates a new integration.
Opens an existing integration.
Prints information about the integration.
Saves the current integration.
Displays the properties for an integration, source, or destination.
Opens the Object Browser.
Opens the Add Source window, from which you select a source for the
current integration. The source you can add depends on the adapter you
have installed. If you do not have any adapters installed, you can still
add an ODBC or a text source.
Opens the Relationships window, where you create relationships
between Text or ODBC source queries.
Button Description
Opens the Add Destination window, from which you select the
destination for the current integration. The destination you can add
depends on which adapters you have installed.
Opens the Integration Mapping window.
Runs the current integration.
Using the shortcut keys

Shortcut keys, also known as accelerator keys, are used with the CTRL key
for menu commands that are used often. Not all menu commands have an
accelerator key.
The following table contains a list of the shortcut keys for commonly used
menu commands.:
Menu command Shortcut key

File New Integration CTRL+N
Open Integration CTRL+O
Save Integration CTRL+S
Print CTRL+P
View Relationships CTRL+L
Integration Add Source CTRL+A
Add Destination CTRL+D
Mapping CTRL+M
Run CTRL+R
Understanding the Integration Manager menus

The following table lists the commands that are available in Integration
Manager. It also lists the access keys corresponding to the commands.
In Microsoft Windows® 2000 and Microsoft Windows XP, access keys are hidden
by default until you press the ALT key.
Menu commands Description Access key

File menu New Integration Creates a new integration. ALT+F+N
Open Integration Opens an existing integration. ALT+F+O
Close Integration Closes the current integration. ALT+F+C
New Integration Creates a new integration ALT+F+G

Group group.
Open Integration Opens an existing integration ALT+F+R
Group group.
Save Integration Saves the current integration. ALT+F+S
Save Integration Makes a copy of the current ALT+F+A

As integration.
Import Imports integrations from other ALT+F+I
Integrations Integration Manager databases
(usually IM.mdb files).
Export Exports integrations to existing ALT+F+E
Integrations IM.mdb files. You also can
create a new IM.mdb file for the
integrations you export.
Print Prints a report of the ALT+F+P
integration.
Exit Exits the current session of ALT+F+X
Edit menu Remove Script In the Integration Mapping ALT+E+S
window, removes the script
associated with a field.
Remove In the Integration Mapping ALT+E+T
Translation window, removes the
translation associated with a
field.

View menu Relationships Opens the Relationships CTRL+L
windows, in which you create
the relationship between the
text or ODBC source queries
used for the current integration.
Properties Displays the properties of the
integration, selected source or
destination.
Integration Add Source Adds a source to the current ALT+I+A
integration.
Add Destination Adds a destination for the ALT+I+D
current integration.
Remove Removes the selected source or
destination from the current
integration.
Mapping Opens the Integration Mapping ALT+I+M
window for the current
integration.
Source Settings Opens the Source Settings ALT+I+U
window allowing you to specify
connection information for the
source adapters that require
these settings.
Destination Opens the Destination Settings ALT+I+S
Settings window, allowing you to
specify connection information
for destination adapters that
require these settings.
Run Runs the current integration. ALT+I+R
Properties Displays the properties of the ALT+I+E

integration.
Tools menu Object Browser Opens the Object Browser ALT+T+O
window.
Registration Allows you to register ALT+T+R
Options Opens a window from which ALT+T+P
you can change options for
Integration Manager such as
the location of the Integration
Manager database (usually
called IM.mdb) or substitute
pathname translations.

Window Tile Horizontally Lists all open windows and ALT+W+H
menu arranges them horizontally.
Tile Vertically Lists all open windows and ALT+W+V
arranges them vertically.
Cascade Displays all open windows in ALT+W+C
cascading order.
Help menu Contents Provides access to the online ALT+H+C
help for Integration Manager.
Index Contains help topics from the ALT+H+I
online help for Integration
Manager.
About this Contains help information ALT+H+W
Window about the window displayed on
the screen.
About Provides the version, location, ALT+H+A
Integration and description of the installed
Manager Integration Manager and its
adapters.
Chapter 2: Understanding the Terminology
Before you begin using Integration Manager, you should familiarize
yourself with the terminology used throughout the product to have a better
understanding of the integration process.
This chapter includes definitions for the following terms:
• Source
• Source adapters
• Integration Manager engine
• Destination
• Destination adapters
• Destination mappings
• Query
• Query relationship
Source
A source indicates where the requested information to be integrated comes
from. In Integration Manager, a source can be anything from a comma- or
tab-delimited file, a database such as an Open Database Connectivity
source (ODBC), and Extensible Markup Language (XML) files. Sources
exist independently of the source adapters. However, which source you can
add to your integration depends on the source adapter you have installed.
Refer to Chapter 4, “Adding Sources,” for more information.
Source adapters
Source adapters connect to sources, filter, and extract data. The data is then
passed on to the Integration Manager engine for processing. The type of
source adapter you install determines which source you can add to your
integration. If you do not have any source adapters installed, you can still
add an ODBC/Text source, which this manual explains how to use.
Integration Manager engine

Working with the source adapter and destination adapter, the Integration
Manager engine helps you map and transform the source data into the
destination.
Destination
A destination indicates where you want the processed information to be
integrated. Destinations can be an application, a database, or an XML file.
Destinations also exist independently of the destination adapters. Examples
of destinations include Microsoft Dynamics GP, and XML files.
Destination adapters
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 any destination. This manual explains
how to integrate data from an ODBC/Text source through the Microsoft
Dynamics GP adapter into the Microsoft Dynamics GP General Ledger.
Destination mappings
Destination mappings define how source data is mapped to the destination.
Typically, the information comes from the source you specified, but it can
also come from a constant value or a default value in the destination. The
Integration Mapping includes several rules you can use when creating a
destination mapping.
Query
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.
Query relationship
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. Query relationships tell Integration Manager how the queries work
together during the integration. For more information on creating query
relationships, refer to Chapter 5, “Creating Query Relationships.”
PART 2: BUILDING AN INTEGRATION
Part 2: Building an Integration
This part of the manual describes how to build an integration. Each chapter
contains a detailed step-by-step procedure that you can refer to later when
creating your own integrations.
This manual uses the sample files GLHEADER.txt and GLLINE.txt. Before you
begin, make sure these files exist in the Samples folder, usually C:\Program
Files\Microsoft Dynamics\Integration Manager\Samples. If the Samples folder
cannot be located at this location, browse to the location where Integration
Manager was installed. If you cannot find these files, contact your system
administrator or Product Support.
This manual is arranged in sequential order. Therefore, it’s important that

you go through the tasks in the order they are presented.
• Chapter 3, “Creating Integrations,” discusses integrations and how you

create them.
• Chapter 4, “Adding Sources,” explains how to add sources, which

retrieve information for the integration.
• Chapter 5, “Creating Query Relationships,” describes why you need to

create query relationships and how to create them.
• Chapter 6, “Adding a Destination,” explains how to select the

destination for the integration.
• Chapter 7, “Mapping Source Data to the Destination,” describes how to

map the source data to the destination.
Chapter 3: Creating Integrations
The first step in building any integration is to create the integration. The
integration is the primary object that manages all the components necessary
to integrate data into a specified destination.
• Creating a new integration

• Removing duplicate sources
Creating a new integration

To begin an integration, you can create a new integration or open an
existing integration. This guide shows you how to create a new integration.
To create a new integration:

1. Start Integration Manager.
2. From the File menu, choose New Integration.
– Or –
From the Integration Manager toolbar, choose New Integration.
The Integration window and then the Properties window opens.
PA RT 2 B U I L D I N G A N I N TE G R A T I O N
3. In the Properties window, enter an integration name.
For this tutorial, use GL-GJ Integration, which stands for General
Ledger to General Journal Integration.
For your own integrations, use any name that helps you identify the
integration easily.
4. Optionally, enter an integration description, such as General Ledger to

General Journal Integration.
For your own integrations, describe them so that you can easily recognize each
integration. Many people enter the source of the data and its destination, while
others include a date.
5. Choose OK to close the Properties window.
The name of your integration now appears in the Integration window.
6. From the File menu, choose Save Integration.
It is a good idea to save the integration immediately after you create it, as well
as whenever you make any changes to it.
Refer to Chapter 4, “Adding Sources,” for information about adding

sources to the integration.
C H A P T E R 3 C R E A T I N G I N T E G R A T I O N S
Removing duplicate sources

If someone on your team has already worked through this Quick Start
guide, then a message similar to the following might be displayed when
you add your sources:
You can use different names for the sources, or you can remove the sources
that were previously created.
Use the following procedure if you need to remove a duplicate source in

order to use this Quick Start guide.
To remove duplicate sources:

1. From the toolbar, choose Objects.
– Or –
From the Tools menu, choose Object Browser.
The Object Browser opens.
2. From the Types pane, expand Source Adapters and then expand
ODBC/Text. Choose Text.
3. From the Objects pane, select GL Header (or GL Line) in this example,
and then choose Delete.
To select multiple sources that appear next to each other, hold down the SHIFT
key as you select the sources. To select multiple sources that are not next to
each other, hold down the CTRL key as you select the sources.
4. When the confirmation message appears, asking if you want to delete

the selected item, choose Yes.
Repeat steps 3 and 4 for GL Line (or GL Header), and then close the
Object Browser.
Chapter 4: Adding Sources
This chapter describes how to add sources to your integration. Specifically,
it describes how to add sources that query text files. Therefore, before you
complete the tasks in this chapter, you must have already created the
integration using the procedure discussed in Chapter 3, “Creating
Integrations.”
• Understanding sources
• Understanding the source files
• Creating the GL Header query
• Previewing source data
• Creating the GL Line query
Understanding sources
A source indicates where the requested information you are integrating
originates. In Integration Manager, a source can be anything from a comma-
or tab-delimited file, a database such as an Open Database Connectivity
source (ODBC), and Extensible Markup Language (XML) files. Sources
exist independently of the source adapters. However, which source you can
add to your integration depends on the source adapters you have installed.
For more information on using the source adapters you have installed, refer
to the documentation installed with each source adapter (if available).
The following table shows several available source adapters and the
supported functionality. The information in the table isn't exhaustive but is
meant to show Integration Manager’s ability to support different source
adapters.
Source adapter Supported Remarks

functionality
ODBC/Text Extracts data from This adapter is always installed with
ODBC/Text sources. Integration Manager.
Integration Manager supports three

types of ODBC/Text Sources: Text, Simple
ODBC, and Advanced ODBC. Text
sources retrieve data from text files.
Simple ODBC sources retrieve data from
an ODBC data source. Advanced ODBC
sources issue SQL statements to retrieve
information from an ODBC data source.
XML Source Adapter Extracts data from Using this adapter, you can use
XML files. Integration Manager to create
integrations that use XML files as source
data and move them into applications
that may not support XML. 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.
C H A P T E R 4 A DD IN G S O U R C E S
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.
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.
The two text files actually contain the same information as the following
two transactions:
This information is contained in

the GLHEADER.txt file.

the GLLINE.txt file.

the GLHEADER.txt file.

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.
GL Line Query This query retrieves data from the GLLINE.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.
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. Open the GL-GJ Integration if it is not already open.
2. 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.
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 GL Header
Description GL Header Query
The Name should describe the type of information retrieved by the

source.
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. Then
choose Open. The path and file name appear in the File field.
• For Delimiter, select Tab.
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.
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.
Then return to the Columns tab and choose Refresh Columns.
If three column names are displayed, the query is set up properly.
8. Choose OK to close the Properties window. The source is added to the

integration.
9. Remember to save the integration. From the toolbar, choose Save.
Previewing source data

Preview the source to verify that the correct data is being returned.
To preview source data:

1. From the Integration window, right-click on the new source.
2. From the Shortcut menu, choose Preview <GL Header>.
The Data Viewer window opens.
The following illustration shows the Data Viewer window with the
values returned by the query:
These values should look just like those in the GLHEADER.txt file.
3. Choose Close when you have finished viewing the query results.
Creating the GL Line query

Now that you have added one source that queries a text file
(GLHEADER.txt), add the second source that queries the text file
GLLINE.txt and then preview it.
To create the GL Line query:

1. Perform steps 1 through 4 exactly as specified in Creating the GL Header
query on page 29 to create another text source.
2. Enter a Name and Description for the source.
Name GL Line
Description GL Line Query
3. Specify the properties in the General tab.
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 GLLINE.txt file is located,

usually C:\Program Files\Microsoft Dynamics\
Integration Manager\Samples, and select GLLINE.txt. Then,
choose Open. The path and file name appears in the File field.
• For Delimiter, select Tab.
As discussed earlier, the items in the GLLINE.txt file are separated

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.
When you have finished entering information, the window should look
like the following illustration:
4. Choose the Columns tab to view the columns from the text file.
If you specified the general properties correctly, the Columns tab

should show four items under Column Name as shown in the
following illustration. If it doesn't, go back to the General tab and
verify that you made the entries correctly.
If four column names are displayed, the query is set up properly.
5. Choose OK to close the Query Properties window and then choose

Save.
The source name appears in the Integration window.
A message appears, explaining that you need to create query relationships. You
will create query relationships in Chapter 5, “Creating Query Relationships,”
so you can ignore this message for now.
6. Preview the source (optional).
The following Data Viewer window shows the values returned by the
query you have just created:
7. Close the Data Viewer window and save the integration.
You have added sources to your integration. You are now ready to create
query relationships in the next chapter.
Chapter 5: Creating Query Relationships
When you add more than one source that queries text files or ODBC
sources, then you need to create relationships between the sources.
Relationships tell Integration Manager how sources work together to
retrieve information for the integration. In this chapter, you create a
relationship between the two text sources you added to the GL-GJ
Integration.
• Relationship guidelines
• Creating relationships
Relationship guidelines
When creating a query relationship, keep in mind the following guidelines:
• There must be only one “root” query that has no arrows pointing into
it. This is the main query that is executed. All other queries must be
related to the “root” query in some way.
• No query or group queries can be unconnected. All queries must be

somehow connected through a sequence of relationships.
• Circular relationships are not allowed. For example, if Source A has a

relationship to Source B, Source B can't have a relationship back to
Source A.
Creating relationships
The GL-GJ Integration uses two text sources; a query relationship,
therefore, needs to be established.
To create a query relationship:

2. From the View menu, choose Relationships.
– Or –
In the Integration window, double-click Query Relationships.
The Relationships window opens showing you the GL Header query,

which retrieves information from the GLHEADER.txt file, and the GL
Line query, which retrieves information from the GLLINE.txt file.
3. Draw a line between the corresponding columns in the two queries to

define the relationship.
In the GL Header window (the master query), click and drag (while
holding down the left mouse button) from DocNum to DocNum in the
GL Line window. Release the button when the text icon appears on
C H A P T E R 5 C R E A TI N G Q U E R Y R E L A T I O N S H I P S
your mouse pointer. A line appears that connects these two queries,
indicating the relationship has been created.
The GL Header query is considered the master, and the GL Line query
is the child. Each time Integration Manager reads a row from the GL
Header query, it should read the corresponding line items from the GL
Line query.
4. Choose Close to close the Relationships window.
All relationships you create are verified. If problems exist, an error

message appears. If an error appears, open the Relationships window
and correct the problem.
You have completed adding sources to the integration and defined their
relationship. Refer to Chapter 6, “Adding a Destination,” for information
on adding the destination to where this source data integrates.
Chapter 6: Adding a Destination
This chapter describes how to add a destination to your integration.
Specifically, it describes how to add a Microsoft Dynamics GP destination,
General Ledger. You can add a destination at any time when you build an
integration, but you might want to add it after you add the source so that
you’ve had a chance to become more familiar with the source data.
• Understanding destinations
• Adding the Microsoft Dynamics GP destination
Understanding destinations
Destinations define where you want the source data to be integrated, and
they can be other applications, a database, or an XML file. Which
destination you can add to your integration depends on which destination
adapters you have installed.
For more information on using the destination adapters you have installed,
refer to the specific adapter guide, if available.
The following table describes several destination adapters. The information

in the table isn’t exhaustive. Instead, it is meant to show Integration
Manager’s ability to support different destinations.
Destination Supported Remarks

adapter functionality
XML Destination Integrates data into The XML Destination Adapter can help
Adapter XML files. you transform just about any source to
any XML format. You define the
destination’s document definition, the
metadata that Integration Manager uses
to describe the structure and content of a
source or destination. Analogous to an
XML schema, the document definition
describes recordsets, hierarchical
relationships, fields, data types, field
lengths, and more.
Destination Supported Remarks

adapter functionality
Great Plains Integrates data into The Great Plains adapter includes
already defined predefined destinations for the following
destinations in Microsoft Dynamics GP modules:
Microsoft Dynamics Financial, Payables Management,
GP. Receivables Management, Sales Order
Processing, Payroll, Inventory, and Setup.
Great Plains SQL Integrates data faster The predefined destinations in the Great
Optimized than the Great Plains Plains SQL Optimized adapter include:
adapter, but it Customer, Inventory Transaction,
includes different Inventory Item, Purchase Order,
destinations. Receivings Transaction, Sales Order
Transaction, and GL Account, GL
Transaction, and Shipping Method.
Direct-to-Table Integrates directly Because this adapter integrates data into
into tables through tables, you can create integrations into
an ODBC data destinations not already defined by
source. Integration Manager (unlike the Great
Plains adapters). It also includes a
custom destination designer.
Adding the Microsoft Dynamics GP destination

This Quick Start explains how to integrate data from an ODBC/Text source
through the Great Plains adapter into the Microsoft Dynamics GP General
Ledger destination.
To add the Microsoft Dynamics GP destination

2. From the Integration menu, choose Add Destination.
– Or –
Right-click on Destination in the Integration window, and from the

menu that appears, choose Add Destination.
C H A P T E R 6 A DD IN G A DE S T IN A T IO N
The Add Destination window opens.
3. In the Add Destination window, expand the Great Plains folder and
choose Financial.
4. In the Destinations pane of the Add Destination window, choose

General Journal and then choose Open.
The General Journal is added as the destination of the integration.
Chapter 7: Mapping Source Data to the
Destination
Before completing the tasks presented in this chapter, be sure that you have
created the queries for the integration, set up the relationship between the
two queries, and selected General Journal as the integration destination.
These tasks are described in the preceding chapters.
• Understanding the Mapping window

• Mapping fields
• Mapping line items for the transaction
• Setting options for the General Journal destination
Understanding the Mapping window

Destination mappings describe how Integration Manager should map
source data to the appropriate fields in the destination. Although many
values come from the source, values can come from constant values or
default values—all are defined in the Integration Mapping window.
To open the Mapping window:

2. From the Integration menu, choose Mapping.
– Or –
In the Integration window, double-click Destination Mapping.
The Integration Mapping window opens.
A mapping is composed of rules, which define where the information

for an item in the destination originates. Several rules are available in
Integration Manager. For more information on rules, refer to the
Integration Manager User's Guide.
You will use the following rules for the GL-GJ Integration:
Use Source Field Information for the field comes from the source.
Use Constant Information for the field comes from a constant value.
Use Default The default or current value from the destination is

used.
Use Positive Source For debit fields, positive values are imported
as is. Negative values are imported as zero.
Use Negative Source For credit fields, negative values are

imported as the corresponding positive value. Positive values are
imported as zero.
C H A P T E R 7 M AP P IN G S O U R C E D AT A T O T H E DE S T IN A T IO N
Mapping fields
Based on the destination you select, Integration Manager maps and sets
rules for several fields, which you can change. In this Quick Start, you will
map the fields in the root recordset labeled General Journal. Specifically,
you will change the rules for and mapping of the Batch ID field, Reference
field, and Transaction field.
To map the Batch ID, Reference, and Transaction

fields:
1. For the Batch ID field, click in the Rule column. Then click the drop-
down arrow and from the list that appears, choose Use Constant.
Click in the Rule

column to display a list
of rules for Batch ID.
Each transaction integrated into the destination is assigned to the batch

indicated by the value in the Batch ID field. For the GL-GJ Integration,
a constant value is being used for the batch ID.
2. To set the constant value for the Batch ID field, click in the Source
column and enter SAMPLE BATCH (in uppercase).
– Or –
In the Rule Properties section of the window, click in the Value column
for Constant Value and enter SAMPLE BATCH (in uppercase).
Enter SAMPLE BATCH

as the constant value.
3. For the Reference field, note that Integration Manager sets the rule to
Use Source Field. This rule indicates that the information comes from
one of the text source files for the integration. This rule is appropriate
for this integration, so do not change it.
4. To map the Reference field, click in the Source column, and a Lookup
(...) button appears. Click the Lookup button to open the Source Object
window.
Click the Lookup

button to select a field
from a query.
If the Lookup button does not appear, click in another field and then click in
the Source column for the Reference field again.
5. In the Source Object window, select the GL Header source from the
drop-down list. Then, choose Reference, and then Select.
Select the GL
Header source.
Choose the
Reference
column from
the query.
In the Integration Mapping window, notice that “Reference” appears in

the Source column.
6. Now, set the rule for transaction date to Use Source Field, and then
click the Lookup button in the Source column.
7. Because the value for transaction date will come from the Date field in
the GL Header source file, make the following selections in the Source
Object window:
Source GL Header
Column Date
8. Choose Select.
The Integration Mapping window should look like the following:
Mapping line items for the transaction

In the upper left pane of the Integration Mapping window, the child
recordsets sit below the root recordset, which is General Journal for this
integration. To map the fields in the child recordsets, select the appropriate
child recordset in this left pane, and its fields appear to the right. For this
Quick Start, you will map the line items that are part of the Entries child
recordset.
To map the line items for the transaction:

1. Choose Entries in the upper-left corner of the Integration Mapping
window. The fields for this recordset appear.
Select Entries to view the

fields in the recordset.
2. For the Account Number field, make sure the rule is set to Use Source
Field and then click in the Source column. The, click the Lookup
button.
The Source Object window, opens.
3. In the Source Object window, make the following selections:
Query GL Line
Column Account Num
In order for the Lookup button to appear, you may need to click in the Rule
column and then in the Source column.
4. In the Source Object window, choose Select.
The Integration Mapping window looks like the following:
5. For the Debit Amount field set the rule to Use Positive Source Field.
This means positive values are imported as they are, while any negative
values are imported as the value 0 (zero).
The line items for the GL-GJ Integration contain only one amount per
line. Some of the transaction amounts are positive, while others are
negative. Positive values are intended to be debit values, while negative
values are intended to be credit values.
Each entry in Integration Manager requires a debit entry and a credit

entry. Integration Manager is capable of using a single value for both
fields by using two special rules: Use Positive Source and Use
Negative Source.
6. For the Debit Amount field, click the Lookup button in the Source
column to display the Source Object window. Make the following
selections and then choose Select.
Query GL Line
Column Amount
The Integration Mapping window should look like the following:
7. For the Credit Amount field, set the Rule column to Use Negative
Source Field.
You are importing negative values which are designated as a corresponding

credit amount.
8. For the Credit Amount field, click the Lookup button in the Source
column to display the Source Object window. Make the following
selections and then choose Select and Close.
Query GL Line
Column Amount
9. Choose Select.
The Integration Mapping window should now look similar to the

following:
Setting options for the General Journal

destination
At the beginning of this lesson you specified that a constant value is used as
the batch ID for this set of transactions. Now you need to create the batch. A
special option for the General Journal destination allows you to do this.
To set the options for the General Journal

destination:
1. From the Integration Mapping window, select the General Journal item
in the upper-left corner of the window.
2. Choose the Options tab.
To view options, select

General Journal and then
choose the Options tab.
3. Set the rule for the Missing Batch option to Add New Batch.
The new batch is created based on the value you supplied for the Batch
ID field.
4. Close the Integration Mapping window.
PART 3: RUNNING AN INTEGRATION
Part 3: Running an Integration
This part of the manual describes how to run an integration, and how to
verify the results. Each chapter contains a step-by-step procedure that you
can refer to later when creating your own integrations.
• Chapter 8, “Running the Integration,” describes how to run an

integration after it has been created.
• Chapter 9, “Verifying the Results,” explains how to verify the results of

the GL-GJ Integration after running it.
Chapter 8: Running the Integration
This chapter describes how to run the GL-GJ Integration you created and
discusses the information you should be aware of before running an
integration.
• Preparing to run the integration

• Running the integration
Preparing to run the integration

Before running the GL-GJ Integration you have created, you must specify
the remaining integration properties.
To prepare to run the Integration:

1. Open the GL-GJ Integration, if it is not already open.
2. From the Integration menu, choose GL-GJ Integration Properties.
– Or –
Right-click on the Integration, and from the menu that appears, choose
GL-GJ Integration Properties.
PA RT 3 R U N N I N G A N I N T E G R A TI O N
3. In the Destination Edit Mode field, click the drop-down arrow and
select Insert Only, if it’s not already selected.
The Destination edit mode indicates how the source data will be
integrated into the Destination. Which mode you can select depends on
the Destination. When you first create an integration, the available
Destination edit mode is Insert Only, the default value.
The following table describes the Destination edit mode:
Mode Description
Insert Only Creates only new records during the integration.
Existing records cannot be updated.
Update Only Updates existing records during the integration. New
records cannot be created.
Insert and Update Creates new records and updates existing records
during the integration.
4. Enter 10 in the Maximum Number of Errors field and the Maximum

Number of Warnings field.
These settings represent the maximum number of errors and warnings

that occur before an integration is automatically stopped.
It is important to understand the difference between an error and a

warning in Integration Manager. When an error occurs, typically
because of a condition in the data that’s not valid, the document fails to
integrate. When a warning occurs, the document does integrate, but
Integration Manager provides information about the problem so that
you can resolve it.
Although this integration doesn’t use them, you can add VBScripts to an
integration by using the Scripts tab. The scripts are executed at various points
during the integration. For more information on adding scripts, refer to the
Integration Manager User's Guide.
C H A P T E R 8 R U N N I N G T H E I N TE G R A T I O N
5. Choose the Logs tab to examine the level of detail to be shown for the
log and the location of the log files created by Integration Manager.
Logs can either be stored in a text file or in the same Access database
file that stores integrations. Storing the log in the Access database file
allows it to be available to users of Integration Manager in a network
environment. See the Integration Manager User’s Guide for more
information about removing log files and compacting the database.
If you store the log in a text file, you need to specify the directory that
will contain the log. By default, text file logs are stored in the Logs
directory located where you installed Integration Manager.
6. After examining the default settings, choose OK to save the log

properties. The Properties window closes.
For more information on logs, refer to the Integration Manager User's

Guide.
7. Choose Save.
Running the integration

Now that you have made final preparations to the integration, you are
ready to run it.
To run the integration:

1. Because you are using the Great Plains adapter, you must open the
Microsoft Dynamics GP application.
2. Start Integration Manager and open the GL-GJ Integration if it’s not
already open.
Running an integration requires that Integration Manager is registered. If you

do not have registration keys, you can sample some adapters, but you cannot
run an integration. To register Integration Manager, see the Integration
Manager User’s Guide.
3. From the Integration menu, choose Run.
The integration begins. After a moment, the Progress window opens.

This window indicates progress as items are read by the integration.
C H A P T E R 8 R U N N I N G T H E I N TE G R A T I O N
If you set up the integration properly, two documents should be

queried and successfully imported with no warnings or errors. If there
are any errors or warnings, check the following items:
• Be sure that the queries are set up and returning the proper data.
• Verify that the query relationship is set up correctly.
• Check the destination mapping to be sure that you have mapped all
of the fields correctly.
4. If the integration completed without any errors or warnings, choose

Close to close the Progress window and continue reading the next
chapter to learn more about verifying the results of an integration.
Chapter 9: Verifying the Results
After you have completed the GL-GJ Integration and it has successfully
run without any errors or warnings, you can verify if the data being
returned is valid. This chapter shows you how to verify the results of the
GL-GJ Integration.
• Verifying the integration results

• What to do next
Verifying the integration results

The GL-GJ Integration you created uses the General Journal object in
Microsoft Dynamics GP as its destination.
To verify the integration results:

1. Open Microsoft Dynamics GP if is not already open.
2. From the Transactions menu, choose Financial, then choose Batches to

open the Batch Entry window.
3. Click the Batch ID lookup button and then select the batch called
SAMPLE BATCH.
4. Choose Transactions to display the transactions that are part of the

new batch.
C H A P T E R 9 V E R I F Y I N G T H E R ES U L T S
5. Click the Previous Record browse button twice to navigate to the first
record in the batch.
This should be the first record that was imported by Integration

Manager.
The Batch ID field, Transaction Data field, Reference field, and all the
line items should match the first sample transaction. Refer to the Source
section in Understanding the source files on page 27
6. Click the Next Record browse button to display the next record in the
batch.
This record should match the second sample transaction. If both

records match, you have successfully completed the GL-GJ
Integration.
What to do next
Now that you are familiar with the basics of Integration Manager, you can
begin creating your own integrations. For more information about how to
use Integration Manager, refer to the Integration Manager User's Guide.
You can also refer to the Integration Manager online help for descriptions of
each window. For more information about adapters, refer to the
appropriate adapter guide (if available).
If you want to continue to learn Integration Manager using samples, you

can use the sample files usually located in C:\Program Files\Microsoft
Dynamics\Integration Manager\Samples.
The steps you take using the samples may be different from the steps in this Quick
Start.
Glossary Destination
Where data gathered by Integration
Double
A data type that stores a double-precision
Manager is placed in Microsoft Dynamics floating point number. The value can
Adapter GP. Integration Manager provides have up to fifteen significant digits.
An Integration Manager component that several common destinations, such as
Negative values must be in the
connects to a destination or source customer information or receivables
application or other data source such as transactions. range –1.79769313486232E308 to
–4.94065645841247E–324.
XML.
Destination adapter
Positive values must be in the
Advanced ODBC query A feature that validates data before
range 4.94065645841247E–324 to
A query that issues a SQL statement to integrating it to the destination
1.79769313486232E308.
retrieve information from an ODBC data application or database such as Microsoft
source. See also Simple ODBC query. Dynamics GP, XML, and Microsoft SQL Enumeration
Server. A data type that is restricted to a fixed set
Boolean
of named values. Enumeration fields in a
The logical value true or false. Destination mapping
destination correspond to list boxes,
Where information for each item in the
Comma-delimited file drop-down lists and other list controls in
integration destination originate. For
A text file that uses commas to separate Microsoft Dynamics GP. When you set
many items in the destination, the
the individual data items in the text file. the value of an enumeration field, you
destination mapping indicates that
supply the integer value that corresponds
Collections information originates from a query. For
to one of the items in the enumeration.
other items, the mapping indicates that a
See Recordset. See also Translation.
constant value or a default value from
.CSV file Microsoft Dynamics GP should be used. Field
An acronym for Comma-Separated In the XML Destination Properties
Values. It indicates a text file that uses
Display name
window, field represents an XML
In the XML Destination Properties
commas to separate the individual data attribute or an XML element containing
items. window, display name refers to the name
only data. It also can represent part of a
of the Root Recordset. You may use any
mixed element.
Currency name that is appropriate for the source
A data type that is intended to hold you are defining. Typically, this is the Filter
monetary values. It can have up to four name of the object that theRoot Recordset Specifies the criteria for determining
decimal places and must be in the range – represents. precisely which documents you want to
922,337,203,685,477.5808 to extract from the source. You can define
922,337,203,685,477.5807.
Document definition
filters only for those fields located in the
The metadata that Integration Manager
Root Recordset.
Data source uses to describe the structure and content
An ODBC data source from which you of a source or destination. It describes Import command
want to retrieve data. recordsets, hierarchical relationships, A command that approximates the
fields, data types, field lengths, and more. structure of an XML source that you
Data type It is analogous to an XML schema, but it select and converts it into recordsets and
A data source setting that indicates what usually contains more information than fields–a structure Integration Manager
type of data is contained in the column of an XML schema. can use.
a data source. Common data types
include booleans, currencies, integers Integer
and strings. A data type that stores integral numeric
values. It must be in the range –32,768 to
Delimiter 32,767.
A character or characters that separate
the individual data items in a text file. Integration group
Commas and tab characters are often A set of integrations that are performed
used as delimiters. in succession in a specified order.
GLOS SA RY
Integration Manager engine Recordset Source

An Integration Manager component that An element that is used to map items in Indicates where the data to be integrated
receives data from the source adapter, an integration destination. There are two comes from. A source can either be a text
provides mapping and transformation types of recordsets. One type of recordset file, a database, or an application
functionality, and passes data to a simply groups related fields in the
destination adapter. destination. The other type of recordset Source adapter
indicates that several sets of fields in the A feature that connects to a database, text
Join recordset can be associated with a single file or application source. It filters and
A database operation that combines some instance of a record imported into the extracts the data from the source before
or all records from two or more tables. destination. These recordsets are passing the information to the
represented by the folder icon. Integration Manager engine.
Long integer
A data type that stores integral numeric Rejection file Source data
values. It must be in the range A text file that contains records that were Shows data from the source one
–2,147,483,648 to 2,147,483,647. rejected from text queries by Integration document at a time and in the structure
Manager. Rejection files have the .rjt of the document definition.
LongVarChar
extension. Source name
A data type that stores a sequence of up
to 65,535 characters. Restriction The name of the source document
A set of criteria that allows you to specify definition that you are setting up. This
Mixed element name appears in the Add Source
Those elements that contain child the rows that will be included in a query.
All rows that do not fit the criteria are window. You may use any name that
elements to attributes as well as data. helps you easily identify this source
excluded.
Null document definition.
A keyword that indicates a field or
Root recordset
In the XML Destination Properties Source settings
variable does not contain valid data. Source settings connect the source
window, root recordset represents the
Numeric object that contains the entire source document definition to an actual source
document definition, including the Root by having you specify certain
A data type specific to Integration
Recordset and its properties, all child parameters. They are additional
Manager. It stores decimal values that
can have up to 19 digits with up to 5 of recordsets of the Root and their properties relating to a source and are
properties, and all fields within all associated with an individual integration.
the digits after the decimal point.
recordsets and their properties. They are not, however, automatically
Query inherited by other integrations that use
A request for information. In Integration Rule the same source document definition.
Manager, a query can request Defines where the information for an
information from text files or from ODBC item in the destination mapping String
originate. A data type that stores a sequence of up
data sources.
to 255 characters.
Query builder Simple ODBC query
A tool in Integration Manager to aid A query that retrieves data from an Tab-delimited file
ODBC data source. See also Adapter. A text file that uses tab characters to
writing a SQL statement to use for an
advanced ODBC query. separate the individual data items in the
Single text file.
Query relationship A data type that stores a single-precision
A relationship between two queries that floating point number. The value can Text query
have up to seven significant digits. A query that retrieves data directly from
defines how they work together to
text files.
retrieve information.
Negative values must be in the range
–3.402823E38 to –1.401298E–45. Translation
Allows you to define a relationship
Positive values must be in the range between values in the source file and
1.401298E–45 to 3.402823E38. corresponding values that are used for
the destination field.
G L O S S A R Y
VBScript
A subset of the Microsoft Visual Basic
programming language that is embedded
into Integration Manager to provide
scripting capabilities.
XML
Extensible Markup Language (XML) is
the standard method of viewing data on
the Web. Rich, structured data from any
application can be easily described in a
standard and consistent manner through
the use of XML. It also is a
complementary format of HTML.
XML node type

The name of the XML node in the source
document that this Recordset represents.
This name must match the one in the

source.
XSLT
eXtensible Stylesheet Language for
Transformations (XSLT) is used as a part
of XSL, which functions as a stylesheet
language for XML. XSL includes an XML
vocabulary for specifying formatting;
XSL specifies the styling of an XML
document by using XSLT to describe how
the document is transformed into another
XML document that uses the formatting
vocabulary.
Index Add Source
command 14
commands (continued)
Export Integrations 13
shortcut key 12 File 13
A Add Source button 11 Help 15
About Integration Manager, command Add Source window Import Integrations 13
15 Adapters pane on 29 Index 15
About this Window, command 15 Sources pane on 30 Integration 14
accelerator keys 11-13 adding keyboard shortcuts 13
access key a destination 44 mapping 14
About Integration Manager 15 a new source 25 New Integration 13
About this Window 15 available, sources 26 New Integration Group 13
Add Destination 14 Object Browser 14
Add Source 14 B Open Integration 13
Cascade 15 Batch Entry window, transactions on Open Integration Group 13
Close Integration 13 68 Options 14
Contents 15 button Print 13
Destination Settings 14 Add Destination 12 Properties 14
Exit 13 Add Source 11 Registration 14
Export Integrations 13 mapping 12 Relationships 14
Import integrations 13 New Integration 11 Remove 14
Index 15 Objects 11 Remove Script 13
mapping 14 Open Integration 11 Remove Translation 13
New Integration 13 Print 11 Run 14
New Integration Group 13 Properties 11 Save Integration As 13
Object Browser 14 Relationships 11 Source Settings 14
Open Integration 13 Run 12 Tile Horizontally 15
Open Integration Group 13 Save 11 Tile Vertically 15
Options 14 Tools 14
Print 13 C Constant value, entering on the
Properties 14 Cascade, command 15 Integration Mapping window 50
Registration 14 Child Recordset Contents, command 15
Remove Script 13 Integration Mapping window for creating
Remove Translation 13 53 a new integration 21
Run 14 Integration Mapping window for a query relationship 39
Save Integration As 13 completed 56 steps to create an integration 2
Source Settings 14 mapping Fields in the 52 the GL Header query 29
Tile Hortizontally 15 Close Integration, commands 13 the GL Line query 34
Tile Vertically 15 commands
adapters About Integration Manager 15 D
destination adapters defined 18 About this Window 15 Data Viewer window
source adapters defined 17 Add Destination 14 for the GL Header query 34
Add Destination Add Source 14 for the GL Line query 37
command 14 Cascade 15 destination
shortcut key 12 Close Integration 13 adding to an integration 44
Add Destination button 12 Contents 15 defined 18
Add Destination window, Financial defined 10 destination adapter
pane on 45 Destination Settings 14 44
Exit 13
I N D E X
destination adapter (continued) GL Line query (continued) M

Direct-to-Table 44 Properties window for 35 Main window, using 10
SQL Optimized 44 GLHEADER.txt file mapping
XML 43 defined 28 command 14
destination adapters, defined 18 displayed 27 Fields 49
Destination Edit Mode 62 GLLINE.txt file Fields in the Child Recordset 52
destination mappings, defined 18 defined 28 Fields on the Integration Mapping
Destination Settings, command 14 displayed 27 window 49
destinations, understanding 43 Great Plains, SQL optimized shortcut key 12
Direct-to-Table, destination adapter destination adapter defined 44 mapping button 12
defined 44 Great Plains adapter defined 44 menus, defined 11
documentation
printable manuals 5 H N
symbols and conventions 4 Help, command 15 navigation, symbols used for 4
help, displaying 5 New Integration
E Help menu, described 5 button 11
engine, Integration Manager engine commands 13
defined 17 I shortcut key 12
errors icons, used in manual 4
New Integration Group, commands 13
Maximum Number of 62 Import Integrations, command 13
when running integrations 65 Index, command 15 O
Exit, command 13 Integration, command 14 Object Browser
Export Integrations, command 13 integration command 14
creating a new 21 window, Types pane on 23
F defined 21 Object Browser window, Objects pane
Field, specifying on the Integration preparing to run an integration 61 on 24
Mapping window 51 running an integration 64 Objects button 11
Fields steps to create 2 ODBC/Text
mapping 49 troubleshooting 65 defined 26
mapping in the Child Recordset 52 Integration Manager Engine, defined sources types 26
File, commands 13 17 Open Integration
Integration Manager Main window 10 commands 13
G Integration Mapping window 48 shortcut key 12
GL Header query Child Recordset on 53 Open Integration button 11
Columns tab on Properties completed 52 Open Integration Group, commands 13
window for 32 entering Constant value on 50 Options, command 14
creating 29 for the Child Recordset completed options, specifying 56
defined 28 56
General tab on Properties window mapping Fields on 49 P
for 31 opening 47 preparing, to run an integration 61
Properties window for 30 Options tab on 57 prerequisites 4
GL Line query specifying a Field on 51 previewing, source data 33
Columns tab on Properties understanding 47 Print
window for 36 Integration Properties window 61 command 13
creating 34 Integration window 22 shortcut key 12
defined 28 Print button 11
General tab on Properties window L
for 36 logs, specifying settings 63
I N D E X
Procedures Relationships window 40, with troubleshooting, integrations 65

creating a new integration 21-22 relationship defined 41
creating GL Header query 29-33 Remove, command 14 U
creating GL Line query 34-37 Remove Script, command 13 Use Constant Rule 48
creating query relationships 40-41 Remove Translation, command 13 Use Default Rule 48
mapping fields 49-52 resources, documentation 5 Use Negative Source Rule 48
mapping Fields in the Child results, verifying 67 Use Positive Source Rule 48
Recordset 53-56 Rules Use Source Field Rule 48
opening the destination Use Constant Rule 48
Integration Mapping window Use Default Rule 48 V
47-48 Use Negative Source Rule 48 verifying, results 67
preparing to run the integration Use Positive Source Rule 48
61-63 Use Source Field Rule 48
W
warnings
previewing source data 33-34 Run
Maximum Number of 62
removing source queries 23-24 button 12
when running integrations 65
running an integration 64-65 command 14
starting Integration Manager 9-10 shortcut key 12 X
verifying results 67-69 running, Integration Manager 9 XML
Progress window 64 destination adapter defined 43
Properties S Source Adapter defined 26
command 14 Save button 11
window 21 Save Integration, shortcut key 12
Properties button 11 Save integration As, command 13
Properties window shortcut keys 11-13
Columns tab on GL Header query source
32 adding a new 25
Columns tab on GL Line query 36 defined 17, 25
for GL Header query 30 duplicate query names 23
General tab on GL Header query previewing data 33
31 understanding sample files 27
General tab on GL Line query 36 source adapters, defined 17
GL Line query 35 Source Object window 51
source sample files 27
Q Source Settings, command 14
query specifying
creating a relationship 39 a Field on the Integration
defined 18 Mapping window 51
duplicate source query names 23 log settings 63
GL Header 29 options 56
GL Line 34 starting, Integration Manager 9
relationship defined 18 symbols, used in manual 4
relationship guidelines 39 symbols and conventions, defined 4
R T
Registration, command 14 terminology 17
Relationship, command 14 Tile Horizontally, command 15
Relationships, shortcut key 12 Tile Vertically, command 15
Relationships button 11 Tools, command 14

IMQuick Start

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

IMQuick Start

Transféré par

Droits d'auteur :

Formats disponibles

Microsoft Dynamics™ GP

Integration Manager Quick Start

Publication date October 2005

Part 1: Getting Started ................................................................................................. 8

Chapter 2: Understanding the Terminology ............................................. 17

Part 2: Building an Integration ...................................................................... 20

Chapter 4: Adding Sources ....................................................................................... 25

Chapter 5: Creating Query Relationships .................................................... 39

Chapter 6: Adding a Destination ......................................................................... 43

Chapter 7: Mapping Source Data to the Destination ....................... 47

Part 3: Running an Integration....................................................................... 60

Chapter 9: Verifying the Results.......................................................................... 67

Basic steps for creating integrations

Whether you’ve used other integration tools or you’re new to integration

This introduction includes the following information:

• What’s in this manual

What’s in this manual

To view information about the release of Integration Manager that you’re

The manual is divided into the following parts:

• Part 1, Getting Started, explains how to start Integration Manager and

• Part 2, Building an Integration, describes the steps used to create an

• Part 3, Running an Integration, explains how to prepare to run the

Also, this manual assumes Integration Manager is already installed.

General Ledger is included in the Microsoft Dynamics GP product. This manual

Symbols and conventions

The warning symbol indicates situations you should be

This manual uses the following conventions to refer to sections, navigation

Resources available from the Help menu

About this window

Send us your documentation comments

The information is divided into the following chapters:

• Chapter 1, “Starting Integration Manager,” describes how to start

• Chapter 2, “Understanding the Terminology,” introduces the

This chapter includes the following information:

• Starting Integration Manager

Starting Integration Manager

To start Integration Manager:

2. From the Integration Manager program group, choose Integration

The main Integration Manager workspace opens.

You also can start Integration Manager from within Microsoft

If the Integration Manager registration window opens, you need to either

You’re now ready to familiarize yourself with the features of Integration

Getting around the main window

The Toolbar The Integration Manager toolbar consists of buttons for

The Menus The menus include the commands available in

Understanding the Integration Manager toolbar

Opens an existing integration.

Prints information about the integration.

Saves the current integration.

Displays the properties for an integration, source, or destination.

Opens the Object Browser.

Opens the Integration Mapping window.

Runs the current integration.

Using the shortcut keys

Menu command Shortcut key

Open Integration CTRL+O

Save Integration CTRL+S

View Relationships CTRL+L

Integration Add Source CTRL+A

Add Destination CTRL+D

Understanding the Integration Manager menus

Menu commands Description Access key