CRM Connectivity Standalone
Contents
Configuration Guide... 1 1 Prerequisites... 1 2 Local Settings ... 1 2.1 SAP CRM ... 12.1.1 Defining Logical System (SAP CRM) ... 1
2.1.2 Assigning Logical System to Client (SAP CRM)... 2
2.1.3 Creating RFC User (SAP CRM) ... 3
3 Cross-Connectivity... 4
3.1 SAP CRM Misc Connections ... 4
3.1.1 Internet Pricing and Configurator (IPC) ... 4
3.1.2 Index Management System (IMS) ... 4
3.1.2.1 Checking RFC Destination for TREX ... 5
3.1.2.2 Creating the Search Server Relation (SAP CRM)... 5
Configuration Guide
1
Prerequisites
Before starting with the installation of this building block, please see the document Quick Guide to Installing SAP Best Practices for CRM.
2
Local Settings
This chapter describes all local settings that are necessary for each required component.
2.1 SAP CRM
2.1.1
Defining Logical System (SAP CRM)
Use
The 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.
Procedure
1. Access the activity using the following navigation options:
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. 3. Enter the following data:
• A name for the logical system that you want to create (Log.System) • A clear description for the logical system (Name)
Log.System Name
<CRM system>CLNT<Client>, (for example, CS7CLNT200)
For example:
“CRM Best Practices” 4. Save your entries.
2.1.2
Assigning Logical System to Client (SAP CRM)
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.
Procedure
1. Access the activity using one of the following navigation options:
Transaction code SCC4
SAP CRM IMG menu Customer Relationship Management CRM Middleware and Related Components Communication Setup Set Up Logical Systems Assign Logical System to Client
2. Choose Display Change.
3. Confirm the message Caution: The table is cross-client. 4. Select your CRM client.
5. Choose Details. The Change View “Clients”: Details screen appears. 6. Enter the following data:
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
Customizing allowed.
Protection: Client Copier and Comparison Tool
Protection level 0: no restriction
Restrictions when Starting CATT and eCATT
eCATT and CATT Allowed
7. Save and confirm the warning message Be careful when changing the logical system. 8. Choose Back twice.
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.
2.1.3
Creating RFC User (SAP CRM)
Use
An RFC user is required for setting up the connectivity between systems.
Procedure
1. Access the activity using one of the following navigation options:
Transaction code SU01
SAP CRM menu Architecture and TechnologySystem Administration
Administration User MaintenanceUsers
2. In the User field, enter RFCUSER.
3. Choose Create (F8). 4. Enter the following data:
Address tab page
Last Name RFCUSER
Function Default-User for RFC connection
Logon data tab page
Password welcome
User Type Communications Data
Defaults tab page
Logon Language EN
Profiles tab page
Profile SAP_ALL and SAP_NEW
The user RFCUSER has the profiles SAP_ALL and SAP_NEW 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.
3
Cross-Connectivity
This chapter describes all settings that are necessary to connect the components of the mySAP 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.
3.1 SAP CRM Misc Connections
3.1.1
Internet Pricing and Configurator (IPC)
Use
The 2005 release of the IPC (SAP AP IPC JAVA 7.00) has major architectural changes compared with CRM IPC 4.0. The IPC no longer exists as a separate server. Instead, the IPC functionality is now delivered as part of SAP AP (Application Platform) and is processed on normal application servers.
Therefore no specific connectivity settings like RFC connections, RFC users are required.
Procedure
Please make sure that the IPC is installed and connected to the installation client of your CRM system.
The latest version of the guides dealing with the IPC installation can be found in the installation guidelines area on the SAP Service Marketplace:
http://service.sap.com/crm-inst
3.1.2
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 providedin the installation guidelines area on the SAP Service Marketplace:
• http://service.sap.com/instguides
• Installation Guide for TREX
3.1.2.1
Checking RFC Destination for TREX
Use
The RFC destination for the TREX is normally created during the installation of the TREX.
Procedure
1. Access the activity using one of the following navigation options:
Transaction code SM59
SAP CRM IMG menu Customer Relationship Management →CRM Middleware
and Related Components Communication Setup Define RFC Destinations
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.
3.1.2.2
Creating the Search Server Relation (SAP CRM)
Use
Before you can publish a product catalog for CRM Internet Sales, you have to create a Search Server Relation.
Procedure
1. Access the activity using one of the following navigation options:
Transaction code SPRO
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 2 – 9.
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) TREXDEFAULT_START or TREXDEFAULT_REG 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 Setting search engine, choose Connection Test.
15. Sometimes you have to restart the transaction SRMO before the connection test works.
Result
A 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.
