CRM Groupware Integration - Configuration and Setup Guide

CRM 5.0 July 2006 English

CRM to Groupware Setup Guide

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany

Building Block Configuration Guide

SAP Best Practices CRM & Groupware Integration Setup Guide

Copyright © Copyright 2006 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

© SAP AG Page 2 of 26


Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation. Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.



Contents Configuration Guide......................................................................................................................... 5

1 Prerequisites......................................................................................................................... 5 2 CRM Local Settings.............................................................................................................. 5

2.1 SAP CRM....................................................................................................................... 5 2.1.1 Determine Parameters for the Groupware Adapter .............................................. 5 2.1.2 Determine relative path of the SOAP Listener ...................................................... 6 2.1.3 Define RFC Destination for the MAPBox .............................................................. 8 2.1.4 Define Internal SyncPoint Settings...................................................................... 10 2.1.5 Fetching Metadata for BUS_TRANS_MSG......................................................... 10 2.1.6 Get Activity Categories for Master Category List ................................................ 11 2.1.7 Get Business Partner Roles for Master Category List ........................................ 12 2.1.8 Applying Filter Conditions to the GWA_APPLN_MSG........................................ 13 2.1.9 Define Filter Conditions for Business Partner Exchange with Groupware.......... 15 2.1.10 Map Activity Status with Groupware.................................................................... 15 2.1.11 Map Activity Text Types and Business Partners to Groupware.......................... 16

2.2 Middleware Setting for Groupware Integration ............................................................ 17 2.2.1 Generate Runtime objects for Groupware Integration ........................................ 17 2.2.2 Creating Sites for the Groupware Adapter .......................................................... 18 2.2.3 Creating Subscriptions for the Groupware Integration ........................................ 20 2.2.4 Maintain General Groupware Settings ................................................................ 22 2.2.5 Loading the Customizing objects to Groupware.................................................. 22 2.2.6 Monitoring Initial Load ......................................................................................... 25



Configuration Guide

1 Prerequisites This document describes the configuration and connectivity in CRM for Groupware Integration. Installation of Groupware Connector and Mapbox are not described in detail, unless required.

• You use SAP CRM 5.0

• You have installed Microsoft Exchange 2000/2003

2 CRM Local Settings This chapter describes all local settings that are necessary for each required component.

2.1 SAP CRM

2.1.1 Determine Parameters for the Groupware Adapter

Use To determine the URL for the SOAP Request

Prerequisites

Procedure 1. Access the activity using one of the following navigation options:

Transaction code SMICM

SAPCRM menu

2. Choose Goto → Services.

3. Go to details



4. Go back to the SAP Easy Access menu.

2.1.2 Determine relative path of the SOAP Listener

Use To determine relative path of the SOAP Listener

Prerequisites


Transaction code SICF

SAPCRM menu

2. Choose Program → Execute.

3. Expand the Tree Structure default_host -> SAP -> bc -> SOAP -> rfc

4. Go to details



5. Go back to the tree node and right click to

6. Following popup will appear, however no details may be seen after.



7. Go back to the SAP Easy Access menu.

2.1.3 Define RFC Destination for the MAPBox

Use The purpose of this activity is to create a logical system for your Groupware System. To enable communication between systems within your system landscape, you must

1. Define the systems as logical systems.

2. Assign the logical system for the Groupware System to a client.

This enables the systems to recognize the target system as an RFC destination. If the logical system has already been created, skip this activity.

Logical systems are defined cross-client

Procedure 1. Access the activity using the following navigation options:

Transaction code Sm59

SAP CRM IMG menu

2. Choose New Entries.

3. In the column Log.System, enter a name for the logical system that you want to create.



We recommend that you use the following naming convention:

<system ID>CLNT<client number> (for example: ES7CLNT020)

• <system ID> is the ID number of your ECC system

• <client number> is the number of the relevant client in your ECC system.

4. In the column Name, enter a description of the logical system.

Log. System Name

<Logical system 2>, (for example ES7CLNT020) Mapbox <Client>

5. Maintain Technical settings as shown below.

Make sure the MAPBOX700 program is registered in the target system.

Make sure is checked in “MDMP & Unicode” tab.

6. Click on and the response should be as shown below. Else Contact MapBox Administrator to restart the MapBox Service.



2.1.4 Define Internal SyncPoint Settings

Use The purpose of this activity is to make an assignment for the logical system. Skip this activity if a logical system is already assigned to your client.


Transaction code

SAP CRM IMG menu CRM CRM MW and related Components Internal SyncPoint Define Internal SyncPoint Settings

2. Choose Enter Mapbox RFC Destination in Configuration table.

3. Maintain the below parameter.

4. Choose Limit the Number of Processing Retries

5. Maintain the below parameter.

2.1.5 Fetching Metadata for BUS_TRANS_MSG

Use




Transaction code SE37

SAP CRM menu

2. Select Function Module GWA_FILL_METADATA_DNLOAD_TABLE and execute

3. In the PI_BDOC_NAME maintain BUS_TRANSACTION_MESSAGE and execute.

2.1.6 Get Activity Categories for Master Category List

Use



SAP CRM menu

4. Select Function Module GWA_FILL_ACTCAT_TO_MASTERCAT and execute

5. All Values should be copied successfully..



2.1.7 Get Business Partner Roles for Master Category List

Use



SAP CRM menu

2. Select Function Module GWA_FILL_BPROLE_TO_MASTERCAT and execute



On Click of execute, nothing happens if successful. ☺

2.1.8 Applying Filter Conditions to the GWA_APPLN_MSG

Use


Transaction code R3AC3

SAP CRM menu

2. Select GWA_APPLN_MSG and choose Details.

3. Choose the Tables/Structures tab.

4. Choose Filter Settings corresponding to the DOKIL table.

5. In the Source Site Name field, select CRM from the drop-down list.

6. Under Filter Settings, enter the following details:

Field name

User action and values

Field Enter OBJECT.

OP Select Between low and high value (Low <= x <= High) from the drop-down list.

LOW Enter GWA_APPLN_MSG000.

HIGH Enter GWA_APPLN_MSG999.



1. To apply filter settings to the DOKTL table, repeat steps 1 to 5.

2. Choose the Tables/Structures tab.

3. Choose Filter Settings corresponding to the T100 table.

4. In the Source Site Name field, select CRM from the drop-down list.

5. Under Filter Settings, enter the following details:

Field name User action and values

Field Enter ARBGB.

OP Select Equality (=Low) from the drop-down list.

LOW Enter GWA_APPLN_MSG.



2.1.9 Define Filter Conditions for Business Partner Exchange with Groupware

Use


Transaction code SPRO

SAP CRM IMG menu CRM CRM MW and related Components Groupware Integration Application Specific Activities Filter Conditions for Business Partners Exchange with Groupware

2. Maintain the following parameters.

Make sure in R3AS transaction download customizing object GWA_BP_CUST if the filter condition is changed.

2.1.10 Map Activity Status with Groupware

Use



SAP CRM IMG menu CRM Transaction Settings for Activities Mapping of Activities to Groupware Map Activity Status to Groupware




Make sure in R3AS transaction download customizing object GWA_STAT_CUST if the filter condition is changed.

2.1.11 Map Activity Text Types and Business Partners to Groupware

Use



SAP CRM IMG menu CRM Transaction Settings for Activities Mapping of Activities to Groupware Map Activity Text types and business partners to Groupware




Make sure in R3AS transaction download customizing object GWA_ACTVCHAR if the filter condition is changed.

2.2 Middleware Setting for Groupware Integration

2.2.1 Generate Runtime objects for Groupware Integration Use In connection with Groupware integration, you must generate services for the following object categories if they were not yet generated.

● BDoc types

● Replication objects

● R/3 Adapter objects A service consists of a group of runtime objects, which include Dictionary objects, function groups and function modules. All of a table’s essential information is contained in a runtime object


Transaction code SMOGGEN

SAP CRM menu SAP Menu → Architecture and Technology → Middleware → Development → Generation → Generation → Generate Services

Then carry out the following steps:

Under Object Categories, choose the appropriate object category and enter the names of the object types to be generated in the field Available Objects. You must generate services for the following objects:

○ BUPA_MAIN



○ BUS_TRANS_MSG

○ EMPLOYEE_WRITE

○ as well as for all BDoc types that begin with the character string GWA.

2. Choose the icon Execute.

3. Carry out the procedure for the following object categories:

a. ○ BDoc types

b. ○ Replication objects

c. ○ R/3 Adapter objects

If you make changes to object types or generation templates later, you must regenerate the services.

The logged in user has the profiles SAP_ALL and SAP_NEW assigned, which gives him full authorization rights. If this authorization is not applicable to your project you can restrict the rights of this user according to SAP Note 0338537.

2.2.2 Creating Sites for the Groupware Adapter

Use You must create sites for the groupware adapter. You need to use the site types Groupware Adapter 01 (mBDoc). You must create a site based on the Groupware Adapter 01 (mBDoc) site type to enable:

● The exchange of Activities and Tasks between CRM Activity Management/Workforce Management and groupware

● The bi-direction exchange of business partner data with the public contact folder of groupware


Transaction code SMOEAC

SAP CRM menu Architecture and Technology → Middleware → Administration → Administration Console


2. Choose and Select Site from the Object Type drop-down list.



3. Choose Object → Create from the application menu or the corresponding symbol from the application toolbar. The Administration Console: Add Site screen appears.

4. Under Object Information: Site, enter the following details: Field Name

Description Req./Opt./Dep. User Action and Values

Name Name of the site

Req. Enter a name for the site.

Description Description of the site

Opt. Enter a description for the site.

Type Site Type Req. Select the Groupware Adapter 01 (mBDoc) site type from the drop-down list.

5. Save the site.



2.2.3 Creating Subscriptions for the Groupware Integration Use

Procedure You use this procedure to create subscriptions for the Groupware Adapter 01 (mBDOc) site type. The subscriptions relate to the following functions:

● Groupware customizing

● Business partner management

● Activity Management The following tables list the subscriptions with the associated publications that are delivered by default.

Groupware customizing

Subscription Publication

Groupware Adapter Customizing (MESG) Groupware Adapter Customizing (MESG)

Groupware Adapter Messages (by object = GWA_APPLN_MSG) (MESG)

Segment name = GWA_MSG_CLASSIC

Segment Field Name = ARBGB

Operator = EQ

Criteria Type = D

Criteria Value Low = GWA_APPLN_MSG

Groupware Adapter - Generic Messages (by object) (MESG)

Groupware Adapter Metadata for all BDoc Types (MESG) Groupware Adapter Metadata for all BDoc Types (MESG)

Groupware Object Master Category List (MESG) Groupware Object Master Category List (MESG)

Groupware Object Selection Filter Fields and Values (MESG) Groupware Object Selection Filter Fields and



Values (MESG)

Business partner management


All Business Partners (MESG) All Business Partners (MESG)

Activity Management


All Business Transactions (MESG) All Business Transactions (MESG)

1. Access the activity using one of the following navigation options:

Transaction code SMOEAC

SAP CRM menu Architecture and Technology → Middleware → Administration → Administration Console

Select Subscription from the Object Type drop-down list.

2. Choose Object → Create from the application menu or the corresponding symbol from the application toolbar. The Subscription Wizard appears.

3. Choose Next.

4. In the Subscription field, enter the required subscription name.

5. In the Publication field, enter the corresponding publication name.

6. Choose Next.

7. Specify criteria fields (if required).

8. Choose Next.

9. Assign the subscriptions to the Groupware site.

10. Choose Next.

11. Choose Complete.

Repeat the steps for each subscription you want to create.



2.2.4 Maintain General Groupware Settings Use Groupware integration requires certain control parameters/properties that can change the behavior of the bidirectional mapping of Groupware objects from an SAP Application to the Groupware Server. The control parameters/properties, their sub-parameters/sub-properties, and their values are maintained in this view.



SAP CRM IMG menu CRM CRM MW and related Components Groupware Integration Maintain General Groupware Settings


If you make changes to object types or generation templates later, you must download the Customizing object GWA_CUSTPROP from R3AS transaction.

2.2.5 Loading the Customizing objects to Groupware Use The customizing objects that you must load from the CRM server to the site of the Groupware adapter are listed below:

● GWA_ACTVCAT

● GWA_ACTVCHAR



● GWA_ADDRCOMMAP

● GWA_APPLN_MSG

● GWA_BPROLES

● GWA_BP_CUST

● GWA_CATG_CUST

● GWA_COUNTRY

● GWA_CUSTPROP

● GWA_CUST_LANGU

● GWA_CUST_PERS3

● GWA_CUST_PRIO

● GWA_DATA

● GWA_GWOMSTRCAT

● GWA_GWO_SELRET

● GWA_MDT

● GWA_PROCTYPE

● GWA_SITETYPE

● GWA_STAREASON

● GWA_STAT_CUST

We recommend that you limit the size of the message (Block Size) to 100 for the loading of the necessary customizing objects. We recommend block size 10 for the customizing object GWA_COUNTRY. To change the block size, call transaction R3AC3 and display the details of the object. Choose Display → Change and enter the value 100, or for the customizing object GWA_COUNTRY, the value 10, in the field Block Size.




Transaction code R3AS

SAP CRM menu Architecture and Technology → Middleware → Data Exchange → Initial Load → Start

2. Under Object, in the Load Object field, enter the name of the customizing object.

In addition, you can choose F4 to select the customizing object from the list.

3. Under Data Flow, in the Source Site (Sender) field, enter CRM.

4. Under Data Flow, in the Destination Site (Receiver) field, enter the name of the site that is based on the Groupware Adapter 01 (mBDoc) site type.

5. Choose Execute.

6. Repeat steps 2 to 5 for each customizing object you want to load.



You must ensure that:

• The queues of type ISP_D*, which process inbound Groupware messages to the Groupware Adapter, are empty. (Transaction smq2)

• The queues of type ISP_D* are registered under the Queue IN scheduler. (Transaction smqr)

• The queues of type CRI* are registered under the Queue IN scheduler. (Transaction smqr)

A dialog box appears indicating that the initial load is in progress. All messages are transferred to one of the ISP_D* queues and processed by MapBox. If you get a pop up with a warning message “………..Do you want to Continue?”, then abort the operation, goto R3AC3 and choose the Customizing object and change the block size to 1.

All messages must be processed without any errors.

We recommend that you restart MapBox after you complete the load of customizing objects.

7. Repeat steps 2 to 5 for each customizing object to load business partner BUPA_MAIN.

8. Block Size Set to 10 in R3AC1 transaction for adapter object BUPA_MAIN

9. Download the Business Partners to Groupware in R3AS transaction

2.2.6 Monitoring Initial Load

Use




Transaction code R3AM1

SAP CRM menu Architecture and Technology → Middleware → Monitoring → Data Exchange → Monitor Objects

2. Under Object, in the Object Name field, enter BUPA_MAIN.

5. Under Additional Selection Criteria, select the required options that indicate the current status. The options available are, Abort, Waiting, Running, and Done.


Date post:	11-Mar-2015
Category:	Documents
Upload:	ameet-paryemalani
View:	1,084 times
Download:	0 times

CRM Groupware Integration - Configuration and Setup Guide

Documents