C71 bb config_guide_en_de(1)

SAP CRM 2007

March 2009

English

CRM Connectivity (C71)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Building Block Configuration Guide

SAP Best Practices CRM Connectivity (C71): Configuration Guide

Copyright

© Copyright 2009 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, Excel, 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, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, 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, Duet, PartnerEdge, 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 31


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.



ContentsConfiguration Guide........................................................................................................................ 6

1 Purpose................................................................................................................................ 6

2 Preparation.......................................................................................................................... 6

2.1 Prerequisites.................................................................................................................. 6

3 Local Settings...................................................................................................................... 6

3.1 SAP ERP....................................................................................................................... 6

3.1.1 Defining Client Administration (SAP ERP)............................................................6

3.1.2 Defining Logical System (SAP ERP).....................................................................7

3.1.3 Assigning Logical System to Client (SAP ERP)....................................................8

3.1.4 Creating an RFC User (SAP ERP)........................................................................8

3.2 SAP CRM...................................................................................................................... 9

3.2.1 Defining Logical System (SAP CRM)....................................................................9

3.2.2 Assigning Logical System to Client (SAP CRM)..................................................10

3.2.3 Creating RFC User (SAP CRM)..........................................................................11

4 Cross-Connectivity.............................................................................................................12

4.1 SAP ERP with SAP CRM............................................................................................12

4.1.1 SAP ERP............................................................................................................12

4.1.1.1 Creating a Logical System for SAP CRM (SAP ERP)...................................12

4.1.1.2 Connecting SAP CRM (SAP ERP)...............................................................13

4.1.1.3 Creating RFC User in Client 000 (SAP ERP)...............................................14

4.1.1.4 Checking Table CRMCONSUM (SAP ERP).................................................15

4.1.1.5 Maintaining Table CRMRFCPAR (SAP ERP)...............................................16

4.1.1.6 Maintaining Table CRMPAROLTP................................................................17

4.1.1.7 Activating Event Control...............................................................................18

4.1.2 SAP CRM............................................................................................................18

4.1.2.1 Defining Logical System for ERP (SAP CRM)..............................................18

4.1.2.2 Connecting SAP ERP (SAP CRM)...............................................................194.1.2.2.1 Creating RFC Destination for the ERP System.........................................194.1.2.2.2 Creating RFC Destination for Replication & Realignment (for Client 000) 204.1.2.2.3 Creating RFC Destination for Replication & Realignment (for Application

Client).......................................................................................................214.1.2.3 Creating RFC User in Client 000 (SAP CRM)...............................................22

4.1.2.4 Site IDs and Subscriptions for OLTP............................................................234.1.2.4.1 Creating Site for OLTP..............................................................................234.1.2.4.2 Creating Subscriptions for OLTP..............................................................24

4.2 SAP CRM Misc Connections.......................................................................................25

4.2.1 Index Management System (IMS).......................................................................25



4.2.1.1 Checking RFC Destination for TREX............................................................25

4.2.1.2 Creating the Search Server Relation (SAP CRM).........................................26

4.2.2 Web Server Environment (Optional)...................................................................27

4.2.2.1 Creating RFC Destination for FTP and HTTP...............................................27

4.2.2.2 Settings on the Web Server..........................................................................274.2.2.2.1 Creating the Directory for Document Publication......................................284.2.2.2.2 Maintaining Properties of the Default FTP Site.........................................284.2.2.2.3 Creating a Virtual FTP Directory...............................................................294.2.2.2.4 Creating a Virtual HTTP Directory............................................................29

4.2.2.3 Setting Target for Publishing Catalog Contents (SAP CRM)........................30



Configuration Guide

1 PurposeThis building block describes the activities that are necessary to connect the various components of an SAP CRM system landscape.

2 Preparation2.1 PrerequisitesBefore starting with the installation of this building block, please see the document Quick Guide to Installing SAP Best Practices for CRM.

3 Local SettingsThis chapter describes all local settings that are necessary for each required component.

3.1 SAP ERP

3.1.1 Defining Client Administration (SAP ERP)

UseThis activity allows you to change Customizing settings and to start eCATT procedures.

Prerequisites

You have logged on to the system in English in order to start with the installation of the Best Practices scenario. The logon language of the installation user must be English (EN) to ensure that the eCATT procedures run correctly.

Procedure1. Access the activity using the following navigation options:

Transaction code SCC4

SAP ERP GUI menu Tools Administration Administration Client Administration Client Maintenance

2. Choose Display Change (Ctrl + F1).

3. Confirm the warning message Caution: The table is cross-client.

4. Select your SAP ERP client and choose Details (Ctrl + F2).



5. In the Change View “Clients”: Details screen, activate the following settings:

Automatic recording of changes

Changes to Repository and cross-client Customizing allowed

eCATT and CATT Allowed.

6. Choose Save.

7. Go back to the SAP Easy Access menu.

3.1.2 Defining Logical System (SAP ERP)

UseThe purpose of this activity is to create a logical system for your SAP ERP system. To enable communication between systems within your system landscape, you have to

1. Define the systems as logical systems.

2. Assign the logical system for the SAP ERP 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.


Transaction code SPRO

SAP ERP IMG menu SAP NetWeaver Application Server IDoc Interface/Application Link Enabling (ALE) Basic Settings Logical systems Define Logical System

2. Choose New Entries (F5).

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 ERP system

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

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

Log. System Name

<Logical system 2>, (for example ES7CLNT020) SAP ERP system



5. Choose Save.A transport request for Workbench appears.

6. Select an existing request or create a new request, if necessary.A transport request for Customizing appears.

7. Select an existing request or create a new request, if necessary.

3.1.3 Assigning Logical System to Client (SAP ERP)

UseThe 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.

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


SAP ERP GUI menu Tools Administration Administration Client Administration Client Maintenance


3. Confirm the warning message Caution: The table is cross client.

4. Select your ERP client and choose Details (Ctrl + Shift + F2).

5. In field Logical System, select the newly created logical system of your SAP ERP client using the input help.

6. Save and confirm the warning message Be careful when changing the logical system.

7. Choose Back twice.

3.1.4 Creating an RFC User (SAP ERP)

UseTo enable communication between the SAP ERP back-end system and other SAP systems, you have to create an RFC user in the SAP ERP system.

The RFC user in the application client enables multiple RFC connections. Skip this activity if an RFC User has already been created.


Transaction code SU01

SAP ERP GUI menu Tools Administration User Maintenance Users

2. In the User field, enter RFCUSER.

3. Choose Create (F8).



4. On the Maintain User screen, enter the following data on the tab entry screens:

Address

Last Name RFCUSER

Function

Logon data

User type Communications Data

Password WELCOME

Defaults

Logon Language EN

Profiles

Profile SAP_ALL

5. Save your entries (Ctrl + S).

The user RFCUSER has the profile SAP_ALL 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.

3.2 SAP CRM

3.2.1 Defining Logical System (SAP CRM)UseThe distribution of data between systems makes it necessary to identify each system as a unique logical system.

A logical system is an application system in which the applications are coordinated to work in one common database. In SAP terms, a logical system corresponds to a client.



SAP CRM IMG menu Customer Relationship Management CRM Middleware and Related Components Communication Setup Set Up Logical Systems Define Logical System

2. Choose New Entries (F5).

3. Enter the following data:

A name for the logical system that you want to create (Log.System)

A clear description of the logical system (Name)



Log.System Name

<CRM system>CLNT<Client>, (for example, CS7CLNT200)

For example: CRM Best Practices


3.2.2 Assigning Logical System to Client (SAP CRM)

UseThe 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.



SAP CRM IMG menu Customer Relationship Management CRM Middleware and Related Components Communication Setup Set Up Logical Systems Assign Logical System to Client


3. Confirm the message Caution: The table is cross-client.

4. Select your CRM client.

5. Choose Details (Ctrl + Shift + F2). The Change View “Clients”: Details screen appears.


Field / Area Entry

Logical system <Logical System of CRM client> (for example, CS7CLNT200)

Client role Customizing

Changes and Transports for Client-Specific Objects

Automatic recording of changes

Cross-Client Object Changes Changes Allowed to Repository and cross-client Customizing.

Protection: Client Copier and Comparison Tool

Protection level 0: No restriction

Restrictions when Starting CATT and eCATT

eCATT and CATT Allowed

7. Save (Ctrl + S) and confirm the warning message Be careful when changing the logical system.



8. Choose Back twice (F3).

These settings cannot be transported. When a new system is being set up, these settings must be made manually after the system installation has been completed.

3.2.3 Creating RFC User (SAP CRM)UseAn RFC user is required for setting up the connectivity between systems.



SAP CRM GUI menu Architecture and Technology System Administration User Maintenance Users




Address tab page

Last Name RFCUSER

Function Default User for RFC connection

Logon data tab page

User Type Communications Data

Password WELCOME

Defaults tab page

Logon Language EN

Profiles tab page

Profile SAP_ALL


The user RFCUSER has the profile SAP_ALL assigned, which gives 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.



4 Cross-ConnectivityThis chapter describes all settings that are necessary to connect the components of the SAP Business Suite landscape with each other. The settings for each combination of two components to be connected are described in a separate structure node. The separate structure nodes make it possible to identify the activities required to connect certain components with each other. The structure nodes for components that are not part of the installation can be skipped.

4.1 SAP ERP with SAP CRM

4.1.1 SAP ERP

4.1.1.1 Creating a Logical System for SAP CRM (SAP ERP)

UseTo enable communication between your SAP CRM and your SAP ERP systems, you need to define logical systems for both systems in your ERP system.

If the logical system has already been created, skip this activity. You can check if the logical system already exists by running the IMG activity Define Logical System.

Procedure1. To define the two required logical systems for your system, access the activity using the

following navigation options:


SAP ERP IMG menu SAP NetWeaver Application Server IDoc Interface/Application Link Enabling (ALE) Basic Settings Logical systems Define Logical System

2. Choose New entries (F5).

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: DS7CLNT712)

<system ID> is the ID number of your CRM system being connected to the back-end ERP system.

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

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

Log. System Name

<Logical system 1> (for example DS7CLNT712) SAP CRM system




6. A transport request for Workbench appears.Select an existing request or create new request, if necessary.

7. A transport request for Customizing appears.Select an existing request or create a new request, if necessary.

4.1.1.2 Connecting SAP CRM (SAP ERP)

UseCommunication between the systems is based on the RFC interface and Remote Function Calls (RFCs) manage the communication process, parameter transfer and error handling between different systems. To set up this functionality for your systems, you need to define RFC destinations in your system landscape.


Transaction code SM59

SAP ERP IMG menu SAP NetWeaver Application Server IDoc Interface/Application Link Enabling (ALE) Communication Create RFC Connections

2. On the Display and maintain RFC destinations screen, choose Create.Enter the data according to the RFC destination:

Field name User action and default values

RFC Destination <SAP CRM System name>CLNT<client>(for example AS7CLNT001)

Connection type 3 (Connection to ABAP System)

Description SAP CRM System

3. Choose Enter.

Technical settings

Load Balancing No

Target host <SAP CRM target host name>, for example pwdf0421

System number <SAP CRM target system number>, for example 74

Save as IP Address

Logon/Security

Security Options

Trusted system No

Logon Screen deselect

SNC Inactive

Logon



Language <empty>

Client <SAP CRM target client>, for example 001

User RFCUSER

Password WELCOME (password you have chosen in user maintenance)

Current User deselect

Unencrypted Password (2.0)

deselect

4. Choose Enter.

MDMP & Unicode

Communication Type with target system

Set Unicode flag if Unicode Test has been executed successfully. This test can be performed by choosing Unicode Test in the menu area. The RFC destination has to be saved first before the test can be performed. An information message appears (Example of a message: “Target is a Unicode system (character size 2”) ).

5. Choose Enter.

Special Options

Trace deselect

Slow RFC Connection deselect

6. Choose Enter.

7. Save (Ctrl + S) your RFC destination.

8. You can now test your newly created RFC connection using the button Connection Test. You can also test the RFC connection using the menu path Utilities Test. There you can choose between the functionalities ‘Connection Test’ or ‘Authorization Test’. The connection test performs only a technical test (Host, IP Address) from the source system to the target system, whereas the authorization test performs a real logon to the target system using the maintained user and password of the maintained RFC destination.

4.1.1.3 Creating RFC User in Client 000 (SAP ERP)

UseThe RFC user in client 000 is required for replication and realignment queues.

PrerequisitesLog on to client 000 in the ERP system.





SAP ERP GUI menu Tools Administration User Maintenance Users



4. On the Maintain User screen, enter the following data:

Address Release 4.0 from Release 4.5 on

Last Name RFC User RFC User

Function Default user for RFC connection Default user for RFC connection

Logon data

User type Background System

Password WELCOME LOGIN

Profiles

Profile SAP_ALL SAP_ALL

5. Save your entries.

4.1.1.4 Checking Table CRMCONSUM (SAP ERP)

UseThe table CRMCONSUM contains the consumers (applications) that are to receive data from the ERP system.



SAP ERP menu System Services Table Maintenance Extended Table Maintenance

2. In the Table/view field, enter the table name CRMCONSUM.

3. Choose Maintain.

4. Check whether the following entry exists:

Column Entry

User CRM

Active √Description CRM

Q-Prefix R3A



5. Create this entry in case it does not exist.

6. Save (Ctrl + S) your entries.

ResultThe table now contains the necessary entry.

4.1.1.5 Maintaining Table CRMRFCPAR (SAP ERP)

UseThe parameters in this table indicate the RFC destinations which receive data. The required parameters include, for example: consumer, client, object name, and download type.

You can send data to a certain consumer only in an initial download and not in a delta download by making the appropriate specifications for the data exchange.


Transaction code SM30 (for R/3 Release 3.1i: SE16)

SAP ERP menu bar System Services Table Maintenance Extended Table Maintenance

2. In the Table/view field, enter the table name CRMRFCPAR.

3. Choose Maintain.

4. Choose New Entries.

If you choose New Entries and some of the fields are not maintainable, go back and choose the Copy As… button.

5. Create the following parameter values:

Parameter name Description Recommended Parameter value

User User that uses the OLTP plug-in functions as data receivers

CRM

Object name Object name *

Destination Specifies the destination of the CRM server <RFC destination of CRM system>(e.g. CS7CLNT200)

Caution: the RFC destination name is case sensitive

Load Type Restricts CRMRFCPAR entries to the initial (I) * All load types



Parameter name Description Recommended Parameter value

or delta (D) download.

Out Queue Name RFC outbound queue

In Queue Name RFC inbound queue

BAPI name

INFO Information/Comments

InQueue flag Controls whether RFC inbound queues are used on the CRM server

X

Send XML XML supports (Should data be sent in XML format?)

Mixed mode

Stop data Causes the OLTP System to place data into the outbound queue. This field can be used to change the behavior of the queue. The field HOLD_DATA replaces the parameter RECORD_ASYNCHRONOUS_MESSAGE in table CRMPAROLTP.

Normally the queue is processed automatically. If an X has been entered, the data is held in an outbound queue in the OLTP system.


For some of the fields left blank here (for example, queue names, BAPI name, description), entries will be added automatically by the system when starting the download of objects at a later stage of the installation.

Be sure that there is only one (the new) entry with Consumer CRM maintained in table CRMRFCPAR. If not, delete other existing entries with CRM as Consumer. Otherwise the download of sales documents ERP CRM might not run through.

4.1.1.6 Maintaining Table CRMPAROLTP

UseThe data flow between the ERP system and the CRM system requires that the CRM release is specified in the ERP system.





SAP ERP menu System Services Table Maintenance Extended Table Maintenance

2. In the Table/view field, enter the table name CRMPAROLTP.

3. Choose Maintain.


Field name Description User action and values

Parameter Name CRM_RELEASE

Param.Value 600

5. Choose Save.

4.1.1.7 Activating Event Control

UseThe activation of the event control is a prerequisite for the replication of data from the ERP system to the CRM system.


Transaction code SM30 (for R/3 Release 3.1i: SE16)

SAP ERP menu bar System Services Table Maintenance Extended Table Maintenance

2. In the Table/view field, enter the table name TBE11.

3. Choose Maintain.

4. Set the applications NDI (New Dimension Integration) to status Active by checking the check box in the column A.

5. Choose Save (Ctrl + S).

4.1.2 SAP CRM

4.1.2.1 Defining Logical System for ERP (SAP CRM)UseThe distribution of data between systems makes it necessary to identify each system as a unique logical system.

A logical system is an application system in which the applications are coordinated to work in one common database. In SAP terms, a logical system corresponds to a client.





SAP CRM IMG menu Customer Relationship Management CRM Middleware and Related Components Communication Setup Set Up Logical Systems Define Logical System


3. Confirm the message Caution: The table is cross-client.


A name for the logical system that you want to create (Log.System).

A clear description of the logical system (Name).

Log.System Name

<ERP OLTP System>CLNT<Client>,(for example, BERPLNT024)

For example:OLTP ERP System


4.1.2.2 Connecting SAP ERP (SAP CRM)

4.1.2.2.1 Creating RFC Destination for the ERP SystemProcedure1. Access the activity using one of the following navigation options:


SAP CRM IMG menu Customer Relationship Management CRM Middleware and Related Components Communication Setup Define RFC Destinations



Field Entry

RFC Destination <ERP system name>CLNT<client>, e. g. CS7CLNT200

Connection Type 3 (Connection to ABAP System)

Description OLTP ERP System

4. Choose Enter.

Technical settings

Load Balancing No



Target host <Target host ERP system>, e. g. pwdf0421

System number <System number of ERP system>

Logon/Security

Trusted system No

Status of Secure Protocol

Inactive

Language <empty>

Client <ERP client>

User <User, created in transaction SU01>

Password <Password, created in transaction SU01>

Current user

Unencrypted password

MDMP & Unicode

Communication Type with target system

Set Unicode flag if Unicode Test has been executed successful. This test can be performed by choosing Unicode Test in the menu area. The RFC destination has to be saved first before the test can be performed. An information message appears (Example of a message: “Target is a Unicode system (character size 2”)).

5. Save (Ctrl + S) your RFC destination.

6. You can now test your newly created RFC connection using the button Connection Test. You can also test the RFC connection using the menu path Utilities Test. Then you can choose Connection Test or Authorization Test. The connection test performs only a technical test (Host, IP Address) of the target system as the authorization test performs a logon to the target system using the maintained user and password of the RFC destination.

4.1.2.2.2 Creating RFC Destination for Replication & Realignment (for Client 000)

This RFC connection has to be created in the current application client and not in client 000.








Field Entry

RFC Destination SAPCRM_MW_RR_000

Connection Type L (Reference Entry (Refers to other destination))

Description Processing R&R queues – client 000

4. Choose Enter.

Logon/Security

Authorization --

Language --

Client 000

User RFCUSER

Password WELCOME

Current user --

Unencrypted password --


4.1.2.2.3 Creating RFC Destination for Replication & Realignment (for Application Client)






Field Entry

RFC Destination SAPCRM_MW_RR_<CRM client>

Connection Type L (Reference Entry (Refers to other destination))

Description Processing R&R queues – application client

4. Choose Enter.

Logon/Security tab page

Authorization

Language --



Logon/Security tab page

Client <your CRM client>

User RFCUSER

Password WELCOME

Current user

Unencrypted password

5. Choose Enter.

Special Options

Trace Deselect

Slow RFC Connection Deselect

MDMP & Unicode

Unicode Select, if the target system is a Unicode system


7. Confirm the information message.

8. You can now test your newly created RFC connection using Test connection.

9. Repeat steps 2 to 8 for all used CRM Clients you are using.

4.1.2.3 Creating RFC User in Client 000 (SAP CRM)

UseAn RFC user is required in client 000 for the replication and realignment queues.



SAP CRM GUI menu Architecture and Technology System Administration User Maintenance Users




Address tab page

Last Name RFCUSER

Function Default User for RFC connection



Logon data tab page

Password WELCOME

User type System

Defaults tab page

Logon Language EN

Profiles tab page

Profile SAP_ALL


The system user RFCUSER is created with the initial password LOGIN.

The user has the profile SAP_ALL assigned, which gives 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.

4.1.2.4 Site IDs and Subscriptions for OLTP

4.1.2.4.1 Creating Site for OLTP

The OLTP ERP system must be defined as a site, like the other systems of the distribution model. The CRM site is already predefined so you need only to create the ERP site.

Once you have created this site, you must define the distribution rules (subscriptions), which determine the data the ERP site is to receive.

ERP Site Definition

The RFC Destination for connection to ERP must be defined before performing ERP Site Definition.


Transaction code SMOEAC

SAP CRM GUI menu Architecture and Technology Middleware Administration Administration Console

2. In the Object Type field in the left screen area, choose Site.

3. Choose Create Object.

4. In the Object information: Site screen area, enter the name OLTP and the description OLTP ERP System and choose the site type R/3.

5. Choose Site attributes next to the Type field.



6. In the Maintenance of R/3 site attributes dialog box, enter the RFC destination for the ERP system.

7. Choose Set the attributes (F2).

8. Choose Save (Ctrl + S).

4.1.2.4.2 Creating Subscriptions for OLTP

UseAfter the definition of the ERP site you create subscriptions using the subscription wizard to enable uploading of the data from CRM to OLTP.


Transaction code SMOEAC

SAP CRM GUI menu Architecture and Technology Middleware Administration Administration Console

2. In the Object type field, enter Subscription.

3. Choose the Create icon.

4. Follow the subscription wizard instructions.

5. Using the subscription wizard, create three subscriptions:

Subscription All Business Partners (MESG) subscription

Publication All Business Partners (MESG)

Subscription All Business Partner Relationships (MESG) subscription

Publication All Business Partner Relationships (MESG)

Subscription All Business Transactions (MESG) subscription

Publication All Business Transactions (MESG)

Subscription All Business Partners Hierarchies (MESG) subscription

Publication All Business Partners Hierarchies (MESG)

6. Assign these subscriptions to your OLTP site.



For the Best Practices scenarios only Business Partners and Business Transactions are replicated from the CRM system into the ERP system. Please create further subscriptions if additional data has to be replicated into the ERP system.

Please refer to the Administration Console documentation for further information on how to create subscriptions.

4.2 SAP CRM Misc Connections

4.2.1 Index Management System (IMS)In this section you can find general information about the settings for the Index Management System (IMS).

The Index Management System itself is part of the Text Retrieval & Information Extraction (TREX.)The installation is part of the system setup and therefore not described here.

For information concerning the installation of the TREX please refer to the installation guide provided in the installation guidelines area on the SAP Service Marketplace:

http://service.sap.com/installNW70

3 - Installation - Standalone Engines

SAP NetWeaver Search and Classification TREX

4.2.1.1 Checking RFC Destination for TREX

UseThe RFC destination for the TREX is normally created during the installation of the TREX.




2. Search for an RFC destination of type TCP/IP Connection that contains the text TREX.

3. Open the connection and choose Connection Test.

4. In case of missing connection or error messages during the connection test please configure the connection according to the TREX installation guide.



4.2.1.2 Creating the Search Server Relation (SAP CRM)UseBefore you can publish a product catalog for CRM Internet Sales, you have to create a Search Server Relation.


Transaction code SRMO

SAP CRM IMG menu SAP Web Application Server Knowledge Management Settings in the Knowledge Warehouse System Text Retrieval & Information Extraction Define Search Server Relation

2. On the Search Server Relation tab, check whether an entry with a Search server ID IMS_SSR exists. If not, run steps 3 – 10.

3. Choose Create SSR. A dialog box appears.

4. In the field Search server relation ID, enter IMS_SSR.

5. Choose Create SSR.

6. In the dialog box that appears, enter the following values:

Field name Value

Search engine DRFUZZY

RFC destination (TCP/IP) Enter RFC destination identified in step Checking RFC Destination for TREX

Description Search Server Relation

7. Save your entries.

8. Select the entry IMS_SSR.

9. Choose Set SSR DEFAULT.

10. In the security prompt, choose Yes.

11. Choose the RFC destinations tab.

12. For the Search Server Relation IMS_SSR two entries should exist. One entry is for indexing (I) and the other one for searching (S).

This search server relation establishes an RFC connection. To test the RFC destination for the search server relation, proceed as follows:

13. Select one of the Search Service Relation entries.

14. From the screen area Search Engine Settings, choose Connection Test.

15. Sometimes you have to restart the transaction SRMO before the connection test works.

ResultA message box appears. If the connection is successful, a green traffic light is displayed and the fields Version info for RFC server and Version info for search eng. contain entries.



4.2.2 Web Server Environment (Optional)UseThe settings in the following sections are only relevant in case you are using the E-Service scenarios.

These settings allow to replicate documents assigned to products in the E-Service product catalog to the Web Server. But this is not mandatory and not in scope of the SAP Best Practices scenarios.

Skip these activities in case this E-Service and document assignments to products is not in scope for you implementation.

4.2.2.1 Creating RFC Destination for FTP and HTTPUseFor replication of data from the CRM system to the Web server, you have to create RFC destinations for the FTP and HTTP.


Transaction code SE38

SAP CRM menu Architecture and Technology ABAP Workbench Development ABAP Editor

2. Enter RSFTP005 in the field Program.

3. Choose Execute.The RFC destinations SAPFTP and SAPFTPA will be created.

4. Choose Back.

5. Enter RSHTTP05 in the field Program.

6. Choose Execute.The RFC destinations SAPHTTP and SAPHTTPA will be created.

4.2.2.2 Settings on the Web ServerUseThese settings refer to the Internet services comprised by the Microsoft Internet Information Server. The CRM system also requires HTTP and FTP services, which have to be configured with the Internet Service Manager.

ProcedureStart the Internet Service Manager. From the Web Server desktop, choose

Web Server Windows NT: Start Windows NT 4.0 Option Pack Microsoft Internet Information Server Internet Service



Manager

Windows 2000: Start Programs Administrative Tools Internet Service Manager

In the left window of the Internet Service Manager, drill down in the file tree structure. In the subdirectories, the Default FTP Site and the Default Web Site are usually displayed. This depends on the configuration of the MS Internet Information Server.

4.2.2.2.1 Creating the Directory for Document PublicationUseThe documents of the product catalog are published to a separate directory, which has to be accessible using FTP and HTTP. For this reason a directory (for example called catalog) has to be a subdirectory of your HTTP root directory.

Procedure

Web Server Creating the Directory for Document Publication

1. To check whether the directory catalog exists, open the directory Default Web Site in the file tree structure. The MS Internet Service Manager displays the subdirectories and the virtual directories mapped to the Default Website.

2. If you do not find the directory catalog attached to the Default Web Site, you first have to find out the path of the HTTP root directory.

3. Select the directory Default Web Site, click the right mouse button and choose Properties.

The tab Home Directory shows the path to the HTTP root directory in the field Local Path, for example C:\Inetpub\wwwroot.

4. With the Windows NT Explorer, open the HTTP root directory and create a new subdirectory called catalog.

5. With the Windows NT Explorer, select the directory catalog and choose File Properties.

6. Choose tab Web Sharing.

7. Select the option Share this folder, enter Default Web Site in the field Share on and enter the alias catalog.

8. Choose tab Sharing.

9. Select option Share this folder and enter the alias catalog.

4.2.2.2.2 Maintaining Properties of the Default FTP Site

ProcedureWeb Server Maintaining Properties of the Default FTP Site

To check the access authorizations of the FTP service, carry out the following steps:

1. In the left window of the MS Internet Information Server, select the Default FTP Site.

2. Click the right mouse button and choose Properties. You find the authorizations in the Security Accounts tab.



3. Select the field Allow Anonymous Connections and choose OK.

ResultTo access the Default FTP Site, the user ANONYMOUS can be used without a password.

You may create and maintain different users according to your security guidelines. In that case you have to note the logon information for later configuration settings.

4.2.2.2.3 Creating a Virtual FTP Directory UseSince the root directories of the FTP and the HTTP services are different, you need to gain FTP-access to the directory catalog by creating a virtual FTP directory that maps to the directory catalog.

If the virtual directory catalog is not displayed as a subdirectory of the Default FTP Site in the MS Internet Information Server, you have to create it.

Procedure

Web Server Creating a Virtual FTP Directory

1. Select the entry Default FTP Site in the left window of the Internet Information Server, click the right mouse button and choose New Virtual Directory.

2. In the Virtual Directory Creation Wizard, choose next and then type the Alias name catalog.

3. Choose Next.

4. Type in the physical path of the ‘real’ directory catalog (for example, C:\Inetpub\wwwroot\catalog).Alternatively, you can choose Browse.

5. Choose Next.

6. Allow Read and Write access and choose Next.

7. Choose Finish.

4.2.2.2.4 Creating a Virtual HTTP Directory UseSince the root directories of the FTP and the HTTP services are different, you need to gain Web access to the directory catalog by creating a virtual HTTP directory that maps to the directory catalog.

If the virtual directory catalog is not displayed as a subdirectory of the Default Web Site in the MS Internet Information Server, you have to create it.

Procedure

Web Server Creating a Virtual HTTP Directory

1. Select the entry Default Web Site in the left window of the Internet Information Server, click the right mouse button and choose New Virtual Directory.

2. In the Virtual Directory Creation Wizard, choose next and then type the Alias name catalog.



3. Choose Next.

4. Type in the physical path of the root directory catalog (for example, C:\Inetpub\wwwroot\catalog).Alternatively, you can choose Browse.

5. Choose Next.

6. Allow Read and Write access and choose Next.

7. Choose Finish.

4.2.2.3 Setting Target for Publishing Catalog Contents (SAP CRM)

UseIn the CRM system you have to define the targets for publishing documents for catalog areas and product items. The necessary HTTP and FTP settings must be configured.



SAP CRM IMG menu Customer Relationship Management Master Data Product Catalog Set Targets for Publishing Catalog Contents

2. Choose New entries.


Field Entry

Publish. target <ID of the publishing target>,for example WEBSHOP

Host name <name of the Web server machine>, for example pgwdf049

HTTP port Port of the default web site, e.g. 80

See entries in your system landscape questionnaire for Web Server.

HTTP directory Describes the directory that is used for publishing documents on the Web server.

Enter the directory you have created in the activity Creating Directory for Document Publication.

Default: Catalog

RFC destination SAPFTPA

FTP Port Port of the default FTP site, e.g. 21

See entries in your system landscape questionnaire for Web Server.



User name Enter the user name of the user you have defined in the activity Selecting the Default FTP Site

Default: ANONYMOUS

Password No password if you have selected Allow Anonymous Connection in the activity Selecting the Default FTP Site.

Otherwise enter the password of the user you have defined for the access.

FTP directory Describes the directory in which the HTTP publication took place.

Enter the directory you have created in the activity Creating a Virtual FTP Directory.

Default: Catalog
