c00 Crm703 Bb Configguide en Xx

EHP3 for SAP CRM 7.0

October 2014

English

SAP Best Practices Installation (C00)

SAP SEDietmar-Hopp-Allee 1669190 WalldorfGermany

Building Block Configuration Guide

SAP Best Practices SAP Best Practices Installation (C00): Configuration Guide

Copyright

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

© SAP SE Page 2 of 16

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


Revision Change Date Description

0



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 field names, screen titles, pushbuttons as well as menu names, paths and options.

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 key words of a programming language, when surrounded by body text, for example, 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 as names 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 the system exactly as they appear in the documentation.

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



Content

1 Preparation........................................................................................................................ 6

1.1 Reading the Quick Guide.........................................................................................6

1.2 Preparing Business Content Activation....................................................................6

1.3 Checking Logon Language......................................................................................6

2 Client Settings....................................................................................................................7

2.1 Defining the Initial SAP Menu..................................................................................7

2.2 Defining Logical System (SAP CRM).......................................................................7

2.3 Maintaining Client Settings (SAP CRM)...................................................................8

2.4 Maintaining Holiday and Factory Calendar..............................................................9

2.5 Checking Currency................................................................................................10

2.6 Deactivating Activation Links.................................................................................10

2.7 Maintaining Profile Parameters - SAP Scripting....................................................11

2.8 Setting Maximum Work Process Run Time...........................................................12

3 User Settings................................................................................................................... 13

3.1 Maintaining Unicode Settings................................................................................13

3.2 Maintaining Language Settings for BC Sets..........................................................13

3.3 Setting Decimal Notation and Date Format...........................................................14

3.4 Allowing GUI Scripting and Disable Screen Size Check........................................14

3.5 Re-Login................................................................................................................15

4 Pre-Assembled Deployment............................................................................................16



SAP Best Practices Installation

1 PreparationBefore starting the installation of this first building block, some preparatory activities must be performed.

1.1 Reading the Quick Guide

UseBefore starting the installation you must read the quick guide for your solution package and execute the activities described there.

ProcedureBefore starting the installation, complete the following activities:

Read the document Quick Guide to Implementing the SAP CRM rapid-deployment solution, which is attached to the SAP Note of this SAP CRM rapid-deployment solution version.

Read the document System Requirements when setting up a new system landscape.

Ensure that you meet all recommended prerequisites.

Read the Quick Guide completely even if you are an experienced SAP Best Practices user.

1.2 Preparing Business Content Activation

UseIf you follow the ‘pre-assembled’ deployment approach (using the SAP Solution Builder) check whether the tasks of section Activation of Business Content in the Quick Guide have all been prepared and followed, especially the following tasks:

Set Documentation Path for Solution Builder

Personalize the Solution or Procedure

Maintaining System Landscape Information for Solution Builder

Handling of Manual Interaction and Errors During Activation

1.3 Checking Logon LanguageThe logon language to any system client for configuration always must be English (EN).



2 Client SettingsBefore starting activation of SAP Best Practices content, you need to make some basic settings. Usually, you have done most of these settings, when you have followed the Quick Guide to Implementing the SAP CRM rapid-deployment solution. In some cases, for example after a system restart, these settings get lost. To make sure that you have set up the system correctly for activation, the critical settings are repeated here.

2.1 Defining the Initial SAP Menu

UseDefine the SAP CRM standard menu CRM_MENU (Customer Relationship Management) as your initial SAP menu.

You need to run this setting only once, so you can skip this activity, if the SAP menu in the SAP CRM system already contains the standard CRM entries.

Procedure1. Run the following activity:

SAP CRM transaction code SSM2

2. On the screen Set Initial Menu for the SAP System, choose Set initial menu systemwide. After starting the search, all possible menus were listed.

3. In the column Area menu, select menu CRM_MENU (Customer Relationship Management).

4. Choose Copy or double-click the entry.

5. In the dialog box Prompt for Workbench request, choose Create Request(F8)or select an existing workbench request.

6. Enter a short description and choose Save or Enter.

7. Choose Continue.

ResultYou have defined the standard menu as your initial SAP menu.

2.2 Defining Logical System (SAP CRM)UseThe distribution of data between systems makes it necessary to identify each system as a unique logical system.

A logical system is an application system in which the applications are coordinated to work in one common database. In SAP terms, a logical system corresponds to a client.

Procedure1. Access the activity using the following navigation options:

Transaction code SPRO



SAP CRM IMG menu Customer Relationship Management CRM Middleware and Related Components Communication Setup Set Up Logical Systems Define Logical System

2. Choose New Entries (F5)and enter the following data:

A name for the logical system that you want to create (Logical System)

A clear description of the logical system (Name)

Logical System Name

<CRM system>CLNT<Client>, (for example, CRMCLNT100)

<your name(for example: CRM Best Practices)

3. Save your entries (Ctrl+S).

ResultYou have successfully created a logical system.

2.3 Maintaining Client Settings (SAP CRM)

UseThis activity adjusts the client settings to enable SAP Best Practices installation.

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

Transaction code SCC4

SAP CRM GUI menu Architecture and Technology System Administration Administration Administration Client Administration Client Maintenance

2. Choose Display <-> Change.

3. Confirm the message Caution: The table is cross-client.

4. Highlight your relevant CRM client and choose Details.

5. On the Change View “Clients”: Details screen, enter the following data:

Field / Area Entry Comment

Logical system <CRM system>CLNT<Client>, (for example, CRMCLNT100)

Client role Customizing

Changes and Transports for Client-Specific Objects

Automatic recording of changes

Cross-Client Object Changes Changes to Repository and cross-client Customizing allowed.

Client Copy and Comparison Tool Protection

Protection level 0: No restriction

CATT and eCATT Restrictions eCATT and CATT Allowed



6. Save and confirm the warning message Be careful when changing the logical system.

ResultThe client settings have been adjusted in order to enable SAP Best Practices Installation.

2.4 Maintaining Holiday and Factory Calendar

UseThe validity of the holiday and factory calendars needs to be checked and extended if necessary. Some of the standard settings are valid until year 2010 only and need to be extended. Several business functions are using the calendar information.

The validity of the Holiday Calendar and the holidays has to be checked according to the legal requirements of the related country. In case of any issues the standard customizing settings have to be corrected in this step in order to meet the legal local requirements.


Transaction code SCAL

SAP CRM IMG menu SAP NetWeaver General Settings Maintain Calendar

2. Select the Holiday calendar and choose Change.

3. On the Change Public Holiday Calendar: Overview screen, select the Holiday Calendar entry specific for your country and region.

4. Choose Change.

5. On the Change Public Holiday Calendar: Details screen, check and change the Valid to field to a future year (for example, +3 years).

6. Check the validity range of every public holiday assigned to the holiday calendar. Extend the validity if necessary.

7. Save your entries. Confirm the message regarding transporting of holiday and factory calendar settings.

8. Choose Back to return to the SAP Calendar: Main Menu screen.

9. Select the Factory calendar and choose Change.

10. On the Change Factory Calendar: Overview screen, select the Factory Calendar entry specific for your country and region.

11. Choose Change.

12. On the Change Factory Calendar: Details screen, check and change the Valid to field to a future year (for example, +3 years).

13. Save your entries. Confirm the message regarding transporting of holiday and factory calendar settings.

14. Leave the IMG activity.

ResultThe validity of both holiday and factory calendar, and the public holidays have been checked and extended to a future year.



2.5 Checking Currency

UseThe currency codes have to be checked.


Transaction code SM30

SAP CRM IMG menu SAP NetWeaver General Settings Currencies Check Currency Codes

2. In field Table/View enter V_CURC and choose Display.

3. On the screen Display View “Currencies”: Overview, check the currency entries for completeness. The currency table must have entries for all currencies that occur in your business transactions.

ResultYou have successfully checked the currency entries.

2.6 Deactivating Activation Links

This activity is not necessary if you follow the manual deployment approach.

UseWe recommend that you turn off the creation of activation links for BC Sets. By doing this, you can significantly increase activation speed and avoid errors.


SAP CRM Transaction code SCPR20

2. On the Business Configuration Sets: Activation screen, go to Utilities System Settings.

3. Choose Display <-> Change (Shift+F1).

4. In screen area Activation set the parameter Do Not Create.

5. Confirm the information message and save your settings.

ResultThe system settings have been successfully changed. You have deactivated the activation links for BC Sets.



2.7 Maintaining Profile Parameters - SAP Scripting


UseeCATTs are used to automate the activation of SAP Best Practices configuration settings. Before activation, you must allow eCATT processing in the system: The profile parameter sapgui/user_scripting must be set.

Only those activation users that do not install the first scenario need to perform this activity (for example, if someone else already installed a specific scenario and you want to install an additional scenario).

All installation users will have to perform this activity, once the server has been restarted.


SAP CRM Transaction code RZ11

2. On the Maintain Profile Parameters screen, enter the following value:

Field name Field value

Parameter name sapgui/user_scripting

Choose Display.

On the Maintain Profile Parameters screen, select Change Value.

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

Field name Field value Note

Parameter Name sapgui/user_scripting

New Value TRUE Enable SAP Scripting

3. Choose Save.

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

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

ResultYou have maintained the profile parameter sapgui/user_scripting.



2.8 Setting Maximum Work Process Run Time

UseDynamic switchable profile parameters (indicated by a flag in the checkbox of the parameter) have to be checked before activation. Therefore, the following profile parameters must be checked and adapted.

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


SAP CRM Transaction code RZ11

2. On the Maintain Profile Parameters screen, enter the following:

Field name Description User action and values Note

Param. Name Profile parameter name rdisp/max_wprun_time

3. Choose Display.

4. On the Maintain Profile Parameters screen, choose Change Value.

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

Field name Field value Note

Parameter Name rdisp/max_wprun_time

New Value 3600 Check and adapt the value if the value is <3600

6. Choose Save.

When you save the change, the window closes and the current value of the parameter has been changed. This change only becomes effective when you log off and then log on to the system again.

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

This parameter value is only needed for activation of SAP Best Practices as there are some processes that need to be performed in dialog and last for more than ten minutes.Switch back to the default value after activation of SAP Best Practices.

ResultYou have successfully changed the value of the parameter.



3 User Settings

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

Usually, you have made the user settings described in this section, when you have followed the Quick Guide to Implementing the SAP CRM rapid-deployment solution. However, if the installation user changes during activation, all user settings have to be made again for the new user.

3.1 Maintaining Unicode Settings

UseBefore each user logs on to the system for the first time, the user’s local GUI must be set to use the Unicode code page.

Procedure1. From the SAP Logon 720 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.

ResultThe user’s local GUI has been set to use the Unicode code page.

3.2 Maintaining Language Settings for BC Sets


UseTo ensure proper activation of the Business Configuration Sets for the installation, you must select all languages relevant for BC Sets.


SAP CRM Transaction code SCPR20

2. On the Business Configuration Sets: Activation screen, choose Utilities User Settings from the menu.

3. In dialog box BC Sets: Change User Settings, on tab General Settings, ensure that checkbox Use User Languages is NOT selected.

4. Choose Copy Settings (Enter).



5. Choose Back.

ResultYou have successfully selected the languages relevant for the BC Sets.

3.3 Setting Decimal Notation and Date Format


UseSome installation data files (TXT) of BP CRM contain dates and numeric values. The user settings of the installation user need to be synchronized with date format and decimal notation of these installation data files.


SAP CRM Transaction code SU3

2. Choose the Defaults tab.

3. Make sure that the Decimal Notation has got value 1.234.567,89.

4. Make sure that the Date Format has got value DD.MM.YYYY.

5. Save your settings.

6. When the complete activation procedure is finished, you may change these values as desired.

ResultThe decimal notation and the date format have been set up according to the format of the data files.

3.4 Allowing GUI Scripting and Disable Screen Size Check


UseThis activity allows the use of your GUI to execute eCATTs GUI scripts in the CRM system.

Additionally, to prevent the dialog box sizing conflicts may appear from appearing during activation, you can deactivate the screen size check.

The following procedure assumes you are using SAP GUI 7.20.



Procedure1. In the SAP Menu, on the right hand side of the standard toolbar, choose button

Customize Local Layout (ALT+F12).

2. From the sub menu choose Options...

3. Open folder Accessibility & Scripting and choose Scripting.

4. Select checkbox Enable Scripting.

5. Deselect both checkboxes Notify when a script attaches to SAP GUI and Notify when a script opens a connection.

6. If folder SAP Internal exists, open it and choose SAP Internal.

7. Deselect the checkbox Enable Dialogbox for Screen Size Check.

8. Choose the OK button.

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

The screen size check has been disabled.

3.5 Re-LoginYou must log into the SAP CRM system again so that the settings made in this section take effect. Then you can continue with the activation process.



4 Pre-Assembled DeploymentUseIf you follow the “pre-assembled deployment” approach, some parts of the SAP Best Practices for CRM content are already activated, whereas others still need to be activated. Therefore, all configuration tasks are classified into one of the following categories:

Pre-Assembly (“Pre”): Configuration tasks classified as ‘Pre-Assembly’ have already been executed and do not need to be re-activated during an implementation project.

Post-Processing (“Post”): ‘Post-Processing’ configuration tasks still need to be performed in the target system landscape.

Some tasks can be classified as both ‘Pre-Assembly’ and ‘Post-Processing’; this means that these tasks have been pre-assembled, but need to be checked and potentially modified during the post-assembly phase.

Configuration TaskERP Integrated CRM Standalone

SystemPre Post Pre Post

1.1 Reading the Quick Guide X X N.A

Error: Reference source not found Preparing BusinessContent Activation

X X CRM

1.3 Checking Logon Language X X ERP & CRM

2.1 Defining the Initial SAP Menu X X CRM

2.2 Defining Logical System (SAP CRM) X X CRM

2.3 Maintaining Client Settings (SAP CRM) X X CRM

2.44 Maintaining Holiday and Factory Calendar X X CRM

2.55 Checking Currency X X CRM

2.66 Deactivating Activation Links X X CRM

2.77 Maintaining Profile Parameters - SAP Scripting X X X X CRM

2.88 Setting Maximum Work Process Run Time X X X X CRM

3.1 Maintaining Unicode Settings X X N.A

3.2 Maintaining Language Settings for BC Sets X X CRM

3.3 Setting Decimal Notation and Date Format X X CRM

3.4 Allowing GUI Scripting and Disable Screen Size Check

X X CRM

3.5 Re-Login X X CRM


Documents

c00 Crm703 Bb Configguide en Xx