Bp Crm Crm702 Quick Guide en Xx

8/17/2019 Bp Crm Crm702 Quick Guide en Xx

http://slidepdf.com/reader/full/bp-crm-crm702-quick-guide-en-xx 1/29

SAP CRM 7.02

SAP CRM 7.02,version for SAP

HANAOctober 2012

English

Document Version 3.1

Quick Guide to Implementing

the SAP Best Practices forEnhancement Package 2 andEnhancement Package 2,Version for SAP HANA, forCustomer RelationshipManagement 7.0

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany



SAP Best Practices Quick Guide to Implementing SAP Best Practices for CRM 702

© SAP AG Page 2 of 29

Copyright

© 2013 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 theexpress 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 componentsof other software vendors.

National product specifications may vary.

These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informationalpurposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errorsor omissions with respect to the materials. The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services, ifany. 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 aretrademarks or registered trademarks of SAP AG in Germany and other countries. Please seehttp://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information

and notices.

http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark







Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include fieldnames, screen titles, pushbuttons as well as menu names, paths, andoptions.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names,program names, transaction codes, table names, and individual keywords of a programming language, when surrounded by body text, forexample, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths,

messages, source code, names of variables and parameters as well asnames of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the

ENTER key.

Example text Exact user entry. These are words or characters that you enter in thesystem exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace thesewords and characters with appropriate entries.





Contents

1 Purpose ................................................................................................................. 5

2 System Setup & Preparation ................................................................................. 6

2.1

Release and Support Package Level .................................................................... 6 2.2

SAP Notes ............................................................................................................. 7

2.3

General Client Settings .......................................................................................... 7

2.3.1

Client Roles ............................................................................................................. 7

2.3.2

Further Client Settings ............................................................................................ 8

2.3.3

Creating an Installation Folder for Content Activation ............................................ 8

2.3.4

Creating a User for Activation of SAP Best Practices Content ............................... 9

2.3.5 Creating Transport Requests for Activation .......................................................... 10

2.3.6 Deselecting Activation Links in BC Sets ............................................................... 11

2.3.7 Setting the Maximum Work Process Run Time .................................................... 11

2.3.8 SAP Scripting ........................................................................................................ 12

2.3.9 Set Default Timeout for HTTP and HTTPS Services ............................................ 13

2.4 Preparing the System User for Content Activation .............................................. 13

2.4.1 SAP Software Change Registration (SSCR): Developer Key .............................. 13

2.4.2 Unicode Settings ................................................................................................... 14

2.4.3 Deactivate Info Dialog Box on Dynpro Size Check .............................................. 14

2.4.4 Allow GUI Scripting ............................................................................................... 14

2.5 Installation of Language- or Country-Specific Content ........................................ 15

3 Activation of Business Content ............................................................................ 17

3.1 Automated Activation of Processes ..................................................................... 17

3.1.1 Getting Started and Navigation ............................................................................. 17

3.1.2

Importing the Solution Scope File ......................................................................... 18

3.1.3 Maintain Path to Installation Data ......................................................................... 18

3.1.4 Set Documentation Path for Solution Builder ....................................................... 19

3.1.5 Upload the Installation Data .................................................................................. 19

3.1.6 Maintain Solution Settings: Select Languages ..................................................... 20

3.1.7 Scope Your Solution ............................................................................................. 20

3.1.8 Personalize the Solution ....................................................................................... 21

3.1.9

Maintaining System Landscape Information for Solution Builder ......................... 21

3.1.9.1

Creating a Solution Builder RFC Destination for an integrated SAP System ....... 22

3.1.9.2

Assigning RFC Destinations to Target Systems ................................................... 23

3.1.10

Starting Activation ................................................................................................. 23

3.1.11

Manual Interaction and Error Handling During Activation ..................................... 25

3.1.12

Processing General Errors during Automated Installation.................................... 26

3.1.13

Deployment of Multiple CRM Solution Packages in One Client ........................... 27

3.2

Manual Implementation ....................................................................................... 28

4

Security Aspects .................................................................................................. 29

4.1

User Administration and Authentication .............................................................. 29





Quick Guide to Implementing the SAP BestPractices for Customer Relationship Management702, and 702 Version for SAP HANA

1 PurposeThis Quick Guide provides step by step information you need to implement the SAP BestPractices for Enhancement Package 2 for CRM 7.0 (CRM 7.02), respectively EnhancementPackage 2 for CRM 7.0, version for SAP HANA, using the SAP Best Practices Solution Builder.

This Quick Guide serves as a foundation for several additional, that is, package-specific QuickGuides for Best Practices and Rapid Deployment solutions based on CRM 7.02 resp. CRM 7.02,version for SAP HANA.

Before proceeding with this document you must have done the following:

Defined the scope relevant for your project

Finalized technical prerequisites

Staffed and made available the required resources

SAP Best Practices for CRM are typically implemented in a new SAP CRM system, i.e. noexisting business processes in the customer’s system landscape have to be considered andintegrated. However SAP Best Practices for CRM can also be an option for existing SAPCRM customers. Such deployments require very detailed knowledge about the alreadyimplemented business processes and the business processes to be implemented by therespective package.

Refer specifically to the Step-by-Step Guide of the SAP CRM rapid-deployment solution(V4.702) for guidance regarding how to proceed and what to consider from an

implementation perspective in case of planned deployments in running SAP CRM systems.

This document does not provide a general overview and explanation of SAP Best Practices. Formore information about the Best Practices concepts, see the related documentation onhttp://service.sap.com/solutionpackages and follow the links to the Learning Maps.

This document is intended for the following project roles, which already have a sound knowledgeof SAP Best Practices, including the tools and documentation:

System administrators

Basis consultants

Business consultants

If you are not familiar with the SAP Best Practices tools, refer to the document SAP BestPractices Tools on http://service.sap.com/bestpractices, and choose: Learning Center ->Learning Map for SAP Business All-in-One.

http://service.sap.com/solutionpackages


http://service.sap.com/bestpractices








2 System Setup & Preparation The customer must provide the system landscape, that means, install the required softwarecomponents, to enable the project team to implement and configure the scope of SAP BestPractices for CRM.

For more information about requirements for the following areas see the Software Requirements

document for your solution package:

System Landscape

Software (Components and Add-ons)

You can find the Software Requirements document here:

For solution package type In the …

Rapid Deployment Solution Step-by-step guide, under Start: Confirm Installation.

SAP Best Practices for BAiO Best Practices documentation package, under Explore:Install SAP Applications.

Additionally, the SAP Notes specified in detail in section SAP Notes in this guide must beimplemented.

2.1 Release and Support Package LevelThe deliverables of SAP Best Practices packages were developed and tested in a systemlandscape with specific release and support package (SPS) level. If the SPS level in your systemis different, there may be errors during the activation. You may be able to perform the activationactivities manually using the configuration guides, but errors may still occur.

Make sure that your system meets the minimum SPS level requirements. In caseyour system has an exceptional SPS level compared to the SAP Best Practicesrequirements, only limited support can be provided.

If you need a higher SPS level in your system, for example, because of additionalfunctionality, first import and activate the SAP Best Practices package on the SPSlevels as mentioned below, then update your system to the target SPS level.

The support package levels relevant for the solution package is documented in the respectiveSoftware Requirements document. You can find the Software Requirements document in one ofthe following ways:

For Solution Package Type In …


Best Practices Best Practices documentation package, under Explore:Install SAP Applications.

Receiving the Software at the Correct SP Level

For delivery of the software, an installation number and a corresponding license agreement arerequired. An S-USER is required to order software in the Software Catalog or download from theSAP Software Download Center (SWDC) on SAP Service Marketplace (SMP). You can onlyorder unrestricted SAP software. Contact the SAP contract department to ask for a physicalshipment or create a customer message on component XX-SER-GEN-CONTR.

For downloading SPSs, use the Maintenance Optimizer in your SAP Solution Manager system.You can also select relevant SPSs manually one-by-one via the SWDC on SAP ServiceMarketplace:

https://service.sap.com/swdc Support Packages and Patches A-Z Index

https://service.sap.com/swdc







Only the current Service Release (SR) is delivered to SAP customers/partners via theSWDC on SMP and standard delivery (for example, the Software Catalogue). If youencounter the situation that the required SPS for correct SAP BP packages activationis based on a SPS level LOWER than the current Service Release, the request forthe necessary SPS is handled by a customer message. For details, see SAP Note925690 Standard Ordering Procedures for SAP Software.

2.2 SAP NotesBefore you start the activation of the related SAP Best Practices scope, check the latest versionof the SAP Note for SAP Best Practices for CRM 7.02 Solution Packages. This asset alsocontains updates and corrections for problems that have become apparent after shipment.

Also follow the guidance and instructions provided by SAP Note 1301301 Release Strategy forSAP Best Practices Package ABAP Add-ons. This SAP Note also refers to other notes. Alwayscheck the referenced notes and follow the instructions.

SAP Note # Description Component

1698296 SAP Best Practices for CRM 7.02 Solution Packages

Attached to this note is the asset ‘SAP NotesOverview List’ (xls). Make sure to implementespecially the notes marked as ‘mandatory’.

Note that two separate assets exist: one related tonon-HANA deployments, and a separate one related toHANA based deployments! Verify you work with theright one.

SV-RDS-CRM

1301301 Release Strategy for SAP Best Practices Package ABAP Add-ons

Attached to this add-on-specific note you can find thecorrections for the add-on. Always also apply the latestcorrection transport for the corresponding add-on!

SV-SMB-AIO-BP

Ensure that all SAP Notes are followed respectively implemented that are mentioned in thisguide.

Apply all SAP Notes to the system via the SAP Note Assistant (transaction SNOTE). All SAPNotes must have the implementation status Completely implemented . Some SAP Notes requiremanual action before you set the status to Completely implemented .

To avoid activation errors as a result of generating loads, perform a mass generation usingtransaction SGEN as described in SAP Note 481548 .

2.3 General Client Settings

Use

After you have set up the required system(s), make the following settings to enable automatic ormanual content activation.

2.3.1 Client RolesThe system must not comprise any clients with the role productive client. If the system contains aproductive client, BC sets cannot be activated as required. As a consequence, the automatic

https://service.sap.com/sap/support/notes/925690









2.3.4 Creating a User for Activation of SAP Best PracticesContent

Use

In this activity, you create a user to run the activation of the related SAP Best Practices scope.

We recommend that you use only one User ID to activate the SAP Best Practicescontent. Thus you avoid changing ownership during the activation of the solution.

SAP Best Practices does not supply separate customizing or setup roles (according to thesecurity guideline). Instead, use the functions provided in Role Maintenance (transaction PFCG).Here you can define a role corresponding to your individual IMG project with all the authorizationsyou need to access the corresponding IMG activities required for the SAP Best Practices scope.For more information about defining a role for a Customizing project, see the documentation fortransaction PFCG.

Alternatively you can use the authorization profile SAP_ALL and remove the profileafter activation. If this authorization does not apply to your authorization concept, youcan restrict the rights of the user according to your internal authorization guidelines.Without profile SAP_ALL, issues may occur during activation which must be solved.

If authorization issues occur during activation, you can use transaction SU53 to getinformation on the missing authorizations and extend the authorizations asnecessary.

Procedure

1. To carry out the activity, choose one of the following navigation options:

SAP Menu Tools Administration User Maintenance Users

Transaction Code SU01

2. On the User Maintenance: Initial Screen, in the User field, enter <User-ID> and choose

Create.

3. Choose the Address tab.

4. Make the following entries:

Field name User action and values Note

Last name <Last name of the user>

First name <First name of the user>

5. Choose the Logon Data tab.



Password <initial password>

User type Dialog

7. Choose the Defaults tab.



Logon language EN

Decimal notation 1.234.567,89

Date format DD.MM.YYYY





Output Device <your printer name>

9. Choose the Roles tab and enter the user role you have created that contains the necessaryauthorization profile.

Alternatively you can assign the profile SAP_ALL on the Profiles tab. Make sure thatthis profile corresponds to your internal security guidelines.

10. Save your entries.

Result

You have created a user to activate SAP Best Practices content.

Repeat the steps above for all systems and clients you use. Make sure that you always create thesame user in all systems and clients.

Directly after activation of the SAP Best Practices content, remove theauthorizations you have given to the system user who has performed the

activation steps. This is for security reasons to avoid that the system user misusesthe authorizations granted before.

2.3.5 Creating Transport Requests for Activation

Use

The activation users created in the preceding section require a workbench and a customizingrequest for running the activation using the SAP Solution Builder.

Transport requests can be created during activation. However, if the activation user is not allowedto create own requests, the system administrator must create these requests in advance and theycan be assigned during activation.

For manual activation (See section Manual Implementation), the system administrator must alsocreate the transport requests manually.

Procedure

1. Run the following procedures, choose the following navigation option:

Transaction Code SE01

Creating a Customizing Request

2. On the Transport Organizer (Extended View) screen, choose the Transport tab-page andclick on the Create button.

3. On the Create Request dialog box, choose Customizing request .4. Press Enter.

5. On the Create Request dialog box, enter a Short Description.


Creating a Workbench Request

2. On the Transport Organizer (Extended View) screen, click on the Create button.

3. On the Create Request dialog box , choose Workbench request .

4. Press Enter.

5. On the Create Request dialog box, enter a Short Description.








Parameter Name Description Newvalue

Note

<3600


Result

The parameter is changed. This change only becomes effective when you log off and then log onto the system again.

Switch back to the default value after activating the SAP CRM solution package.

The change is lost when you restart the server (as all profile parameters). If youmust restart the server, repeat these settings.

2.3.8 SAP Scripting

Use

eCATTs are used to automate the activation of SAP CRM rapid-deployment solutionconfiguration settings. Before activation, allow eCATT processing in the system by setting theprofile parameter sapgui/user_scripting . The value for Enable or disable user scripting on thefront-end must be set to true.

Procedure

1. Run the following activity:

Transaction Code RZ11

2. On the Maintain Profile Parameters screen, make the following entries:

Field name Description User action andvalues

Note

Param. Name Profile parameter name sapgui/user_scripting

3. Choose Display .

4. On the Display Profile Parameters Attributes screen, select Change values.

5. On the Change Parameter Value screen, make the following entries:

Field name Description User action and values Note

New Value New Value for userscripting

TRUE Enable SAP Scripting

6. Choose Save.

When you save the change, the window closes and the current value of theparameter changes to TRUE. This change only becomes effective when you log onto the system again.

If the parameter is set in RZ11, you lose the change when you restart the server.





2.3.9 Set Default Timeout for HTTP and HTTPS Services

Use

We recommended that you set the following system parameters for both services TIMEOUT andPROCTIMEOUT to 300 seconds or 600 seconds. The default is 60 seconds.

Procedure

1. Run the following activity:

Transaction Code RZ10

2. On the Edit Profiles screen, enter your instance profile.

3. In the Edit Profile box, select the radio button for Extended maintenance and choose Change.

4. On the Maintain Profile screen, make the following entries:

Parameter Name Description New value Note

icm/server_port_<*> Standard value for*:

0: http, 1 or 2: https

300or600

Set to 300 or 600(seconds) forTIMEOUT andPROCTIMEOUT

icm/server_port_0 = http

PORT=8000

PROCTIMEOUT=300TIMEOUT=600

Example

icm/server_port_2 = https

PORT=44300

PROCTIMEOUT=300TIMEOUT=600

Example

5. Choose Back.

6. Choose Save.

2.4 Preparing the System User for Content Activation

2.4.1 SAP Software Change Registration (SSCR): DeveloperKey

Use

You must register the user ID that you use for activation as developer on SAP ServiceMarketplace (SAP Software Change Registration (SSCR)). For more information, see SAP Note86161. The SSCR developer key is needed, because the user ID used for SAP Best Practicesactivation creates and changes objects from the customer name range during the SAP Best

Practices activation process. If the SAP Best Practices activation user is not registered as adeveloper, the automated SAP Best Practices activation incurs errors.

Procedure

1. Access the SAP Service Marketplace at http://service.sap.com/sscr .

2. On the SAP Software Change Registration (SSCR) start page, you get the detailed userdocumentation on how to proceed to get the SSCR developer key.

An SSCR developer key is a 20 character combination of digits that is queried whenan SAP ERP user tries to create or change an object from the customer name rangeFOR THE FIRST TIME. The prompting message for the developer key appears once

for each SAP ERP user; if registration is successful, this SAP ERP user is no longer

http://service.sap.com/sscr








prompted to enter a developer key. The SSCR developer key is generated from theinstallation number of the affected installation and the SAP ERP user name.

2.4.2 Unicode Settings

UseBefore each user logs on to the system for the first time, his/her local GUI must be set to use theUnicode code page.

Procedure

1. From the SAP Logon pad, select your system ID. In the context menu, choose Properties.

2. On the System Entry Properties dialog box, choose the Code Page tab.

3. On the Encoding dropdown, select Unicode (UTF-16BE).

4. Choose OK .

2.4.3 Deactivate Info Dialog Box on Dynpro Size CheckUse

This section is only relevant for SAP internal users.

To prevent the dialog box Sizing conflicts may appear from appearing during activation, you can

deactivate the screen size check.

Procedure for GUI Version Below 720

1. Log on with the user in the system.

2. Choose the first button on the right of the standard toolbar (Customize Local Layout) or

choose ALT + F12.

3. Choose the Options menu item.

4. Choose the SAP Internal node.

5. Choose the SAP Internal page.

6. Deselect the Enable Dialog Box for Dynpro Size Check checkbox.

7. Choose OK .

Procedure for GUI Version 720

1. Log on with the user in the system.

2. Choose the first button on the side of the standard toolbar (Customize Local Layout) or

choose ALT + F12.

3. Choose the SAP Internal node.

4. Choose SAP Internal.

5. Deselect the Enable Dialog Box for Screen Size Check checkbox.

6. Choose OK .

2.4.4 Allow GUI Scripting

Use

Perform this activity so that eCATTs GUI scripts can be executed with your GUI.

Procedure for GUI Version Below 7201. Log on to the system.





2. Choose the first button on the right side of the standard toolbar (Customizing of Local Layout )

or choose ALT + F12.

3. Select the Options menu item.

4. Choose the Scripting tab.

5. Select the Enable scripting checkbox.

6. Deselect the checkboxes Notify When a Script Attaches to a Running GUI and Notify When aScript opens a Connection.

7. Choose OK .

Procedure for GUI 720 and above

1. Log on to the system.

2. Choose the first button on the right of the standard toolbar (Customize Local Layout) or

choose ALT + F12.

3. Choose the Options menu item.

4. Choose the Accessibility & Scripting node.

5. Select the Scripting page.

6. Select the Enable scripting checkbox. 7. Deselect the checkboxes Notify When a Script Attaches to a Running GUI and Notify When a

Script Opens a Connection.

8. Choose OK .

Result

You are now able to use your GUI to execute eCATTs GUI scripts in the system.

2.5 Installation of Language- or Country-Specific

ContentSAP CRM supports a wide range of languages. The preconfiguration of SAP Best Practices forSAP CRM is also available in various languages. For detailed and latest information regardinglanguage availability, see the SAP Note specific for your CRM solution package, which is linkedto the overall CRM Best Practices SAP note

SAP Note # Description Component

1698296 SAP Best Practices for CRM 7.02 Solution Packages(http://service.sap.com/sap/support/notes/1698296)

SV-RDS-CRM

When you use the SAP Best Practices Solution Builder, language-specific customizing andmaster data is automatically installed in the CRM system. For manual configuration activities, youmust manually maintain language-specific texts. In this case, the translation is provided in the

respective configuration guides.Typically, configuration content is activated in the master language English and a second locallanguage. You can also activate content in additional languages.

The language-specific customizing also includes basic customizing settings related to country,currency, factory calendar, and the language itself. Additionally, the country has impact on theexample master data (for example, business partner address data) that is created based on thepreconfiguration. That means the language-specific preconfiguration content is alwaysimplicitly related to a country. The following table indicates the relation of some languages tospecific countries as they apply to CRM solution packages. Note however, that this list is not a listof available translations. Always check in the SAP Note for your solution package, whichlanguages are available for your package.

Language Country of Reference

http://service.sap.com/sap/support/notes/1698296

http://service.sap.com/sap/support/notes/1698296





English (EN) United States of America

German (DE) Germany

Spanish (ES) Spain

French (FR) France

Italian (IT) Italy

Japanese (JA) Japan

Portuguese (PT) Portugal

Russian (RU) Russia

Chinese, simplified (ZH) China

Arabic (AR) Saudi Arabia

Apart from above-mentioned language-specific or country-specific configuration and master data,localized (country-specific) versions of the implementation content (preconfiguration) for the SAP

CRM solution package are not available.

If you need to implement the SAP CRM solution package based on above languages butfor other countries, manual adjustments are necessary.





3 Activation of Business Content

Use

In the Rapid Deployment Solutions implementation methodology (step-by-step guide),you have now completed the Start phase and are moving on to phase Deploy: ActivateSolution.

In the Best Practices methodology, the documentation package, you are now moving onto the steps Explore: Activation and Explore: Manual Configuration.

The following section describes the activities that are carried out by the consultant activating SAPBest Practices in the system (“activation user”).

Prerequisites

Before you can start activating the business content, ensure that the following prerequisites aremet:

System LandscapeThe system landscape is up and running according to the Software Requirements document. Youcan find the Software Requirements document in one of the following ways:

For Solution Package Type In …


Best Practices Best Practices documentation package, under Explore:Install SAP Applications.

Activation Language

Make sure that your logon language is always English (and NOT your local language) for allactivation activities.

Business Content for Activation

You have downloaded the solution scope files and the installation data files for your solutionpackage from the SAP Software Download Center (SWDC) to the installation data folder that youhave created in section Creating an Instal lat ion Fold er for Content A ctivation in this guide.

For some packages, you can download additional business content.

For more information, see section Getting the Business Content for Activation in the AdditionalGuide for your specific CRM solution package.

3.1 Automated Activation of Processes

Make sure that you only have one single SAP GUI session running when youactivate SAP Best Practices. If you run several SAP GUI sessions, some automatedinstallation activities may run into errors.

3.1.1 Getting Started and Navigation

Use

After successful installation, the Solution Builder is started by using the transaction code - there isno menu path in the standard SAP menu.

Procedure

1. To start the SAP Solution Builder, use the following navigation option:





Transaction name Solution and Implementation

Transaction code /n/SMB/BBI

We recommend that you add the transaction for the Solution Builder (/SMB/BBI) to

the favorites of your SAP user menu.

2. The Solution Editor screen appears, listing all solutions available in the system.

The solution list is empty the first time you enter the Solution Editor (if no other usershave uploaded or created solutions in the system).

3.1.2 Importing the Solution Scope File

Use

In order to install the SAP Best Practices content using the SAP Solution Builder, upload theSolution Scope File (XML) containing business processes and building blocks into the CRMsystem.

Procedure

1. On the Solution Builder – Solution Editor screen, from the menu, choose Solution Import .

2. On the Select one format to import dialog box, choose the Import XML file button.

3. On the Select the XML file dialog box, browse to the location of your XML file (in the folderyou created during step Creating a Folder for the SAP Best Practices Activation, see above),select it, and choose Open.

4. Set the uploaded solution as the favorite solution: choose Solution Set Favorite.

3.1.3 Maintain Path to Installation Data

Use

The solution scope and the installation data define the solution content that is implemented. Tosimplify the procedure and to avoid confusion with different sets of installation data, we stronglyrecommend to assign the path of the installation data directory to the solution. This is done in theuser settings (because path information is often user-dependent). This is an important step forconsultants who have imported multiple solutions in the solution builder.

Procedure

1. On the Solution Builder – Solution Editor screen, choose Goto User Settings from the

menu. 2. On tab page Solution Specific - Installation Data, select the installation folder where the

installation data files (TXT) have been stored.

a. When using installation files that have been uploaded to the solution before (for moreinformation, see Upload the Installation Data ), deselect checkbox Allow Activation WithExternal Data.

b. When using installation files that have been externally stored on an installation folder,select checkbox Allow Activation With External Data

3. Choose OK to confirm the settings.





The user settings are solution-specific. To maintain the user settings for anothersolution, select this other solution as a Favorite before maintaining the solution-specific user settings.

Result

The path to the installation data directory that is assigned to the solution is now set as defaultentry for the particular solution.

3.1.4 Set Documentation Path for Solution Builder

Use

By setting the path to SAP documentation in SAP Solution Builder, the relevant configurationguides automatically appear during activation. This enables you to process manual installationsteps.

Procedure

1. From the SAP Best Practices Solution Builder menu, choose Goto User Settings.

2. Choose the External Documents tab.

3. Choose the Display <> Change button.

4. Choose the Insert Row button.


Parameter Value

DOCUMENTATION http://help.sap.com/saap/sap_bp/BBLibrary/HTML

6. Choose Save.7. Choose Back .

3.1.5 Upload the Installation Data

Prerequisites

The installation data files have been downloaded to the local directory you created in stepCreating an Instal lat ion Fold er for Content Activatio n .

The Solution Scope file has been uploaded into the CRM system.

For the user who activates this solution, the following user settings must be set under Solution

Builder

Solution Editor

Goto

User

Settings, tabstrip General : Deselect the setting Check consistency with eCATT definitions during Installation data

upload.

Deselect checkbox Enable activation with BC Set API.

Procedure

1. From the SAP Best Practices Solution Builder main menu, choose Upload Installation Data(Ctrl + F5).

2. On the Upload and Download external file data dialog box, browse to the location of yourinstallation data files, select the files, and choose Continue.





3.1.6 Maintain Solution Settings: Select Languages

Use

The configuration content (customizing) of BP CRM is provided in several languages.On solution level, you can define which languages will be activated for language-specificcustomizing.

In the default settings, all languages supported by BP CRM are selected. Reduce the list oflanguages only in the following cases:

Only a subset of languages is required for your solution.

Some languages that are active on solution level have not been installed in your CRMsystem.

Procedure

1. On the Solution Builder – Solution Editor screen select your favorite solution.

2. Choose Change Solution.

3. In the Change Solution dialog box and screen area Released Languages, deselect thoselanguages that are not relevant for your project or that are not installed in the CRM system.

Language EN always has to be active.

Use transaction SMLT to identify the installed system languages.

4. Choose Enter.

Result

All languages that are relevant for the activation of the appropriate solution have been selected.

3.1.7 Scope Your Solution

Use All processes of an uploaded solution represent the maximum scope that can be implemented.Depending on the individual requirements, a smaller solution scope may be sufficient. Thescoping tool provides an easy to use graphical user interface that provides additional detailsabout each process, and an easy select/deselect-function to add or remove processes in ascope.

Prerequisites

You have imported the solution scope file (XML) successfully.

Procedure

1. From view Solution Builder – Solution Editor , choose Solution →Create →.Customer Solution

(Ctrl+F9).The scope matrix for your CRM solution appears.

2. Initially all processes are selected. Click on a process And choose Details to get moreinformation about a process.

3. Deselect the process to remove it from the scope.

4. After completion of scoping, choose Save Data to save your result.

5. Enter a Solution ID and a Description for your individual scope.

6. Choose Back.

Result

The custom solution with the selected scope of processes is created.

If you have uploaded the installation data before the scoping process (as described





in this documentation), the installation data is copied automatically to the customsolution. In this case, you do not need to perform an upload of installation data for thecustom solution.

To continue the following operations regarding your custom solution, ensure that your

solution has been defined as Favorite solution (On the view Solution Builder – Solution Editor, choose the Favorite button).

3.1.8 Personalize the Solution

Use

This step is mandatory to check the interfaces and integration points in the back end client. It isessential for the activation of the package that all personalization steps are executed accurately.

Wrong maintenance of the personalization and integration data may lead to issues duringthe activation and the usage of the package.

Procedure

1. Choose Personalization (Ctrl+F8) On the Generic Personalization Composer screen, you can see all activities that are can be

personalized. These personalization steps are mandatory to handle the back end clientintegration.

2. Navigate to all activities and double-click the activity to maintain the required data.

A document is attached for each step. These documents describe which data has to bemaintained and how to determine the required values in the back end client. To open thedocument, choose Display documentation.

Make any personalized entries and set the status to document the progress of your

personalization activities.3. Save your entries.

Result

You have personalized the solution.

You can get the list of default values and their personalized values. To generate a list containingdefault and personalized values refer to SAP Note 1421667.

3.1.9 Maintaining System Landscape Information for SolutionBuilder

UseWhen you activate integrated processes via the Solution Builder , access to different systems isrequired (e.g. to ERP or BW). Therefore, you must maintain RFC connections and assign them tothe project. You make these settings in the Solution Builder System Landscape Maintenancedialog.

This step is only necessary if you activate your solution using SAP SolutionBuilder . If you configure your system manually, skip this step.

You also need to maintain system landscape information if you implement CRMas standalone deployment. In that case however leave the values for the fieldsSAP_DEFAULT, ECC, CRM and REP blank.





3.1.9.1 Creating a Solution Builder RFC Destination for anintegrated SAP System

Use

In this activity, you set up RFC connections in Solution Builder to activate your solution in

integrated systems, for example CRM with SAP ERP, or with SAP BW.

Procedure

1. Access the activity using one of the following navigation options:

Transaction code SM59

SAP CRM IMG menu Customer Relationship Management CRM Middleware and

Related Components Communication Setup Define RFCDestinations

2. Choose Create (F8).

3. Enter the following data:

Field Entry

RFC Destination <system name>CLNT<client>_A (the postfix _A is mandatory),

for example: RT1CLNT100_A

Connection Type 3 (Connection to ABAP System)

Description Include the solution name, for example:

OLTP ERP System for Solution Builder Activation

4. Choose Enter.

Technical settings

Load Balancing No

Target host <Target host ERP or BW system>, e. g. pwdf0421

System number <System number of ERP or BW system>

Logon/Security

Trusted Relationship No

Status of SecureProtocol

Inactive

Language <blank>

Client <ERP or BW client>User <Installation user created according to this Quick Guide>

Password <Enter the password>

Unicode

Communication Typewith target system

Set the Unicode flag if the Unicode Test has been executedsuccessfully. You can perform this test by choosing UnicodeTest in the menu area. The RFC destination has to be saved

first before the test can be performed. An information messageappears (Example of a message: “Target is a Unicode system(character size 2”)).

5. Save your RFC destination.





Result

You have successfully created the RFC connection.

You can now test your newly created RFC connection using the Connection Test button. You can

also test the RFC connection using the menu path Utilities Test. Then you can choose Connection Test or Authorization Test .

The connection test performs only a technical test (Host, IP Address) of the target system.

The authorization test performs an invisible logon to the target system using the maintaineduser and password of the RFC destination.

3.1.9.2 Assigning RFC Destinations to Target Systems

Use

The RFC destinations created in the preceding step have to be assigned to the target systems inthe System Landscape Maintenance.

Procedure1. From view Solution Builder – Solution Editor, choose Goto → System Landscape

Maintenance

2. On the System Landscape Maintenance dialog box, select the Solution ID of the solution tobe activated.

3. Mark the row with target system ECC if an ERP system is required for the solution.

4. Choose Edit Entry .Enter the RFC destination for the ERP system created in the preceding step.

5. Repeat this RFC destination assignment for target system BW if a BW system is required forthe solution.No RFC destinations have to be assigned to the remaining target systems.

6. Choose OK .

Result

You have maintained the System Landscape information required to activate configurationcontent remotely.

3.1.10 Starting Activation

Prerequisites

Ensure that your solution is set as a favorite solution.

If several people are involved in the implementation, make sure that you take activation

ownership (choose Change Activation Owner ). Otherwise, the solution is locked.

Procedure

1. From the Solution Builder – Solution Editor view, choose Goto Implementation Assistant .

2. Select the top node of the solution, and choose Activate.

3. On the Activate solution dialog box, make the following entries:

Field name User action andvalues

Comments

TargetLanguage

EN You can also use another target language (forexample, DE). As a result, selected languageindependent fields are filled with target languagedescription texts instead of English texts.







X Test Configuration <YOUR TEST CONFIGURATION>

3. Choose Execute.

4. On the Start Options – Test Configuration <YOUR TEST CONFIGURATION >screen on the Variants tab make sure that you have mapped the correct path tothe location of your external variant files.

5. Choose the UI Control tab. In the TCD screen area, make the following entries:

Start Mode for Command TCD Process in Foreground, Synchronous Local

6. Choose Execute.

Result

The activation starts. Depending on the number of manual activities and possible errors duringimplementation, the activation may stop occasionally, requiring for manual input ortroubleshooting.

If issues occur during activation always check section Processin g General Errors

dur ing Autom ated Insta l lat ion .

3.1.11 Manual Interaction and Error Handling During Activation

Use

The installation procedures of some building blocks contain manual installation steps and / orrequire manual confirmation. This section describes how to handle manual steps in the SAP BestPractices Solution Builder.

Procedure

If the SAP Best Practices Solution Builder stops because of a manual activity proceed as follows:

When you have set the user parameters in the Solution Builder, the respective configurationguide is automatically opened at the activation start of each building block. Keep this documentopen until you have finished all relevant activities for this building block. Confirm the informationscreen.

If the respective configuration guide does not open automatically, access the BuildingBlock Library via the Step-by-Step Guide Deploy Activate Solution Manual Activation and Configuration Content Library <CRM Standalone / ERP Integrated>.

Navigate to the corresponding Building Block and open the configuration guide.

1. Use Ctrl+C to copy the task description to the clipboard. Use the Search function (Ctrl+F) to

find the corresponding step in the configuration guide.2. In the Solution Builder, choose the proposed navigation option, for example, Navigate to IMG,

and execute the configuration activity manually by following the instruction of the relatedsection in the Configuration Guide.

3. Choose Back (from the IMG activity or the transaction).

4. Choose Proceed.

5. In the Implementation Assistant – Scenario Edit View choose Confirm Manual Step.

6. Enter a reason (optional) and choose Enter .

7. Proceed with the activation.

Result

You have successfully processed a manual activity.





3.1.12 Processing General Errors during AutomatedInstallation

Use

When an activation of an automated task runs into errors, the activation stops at the point of the

error. No further implementation can be done until the error is resolved.

Before you start with detailed error analyzing and working through the errorprocessing as described below, proceed as follows:

Activate your solution or the respective process in the Solution Builderimplementation assistant again. It may be that the error does not reappear. In thiscase, no correctional activities are needed and the installation is proceeding.

Procedure

1. On the Implementation Assistant – Solution View screen, select a task that has a red light inthe Current status column.

2. Expand the task and choose the log that is assigned to this task.Detailed information about the error is displayed in the Error List pane.

3. In the Error List pane, choose Display Detailed Log . The detailed log information about an

eCATT or BC set activation is displayed.

4. In this log information, check entries with a red light to identify the reason for the error.

a. If the error can be solved based on the log information, you can run the eCATTor BC set again.

If the activation fails because of locked objects, make sure that no objectsare locked by any users. Then try to activate the activity again.

5. If the log information is not sufficient to solve the problem proceed as follows:

Execute the task manually: use the description of the related section in theconfiguration guide for executing the task

Open a customer message for this problem specifying the component.

Do NOT delete Solution Builder processes after they have been activated. If youdelete processes, the activation history and the respective logs are lost and it is notpossible to find possible error reasons.

In such cases NO SAP SUPPORT CAN BE PROVIDED.

6. When you have solved the problem (either executed the task manually or a solution has beenprovided via customer message), choose the Change button that is displayed in the OldStatus column to the right of the task.

Do NOT proceed with installation if the problem has not been solved. If you continuewithout solving the problem, severe errors might result in the subsequent installationsteps that cause incalculable efforts to fix.

In such cases NO SAP SUPPORT CAN BE PROVIDED.

7. Choose the Change button that is displayed in the Old Status column to the right of the task.

8. On the Confirmation dialog box, choose OK to change the status to Successful manually.

9. On the Information dialog box, enter a reason for changing the status.

10. Choose Continue.





The information is saved in a log. To view details for a changed task, choose the redlight in the Original Status column for that task. A dialog box displays the user who

performed the change, the date of the change, and the reason for the change.Choose Continue to close the dialog box.

11. Choose Activate to continue with the installation.

3.1.13 Deployment of Multiple CRM Solution Packages in OneClient

UseIf you would like to activate scope items from different CRM solution packages in one client,proceed as follows.

Procedure

1. Make your scope decision.

Analyze which scope item(s) from which CRM solution package you would like toimplement. Note that you can only ‘mix’ scope items which have been released on thesame software release, like scope items of the solution packages mentioned in SAP Note1698296 – SAP Best Practices for CRM 7.02.

If the required scope items are distributed across multiple solution packages note downthe title of all relevant solution scope files, as documented in the related quick guides(e.g. SOL_RDS_CRM_CRM702V4_ERP_BP_CRM702Vy.ZIP andSOL_ RDS_CRM_SERV_CRM702V1_ERP_BP_CRM702Vy.ZIP).

2. Download all related solution scope files and installation files.

Download from the SAP Service Marketplace: http://service.sap.com/bp-implcontent

3. Upload the solution scope files to the SAP Solution Builder.

Open the SAP Solution Builder with transaction /n /smb /bb i and from the menu chooseSolution Import Solution (ZIP). Import all relevant solutions into the SAP SolutionBuilder.

4. Perform all required preparation steps mentioned in this Quick Guide for each solutionscope, for example:

Upload installation data files (note: although it’s the same file set for all solution packagesmentioned above, you need to re-do this upload into each solution scope).

Maintain System Landscape Maintenance settings in the SAP Solution Builder.

Maintain the user settings for the activation user.

Personalize the solution.

It is essential, that the personalization settings for all solutions are maintainedequally.

5. Activate the solutions.

Activate the solutions one after the other. Building blocks which are used by variousscope items only need to be activated once – the SAP Solution Builder will recognize if abuilding block has already been activated with another solution.

Note: You don´t need to activate all scope items of a solution if not required.

For additional details related to individual steps refer to the Quick Guides being relevantfor each solution package.

http://service.sap.com/bp-implcontent








Result

You have successfully implemented scope items from muliple CRM solution packages in oneclient.

3.2 Manual ImplementationUse

SAP Best Practices for CRM can also be implemented manually by following the configurationguides according to the sequence of the SAP Best Practices Prerequisites Matrix . ThePrerequisites Matrix gives an overview of the configuration building blocks, and relatedconfiguration guides, required for each business process, and the correct sequence forimplementing the building blocks. There is a specific Prerequisites Matrix for CRM deploymentwith integration to SAP ERP, and one for CRM standalone deployment.

You can find the Prerequisites Matrix for your solution package

Solution Package Type Documentation in:

Rapid Deployment Solution Step-by-Step Guide, under Deploy: Activate Solution → Manual Activation and Configuration → Content Library <CRMStandalone / ERP Integrated> → Prerequisites Matrix

SAP Best Practices for BAiO BP Documentation Package, under Explore: ManualConfiguration → Prerequisites Matrix

For more information on the manual activation of eCATTs and BC Sets, see the document SAP

Best Practices Tools, in the BP documentation package under Technical Information Concepts

Best Practices Tools.

Prerequisites

Before you can start activating the business processes manually, the following activities must be

completed: The system landscape has been set up according to the Software Requirements

document in the[RDS] Step-by-step guide, under Start: Confirm Installation.

[BP] BP documentation package, under Explore: Install SAP Applications.

The current SAP Best Practices for CRM content add-on BP-CRM

702V<versionnumber> has been installed. This is necessary because the content add-on contains the CRM-package-specific authorization roles that you need to run thebusiness processes.

The general system settings have been made. For more information, see sectionGeneral Client Sett ings in this guide.

An activation user has been created and set up for activation. For more information, seesection Prepar ing the System User for Content Act ivat ion in this guide.




4 Security Aspects

Use

This section provides an overview of the security-relevant information that applies to the

deliverables of this solution package.

The following topics are relevant for the security of your solution:

User Administration

RFC Destinations

Roles Management

As these topics are specific for each CRM solution package, refer to section Security Aspects inthe Additional Guide for your solution package.

For an overview of the security-relevant information that applies to SAP CRM in general, see theSecurity Guid e for SAP enhancement package 2 for SAP CRM 7.0 .

To access the latest version of the security guide, log on to SAP Service Marketplace(www.service.sap.com/crm-inst). Go to section SAP enhancement package 2 for SAP CRM 7.0 → Operate → Security.

4.1 User Administration and Authentication

Use

The following user is required for all CRM-702-related solution packages:

Purpose User ID UserType

CreatedIn

InitialPassword

AuthorizationProfile

Comment

Activation

User

User ID is

defined byyour systemadministrator

Dialog

(Type A)

Creation

describedin thisQuickGuide

Password is

defined byyour systemadministrator

SAP_ALL, or

defined by yoursystemadministrator(see recommen-dation below)

You can check the users in transaction SU01.

For an efficient activation of the SAP Best Practices for CRM content, we recommend togrant SAP_ALL authorization temporarily. This authorization profile will provide full

authorization rights. If this is not an option for your project, restrict the rights of theactivation user according to your company’s security policy.

After the activation is completed, we recommend that you remove the authorizations youhave given to the users who have performed the implementation steps, for securityreasons.

For more information on users and authentication, see section User Administration and Authentication in the Additional Guide for your solution package.

http://www.service.sap.com/crm-inst



http://help.sap.com/saphelp_nw04s/helpdata/en/99/acdc3ed98f7650e10000000a114084/content.htm

http://help.sap.com/saphelp_nw04s/helpdata/en/99/acdc3ed98f7650e10000000a114084/content.htm
