Skip to Content

Introduction: This blog contains how to integration SAP Cloud for Customer  with an existing on premise SAP CRM system using PI system.

This blog is intended only as a guide to help you prepare and apply the steps necessary for successful integration. I also mentioned features and benefits of integration which will give more clarity on purpose of this integration. It has 3 stages configurations and each stage has sub stages which I explained in detail.

Summary: Many companies have an on premise solution that contains master data, customer and product information, and pricing data. Following are the key reasons why an integration is required with SAP CRM to SAP Cloud for Customer.

  • To provide an organization level solution for all sales, marketing and service activities including all subsidiaries, sales offices.
  • Many companies prefer as SAP Cloud solution for customer user experience that helps sales representatives to provide outstanding customer experience and SAP CRM as back end system to support key activities.
  • An organization wants to extend existing CRM platform to new users.
  • SAP CRM system is up and running smoothly but the company wants to switch over to cloud solution for managing new deployments and releases.
  • To replace existing cloud SFA solution with SAP Cloud for Customer.

Features and Benefits of SAP CRM Integration with SAP Cloud for Customer

  • Features
  • Bi-Directional – Once SAP Cloud for Customer integrated with SAP CRM on premise then data will flow from bi directional. Changes will flow from on premise to SAP Cloud for Customer and SAP Cloud for Customer to on premise.
  • Real – time Integration: Real-time integration of master data for example, accounts, account hierarchies, prospects, competitors, contracts, territory assignments, products, employee’s, social media profiles, marketing attributes
  • Integration of transactional data – Full integration of transactional data for example, campaign headers, leads, opportunities, etc.
  • Benefits: –
  • SAP Cloud for Customer can act as an immediate “mobile layer” on top of CRM
  • For the end users, SAP Cloud for Customer and CRM seem to be “ONE” system as such
  • Customers can leverage their existing investments in CRM, but use innovations delivered constantly in SAP Cloud for Customer Below I captured examples for bi directional and Uni-directional

 

 

Marketing Attribute Definition

  • Marketing attributes are defined in SAP CRM
  • Example: Revenue Marketing Attribute that contains selection of:
  • < 2 Million
  • >2 million and <5 million
  • > 5 million
  • The integration of the definition of the marketing attribute is Uni-directional from SAP CRM to SAP Cloud for Customer

Marketing attribute Values

  • Marketing attribute values have bi-directional integration. For example:

In SAP Cloud for Customer update the Revenue Marketing Attribute for Customer ‘Future Vision” to be > 5 million

STAGES:

 

I. Configuring SAP Cloud for Customer for Integration with SAP CRM

II. Configuring SAP CRM for Integration with SAP Cloud for Customer

III. Configuring SAP PI  for Integrating SAP Cloud for Customer with SAP CRM

 

I. Configuring SAP Cloud for Customer Integration with SAP CRM

This stage has 4 sub stages as shown below:

1. Scope to SAP CRM

2. Select scenarios for integration

3. Set up communication system and arrangements

4. Perform code listing mapping

 

1. Scope to SAP CRM: SAP CRM on premise system should have below configuration then only we can connect to cloud system.

a. SAP CRM 7.0 is required, with at least support package BBPCRM 700 SP06 (SAPKU70006)

b. For Attachment replication in Opportunities and Leads, SAP CRM 7.0 EHP0, SP07 is required

c. The SSL client SSL client (standard) should install which will be used for authentication for calls made from CRM into the HCI system.

 

2. Select scenarios for integration: Configure Integration in Cloud Solution

Activate SAP CRM Integration in Scoping

a. Connect to the SAP Cloud for Customer system using the internet browser and open the Business Configuration tab.

b.Click All Current Projects

c.Select the project and click Edit Project Scope

d. Click Next

e. Click next and under Communication and Information Exchange → Integration with External Application and Solutions → select Integration with SAP CRM, Integration of Master Data and Integration into Sales, Service and Marketing Processes

f. Click next and under Communication and information Exchange → Integration with External Application and Solutions → Integration of Master Data, select the following scenarios:

→ Do you want to replicate business partner data from an external application or solution to your cloud solution?

→ Do you want to replicate business partner data from your cloud solution to an external application or solution?

→ Do you want to replicate account hierarchy data from an external application or solution to your cloud solution?

→ Do you want to replicate product data from an external application or solution to your cloud solution?

→ Do you want to replicate product category data from an external application or solution to your cloud solution?

→ Do you want to replicate employee data from an external application or solution to your cloud solution?

→ Do you want to replicate sales territory data from an external application or solution to your cloud solution?

 

g. Under Communication and information Exchange → Integration with External Application and Solutions → Integration into Sales, Services, and Marketing Processes select the following scenario:

  • Do you want to replicate campaign documents from an external application or solution to your cloud solution?
  • Do you want to replicate activities from your cloud solution to an external application or solution?
  • Do you want to replicate activities from an external application or solution to your cloud solution?
  • Do you want to replicate leads from an external application or solution to your cloud solution?
  • Do you want to replicate leads from your cloud solution to External Application?
  • Do you want to replicate opportunities from your cloud solution to an external application or solution?
  • Do you want to replicate opportunities from an external application or solution to your cloud solution?
  • Do you want to delegate service requests from your cloud solution to an external application or solution?

h. Click Next and then Finish

 

3. Set Up Communication System

a. Under the tab Administrator, click Communication Systems.

 

b.  Click New to create a new communication system

c. Enter the information about the backend CRM system

d. Click Actions Set to Active

 

 

e. Click Save and Close

 

4. Perform Code List Mapping –

 a. In the Business Configuration Work Center, choose DOWNLOAD CODE LIST.

b. Click on the link Download Code List.

c. Enter the details like Code List Mapping Group (example 03), Language, CSV Delimiter and select Download.

d. Save the file as a zip file. For example, codelist.zip.

e. Close the window.

f. Log in to the CRM back-end system that the SAP Cloud for Customer system is connected to.  

g. Open the transaction SE38 and run the report CRMPCD_CUST_EXCHANGE.

h. Choose Execute

I. Alternatively, we can access the same report via IMG Menu path. Go to transaction SPRO.

j. Select SAP Reference IMG

k. Expand IMG menu path Integration with Other SAP Components Integration with SAP Cloud for Customer and choose IMG activity Download CRM Customizing Information for Code lists.

l. Enter the Main Language and other parameters as shown below Merged Customizing directory is where you want the merged code list mappings filled. Cloud for Customer Business Configuration File is the codelist.zip file that was downloaded from the Cloud for Customer system.

 

m. Choose Execute to run the report.

The output file (example CodeOutput.zip) will be found in the folder you specified.

This file contains all the code lists and mappings for the requested languages.

n. Login to the SAP Cloud for Customer system again

o. In the Business Configuration Workcenter, choose UPLOAD CODE LIST.

 

p. Click on the link Upload Code List.

q. Select the Code List Mapping Group (example 03) and choose Upload.

Note: In case of errors during the upload, refer to SAP Note 2091243 for doing manual corrections described in the note.

 

r. Provide the CodeOutput.zip

 

s. Now the code list mapping in SAP Cloud for Customer is updated

t. Go to code list to check status of the uploaded code list for this click on Business Configuration → Upload Code List.

u. Click on Application Log to check the status of the code list upload.

 

II. Configuring SAP CRM for Integration with SAP Cloud for Customer

 

  1. SSL client certificate configuration (same as ERP)
  2. Business Partner Customizing
  3. Middleware configuration
  4. Configuration of asynchronous web services
  5. Pricing Configuration
  6. ALE settings

 

  1. SSL client certificate configuration (same as ERP)

 

a. Download the root certificates from the following URL

https://secure.omniroot.com/support/sureserver/rootcert.cfm

b. Now log in to PI system and Open SAP Net Weaver Administrator

c. Under the tab Configuration, click Certificates and Keys.

d. Look for the view called TrustedCAs, and select it.

e. Import the two root certificates that were downloaded using the Import Entry button under TrustedCAs.

f.Select the entry type X.509 Certificate and the location of the certificate file and click Import.

 

 

g. Repeat the process for the second certificate.

 

2. Business Partner Customizing

First create Business Partner Identification Type using below path

 

a. Call transaction SPRO and click SAP Reference IMG Click SAP Customizing Implementation Guide → Cross-Application Components SAP Business Partner →Business Partner →Basic Settings →Identification Numbers →Define e Identification Types.

 

b. Enter the following settings and save the

New entry: ID type: CRMPCD

Description: CoD Identification

Number ID Category: CRMPCD

Select the checkboxes for Persons and Organization

 

c. Create Business Partner Number Range

 

d. Choose Insert line to maintain a new number range interval. In this check filed external assignment and also ensure the account number in SAP CRM system is the same as in SAP cloud for customer system.

e. Create Groupings and Assign Number Ranges: Execute Transaction SPRO → Click on SAP Reference IMG node → Navigate to Cross-Application Components àSAP Business Partner àBusiness PartneràBasic Settings àNumber Ranges and Groupings àDefine Groupings and Assign Number Ranges

 

3. MIDDLEWARE CONFIGURATION:

a. Execute CRMPCD_CONNECTIVITY_SIM

b. Choose SAP Process Integration as the Middleware and select next

c. Select the scenarios you would like to generate the configuration entities for and choose Next.

Note: Select the Marketing Attribute Message types for creating the ALE Distribution Model.

 

d. Choose the Logical System of Cloud for Customer that you want to connect to and choose Next. In case the logical system is not created, you can create one using the button Create Logical System.

e. Enter the PI system details like host name, system no and logon details of PI system. Choose Next.

f. In the summary screen, select the Generate button to generate the configuration entities.

g. In the confirm pop-up screen, choose Yes

 

h. In the log you can check which entities were created.

 

3.1 Create RFC Destination

The RFC destination should be IDOC_AAE<PI system> and point to connection type “T”.

RFC Destination to PI from SAP CRM

a. Call transaction SM59 and create an RFC destination to PI system of type 3.

b. Click in the Logon and Security tab and enter the user and password required to connect to PI system. The PI user should have the role SAP_XI_APPL_SERV_USER.

 

3.2 RFC Destination to PI (IDOC AAE Adapter Only)

 

a. Call transaction SM59 and create an RFC destination IDOC_AAE_<PI system> to point the PI system of type T.

 

b. In Technical settings, enter registered server program ID of the PI system

 

c. Enter Gateway details where the program ID is registered.

Note: The Program ID, Gateway host and Gateway service details can be found under Configuration → Infrastructure → Application Resources →  Inbound RA resource adapter in NWA of PI system

 

3.3 Creation of IDoc port and partner profile with the required configuration for outbound and inbound message types

 

IDOC configuration for inbound and outbound message

a. Execute transaction code SA38 and execute program RBDMANI2

 

b. Enter the following parameters

Message Type = CRMXIF_PARTNER_REL_SAVE_M

Sender partner Type = LS

Sender partner no. = <logical system name of the Cloud system>

 

c. Schedule the program to be executed in background selecting the menu Program →

Execute in Background

d. Verify the output device and click Check.

e. The job has to be scheduled and be repeated, the frequency can vary depending of the specific needs. The frequency can be defined in the Period Values button

f. Finally click in the Save icon to schedule the periodic background job.

 

4. Configuration of asynchronous web services

a. Call transaction SOAMANAGER and login with your credentials if asked for.

 

b. Choose Simplified Web Service Configuration under the tab Service Administration.

c. Search for the object name: SalesOrderPricingInformationQueryResponse_In.

d. Select the Web service name and click on Set Selected. Check the fields User Name/Password (Basic) and X.509 Client Certificate

e. Choose Save.

 

5. Pricing configuration

Configuration for receiving pricing information from SAP CRM

a. Select Object Type as Service Definition and Object Name as EXTERNALSALESDOCUMENTDATAQUERY and choose Search. Select the hyperlink in the result list.

b. Under Configurations, choose Create Service.

 

c. Provide a Service Name, Description, and Binding Name. Choose Next.

 

d. Under Provider Security, check SSL (https) for Transport level security and X.509 SSL Client Certificate for Transport Channel Authentication. Choose Next.

 

e. Choose Finish.

 

Service Definition is created and Binding Generated.

 

6. ALE settings

 

a. Open transaction OYEA

b. Choose Edit and set Start W/O Event Linkage under IDoc Inbox HTTP in the Global Parameters for IDoc Interface screen.

 

c. Choose Save.

 

III. Configuring SAP PI  for Integrating SAP Cloud for Customer with SAP CRM

1. Value Mapping fields in SAP PI

a. Value Mapping Fields in SAP Platform Integration: Open the value_mapping.xml file within the project com.sap.scenarios.c4c.valuemapping from the Integration Designer perspective.

b. Maintain the value mapping by providing source agency name, source schema name, source value with respective target agency name, target schema name and target value.

Below is an example of RoleCode value mapping.

c. Save the value_mapping.xml file.

 

d. Select the project for deployment by right clicking on the context menu from the Integration Designer perspective and choose Deploy Integration Content.

 

e. Enter the Tenant ID and click OK.

f. Click OK – Within the Console tab it is possible to see if the deployment process was successful.

 

Activate the area menu CRMPCD_INT_MENU for data load and messaging reports and activities.

 

Area menu CRMPCD_INT_MENU is a central location for monitoring and performing initial loads. All load reports are centralized to the area menu.

When you expand the menu Initial Loading or Resending Objects form SAP CRM to SAP Cloud for Customer, you will see the supported objects.

You display the documentation for each report. The documentation will include any prerequisites for the initial load. The following example shows the documentation for the employee’s initial load report

 

Conclusion:

This document details the steps required to communication between an SAP Cloud for Customer and SAP CRM systems, using SAP Process Integration as the on-premise middleware layer. After this configuration system will be more friendly because user can create/change data either in on premise or Cloud for Customer.

I will be sharing another document on integration with SAP CRM with SAP Cloud for Customerusing Cloud Platform Integration (CPI)

 

 

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply