Bp Crm Crm703 Quick Guide en Xx

8/10/2019 Bp Crm Crm703 Quick Guide en Xx

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



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

© SAP AG Page 2 of 32

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 theexpress 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 aretrademarks 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 additionaltrademark information and notices.

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 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 companyproducts 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 businessoutlined in this document or any related presentation, or to develop or release any functionality mentionedtherein. This document, or any related presentation, and SAP AG’s or its affiliated companies’ strategy andpossible future developments, products, and/or platform directions and functionality are all subject to changeand may be changed by SAP AG or its affiliated companies at any time for any reason without notice. Theinformation 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 causeactual results to differ materially from expectations. Readers are cautioned not to place undue reliance onthese forward-looking statements, which speak only as of their dates, and they should not be relied upon inmaking purchasing decisions.

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







Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Typographic Conventions

Type Style DescriptionExample text Words or characters that appear on the screen. These include field

names, 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, for example, SELECT and INCLUDE.

Exampl e t ext 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 ...................................................................................................................... 62.3 General Client Settings ................................................................................................... 7

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

2.3.2 Further Client Settings ........................................................................................ 7

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

2.3.4 Creating a User for Activation of SAP Best Practices Content ............................. 8

2.3.5 Handling of Authorizations for Activation User ..................................................... 9

2.3.5.1 Unlimited Authorization Assignment .................................................................. 10

2.3.5.2 Individual Authorization Activation Role ............................................................. 10

2.3.5.3 SAP Best Practices Activation Authorization Role ............................................. 10

2.3.6 Creating Transport Requests for Activation ....................................................... 12

2.3.7 Deselecting Activation Links in BC Sets ............................................................ 12

2.3.8 Setting the Maximum Work Process Run Time.................................................. 13

2.3.9 SAP Scripting ................................................................................................... 13

2.3.10 Set Default Timeout for HTTP and HTTPS Services.......................................... 14

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

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

2.4.2 Unicode Settings .............................................................................................. 15

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

2.4.4 Allow GUI Scripting ........................................................................................... 16

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

3 Activation of Business Content ........................................................................................... 18

3.1 Automated Activation of Processes ............................................................................... 18

3.1.1 Getting Started and Navigation ......................................................................... 18

3.1.2 Import the Solution Scope File .......................................................................... 19

3.1.3 Maintain Path to Installation Data ...................................................................... 19

3.1.4 Set Documentation Path for SAP Solution Builder ............................................. 20

3.1.5 Upload the Installation Data .............................................................................. 20

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

3.1.7 Scope Your Solution ......................................................................................... 21

3.1.8 Personalize the Solution ................................................................................... 22

3.1.9 Maintaining System Landscape Information for Solution Builder ........................ 22

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 ................................................ 24

3.1.10 Starting Activation ............................................................................................. 24

3.1.11 Manual Interaction During Activation ................................................................. 26

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

3.1.13 Deployment of Multiple CRM Solution Packages in One Client .......................... 28

3.2 Manual Implementation ................................................................................................. 30

4 Security Aspects ................................................................................................................ 31

4.1 User Administration and Authentication ......................................................................... 31

4.2 Roles Management ....................................................................................................... 31





Quick Guide to Implementing the SAP BestPractices for Enhancement Package 3 for Customer Relationship Management 7.0

1 PurposeThis Quick Guide provides step by step information you need to implement the SAP BestPractices for Enhancement Package 3 for CRM 7.0 (SAP CRM 7.03).

This general guide is complemented by package-specific, additional guides. Package-specificguides exist for

the SAP CRM rapid-deployment solution V6.703 (see SAP Note 1958660)

the SAP CRM Service Management rapid-deployment solution V2.703 (see SAP Note1945332).

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, thatmeans, no existing business processes in the customer’s system landscape have to beconsidered and integrated. However SAP Best Practices for CRM can also be an option for existing SAP CRM customers. Such deployments require very detailed knowledge about thealready implemented business processes and the business processes to be implemented bythe respective package. Additional customizing (for example, as suggested by SAP BestPractices for CRM) needs to be applied carefully then and potentially arising ‘customizing

conflicts’ need to be resolved individually. Implementation of SAP Best Practices basedconfiguration needs to happen manually in that case, that means, based on configurationguides and not via SAP Best Practices Solution Builder.

This document does not provide a general overview and explanation of SAP Best Practices. For more information about the SAP 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 -> LearningMap for SAP Business All-in-One.

http://service.sap.com/solutionpackages


http://service.sap.com/bestpractices








2 System Setup & PreparationThe 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 regarding Software and System Landscape see the

Software Requirements document for your solution package. You can find the SoftwareRequirements document in the respective SAP Best Practices documentation package.

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 are developed and tested in a systemlandscape with specific release and support package stack (SPS) level. SAP recommends tomeet this SPS as minimal 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 therelated SAP Best Practices documentation package.

If you need a higher SPS level in your system, for example, because of additional functionality,ideally first import and activate the SAP Best Practices package on the mentioned SPS level,then update your system to the target SPS level.If SAP Best Practices content is activated directly on a higher SPS level (for example, if therecommended SPS level is not available anymore), some automated activation steps might fail,however still can be processed manually following the related configuration guide. Also note thatsome of the SAP notes which are considered relevant for the scope of the solution package mightbe obsolete due to a higher SPS level, and additional SAP notes could exist.

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:

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

2.2 SAP NotesBefore you start the activation of the related SAP Best Practices scope, always check the latestversion of the SAP Note for SAP Best Practices for CRM 703 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 for SAP Best Practices Package ABAP Add-ons. This SAP Note also refers to other notes. Always

check the referenced notes and follow the instructions.

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

SAP Note # Description Component

http://service.sap.com/swdc

http://service.sap.com/swdc





SAP Note # Description Component

1958683 SAP Best Practices for CRM 7.03 Solution Packages

Attached to this SAP Note is the asset ‘SAP NotesOverview Li st’ (xls). Make sure to implement

especially the notes relevant for your planned solutionscope and marked as ‘mandatory’. Also note that someof the SAP Notes are only relevant in the context of SAP CRM powered by SAP HANA. Filter the listaccordingly.

SV-RDS-CRMSV-SMB-AIO-BP

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

BC-UPG-ADDON

2043344 SAP Best Practices Add-on Installation;DVD BP BAIO2014-Q4'

Attached to this add-on-specific note you can find the

corrections for the add-on. Always also apply the latestcorrection transport for the corresponding add-on!

Note that this SAP Note also refers to other SAPNotes. Make sure to always check the referenced SAPNotes, too and follow the instructions.

BC-UPG-ADDON

Apply all SAP Notes to the system via the SAP Note Assistant (transaction SNOTE). All SAP

notes 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 or manual content activation.

To check and maintain the settings of clients in your system, use transaction code SCC4.

2.3.1 Client Roles

The 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 automaticactivation of SAP Best Practices content using the SAP Best Practices Solution Builder is notpossible.

2.3.2 Further Client Sett ings

Changes and Transport for Client-specific Objects

To activate SAP Best Practices packages, an automatic recording of changes is required. Toensure that all the changes are automatically recorded in a change request, in Changes andTransport for Client-specific Objects group box, choose Automatic recording of Changes.





Cross-client Object Changes

During the activation of an SAP Best Practices package, cross-client objects are created. Cross-client functions include all cross-client customizing objects (for example, factory calendar) and allobjects of the SAP Repository (reports, module pools, screens, data dictionary, and so on).

To enable changes to cross-client objects, in the Cross-Client Object Changes group box, choose

Changes to Repository and Cross-client Customizing allowed.

In case you have not allowed changes to Repository and cross-client Customizing, youwill be asked during activation of the package if these settings should be doneautomatically by the SAP Solution Builder. If you reject the required changes, theactivation cannot be executed automatically.

2.3.3 Creating an Installation Folder for Content Act ivation

Use

The scoping, personalization, and installation phase of the SAP Solution Builder require solutionscope and installation data files in a local directory.

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

Procedure

1. Create an installation data folder on a server that can be accessed from within the SAPsystem in which you want to install the SAP solution package. Ensure that the folder fulfillsthe following criteria:

The persons who installs the SAP solution package must have the necessary user rightsto access this folder.

The length of the directory path must not exceed 128 characters.

The folder must not be located on the root directory of your local drive (for example, C:\).

2. Extract the files from the ZIP files you will be asked to download below (solution scope file,variant files) into the folder you created in step 1. You should have one solution scope file(*.xml) and many variant files (*.txt).

Result

You can use this installation folder to store all downloaded data files for solution scope,installation data and import the files into SAP Solution Builder.If your solution package also provides sample content (for example, survey templates), you candownload this sample content here, too.

2.3.4 Creating a User for Activation of SAP Best Pract icesContent

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.

For the activation of SAP Best Practices content, specific SAP system authorizations are requiredand have to be assigned to the activation user. For details see section Handling of Authorizations

for Activation User of this guide.





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 and maintain 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 and maintain the following entries:


Password <initial password>User type Dialog

7. Choose the Defaults tab and maintain the following entries:


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 that contains the necessary authorizationprofile. For details see section Handling of Authorizations for Activation User of this guide.

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 Handling of Authorizations for Activation User The activation of SAP Best Practices content in a prototype or development system requirescomprehensive system authorizations for the activation user because the configuration scopeconsists of:

basis system administration (for example, system parameter settings)

technical configuration (for example, RFC destinations)

user and role management (technical and sample users, end-user roles)

business configuration (organizational data, master data and process customizing)





Depending on the authorization policy of your company you can choose between the followingappproaches to provide sufficient authorizations to the activation user:

Unlimited authorization assignment

Individual authorization role

SAP Best Practices activation authorization role

2.3.5.1 Unlimited Authorizat ion Assignment

Use

The composite profile SAP_ALL contains all SAP authorizations, meaning that a user with this

profile can perform all tasks in the SAP system.

Therefore it is in general not recommended to assign this authorization profile to any of your users.

Using the profile SAP_ALL is the easiest way to avoid any authorization issues during activationin case your authorization policy does not require any authorization limitations in the target SAPsystem landscape of the SAP Best Practices content.

2.3.5.2 Individual Authorization Activation Role

Use

You may already have established an elaborated authorization concept including authorizationroles for the users running customizing activities in the SAP system based on experiences fromprevious SAP implementation projects.

Activation of SAP Best Practices content typically requires additional SAP product-specificauthorizations not covered by these individual authorization roles.

Procedure

Enhance the authorization scope of the existing authorization roles by

Running an authorization trace during activation and add missing authorizations

Comparing the existing roles with the SAP Best Practices activation authorization roles(see next section) and adding not already covered authorizations.

2.3.5.3 SAP Best Practices Activation Authorization Role

Use

In case the security policy of the implementation project does not allow the grant of SAP_ALLauthorization to the activation user and no dedicated authorization concept is establishedauthorization roles have to be developed.

To avoid additional effort and time delay in the implementaton project specific authorization(PFCG) roles, so called activation roles, are provided as part of the solution package delivery.

These roles can be applied to activate the solution packages

SAP CRM rapid-deployment solution V6.703

SAP CRM Service Management rapid-deployment solution V2.703

The roles comprise all authorizations required to

manually execute the configuration activities of the configuration guides

automatically execute the configuration activities using the SAP Solution Builder

execute all system related activities mentioned in the Quick Guide and Additional Guide.

The role menu is structured according to the Building Block structure:

A folder General containing general transactions mentioned in this Quick Guide andrequired for all Building Blocks









3. Choose Change (Shift + F1).

4. In the Activation section, select the radio button for parameter Do Not Create.

5. Confirm the information message and save your settings.

2.3.8 Setting the Maximum Work Process Run TimeUse

Dynamic switchable profile parameters (indicated by a flag in the check box of the parameter)need to be checked before activation. Therefore, check and adapt the following profileparameters.

For the activation of the SAP Best Practices for CRM, the parameter value for maximum workprocess run time must be increased because there are some processes that must be performedin dialog and that last for more than 10 minutes.

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 and values Note

Param. Name Profile parameter name rdisp/max_wprun_time

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.

Parameter Name Description Newvalue

Note

rdisp/max_wprun_time Max work process runtime 3600 Check and adapt thevalue if the value is<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.9 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 the

front-end must be set to true.





Procedure

Run the following activity:


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

Choose Display.

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

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

Field name Description User action and values Note

New Value New Value for user scripting

TRUE Enable SAP Scripting

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.10 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 even 600 seconds. The default is 60 seconds.

Procedure

1. Run the following activity:


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

300or 600

Set to 300 or 600(seconds) for TIMEOUT andPROCTIMEOUT

icm/server_port_0 = httpPORT=8000

PROCTIMEOUT=300TIMEOUT=600

Example

icm/server_port_2 = https

PORT=44300

PROCTIMEOUT=300

TIMEOUT=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): Developer Key

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 BestPractices 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 user

documentation 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 oncefor each SAP ERP user; if registration is successful, this SAP ERP user is no longer 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

Use

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

If you access, for example, a customer system via OSS connection, you can handle thisactivity as optional.

Procedure

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

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

3. On the Encoding dropdown, select a value for Unicode systems (for example Unicode (UTF-16BE)).

4. Choose OK.

http://service.sap.com/sscr







2.4.3 Deactivate Info Dialog Box on Dynpro Size Check

Use

This section is only relevant for SAP internal users.

To prevent the dialog box Sizing conflicts may appear from appearing during activation, you candeactivate 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 720

1. 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 aScript 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-Specif icContent

SAP CRM supports a wide range of languages. The preconfiguration of SAP Best Practices for CRM is also available in various languages. For detailed and latest information regardinglanguage availability, see the SAP note specific for the CRM solution package you intend toimplement:

SAP Note 1958660: SAP CRM rapid-deployment solution V6.703

SAP Note 1945332: SAP CRM Service Management rapid-deployment solution V2.703

When you use the SAP Solution Builder, language-specific customizing and master data isautomatically installed in the CRM system. However for manual configuration activities, you mustmanually maintain language-specific texts. In this case, the translation is provided in therespective sections of the 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-specifi c preconfiguration content is alwaysimplic itly related to a country .The following table indicates the relation of languages to specific countries as they apply to SAPCRM solution packages. Note however, that this list is not a list of available translations. Alwayscheck in the SAP Note for your solution package, which languages are currently available for your package.

Language Country of Reference

English (EN) United States of America (US)

German (DE) Germany (DE)

Spanish (ES) Spain (ES)

French (FR) France (FR)

Japanese (JA) Japan (JP)

Portuguese (PT) Portugal (PT)

Russian (RU) Russia (RU)

Chinese, simplified (ZH) China (CN)

Apart from above-mentioned language-specific or country-specific configuration and master data,separate 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

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:

(1) System Landscape

The system landscape is up and running according to the respective Software Requirementsdocument. You can find the Software Requirements document in the SAP Best Practicesdocumentation package for the related solution package.

(2) Activation Language

Make sure that your logon language is always English (and NOT your local language) for all

activation activities.

(3) 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 Installation Folder for Content Activation in this guide.

For some packages, you can download additional business content, such as sample files.

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 due to locked data.

3.1.1 Gett ing Started and Navigation

Use

After successful installation, the SAP Solution Builder is started by using the below transactioncode - there is no menu path in the standard SAP menu.

Procedure1. 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 SAP 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 Import the Solution Scope FileUse

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 folder you created during step Creating an Installation Folder for Content Activation, see above),

select it, and choose Open.4. If not done automatically, 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 for

consultants who have imported multiple solutions into the SAP Solution Builder.

Procedure

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

2. On tab page Solution Specific, in field Installation Data, select the installation folder where theinstallation 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 another solution, select this other solution as a Favorite solution before maintaining thesolution-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 SAP Solution Builder

Use

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

Prerequisites

SAP note 1584363 (Solution Builder WEBGUI Access to Offering)

Procedure

1. From the SAP 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.

5. Make the following entries:

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 Installation Folder for Content Activation.

The solution scope file has been uploaded into the SAP Solution Builder of your SAP CRMsystem.

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

Builder - Solution Editor , menu Goto User Settings, tabstrip General:

Select Enable activation with BC Set API.

Procedure

1. From the SAP 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 your

installation data files, select the files, and choose Continue.

3.1.6 Maintain Solut ion Settings: Select Languages

Use

The configuration content (customizing) of SAP Best Practices for 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 SAP Best Practices for CRM areselected. Reduce the list of languages 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 SAP 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 SAP 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 Solut ion

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 (Scoping).The scope matrix for your CRM solution appears.

2. Initially all processes are selected.Click on a process and choose Details to get more information 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 describedin 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 Solut ion

Use

This step is mandatory to check the interfaces and integration points in the SAP ERP back endclient. It is essential for the activation of the package that all personalization steps are executedaccurately.

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 bepersonalized. These personalization steps are mandatory to handle the SAP ERP back endclient integration.

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.


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

Use

When you activate integrated processes via the SAP Solution Builder, access to different systemsis required (for example, to SAP ERP). Therefore, you need to maintain RFC connections andassign them to the project. You make these settings in the SAP Solution Builder SystemLandscape Maintenance dialog.

This step is only necessary if you activate your solution using SAP Solution

Builder . If you configure your system manually, skip this step. You also need to maintain system landscape information if you implement SAP

CRM as standalone deployment. In that case however leave the values for thefields SAP_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 SAP Solution Builder to activate your solution inintegrated systems, for example, SAP CRM with SAP ERP.





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 of system>, e. g., of SAP ERP system

System number <System number> e.g., of SAP ERP system

Logon/Security

Trusted Relationship No

Status of SecureProtocol

Inactive

Language <blank>

Client <System client>, e. g., of SAP ERP system

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 Unicode

Test in the menu area. The RFC destination has to be savedfirst 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 chooseConnection 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

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

Procedure

1. From view Solution Builder – Solution Editor, choose Goto System LandscapeMaintenance

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

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

4. Choose Edit Entry.

Enter the RFC destination for the SAP ERP system created in the preceding step.5. Repeat this RFC destination assignment for any target system, for example, if a SAP BW

system is required for the solution.(RFC destinations don’t need to be assigned to all other target systems defined)

6. Choose OK.

Result

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

3.1.10 Starting Act ivation

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 (for example, DE). As a result, selected languageindependent fields are filled with target languagedescription texts instead of English texts.

SupplementalData

<location of folder with installationdata>

For example,Z:\crm\files

This folder has been created in step Creating anInstallation Folder fo r Content Activation andassigned in step Maintain Path to InstallationData.





Field name User action andvalues

Comments

Workbench <workbenchrequest number>

Select an existing workbench request number, or select the Create checkbox to let the SAP SolutionBuilder create one automatically.

Customizing <customizingrequest number>

Select an existing customizing request number, or select the Create checkbox to let the SAP SolutionBuilder create one automatically.

Skip thisscreen

Select If selected, the system does not display the Activate solution dialog box when you resumeactivation after an error or manual activity.

If deselected, the Activate solution dialog box willbe displayed every time when you resumeactivation.

With demodata

Select If selected, system executes activation steps thatcreate demo data.

If deselected, these steps are not executed butskipped.

Act ivation without demo data

If you have activated the SAP Best Practices package without demo data, you will notbe able to test the business processes right away after activation is completed. Theprocess testing requires demo data and related configuration settings.

To test the business processes with customer demo data, create your own demodata. Proceed as follows:

Select the business process you want to test.

Check the row in the Prerequisites Matrix file for this process to determine therequired prerequisite building blocks.

Go to the Solution Builder Building Block Builder – Scenario Edit View.

Look at the steps that have the check box activated in column De (Demo) for allbuilding blocks that belong to the process.

Refer to the corresponding Configuration Guide and create the requiredconfiguration and master data activities manually.

4. Choose Continue.

Running an eCATT in Foreground Mode

Some activation activities require to run an eCATT in foreground mode. The followingdescription provides an instruction on how to run the eCATT in the foreground mode.

1. Enter transaction SECATT.

2. On the Extended Computer Aided Test Tool: Initial Screen, make the following

entries:

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 to

the 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 during

implementation, the activation may stop occasionally, requiring manual input or troubleshooting.

If issues occur during activation always check section Processing General Errorsduring Automated Installation .

3.1.11 Manual Interaction During Activation

Use

The installation procedures of some building blocks contain manual installation steps and / or require manual confirmation. This section describes how to handle manual steps in the SAP

Solution Builder.

Procedure

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

When having set the user settings in the SAP Solution Builder, the HTML page of the respectivebuilding block is automatically opened from SAP Help Portal at the activation start of eachbuilding block. Here you find the link to the according configuration guide. Open the configurationguide and keep this document open until you have finished all relevant activities for this buildingblock.

1. Confirm the information screen.

If the respective HTML page does not open automatically, access the Building BlockLibrary via the SAP Best Practices documentation package for the related solutionpackage. Navigate to the corresponding building block and open the configuration guide.

2. Use Ctrl+C to copy the task description to the clipboard. Use the Search function (Ctrl+F) tofind the corresponding step in the configuration guide.

3. In the SAP Solution Builder, choose the proposed navigation option, for example, Navigate toIMG, and execute the configuration activity manually by following the instruction of the relatedsection in the configuration guide.

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

5. Choose Proceed.

6. In the Implementation Assistant – Solution View screen choose Confirm Manual Step.

7. Enter a reason (optional) and choose Enter .8. 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 theerror. No further implementation can be done until the error is resolved.





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

Activate your solution or the respective process in the SAP Solution Builder implementation assistant again. It may be that the error does not reappear. In this

case, 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 aneCATT 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.For example, if the activation fails because of locked objects, make sure that noobjects are locked by any users. Then try to activate the activity again.

b. If the eCATT log reports error messages like Entry already exists or Entryalready created check if the entry is configured according to the respectiveconfiguration guide. If the settings are correct proceed with the installation.

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 continue

without 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 red

light 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 Solut ion Packages in OneClient

UseIf you would like to activate scope items from different CRM solution packages in one client, for example, ‘mix’ scope items from CRM RDS and CRM Service Management RDS, proceed asfollows.

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 the

same software release, that is scope items of the solution packages mentioned in SAPNote 1958683 – SAP Best Practices for CRM 7.03.

If the required scope items are distributed across multiple solution packages note downthe file name of all relevant solution scope files, as documented in the related, package-specific quick guides.

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/bbi and from the menu chooseSolution Import Solution (ZIP). Import all relevant solutions into the SAP Solution

Builder.4. Perform all required preparation steps mentioned in this Quick Guide for each solut ion

scope, for example:

Upload installation data files

Although it’s the same file set for all solution packages mentioned above, youneed 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. You don´t need toactivate all scope items of a solution if not required.

For additional details related to individual steps refer to the Quick Guides being relevant

for each solution package.

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

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





Result

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





3.2 Manual Implementation

Use

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 for implementing the building blocks. There is a specific Prerequisites Matrix for deployment withintegration to SAP ERP, and one for SAP CRM standalone deployment.

You can find the Prerequisites Matrix for your solution package in the respective SAP BestPractices documentation package.

Prerequisites

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

The system landscape has been set up according to the Software Requirementsdocument (available in the SAP Best Practices documentation package for the respectivesolution package).

The most current SAP Best Practices for CRM content add-on BP-CRM713V<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 Settings in this guide.

An activation user has been created and set up for activation. For more information, seesection Preparing the System User for Content Activation 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 SAP CRM solution package, refer to section Security Aspects in the Additional Guide for your solution package.

For an overview of the security-relevant information that applies to SAP CRM in general, see theSecurity Guide for SAP enhancement package 3 for SAP CRM 7.0. To access the latest versionof the security guide, log on to SAP Service Marketplace (www.service.sap.com/crm-inst). Go tosection SAP enhancement package 3 for SAP CRM 7.0 Operate Security.

4.1 User Administration and Authentication

Use

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

Purpose User ID User Type Created In Init ialPassword

Author izationProfile

Comment

ActivationUser

User ID isdefined byyour systemadministrator

Dialog(Type A)

Creationdescribedin thisQuickGuide

Password isdefined byyour systemadministrator

SAP_ALL, or defined by your systemadministrator (seerecommen-dationbelow)

You can check the users in transaction SU01.

For more information about the authorizations assigned to the activation user see sectionHandling of Authorizations for Activation User of this guide

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

reasons.

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

4.2 Roles Management

Use

The following cross-package specific activation authorization roles are provided for SAP BestPractices for CRM content. For details see section Handling of Authorizations for Activation User in this guide.

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

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




Customer Role(copied from SAP Original Role)

Description SAP Original Role

Package-specific CRM role (SAP Best Practices for CRM)

Z_A_RDSCRM_CRM SAP Best Practices Activation Authorization Role for RDS CRM(CRM System)

SAP_CBPR_A_RDSCRM_CRM

Package-specific ERP role (SAP Best Practices for CRM)

Z_A_RDSCRM_ERP SAP Best Practices Activation Authorization Role for RDS CRM(ERP System)

SAP_NBPR_A_RDSCRM_ERP