How-To Guide SAP Cloud for Customer Document Version: How to Perform Initial Load of data from SAP CRM to SAP Cloud for Customer

Transcription

1 How-To Guide SAP Cloud for Customer Document Version: How to Perform Initial Load of data from SAP CRM to SAP Cloud for Customer

2 Document History Document Version Description 1.0 First official release of this guide Business Scenario 2014 SAP AG or an SAP affiliate company. All rights reserved. 2

3 Table of Contents 1 Business Scenario Background Information Prerequisites Initial Load of Master Data from SAP CRM to SAP Cloud for Customer Step-by-Step Procedure Initial Load of Organization Data Initial Load of Territories Initial Load of Accounts/Contacts/Prospects/Competitors (Business Partner) Initial Load of Employees Initial Load of Product Hierarchy Initial Load of Product Materials Initial Load of Business Partner Relation (Account Hierarchy, Account-Employee, Account-Contact) Initial Load of Transaction Data from SAP CRM to SAP Cloud for Customer Step-by-Step Procedure Initial Load of Leads Initial Load of Opportunities Initial Load of Activities Business Scenario 2014 SAP AG or an SAP affiliate company. All rights reserved. 3

4 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. Business Scenario 2014 SAP AG or an SAP affiliate company. All rights reserved. 4

5 The following table gives the list of reports needed to set up the master data objects: Master Data object Sales Organization Employee Account Sales Territory Contact Prospect Competitor Product Hierarchy Product Materials Account Hierarchy Account- Employee Relation Account- Contact Relation Bulk Initial Load Business Object Organization Model Business Partner Business Partner Territory Model Business Partner Business Partner Business Partner Product Hierarchy Product Materials Business Partner Relation Business Partner Relation Business Partner Relation All Objects Report CRMPCD_ORG_UNIT_ EXTRACT CRMPCD_EMPLOYEE_ EXTRACT CRMPCD_BUPA_EXTR ACT CRMPCD_TERRITORY_ TEST CRMPCD_BUPA_EXTR ACT CRMPCD_BUPA_EXTR ACT CRMPCD_BUPA_EXTR ACT CRMPCD_PROD_HIEA RCHY_TEST CRMPCD_PRODUCT_ EXTRACT CRMPCD_BUPA_REL_ EXTRACT CRMPCD_BUPA_REL_ EXTRACT CRMPCD_BUPA_REL_ EXTRACT CRMPCD_IDOC_SEND _BY_CONTENT Prerequisite Business Object(s) None Sales Organization Sales Organization Employee, Account None Sales Organization Sales Organization None Product Hierarchy Sales Organization, Account Sales Organization, Account, Employee Sales Organization, Account, Contact See object level dependency Enhancement Spot CRMPCD_OR G_UNIT_REP LICATION CRMPCD_EM PLOYEE_REP LICATION CRMPCD_TE RRITORY_RE PLICATION CRMPCD_PC H_REPLICATI ON Classic BADI CRMXIF_PA RTNER_MA P CRMXIF_PA RTNER_MA P CRMXIF_PA RTNER_MA P CRMXIF_PA RTNER_MA P COMXIF_P ROD_MAT_ MAP CRMXIF_PA RTNER_R_ MAP CRMXIF_PA RTNER_MA P CRMXIF_PA RTNER_MA P Initial Load of Master Data from SAP CRM to SAP Cloud for Customer 2014 SAP AG or an SAP affiliate company. All rights reserved. 5

6 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 Select Root Org. Unit is Company Step-by-Step Procedure 2014 SAP AG or an SAP affiliate company. All rights reserved. 6

7 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: Procedure Maintain code values for accounts Employee Account 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. Step-by-Step Procedure 2014 SAP AG or an SAP affiliate company. All rights reserved. 7

8 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. Step-by-Step Procedure 2014 SAP AG or an SAP affiliate company. All rights reserved. 8

9 5.3 Initial Load of Accounts/Contacts/Prospects/Competitors (Business Partner) Pre-requisites Procedure Set up Sales Organization Data Maintain Code Values for Business Partner 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 AcademicTitle Code AddressUsage Code BusinessPartn erfunctiontyp ecode BusinessPartn errolecode CRM Location Path General Business Partners Maintain Academic Title Default Contacts Functions Cloud for Customer Path Maintain Academic Titles under SAP customizing Implementation Guide Cross- Application Components SAP Business Partner Business Partner Persons Name Components 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 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 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 Partner Roles Step-by-Step Procedure 2014 SAP AG or an SAP affiliate company. All rights reserved. 9

10 Local Data Type BusinessPartn erfunctionalar eacode BusinessPartn errelationship CategoryCode CashDiscount TermsCode Communicatio n Medium Type Code CompanyLega lformcode CustomerGrou pcode CustomerABC Classification Code DistributionCh annelcode CRM Location Path Contacts Departments General Business Partners Maintain Legal Form Accounts Maintain ABC Classification Cloud for Customer Path 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 Properties of Business Partner Relationship Categories under SAP Customizing Implementation Guide Cross-Application Components SAP Business Partner Business Partner Relationships Basic Settings 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 Define Customer Class under SAP Customizing Implementation Guide Customer Relationship Management Master Data Business Partner Define Attributes 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 Step-by-Step Procedure 2014 SAP AG or an SAP affiliate company. All rights reserved. 10

11 Local Data Type FormOfAddres scode IndustrialSect orcode IndustryClassif icationsystem Code MaritalStatusC ode NielsenRegion Code OccupationCo de CRM Location Path General Business Partners Maintain Titles General Business Partners Industries General Business Partners Accounts-> Nielsen General Business Partner Profession Cloud for Customer Path 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 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 Maintain Marital Status under SAP Customizing Implementation Guide Cross-Application Components SAP Business Partner Business Partner Persons Marital Statuses Define Nielsen ID under SAP Customizing Implementation Guide Customer Relationship Management Master Data Business Partner Define Attributes 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 TextCollection TextCode Define Identification Categories under SAP Customizing Implementation Guide Cross- Application Components SAP Business Partner Business Partner Basic Settings Identification Numbers Step-by-Step Procedure 2014 SAP AG or an SAP affiliate company. All rights reserved. 11

12 Local Data Type VIPReasonCo de IncotermsClas sificationcode PartyRoleCod e CRM Location Path Contacts VIP contacts Party Role Definition Cloud for Customer Path 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 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. Step-by-Step Procedure 2014 SAP AG or an SAP affiliate company. All rights reserved. 12

13 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 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) Procedure 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. 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 FormofAddressCode General Business Partners Maintain Academic Title General Business Maintain Titles Maintain Academic Titles under SAP Customizing Implementation Guide Cross-Application Components SAP Business Partner Business Partner Persons Name Components 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 Step-by-Step Procedure 2014 SAP AG or an SAP affiliate company. All rights reserved. 13

14 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. Step-by-Step Procedure 2014 SAP AG or an SAP affiliate company. All rights reserved. 14

15 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. Step-by-Step Procedure 2014 SAP AG or an SAP affiliate company. All rights reserved. 15

16 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 CRM: Customer Enhancements (BAdI Definitions) section. Step-by-Step Procedure 2014 SAP AG or an SAP affiliate company. All rights reserved. 16

17 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 Procedure Maintain code values for Products, Setting up Product Hierarchy Data 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. For information, see section above on how to setup Product Hierarchy Data. Step-by-Step Procedure 2014 SAP AG or an SAP affiliate company. All rights reserved. 17

18 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 Procedure Maintain code values for Accounts Setting up Sales Organization Data 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) Has/Is the Employee Responsible For (BUR011) Step-by-Step Procedure 2014 SAP AG or an SAP affiliate company. All rights reserved. 18

19 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 Prerequisite Business Object(s) Leads Order CRMPCD_ORDER_EXTRACT Sales Organization, Account, Contact, Employee, Opportunities Order CRMPCD_ORDER_EXTRACT All Master Data Activities Task Order CRMPCD_ACTIVITY_EXTRACT All Master Data Activities Appointment Order CRMPCD_ACTIVITY_EXTRACT All Master Data Activities Order CRMPCD_ACTIVITY_EXTRACT All Master Data Activities Order CRMPCD_ACTIVITY_EXTRACT All Master Data Classic BADI CRMXIF_O RDER_MAP CRMXIF_O RDER_MAP CRMXIF_O RDER_MAP CRMXIF_O RDER_MAP CRMXIF_O RDER_MAP CRMXIF_O RDER_MAP Initial Load of Transaction Data from SAP CRM to SAP Cloud for Customer 2014 SAP AG or an SAP affiliate company. All rights reserved. 19

20 Phone call Order CRMPCD_ACTIVITY_EXTRACT All Master Data Bulk Initial Load All Objects CRMPCD_IDOC_SEND_BY_CO NTENT See object level dependency CRMXIF_O RDER_MAP Initial Load of Transaction Data from SAP CRM to SAP Cloud for Customer 2014 SAP AG or an SAP affiliate company. All rights reserved. 20

21 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. Step-by-Step Procedure 2014 SAP AG or an SAP affiliate company. All rights reserved. 21

22 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. Step-by-Step Procedure 2014 SAP AG or an SAP affiliate company. All rights reserved. 22

23 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. Step-by-Step Procedure 2014 SAP AG or an SAP affiliate company. All rights reserved. 23

24 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. SAP 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 other countries. Please see index.epx for additional trademark information and notices.