SAP CRM Middleware

SAP CRM Middleware
Step by Step Instructions
Why I wrote this book Who can use this book How to use this book Table of Contents
Why I wrote this book .................................................................................................1 Who can use this book ................................................................................................1 How to use this book ..................................................................................................1 What is SAP CRM Middleware .....................................................................................1 System preparation ....................................................................................................2
What is SAP CRM Middleware Why is SAP CRM Middleware used ? Lets see it in Action
Go to R3AC1 and select the adapter object CUSTOMER_MAIN.
SAP CRM Middleware

Copyright of SAP AG
We dont want all the customers to be downloaded here. R3AC1 Configure Adapter Object R3AS Start Initial Download R3AM1 Monitor Adapter Objects SMQ1 Inbound Queue
How is this happening ? Some Geeky Stuff System preparation

All of the steps in this section are going to be done by your Basis & Security Consultants. However, only a functional consultant will understand the logical data flow and you will have to guide your Basis consultants when it comes to creating systems, destinations, sites, subscriptions etc. For example, you would know that say Rebate Agreements do not replicate between ECC and CRM. So, you would have to let your basis consultant know that Rebate Agreements and Settlements need not be added as a subscription to the R/3 site. Also, if transactions are replicated between an external ordering system to CRM, the corresponding settings need to be specified to your Basis consultant. Refer to Building Block CRM Connectivity (C71) for more details.
SAP CRM Middleware

The Handshake
SAP ERP ( ECC ) and CRM speak to each other via RFC. Lets do a bunch of settings to enable the communication to happen. The settings would be similar even for systems that interact via other means , say HTTP or TCP/IP. Examples for these could be interaction with Tax Servers like Vertex or external WebShops. Step 1 Logical System Name Get the names of each of the systems Go to SCC4, identify the client and double click it.
Copyright of SAP AG
This name is always unique across all the SAP systems ( For a combination of Instance and Client)in the company. This is the name that is uniquely referenced to connect to them. And this is case sensitive, so , please always maintain the same case all capitals as the convention is. I had to debug for 2 days to find this out the hard way. You would also find out the same for the CRM system. It is DTZ_800 for the CRM system.
Copyright of SAP AG
These names are originally created under NetWeaver settings ( SPRO -> IMG -> SAP NetWeaver -> Application Server -> IDOC Interface -> Basic Settings -> Logical Systems -> Define Logical System ). Since you are working on an IDES system, this would already be defined for you.
SAP CRM Middleware

Step 2 Create remote users Create remote users in each of the systems. RFC connections are authenticated with standard user and password combination. Go to SU01 and create users with SAP_ALL privileges. Refer your Security Consultant to note 338537 to restrict the privileges appropriately.
Copyright of SAP AG
Step 3 Let them know each others names. Its not just enough that the ECC system knows its name. Step 3 Lets hook them up. Lets first connect to the CRM system from ECC. RFC Connections are created in SM59. Open the ABAP Connections section and click on the new button.
Copyright of SAP AG
SAP CRM Middleware

In an IDES system, this would already be created It is DTZ_800. Open it in edit mode
Copyright of SAP AG
Give it a meaningful name, specify the Target host ( either use a domain name or the IP address ), specify the system number and specify the logon information by selecting Trusted System as No.
SAP CRM Middleware

Copyright of SAP AG
Save it, and click on the Connection Test button on the top to see if the system can be reached.
Copyright of SAP AG
You should see something like this. What this means is that the ECC system is able to see the CRM system.
SAP CRM Middleware

Copyright of SAP AG
It does not mean that the RFC connection can be made. You would have to test that by clicking on the Remote logon button on the top
Copyright of SAP AG
If the ECC system opens up, that means that a RFC connection has been successfully made. Caution Ensure that the RFC Destination name is the same as the logical system name of the remote system. In this case, the RFC destination name DTZ_800 is the same as the logical system name of the CRM System DTZ_800 as specified in SCC4. Now, do the same thing on the CRM end as well and ensure that the connections are successful.
SAP CRM Middleware

Copyright of SAP AG
Replication and Re-alignment Settings

TBD
Consumers and Producers

Triggers are based on Business Transaction event (BTE) technology. For example, if a Customer changes in ECC, a BTE is triggered which will trigger the delta load of the Customer to CRM. Refer to Note 430980 for a comprehensive list of settings and troubleshooting. Some basic Settings are needed for BTE to work. All consumers of ECC data needs to be specified in table CRMCONSUM. Go to SM30, specify the table CRMCONSUM, and click maintain.
SAP CRM Middleware

Copyright of SAP AG
Make sure the entry for CRM exists.
Copyright of SAP AG
As you will see going forward all queues start with the prefix R3A* and this is where the name comes from. The corresponding RFC destinations, which receive the data, are specified in table CRMRFCPAR. Once again, go to SM30, specify the table and ensure that the following entry exists.
SAP CRM Middleware

Copyright of SAP AG
Here we are specifying that the CRM system , identified by the RFC destination DTZ_800 is a receiver of the R/3 Plugin data. Specify the CRM release in table CRMPAROLTP.
Copyright of SAP AG
Activate the BTE event control in table TBE11 by making an entry for NDI. NDI is an old name for R/3 plugin.
SAP CRM Middleware

Copyright of SAP AG
It just a dumb setting that should exist for R/3 plugin to be active.
Sites and Subscriptions

This is where you define the type of data that needs to be synced between CRM and other systems. For example, you can only choose to sync the Business Partners and sales transactions between ECC and CRM and not billing documents or rebate agreements. Also, if you have an external credit management system that requires Business Partners from CRM, this is where you would specify it. Depending on the type of communication, the appropriate type would be selected in the Site definition. For example, if the communication with this credit management system happens via IDOCs or XML, select that interface. On the CRM end, ECC should be defined as a site that receives subscriptions. Think of site as an RFC Destination and subscription as a class of message that is synced. Both the CRM system and Mobile database( CDB ) are already created. You will have to create ECC and other external interfaces for data transfer. Create ECC as a site The list of available Sites will be shown in SMOEAC by selecting Site in the Object type.
SAP CRM Middleware

Copyright of SAP AG
Select the new button while Sites is selected and create a new site called ECC and select R/3 in the Type dropdown.
Copyright of SAP AG
Click on the Site Attributes button to specify the communication details of the site like RFC destination etc. You can select the RFC destination from the pop-up search and click on get values to get the version details.
SAP CRM Middleware

Copyright of SAP AG
Add the Subscriptions Not all messages need to be subscribed to like we discussed in the previous paragraph. Lets subscribe to Business Partner for example. Select Subscription in the object type and click on the new button.
Copyright of SAP AG
SAP CRM Middleware

A little pop-up opens up with a wizard , just click continue. We want CRM to subscribe to all Business Partners. So the publication to subscribe to would be All Business Partners and you can give any subscription name you want.
Copyright of SAP AG
In the next step, select the site - in this case ECC. Click on the new button
Copyright of SAP AG
Select ECC from the site and click OK and continue to complete the wizard.
SAP CRM Middleware

Copyright of SAP AG
For now, its all customers, but we can restrict them by specifying criteria. So, we now have a new subscription, with the site ECC that publishes the Business Partner.
Copyright of SAP AG
Thats it Our basic connections are setup and good to go.
SAP CRM Middleware

Adapter Objects
Finding adapter objects based on tables - DNL_CUST_PRICE

SAP CRM Middleware

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

SAP CRM Middleware

Enviado por

Direitos autorais:

Formatos disponíveis

SAP CRM Middleware

Step by Step Instructions