EHP3 for SAP CRM 7.0 May 2014 English SAP Fiori Sales Rep & SAP CRM Rapid- Deployment Solution Configuration Delta Guide for the CRM rapiddeployment solution V6.703 and the SAP Fiori Apps rapid-deployment solution SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany Public
Copyright 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. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG (or an SAP affiliate company) in Germany and other countries. Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices. 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 or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP AG or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP AG or SAP affiliate company 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. In particular, SAP AG or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP AG s or its affiliated companies strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP AG or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions. SAP AG Public Page 2 of 10
Revision Change Date Description 0 SAP AG Public Page 3 of 10
Icons Icon Meaning Caution Example Note Recommendation Syntax Typographic Conventions Type Style Example text Example text EXAMPLE TEXT Example text EXAMPLE TEXT Example text <Example text> Description Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options. Cross-references to other documentation. Emphasized words or phrases in body text, titles of graphics and tables. Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE. Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools. Keys on the keyboard, for example, function keys (such as F2) or the ENTER key. Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries. SAP AG Public Page 4 of 10
Content 1 Purpose... 6 2 Preparation... 6 2.1 Prerequisites... 6 3 Configuration... 6 3.1 Define Text Determination for Opportunity... 6 3.2 Define Text Determination for Leads... 7 3.3 Define Virus Scan Profile... 7 3.4 Configure SAP Fiori Launchpad Designer... 7 3.5 Define Settings for My Tasks App... 8 3.6 Define Settings for My Appointment App... 9 3.7 Define Settings for My Opportunities App... 9 4 Next steps... 10 SAP AG Public Page 5 of 10
SAP Fiori Sales Rep & SAP CRM Rapid- Deployment Solution: Configuration Delta Guide 1 Purpose The purpose of this document is to describe specific, additionally required system configuration on top of the configuration suggested by the solution packages SAP CRM rapiddeployment solution V6.703 and SAP Fiori Apps rapid-deployment solution V1.20. This configuration is required when implementing both packages together, i.e. with the aim to use SAP Fiori apps for Sales Reps on top of the scope of the SAP CRM rapid-deployment solution. 2 Preparation 2.1 Prerequisites Before starting to implement the additional configuration suggested below, configure your SAP CRM system based on the SAP Best Practices for the SAP CRM rapid-deployment solution (V6.703), and implement the SAP Fiori apps based on SAP Best Practices provided by the SAP Fiori Apps rapid-deployment solution. Note that the configuration documented in this configuration guide has been developed and validated with the SAP Fiori Apps rapid-deployment solution V1.20. If implemented based on a higher version of that package, the configuration suggested below might not be fully applicable. For more information, refer to the respective solution package content. 3 Configuration The following section describes the required additional settings. The purpose of these activities is to make the following SAP CRM-based Fiori apps run on top of a system configured according to the SAP CRM rapid-deployment solution: My Accounts My Contacts (CRM) My Appointments My Tasks My Leads My Opportunities My Notes Simulate Sales Pipeline Track Sales Pipeline 3.1 Define Text Determination for Opportunity SAP AG Public Page 6 of 10
SAP Reference IMG menu Customer Relationship Management Basic Functions Text Management Define Text Determination 2. Choose object CRM_ORDERH. 3. Double-click. 4. Select the text determination procedure that has been specified for transaction type of opportunities (OPSM0001). 5. Select the Definition of view. 6. Specify the value P (Log) in the Changes field for at least one text type. 7. Choose Save. 3.2 Define Text Determination for Leads SAP Reference IMG menu Customer Relationship Management Basic Functions Text Management Define Text Determination 2. Choose object CRM_ORDERH. 3. Double-click. 4. Select the text determination procedure that has been specified for transaction type of opportunities (LEAD0001) 5. Select the Definition of view. 6. Specify the value P (Log) in the Changes field for at least one text type. 7. Choose Save. 3.3 Define Virus Scan Profile SAP Reference IMG menu SAP NetWeaver Gateway odatachannel Administration General Settings Define Virus Scan Profile 2. Choose Virus Scan Switched Off. 3. Choose Execute. 3.4 Configure SAP Fiori Launchpad Designer 1. The Launchpad Designer can be accessed using the following URL: http://<gatewayhost>:<port>/sap/bc/ui5_ui5/sap/arsrvc_upb_admn/main.html?sapclient=<number> 2. Configure Fiori Apps: Fiori App Name Semantic Object Action My Contacts (CRM) ContactPerson MyContacts SAP AG Public Page 7 of 10
Fiori App Name Semantic Object Action My Accounts Account MyAccounts My Appointments Appointment myappointments My Tasks Task Tasks My Opportunities Opportunity Opportunities My Leads Lead lead My Notes Note mynotes Simulate Sales Pipeline Opportunity simulatesalespipeline Track Sales Pipeline Opportunity tracksalespipeline 3. Configure Fiori Apps Target Mapping (for all entries Launchpad Role: UICRM001, Launchpad Instance: TRANSACTIONAL): Fiori App Name Semantic Object Action Application Alias My Contacts (CRM) ContactPerson MyContacts MyContacts My Accounts Account MyAccounts MyAccounts My Appointments Appointment myappointments CRMMyCalendar My Tasks Task Tasks ManageTasks My Opportunities Opportunity Opportunities MyOpportunities My Leads Lead lead MyLeads My Notes Note mynotes CRMMyNotes Simulate Sales Pipeline Track Sales Pipeline Opportunity simulatesalespipeline SalesPipelneSimulator Opportunity tracksalespipeline SalesPipelneTrack 3.5 Define Settings for My Tasks App SAP Reference IMG menu Customer Relationship Management Transaction Settings for Activities Define Settings for My Tasks App 2. Create the following entry: Field Transaction Type Text Type for Title Text Type for Note Value Y030 (BP Task) A001 (Description) A001 (Description 3. Choose Save. SAP AG Public Page 8 of 10
3.6 Define Settings for My Appointment App SAP Reference IMG menu Customer Relationship ManagementTransactionSettings for Activities Define Settings for My Appointments App 2. Create the following entry: Field Transaction Type Text Type Int. Partner Field Ext. Partner Value Y020 (BP Appointment) A002 (Note) 00000014 (Employee Responsible) Value 00000015 (Contact Person) 3. Choose Save. 3.7 Define Settings for My Opportunities App SAP Reference IMG menu Customer Relationship ManagementTransactionSettings for Opportunities Define Settings for My Opportunities App 2. Create the following entry: Field Transaction Type Value Y002 (BP Opportunity) 3. Choose Save. SAP AG Public Page 9 of 10
4 Next steps After having successfully configured your SAP CRM system based on the SAP CRM rapiddeployment solution (V6.703), the SAP Fiori Apps rapid deployment solution and this delta guide you can run the processes with the help of the business process documentation SAP Fiori Sales Representative (MEC). The following chapters of the SAP Fiori Sales Representative documentation are relevant for the combination of the SAP Fiori Apps and the SAP CRM rapid deployment solution, with the deviations mentioned below: SAP My Accounts SAP My Tasks (use transaction type BP Task instead of Task Fiori) SAP My Appointments (use transaction type BP Appointment instead of Appointment) SAP My Contacts (CRM Role) SAP My Opportunities (use transaction type BP Opportunity instead of Opportunities) SAP My Leads SAP My Notes SAP Simulate Sales Pipeline SAP Track Sales Pipeline To access the WebClient UI, the sales user should be assigned to business role YBP_SLS_EMPL (instead of business role sales professional) as described in the configuration guide CRM Web Client UI for Sales (C07), which is part of the SAP CRM rapiddeployment solution. SAP AG Public Page 10 of 10