How-To Guide
SAP Cloud for Customer
Document Version: 1.0 - 2014-04-09
How to Perform Initial Load of data from SAP CRM
to SAP Cloud for Customer
Document History
Document Version Description
Table of Contents
1 Business Scenario ... 4
2 Background Information ... 4
3 Prerequisites ... 4
4 Initial Load of Master Data from SAP CRM to SAP Cloud for Customer ... 4
5 Step-by-Step Procedure ... 6
5.1 Initial Load of Organization Data ... 6
5.2 Initial Load of Territories ... 7
5.3 Initial Load of Accounts/Contacts/Prospects/Competitors (Business Partner) ... 9
5.4 Initial Load of Employees ... 13
5.5 Initial Load of Product Hierarchy ... 15
5.6 Initial Load of Product Materials ... 17
5.7 Initial Load of Business Partner Relation (Account Hierarchy, Account-Employee, Account-Contact) ... 18
6 Initial Load of Transaction Data from SAP CRM to SAP Cloud for Customer ... 19
7 Step-by-Step Procedure ... 21
7.1 Initial Load of Leads ... 21
7.2 Initial Load of Opportunities ... 22
1 Business Scenario
For most existing customers already using SAP On-premise systems, implementing a cloud solution means leveraging their existing data (both master data and transaction data). To speed up the process of replicating such data from customers on premise SAP CRM system to customer’s SAP Cloud for Customer tenant, SAP has provisioned standard ABAP reports. The reports are designed to drastically reduce initial load times of your data into SAP Cloud for Customer.
2 Background Information
This section describes how to extract data from the SAP CRM system and load it into the Cloud Solution.
3 Prerequisites
Technical connectivity between SAP CRM and SAP Cloud for Customer and vice-versa.
Integration Configuration settings specified in the Configuration guide for the SAP CRM, SAP middleware such as NetWeaver Process Integration or HANA Cloud Integration, and Cloud Systems.
4 Initial Load of Master Data from SAP CRM to
SAP Cloud for Customer
For integrating your SAP CRM system to your SAP Cloud for Customer solution, one of the critical aspects is loading of your master data. The diagram below captures the sequence in which you should perform the initial load.
The following table gives the list of reports needed to set up the master data objects: Master Data object Business Object Report Pre-requisite Business Object(s) Enhancement Spot Classic BADI Sales Organization Organization Model CRMPCD_ORG_UNIT_ EXTRACT None CRMPCD_OR G_UNIT_REP LICATION Employee Business Partner CRMPCD_EMPLOYEE_ EXTRACT Sales Organization CRMPCD_EM PLOYEE_REP LICATION Account Business Partner CRMPCD_BUPA_EXTR ACT Sales Organization CRMXIF_PA RTNER_MA P
Sales Territory Territory Model CRMPCD_TERRITORY_ TEST Employee, Account CRMPCD_TE RRITORY_RE PLICATION Contact Business Partner CRMPCD_BUPA_EXTR ACT None CRMXIF_PA RTNER_MA P Prospect Business Partner CRMPCD_BUPA_EXTR ACT Sales Organization CRMXIF_PA RTNER_MA P Competitor Business Partner CRMPCD_BUPA_EXTR ACT Sales Organization CRMXIF_PA RTNER_MA P Product Hierarchy Product Hierarchy CRMPCD_PROD_HIEA RCHY_TEST None CRMPCD_PC H_REPLICATI ON Product Materials Product Materials CRMPCD_PRODUCT_ EXTRACT Product Hierarchy COMXIF_P ROD_MAT_ MAP Account Hierarchy Business Partner Relation CRMPCD_BUPA_REL_ EXTRACT Sales Organization, Account CRMXIF_PA RTNER_R_ MAP Account-Employee Relation Business Partner Relation CRMPCD_BUPA_REL_ EXTRACT Sales Organization, Account, Employee CRMXIF_PA RTNER_MA P Account-Contact Relation Business Partner Relation CRMPCD_BUPA_REL_ EXTRACT Sales Organization, Account, Contact CRMXIF_PA RTNER_MA P Bulk Initial Load
All Objects CRMPCD_IDOC_SEND _BY_CONTENT
See object level dependency
5 Step-by-Step Procedure
5.1 Initial Load of Organization Data
1. Select the organizational structure you want to replicate from SAP CRM. 2. Enter the transaction code PPOMA_CRM.
Note
You can also search for the company in Organization Unit. For example, you want to replicate the entire organization structure for a company Almica.
3. Maintain code values for organization data.
Note
To maintain complete code lists in Cloud for Customer, please refer to chapter 7.1 in the integration guide.
Local Data Type CRM Location Path Cloud for Customer Path
RegionCode Insert Regions under, SAP Customizing
Implementation Guide SAP NetWeaver General Settings Set Countries
Region
4. Enter transaction code SE38, and execute the report CRMPCD_ORG_UNIT_EXTRACT.
5. Enter the details below to execute the report:
Select Initial Load
Enter Root Organization Unit
Enter Plan Version
Enter Key Date
Enter Package Size
Enter Site Name
6. After successfully executing the report, go to transaction code we05 to view the status of the IDocs.
7. Once you have confirmed, the IDoc status is successful. You can also check the status, in the Administrator work center Web Service Message Monitoring view.
As the organization entities are first replicated into the Staging Business Object (under Data Integration work center Organization Replication view), the organization entities need to be activated in the Staging Area for successful replication into Cloud for Customer.
Successful organizational mode replication should automatically maintain the ID mapping (under Application and User Management Edit ID mapping for Integration)
5.2 Initial Load of Territories
Pre-requisite:
Maintain code values for accounts
Employee
Account
Procedure
1. Select the territory hierarchy you wish to replicate.
2. Use transaction CRMPCD_TERRITORY_TEST to run the report. 3. Maintain code values for Sales Territory Data.
Note
To maintain complete code lists in Cloud for Customer, please refer to chapter 7.1 in the integration guide.
Local Data Type CRM Location Path Cloud for Customer Path
HierarchyLevelCode 4. Execute the report.
Note
In this example, company level 00 for 1TERY1, 2132FG and 21FINA is used.
Enter the below details to execute the report
Select Initial Load
Enter Territory ID
Enter Territory Level
Enter Package Size
Enter Site Name
5. After successfully executing the report, go to transaction code we05 to view the status of the IDocs. Once you have confirmed the IDoc Status is successful. You can also check the status, in the Administrator work center Web Service Message Monitoring view.
5.3 Initial Load of Accounts/Contacts/Prospects/Competitors
(Business Partner)
Pre-requisites
Set up Sales Organization Data
Maintain Code Values for Business Partner
Procedure
1. Maintain Code values for Business Partner
Note
To maintain complete code lists in Cloud for Customer, please refer to chapter 7.1 in integration guide.
Local Data Type
CRM Location Path Cloud for Customer Path
AcademicTitle Code
General Business Partners Maintain Academic Title
Maintain Academic Titles under SAP customizing Implementation Guide Cross-Application Components SAP Business Partner Business Partner Persons Name Components
AddressUsage Code
Default Define Address Types under SAP Customizing
Implementation Guide SAP Portfolio and Project Management Portfolio Management
Base System Interfaces SAP Human
Capital Management Integration SAP Portfolio and Project Management System Customizing for SAP HCM SAP Business Partner
Business Partner Basic Settings Address
Determination
BusinessPartn erFunctionTyp eCode
Contacts Functions Define Functions under SAP Customizing
Implementation Guide SAP Portfolio and Project Management Portfolio Management
Base System Interfaces SAP Human
Capital Management Integration SAP Portfolio and Project Management System Customizing for SAP HCM SAP Business Partner
Business Partner Relationships Contact
Person
BusinessPartn
erRoleCode Define BP Roles under SAP Customizing Implementation Guide SAP Portfolio and
Project Management Portfolio Management
Base System Interfaces SAP Human
Capital Management Integration SAP Portfolio and Project Management System Customizing for SAP HCM SAP Business Partner
Business Partner Basic Settings Business
Local Data Type
CRM Location Path Cloud for Customer Path
BusinessPartn erFunctionalAr eaCode
Contacts
Departments Define Departments under SAP Customizing Implementation Guide SAP Portfolio and
Project Management Portfolio Management
Base System Interfaces SAP Human
Capital Management Integration SAP Portfolio and Project Management System Customizing for SAP HCM SAP Business Partner
Business Partner Relationships Contact
Person
BusinessPartn erRelationship CategoryCode
Properties of Business Partner Relationship Categories under SAP Customizing
Implementation Guide Cross-Application Components SAP Business Partner
Business Partner Relationships Basic
Settings CashDiscount TermsCode Communicatio n Medium Type Code CompanyLega lFormCode General Business Partners Maintain Legal Form
Maintain Legal Forms under SAP Customizing Implementation Guide SAP Portfolio and Project Management Portfolio Management
Base System Interfaces SAP Human
Capital Management Integration SAP Portfolio and Project Management System Customizing for SAP HCM SAP Business Partner
Business Partner Organizations CustomerGrou pCode CustomerABC Classification Code Accounts Maintain
ABC Classification Define Customer Class under SAP Customizing Implementation Guide Customer Relationship
Management Master Data Business Partner Define Attributes
DistributionCh
annelCode Define Distribution Channels under SAP Customizing Implementation Guide Customer
Relationship Management Master Data Organizational Management Organizational Data for Sales Scenario
DivisionCode Division Define Divisions under SAP Customizing
Implementation Guide Customer Relationship Management Master Data Organizational
Management Division Settings
DocumentTyp eCode
Local Data Type
CRM Location Path Cloud for Customer Path
FormOfAddres sCode
General Business Partners Maintain Titles
Maintain Forms of Address under SAP Customizing Implementation Guide SAP Portfolio and Project Management Portfolio Management Base System Interfaces SAP Human Capital Management Integration SAP Portfolio and Project Management System Customizing for SAP HCM SAP Business Partner Business Partner Basic Settings Forms of Address IndustrialSect orCode General Business Partners Industries IndustryClassif icationSystem Code
Maintain Industry Systems and Industries under SAP Customizing Implementation Guide SAP Portfolio and Project Management Portfolio Management Base System Interfaces SAP Human Capital Management Integration SAP Portfolio and Project Management System Customizing for SAP HCM SAP Business Partner Business Partner Organizations
MaritalStatusC ode
General Business
Partners Maintain Marital Status under SAP Customizing Implementation Guide Cross-Application
Components SAP Business Partner
Business Partner Persons Marital
Statuses
NielsenRegion Code
Accounts-> Nielsen Define Nielsen ID under SAP Customizing
Implementation Guide Customer Relationship Management Master Data Business Partner Define Attributes
OccupationCo de
General Business
Partner Profession Maintain Occupations under SAP Customizing Implementation Guide Cross-Application
Components SAP Business Partner Business Partner Persons Occupations
RegionCode Region Insert Regions under SAP Customizing
Implementation Guide SAP NetWeaver General Settings Set Countries
PartyIdentifier
TypeCode Define Identification Categories under SAP Customizing Implementation Guide
Cross-Application Components SAP Business Partner Business Partner Basic Settings
Identification Numbers TextCollection
Local Data Type
CRM Location Path Cloud for Customer Path
VIPReasonCo de
Contacts VIP
contacts Define VIP Entries under SAP Customizing Implementation Guide SAP Portfolio and
Project Management Portfolio Management
Base System Interfaces SAP Human
Capital Management Integration SAP Portfolio and Project Management System Customizing for SAP HCM SAP Business Partner Business Partner Relationships
Contact Person IncotermsClas
sificationCode PartyRoleCod e
Party Role Definition
2. Execute the report CRMPCD_BUPA_EXTRACT to load Business Partners from SAP CRM to SAP Cloud for Customer.
Note
When you load business partners into the Cloud solution, only the following roles are supported.
Account (CRM000)
Competitor (CRM005)
Contact Person (BUP001)
Employee (BUP003) Optional
Prospect (BUP002)
Caution
If time-dependent data (such as different time-dependent addresses) is maintained in SAP CRM, only the data that is currently valid is transferred to the SAP Cloud solution. If a business partner address in SAP CRM contains multiple communication data (such as multiple telephone or fax numbers), only the default communication data is transferred to the Cloud solution.
5.4 Initial Load of Employees
Prerequisites
Maintain code values for Employee,
Setting up Sales Organization Data
You have two possibilities for replicating employee data from SAP CRM to SAP Cloud for Customer
Option 1: Using the Employee web service (by selecting Employee replication in the
Business Adapting Catalog)
Option 2: Using the Business partner replication service (by selecting Role category
BUP003)
Note
We recommend that you use Option 1 as it includes information such as Personnel number, log-on user ID and Sales organization assignments.
Points to consider while using Option 1:
The business roles are not filled by default; They can be filled by implementing a BADI in the Employee IDoc
If user id is not maintained in Business Partner, then the user id of the employee is defaulted to his/her e-mail address.
The validity period of the employee is set to the validity period of his/her role assignment in SAP CRM.
By default, users are activated in SAP Cloud for Customer
The replicated business object is not directly saved in the target business object but the saving needs to be triggered by the business user in the Data Integration work center or an automatic batch job. (Staging Business Object)
Note
Replication messages of employees are processed by a background job (scheduled job). Employees are not visible in the cloud solution immediately but are available after the next scheduled run of the job.
Procedure
1. Maintain code values for Employee.
Note
To maintain code lists in Cloud for Customer, please refer to chapter 7.1 in the integration guide.
Local Data Type CRM Location Path Cloud for Customer Path
AcademicTitleCode General Business Partners Maintain Academic Title
Maintain Academic Titles under SAP Customizing Implementation Guide Cross-Application Components SAP Business Partner Business Partner
Persons Name Components FormofAddressCode General Business
Maintain Titles Maintain Forms of Address under SAP Customizing Implementation Guide
SAP Portfolio and Project Management
Local Data Type CRM Location Path Cloud for Customer Path
MaritalStatusCode General Business Partners Maintain Marital Status under SAP
Customizing Implementation Guide Cross-Application Components SAP Business Partner Business Partner
Persons Marital Statuses WorkAgreementCompens
ationCategoryCode GenderCode
WorkAgreementTypeCode
2. Enter transaction code SE38 and execute the report CRMPCD_EMPLOYEE_EXTRACT.
3. Enter the below details to execute the report.
Select Initial Load
Enter Business Partner Number Range
Enter Key Date
Enter Package Size
Enter Site Name
After successfully executing the report, go to transaction code we05 to view the status of the IDocs.
4. Once you have confirmed, the IDoc Status is successful. You can also check the status, in the Administrator work center Web Service Message Monitoring view.
As the Employees are first replicated into the Staging Business Object (under Data Integration work center -> Complete Employee Master Data Replication view the Employee records need to be activated in the Staging Area for successful replication into Cloud for Customer.
Successful Organizational mode replication should automatically maintain the ID mapping (under Application and User Management Edit ID mapping for Integration)
5.5 Initial Load of Product Hierarchy
1. Open the product hierarchy that needs to be transferred in the SAP CRM Web UI or by starting transaction COMM_HIERARCHY.
2. Identify the hierarchy you wish to replicate to the cloud solution.
3. Execute the report CRMPCD_PROD_HIERARCHY_TEST for the product category hierarchy distribution.
Note
It is possible to have only one product hierarchy modeled in the cloud solution. For this reason, you can only transfer the hierarchy that is assigned to the Sales application. This is the default implementation in the CRMPCD_PCH_FILTER BAdI. If you want to change this behavior, then you need to adjust the BAdI implementation. For more information, see the
4. After successfully executing the report, go to transaction code we05 to view the status of the IDocs.
Once you have confirmed the IDoc Status is successful. You can also check the status, in the Administrator work center Web Service Message Monitoring view.
Successful Product Hierarchy replication should automatically maintain the ID mapping (under Application and User Management Edit ID mapping for Integration)
5.6 Initial Load of Product Materials
Prerequisite
Maintain code values for Products,
Setting up Product Hierarchy Data
Procedure
1. For Product Material replication, first select the products you wish to replicate from SAP CRM to SAP Cloud for Customer.
2. Maintain code values for Products.
Note
To maintain code lists in Cloud for Customer, please refer to chapter 7.1 in integration guide.
Local Data Type CRM Location Path Cloud for
Customer Path
DistributionChannelCode DivisionCode
MeasureUnitCode
3. Set up Sales Organization Data.
For more information, see section 5 on how to setup Sales Organization Data in Cloud for Customer.
4. Set up Product Hierarchy Data.
5. Enter transaction code SE38 and execute the report CRMPCD_PRODUCT_EXTRACT.
6. Enter the below details to execute the report.
Product ID
Product Type
Package Size
Site Name
7. After successfully executing the report, go to transaction code we05 to view the status of the IDocs. Once you have confirmed the IDoc Status is successful. You can also check the status, in the Administrator work center Web Service Message Monitoring view.
5.7 Initial Load of Business Partner Relation (Account
Hierarchy, Account-Employee, Account-Contact)
Prerequisites
Maintain code values for Accounts
Setting up Sales Organization Data
Procedure
Execute the report
To trigger the initial load, go to transaction code SE38 and execute the report CRMPCD_BUPA_REL_EXTRACT.
Note
As only one Root Account Hierarchy can be maintained on the Cloud for Customer Solution, select the parent-child relationship on SAP CRM solution that you wish to replicate.
When you load Business Partner Relations into the Cloud solution, only the following relationship categories are supported. (This is true for both initial download as well as data replication.)
Parent/Child Relationship
Custom Relationships
Has/Is Contact Person (BUR001)
6 Initial Load of Transaction Data from SAP
CRM to SAP Cloud for Customer
The diagram below captures the sequence in which you should perform the initial load for transactional data.
The following table gives the list of reports needed to set up the master data objects:
Transaction Data object Busines s Object Report Pre-requisite Business Object(s) Classic BADI
Leads Order CRMPCD_ORDER_EXTRACT Sales Organization , Account, Contact, Employee, CRMXIF_O RDER_MAP
Opportunities Order CRMPCD_ORDER_EXTRACT All Master Data
CRMXIF_O RDER_MAP Activities Task Order CRMPCD_ACTIVITY_EXTRACT All Master
Data
CRMXIF_O RDER_MAP Activities
Appointment
Order CRMPCD_ACTIVITY_EXTRACT All Master Data
CRMXIF_O RDER_MAP Activities Email Order CRMPCD_ACTIVITY_EXTRACT All Master
Data
CRMXIF_O RDER_MAP
Phone call Order CRMPCD_ACTIVITY_EXTRACT All Master Data
CRMXIF_O RDER_MAP Bulk Initial Load All Objects CRMPCD_IDOC_SEND_BY_CO
NTENT
See object level dependency
7 Step-by-Step Procedure
7.1 Initial Load of Leads
Prerequisites
Maintain Code Values for Leads
All Master Data
Procedure
1. Enter transaction code SE38 and execute the report CRMPCD_ORDER_EXTRACT.
2. Enter the below details to execute the report.
Enter the Order ID range
Enter LEAD as the Process Type
Enter additional filter criteria such as Sales org, Status if required
Enter Package Size
Enter Site Name
3. After successfully executing the report, go to transaction code we05 to view the status of the IDocs. Once you have confirmed the IDoc Status is successful. You can also check the status, in the Administrator work center Web Service Message Monitoring view.
7.2 Initial Load of Opportunities
Prerequisites
Maintain code values for Opportunities
All Master Data
Procedure
1. Enter transaction code SE38 and execute the report CRMPCD_ORDER_EXTRACT.
2. Enter the below details to execute the report.
Enter the Order ID range
Enter OPPT as the Process Type
Enter additional filter criteria such as Sales org, Status if required
Enter Package Size
Enter Site Name
3. After successfully executing the report, go to transaction code we05 to view the status of the IDocs. Once you have confirmed the IDoc Status is successful. You can also check the status, in the Administrator work center Web Service Message Monitoring view.
7.3 Initial Load of Activities
Prerequisites
Maintain code values for Opportunities
All Master Data
Procedure
1. Enter transaction code SE38 and execute the report CRMPCD_ACTIVITY_EXTRACT.
2. Enter the below details to execute the report.
Enter the Order ID range
Enter the Activity types such as CX01, CX02, CX03 and CX04
Enter additional filter criteria such as Sales org, Status, reference to Opportunity if required
Enter Package Size
Enter Site Name
3. After successfully executing the report, go to transaction code we05 to view the status of the IDocs. Once you have confirmed the IDoc Status is successful. You can also check the status, in the Administrator work center Web Service Message Monitoring view.
www.sdn.sap.com/irj/sdn/howtoguides
© 2014 SAP AG or an SAP affiliate company. 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. National product specifications may vary.
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.