87077245 charm configuration guide

5/22/2018 87077245 ChaRM Configuration Guide

1/129

Change Request Management -

Configuration and Upgrade Guide

Applicable Releases:

SAP Solution Manager 7.1 SP 03 (onwards)

SAP Solution Manager Scenarios:

Change Request Management

Version 1.1

January 2012


2/129

Copyright 2012 SAP AG. All rights reserved.

No part of this publication may be reproduced or

transmitted in any form or for any purpose without the

express permission of SAP AG. The information contained

herein may be changed without prior notice.Some software products marketed by SAP AG and its

distributors contain proprietary software components of

other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are

registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel

Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390,

OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP,

Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix,

i5/OS, POWER, POWER5, OpenPower and PowerPC are

trademarks or registered trademarks of IBM Corporation.Adobe, the Adobe logo, Acrobat, PostScript, and Reader

are either trademarks or registered trademarks of Adobe

Systems Incorporated in the United States and/or other

countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered

trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame,

WinFrame, VideoFrame, and MultiWin are trademarks or

registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or

registered trademarks of W3C, World Wide Web

Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems,

Inc., used under license for technology invented and

implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP

NetWeaver, and other SAP products and services

mentioned herein as well as their respective logos are

trademarks or registered trademarks of SAP AG in

Germany and in several other countries all over the world.

All other product and service names mentioned are the

trademarks of their respective companies. Data contained

in this document serves informational purposes only.

National product specifications may vary.

These materials are subject to change without notice.

These materials are provided by SAP AG and its affiliated

companies ("SAP Group") for informational purposes only,

without representation or warranty of any kind, and SAP

Group shall not be liable for errors or omissions withrespect to the materials. The only warranties for SAP

Group products and services are those that are set forth in

the express warranty statements accompanying such

products and services, if any. Nothing herein should be

construed as constituting an additional warranty.

These materials are provided as is without a warranty of

any kind, either express or implied, including but not

limited to, the implied warranties of merchantability,

fitness for a particular purpose, or non-infringement.

SAP shall not be liable for damages of any kind including

without limitation direct, special, indirect, or consequential

damages that may result from the use of these materials.

SAP does not warrant the accuracy or completeness of the

information, text, graphics, links or other items contained

within these materials. SAP has no control over the

information that you may access through the use of hot

links contained in these materials and does not endorse

your use of third party web pages nor provide any warranty

whatsoever relating to third party web pages.

SAP NetWeaver How-to Guides are intended to simplify

the product implementation. While specific product

features and procedures typically are explained in a

practical business context, it is not implied that those

features and procedures are the only approach in solving a

specific business problem using SAP NetWeaver. Should

you wish to receive additional information, clarification or

support, please refer to SAP Consulting.

Any software coding and/or code lines / strings (Code)

included in this documentation are only examples and are

not intended to be used in a productive system

environment. The Code is only intended better explain and

visualize the syntax and phrasing rules of certain coding.

SAP does not warrant the correctness and completeness of

the Code given herein, and SAP shall not be liable for

errors or damages caused by the usage of the Code, except

if such damages were caused by SAP intentionally or

grossly negligent.

Disclaimer

Some components of this product are based on Java. Any

code change in these components may cause unpredictable

and severe malfunctions and is therefore expressively

prohibited, as is any decompilation of these components.

Any Java Source Code delivered with this product is only

to be used by SAPs Support Services and may not be

modified or altered in any way.


3/129

Document HistoryDocument Version Description

1.1 Updated version, including additional topics/detailed information about

Copy Control for Partners

Publishing of Saved Searches

Creating customer UI configuration

Defining mandatory fields

Creating system wide text-templates

Information about migrating customer fields

Useful Notes updated

1.00 First official release of this guide


4/129

TypographicConventionsType Style Description

Example Text Words or characters quoted

from the screen. These

include field names, screen

titles, pushbuttons labels,

menu names, menu paths,

and menu options.

Cross-references to other

documentation

Example text Emphasized words or

phrases in body text, graphic

titles, and table titles

Example text File and directory names and

their paths, messages,

names of variables and

parameters, source text, and

names of installation,

upgrade and database tools.

Example text User entry texts. These are

words or characters that you

enter in the system exactly as

they appear in thedocumentation.

Variable user entry. Angle

brackets indicate that you

replace these words and

characters with appropriate

entries to make entries in the

system.

EXAMPLE TEXT Keys on the keyboard, for

example, F2or ENTER.

IconsIcon Description

Caution

Note or Important

Example

Recommendation or Tip


5/129

Table of Contents

1. General Information............................................................................................................. 1

1.1 Change Request Management Overview .................................................................... 1

1.2 Chapters Overview ....................................................................................................... 2

2. Standard Configuration ...................................................................................................... 3

2.1 Check-Prerequisites ..................................................................................................... 3

2.1.1 Required Activities ........................................................................................... 3

2.1.2 Basic Configuration SAP Solution Manager .................................................... 3

2.1.3 Piece List Activation ......................................................................................... 5

2.2 Implementation of Notes ............................................................................................... 6

2.3 Copy Transaction Types ............................................................................................... 7

2.3.1 Copy Transaction Types via Report ................................................................ 8

2.3.2 Manual Copy .................................................................................................. 122.4 Automatic Configuration ............................................................................................. 12

2.5 Manual Configuration ................................................................................................. 13

2.5.1 Transport Management System .................................................................... 13

2.5.2 Authorizations ................................................................................................ 14

2.5.3 Business Roles and Authorizations ............................................................... 14

2.5.4 Create a SAP Solution Manager Project to activate Change Request

Management .................................................................................................. 15

2.5.5 Managed System information (IBase) ........................................................... 25

2.5.6 Master Data ................................................................................................... 26

3. Additional Configuration .................................................................................................. 33

3.1 Additional Functions ................................................................................................... 33

3.1.1 CRM Field Customizing ................................................................................. 33

3.1.2 Approval Procedures ..................................................................................... 38

3.1.3 Scope Assignment Block ............................................................................... 42

3.1.4 Transport Management Assignment Block .................................................... 44

3.1.5 Landscape Assignment Block ........................................................................ 46

3.1.6 Project, Solution, Document & Test management Assignment Block ........... 47

3.1.7 SAP WebClient UI Configuration & Personalization ...................................... 49

3.1.8 Adding Custom Actions to the SAP WebClient UI ......................................... 49

3.1.9 TREX Set-up .................................................................................................. 50

3.1.10 Support Team Determination (optional) ......................................................... 50

3.1.11 Multilevel Categorization ................................................................................ 50

3.1.12 Publishing of Saved Search ........................................................................... 51

3.1.13 Create a system wide text Template ............................................................. 51

3.1.14 Create customer specific UI configuration ..................................................... 53

3.1.15 How to define mandatory fields ..................................................................... 56

3.2 Customer Specific Setup ............................................................................................ 58

3.2.1 Transaction Type ........................................................................................... 58

3.2.2 Text Determination Procedure ....................................................................... 61

3.2.3 Partner Determination Procedure .................................................................. 65

3.2.4 Status Profile .................................................................................................. 66


6/129

3.2.5 Date Profile .................................................................................................... 68

3.2.6 Action Profile .................................................................................................. 69

3.2.7 Number Ranges ............................................................................................. 71

3.2.8 Assign new transaction types to Change Request Management .................. 72

3.2.9 Integration with other Processes (Copy Control) ........................................... 73

3.2.10 Notifications ................................................................................................... 75

3.3 Example Use Case: How to enhance the standard workflow .................................... 76

3.3.1 Step 1: Status Profile ..................................................................................... 76

3.3.2 Step 2: Actions ............................................................................................... 77

3.3.3 Step 3: Conditions .......................................................................................... 78

3.3.4 Step 4: Create new condition ......................................................................... 81

3.3.5 Step 5: Define Status Attributes ..................................................................... 86

3.3.6 Optional: ChaRM Actions & Conditions ......................................................... 86

4. Upgrade .............................................................................................................................. 88

4.1 Overview ..................................................................................................................... 88

4.1.1 Transition phase ............................................................................................ 88

4.1.2 Upgrade Roadmap ......................................................................................... 89

4.2 Options to take over open transactions ...................................................................... 90

4.3 Configuration Comparison (7.0 7.1) ...................................................................... 91

4.3.1 Overview Status Profiles ................................................................................ 91

4.3.2 Overview CRM PPF Actions .......................................................................... 94

4.3.3 Overview ChaRM-Actions .............................................................................. 98

4.3.4 Overview CRM PPF-Conditions .................................................................. 100

4.3.5 Overview ChaRM-Conditions....................................................................... 1024.3.6 BadIs in Change Request Management ...................................................... 105

4.3.7 Searching old transaction types in Web Client ............................................ 105

4.3.8 Copy Control ................................................................................................ 107

4.3.9 Categorization & Subject Profile .................................................................. 108

4.3.10 Customizing Approval Settings .................................................................... 108

4.3.11 Remote Connectivity for Managed Systems................................................ 110

4.3.1 Migration of Customer specific fields ........................................................... 111

5. Background Jobs ............................................................................................................ 112

5.1 Which Jobs are relevant for Change Request Management? ................................. 112

6. Troubleshooting .............................................................................................................. 113

6.1 Useful SAP Notes ..................................................................................................... 113

6.2 Known Pitfalls & Resolution ...................................................................................... 113

7. Additional Resources ...................................................................................................... 123

7.1 IT Service Management ........................................................................................... 123

7.2 Change Request Management ................................................................................. 123

7.3 Web Client UI Framework ........................................................................................ 123


7/129

Change Request ManagementConfiguration Guide

February 2012 1

1.General Information

This guide describes the configuration of the Change Request Management with SAP Solution Manager 7.1.

1.1 Change Request Management OverviewIn today's distributed environments, comprehensive change control management plays a crucial role. With

standardized processes, methods and tools, it ensures high transparency and continuous quality of the

change processes, during the entire application life cycle.

Change Request Management comes with a predefined set of workflows and processes, which are all

compliant to the recommendations provided by the IT infrastructure library (ITIL). This will support you when

trying to setup an ITIL compliant change management process in your company.

Change Request Management coordinates all changes in a software landscape, to ensure that changes do

not conflict with each other. It also ensures that changes are made without disrupting the ongoing business.

This results in improved quality of the software landscape, higher availability of IT solutions, and lower total

cost of ownership. Change Request Management ensures that the performed changes remain transparent

and traceable.

Change request management enables you to manage your Solution Manager projects (maintenance,

implementation, template, and upgrade) from end to end: starting with change management and project

planning, to physical transports of changes from the development environment into the productive

environment.

The processes supported by change request management includes urgent corrections for implementing fast

and direct changes in the productive environment, and activities for maintenance projects, and

implementation, upgrade, and template projects. Cross-system and cross-component changes are supported

and secure by sophisticated functionalities.

Change request management offers a lot of benefits, like ensuring a comprehensible documentation of

planned and implemented changes and their consequences. By having a tight integration with the SAP

transport management system, it guarantees a complete coverage of change requests to technical transports.

This will also result in a consistent documentation of all change requests, which makes it easy to comply with

compliance auditions.

By using this infrastructure and toolset the efficiency of change management projects will improve significantly.

The usage of preconfigured workflows and holistic change processes will not only reduce the workload of IT

specialists, but also minimize business disruptionsfinally resulting in reduced costs.

This approach will help you to increase the transparency of your solution, make it easier to get an overview

and help to achieve a higher quality of changes.

With Change Request Management, SAP delivers an end-to-end solution that comes with no additionallicense costs and that is already available on your SAP Solution Manager. Benefit from the tight integration in

SAPs Application Lifecycle Management and make Change Request Management to the change

management tool of your organization.

Changes and Enhancements with the new Release

The Change Request Management scenario in SAP Solution Manager 7.1 comprises various new

functionalities which are based on SAP CRM 7.1 IT Service Management. It includes the web-based user

interface SAP Web Client which replaces the SAP GUI transactions CRMD_ORDER and

CRM_DNO_MONITOR. SAP WebClient is the new main workplace of all user groups in Change Request

Management. The Work Center Change Management is still available in SAP Solution Manager 7.1 SP01 and

could be used.


8/129


February 2012 2

The SAP ITSM functions have been developed on new object types, so that it was necessary to have new

transaction types for Incident and Change Management. The former SDCR, SDHF, SDMJ etc. based

documents cannot be displayed or processed in the SAP WebClient. Therefore,

new transaction types (SMCR, SMMJ, SMHF, SMAD, SMCG, SMTM) are introduced. They replace the

transaction types SDCR, SDHF, SDMJ etc. which were used in the Change Request Management Scenario in

SAP Solution Manager 7.0.

1.2 Chapters Overview

Chapter 2 provides information about the standard configuration of Change Request Management. This

includes detailed information about the guided procedure within SOLMAN_SETUP. After completing this

chapter, the standard Change Request Management functionalities have been configured in your system.

Chapter 3 provides detail information about additional functionalities and configuration options of Change

Request Management. The chapter is divided into two main sections: Additional Functionalities covering

standard functionalities that are used by Change Request Management and how they can be configured. The

area Customer Specific Setup contains an overview, how the standard process and workflow of Change

Request Management can be adapted to your individual requirements.

Chapter 4 is the upgrade chapterproviding a detailed overview of all the things that have been changed in

Change Request Management between 7.0 and 7.1. The chapter contains a detailed comparison of

configurations and technical details between the two releases - this shall guide you through the transition

phase (e.g. from SDCR to SMCR).

Chapter 5 provides a quick overview about background jobs of Change Request Management.

Chapter 6 covers a list of useful SAP Notes in the area of Change Request Management and gives an

overview about known pitfalls from other projects and their resolution.

Finally, Chapter 7 contains a list of additional resources for Change Request Management, IT Service

Management and the SAP Web Client User Interface. Those resources are especially important when you

want to get more information on the topic, e.g. in regards to UI enhancements or the functionalities of IT

Service Management in general.

Prerequisite for the configuration of the Change Request Management is an installed SAP Solution

Manager 7.1 SPS 3. For more information, please see the SAP Solution Manager Installation Guide

available in SAP Service Marketplace.


9/129


February 2012 3

2.Standard Configuration

SAP Solution Manager provides a setup procedure for the IT Service Management topic, including Change

Request Management. This setup procedure will guide you through the setup of SAP Solution Manager in

general, as well as the different scenarios.

You can access the procedure via transaction SOLMAN_SETUP and reach the IT Service Management area

in the menu on the left by clicking IT Service Management. This area is further divided into Incident &

Problem Management and Change Request Management.

This chapter will guide you through the different setup steps and describe some of the important activities

more in detail.

2.1 Check-Prerequisites

2.1.1Required Activities

Before you get started with the setup of the Change Request Management scenario you need to make sure

that the SAP Solution Manager is correctly installed. SAP provides a number of installation guides for different

Operating System and Database combinations.

The guides can be accessed via the SAP Service Marketplace:http://service.sap.com/instguides

2.1.2Basic Configuration SAP Solution Manager

Before starting with the Basic Configuration of your Solution Manager system you should read the

documentation and initial descriptions available in the Implementation Guide (transaction SPRO).

Therefore, navigate to SAP Solution Manager Implementation Guide SAP Solution Manager Basic

Configuration Basic Configuration: Guided Procedure
http://service.sap.com/instguideshttp://service.sap.com/instguideshttp://service.sap.com/instguideshttp://service.sap.com/instguides


10/129


February 2012 4

Via the transaction SOLMAN_SETUP, you start the initial configuration of the SAP Solution Manager system.

In the navigation area on the left, you can access the following guided procedures which contain configuration

steps relevant for the Change Request Management scenario:

System Preparation: In this guided procedure, you make settings preliminary for the Solution

Manager Configuration, such as creation of dialog users with the required authorizations,

implementation of the central correction note and web service configuration.

Basic Conf igurat ion: This guided procedure leads you through all configuration steps which you

must perform to enable basic scenarios in the SAP Solution Manager. As part of the basicconfiguration, you set up the connection to SAP, schedule relevant background jobs and activate

piece lists which contain important settings, such as standard customizing.

Managed System Conf igurat ion: In the Managed System Configuration, you connect satellite

systems to the Solution Manager via RFC. This is important since Change Request Management

requires a READ, TMW and TRUSTED RfC to every Managed System/Client. In order to ensure that

Change Request Management works perfectly with Managed Systems a minimum SP Level is

required. Please check SAP Note 907768 for further details.


11/129


February 2012 5

Please, confirm you have successfully performed those three configuration steps according to the guided

procedure documentations!

In addition to the Basic Configuration you can run now the Basic Configuration for Change RequestManagement

2.1.3Piece List Activation

The activity in Check Prerequisites will check whether the piece list of IT Service Management, containing all

the standard customizing for Incident-, Problem- and Change Management, was imported correctly.

More Details regarding the Customizing Piece List

The Standard Customizing of Change Request Management and all other IT Service Management relevant

areas is delivered via a so called customizing piece list. This piece list needs to be activated as part of

SOLMAN_SETUP and will copy the standard customizing from Client 000 into the working client.

Activating the piece list again will overwrite all existing standard customizing with the content of the piece list

therefore it is strictly recommended to copy all transaction types into the customer namespace, before starting

to use Change Request Management on customer site.

The existing BC-Sets of Change Request Management are not supposed to be activated within a 7.1

system, since they are replaced by the customizing piece list!


12/129


February 2012 6

2.2Implementation of Notes

The next step of the setup procedure covers the download, import and post processing process for some

important Change Request Management Notes.

It is highly recommended to implement the latest Notes in order to make sure that all Change Request

Management functionalities are running correctly. Besides the recommended mandatory SAP Notes, there are

additional optional notes that contain further bug fixes, that might not be required by all customers. Most of

those notes are for some specific Change Request Management scenarios.

Additional Information reg. Note Implementations and Basic ChaRM

Configuration

Before you start to configure Change Request Management please review the according Master Note that fits

to your SP Level and implement the latest version before moving on with configuration.

1606456Master Note for Change Request Management ST 7.1 SP3

1574224 - General note for Change Request Management ST 7.1

To reach the basic configuration for Change Request Management call transaction SPRO and navigate to

SAP Solution Manager Implementation Guide SAP Solution Manager Capabilities (Optional) Change

Management Basic Configuration

This area contains four individual tasks:

1. Transport Management System

2. Activate Integration with Change Request Management

3. Set up Authorization and Work Center Navigation

4. Activate Solution Manager Services


13/129


February 2012 7

2.3Copy Transaction Types

One of the most important activities (and time consuming in the past) was the copy of the transaction types

into the customer namespace. This activity is so important because once you would start to customize the

standard delivered processes, by overwriting and changing the standard your entire customizing might get

lost, in case SAP would deliver new customizing via the piece list with an upgrade. By copying all the profiles


14/129


February 2012 8

and settings into the customer namespace, you ensure that these settings will be save, even when doing an

upgrade or implementation of an service pack.

Also you can keep the SAP standard workflows as a reference, so in case of an error in your workflow you can

check if the same error happens in the SAP standard workflow and like this easily determine if the issue is

caused by customizing or any custom specific setup or if it is a general problem.

2.3.1Copy Transaction Types via Report

As part of step 3 in SOLMAN_SETUP for Change Request Management there is a link to a copy report to

copy the standard transaction types into the customer namespace.

Please make sure to activate the piece list, so the standard customizing is implemented correctly, before

copying the transaction types.

Please ensure that when you copy into your namespace you only exchange the first character of the

Transaction Type, e.g. SMCR to YMCR or ZMCR. Changes of more than the starting character could cause

issues in the phase controller and will require a significant amount of manual customizing effort, which is not

recommended at all.

2.3.1.1 Scope:

The transaction AI_CRM_CPY_PROCTYPE provides the following functions

Copies a transaction type into customer namespace

o The copy includes almost all relevant entries including

Status Profile

Action Profile

Data Profile

o The usage of an transaction type is not be copied, these settings must be made manual

DNO_CUST04

Usage in SOLAR01/02 and test workbench

Update a already copied transaction type Display and transaction type


15/129


February 2012 9

All customizing which is created with the transaction will be stored on a transport request depending on the

client settings (SCC4)

All entries which are created are written to a log, which is used by the update logic and can be displayed by

transaction AI_CRM_CPY_PTYPE_LOG.

2.3.1.2 Function in Details

Copy transaction type

1. Select a source transaction type using value help2. Enter a target transaction type

a. The target transaction type will be checked

i. If it exist, it cannot be used

ii. If the key differentiate in the last three characters you will get a warning when you

execute(4.)

3. If you let the check box Display selected data on screen first you will get an overview of the entries

which will be created


16/129


February 2012 10

4. Execute

5. In the popup you see the source profile and the proposed names of the target profile

a. If you remove a profile then the source profile will be assigned (no copy)

b. If you change a profile to an existing profile, the profile will be assigned but noadaption/copy

will be done to the profile

c. If you change a profile to a not existing profile this profile will be created. In case of actions the

actions IDs will start with the first 4 characters of the profiled. It is recommended to change the description of the target profiles, if not the IMG activity will

send warnings same description.

6. Execute


17/129


February 2012 11

Here you see all tables, all keys, all values which will be created, you can drill down for each profile

and you can also see some SAP Solution Manager tables with specific content which will be copied.

The green field contains the keys and changed values.

7. Executing the Copy Icon the copy process runs.

a. Depending on the client settings a pop up for a transport request will pop up


18/129


February 2012 12

2.3.2Manual Copy

Besides the automatic copy of the transaction types there is still the manual way through the IMG-Guide,

which is available via transaction SPRO.

Since the report will take over the copy process automatically, this guide will not cover a detailed description of

the manual copy process. More information can be found in the documentation of the IMG-Guide, attached to

each customizing activity.

The general path to the Change Request Management customizing options:

Transaction SPRO SAP Reference IMG SAP Solution Manager Capabilities (optional) Change

Management

2.4Automatic Configuration

The automatic configuration step will create the required entries for Change Request Management in table

BCOS_CUST as well as setting the CHARM_CLIENT to the current working client. Especially the

CHARM_CLIENT is required to run Change Request Management correctly, because it will tell the system

which client will actually host the Change Request Management scenario.


19/129


February 2012 13

2.5Manual Configuration

In the manual configuration step, all those activities that are required or recommended to run Change Request

Management can be configured. Since those steps are manual, the system cannot do it automaticallybut

the procedure will guide you through the process and navigate you to the related node in the IMG Guide of

SAP Solution Manager.

The following sections will describe those activities more in detail:

2.5.1Transport Management SystemHere you find a section for Transport Management Configuration. This section provides solely information how

to setup a TMS to make it work together with Change Request Management.

The steps that are required can be found in the IMG of SAP Solution Manager:

IMG SAP Solution Manager Capabilities (Optional) Change Management Basic Configuration

Transport Management System

This step cannot be further automated, because every customer might have a different system landscape.

You can find a basic description, how you setup the Transport Management System for a simulated 3-

system landscape in the Change Request Management RKT-Materials viahttp://service.sap.com/rkt-solman
http://service.sap.com/rkt-solmanhttp://service.sap.com/rkt-solmanhttp://service.sap.com/rkt-solmanhttp://service.sap.com/rkt-solman


20/129


February 2012 14

2.5.2Authorizations

Review the documentation for details about standard roles provided. There is a guide available in the SAP

Service Marketplace that contains more information about authorizations:

http://service.sap.com/instguidesSAP Components SAP Solution Manager Release 7.16

Additional Guides Business and Authorization Roles (ITSM)

Standard roles in SAP Solution Manager

SAP_CM_DEVELOPER_COMP

SAP_CM_CHANGE_MANAGER_COMP

SAP_CM_TESTER_COMP

SAP_CM_OPERATOR_COMP

SAP_CM_REQUESTER_COMP

SAP_CM_ADMINISTRATOR_COMP

2.5.3Business Roles and Authorizations

For the ITSM (Incident Management, Problem Management, Change Management) scenario in the SAP

Solution Manager, SAP provides the predefined business role SOLMANPRO for SAP Web Clientconfiguration including predefined authorization (PFCG) roles for setting up an authorization concept.

You use the business role SOLMANPROto control the navigation bar, logical links and user authorizations.

For further information about all PFCG roles which are relevant for the Change Request Management

scenario, please refer to the SAP Solution Manager Security Guide. This guide is available in SAP Service

Marketplace.

The business role SOLMANPROand the authorization roles are only intended to be used as a template

for Best Practices scope. The roles have to be validated and adapted to the specific customer

requirements.

For detailed instructions on how to adapt business and PFCG roles, please refer to the configuration guide

Business and Authorization Rolesavailable in SAP Service Marketplace.

Also check the following SAP Notes for further details.

1481246 Hinweis Berechtigungen fr den Service Desk Release 7.1

1436271 UIU framework SM

1436270 Sammelhinweis Berechtigungen Solution Manager Release 7.1
http://service.sap.com/instguideshttp://service.sap.com/instguideshttp://service.sap.com/instguides


21/129


February 2012 15

2.5.4Create a SAP Solution Manager Project to activate Change

Request Management

After the successful setup of Change Request Management and the creation of business partner and system

information (Ibase) a final step need to be performed. A SAP Solution Manager project needs to be definedand activated for Change Request Management.

The following picture describes the project structure and components for Change Request Management.

Starting point is always a SAP Solution Manager Project. Later on a Project Cycle is created out of a SAP

Solution Manager Project. This Project Cycle contains different components for Change Request Management

e.g. Task List, IMG Project and CTS Project, Project Phases etc.

Within a SAP Solution Manager Project the managed system landscape can be define. This is done with

logical components. A logical component consists of several logical systems (system/client combination).

Each logical system gets within a logical component a description and a system role assigned. The definition

of a logical component is done in transaction SMSY.

Call SMSY and navigate to System Groups and Logical Components.Logical components are based on product version. Choose a product and press with the right mouse button

on the product description.


22/129


February 2012 16

Define the description and name for the logical component. Confirm your settings.

On the right side of the screen you can now assign logical systems to some predefined named categories.

Assign your systems accordingly to the logical component. Change Request Management requires at least

two systems.


23/129


February 2012 17

Each category has a System Role assigned. This can be checked by pressing the button System Role.


24/129


February 2012 18

Change Request Management requires at least one logical system with System Role Source Systemand one

logical system with System Role Production System.

Below an example for a three tier landscape defined in one logical component.

Call transaction SOLAR_PROJECT_ADMIN. Press the button Create Project.

Define a Project Name, select a project type (e.g. Maintenance) and Confirm.

Maintain a Title and choose a language.


25/129


February 2012 19

Confirm the Pop-Up asking for the document enhancement.

Navigate to the tab System Landscape and select (use value help) the logical component defined before.

The logical component will be put into the project definition. Save your settings.


26/129


February 2012 20

Navigate to the tab Change Management and activate the Change Management integration for this project.

Confirm the pop-up window.

Before creating the project cycle and taks list run a check for the project definition. Press the button Check.


27/129


February 2012 21

This Check covers different aspects. Initial configuration, correct transport management setup or assigned

business partner. The result list shouldnt contain any errors. In case of check for the error message and also

the application log (button right next to the Check button).

When the project check was successful you create a project cycle and a task list. To do this just press the

button Create Task List.


28/129


February 2012 22

Define a name for the Task List and confirm.

After the successful creation this pop-up will show up.

You can now navigate to the Task List directly. The initial phase value will be Development without Release

and the tasks for the project track will still be locked. You can unlock the tasks either by pressing on it with theright mouse button or use the task Lock/Release Transport Tracks incl. Role Types.


29/129


February 2012 23

Example: Unlock task with right mouse button

Example: Open tasks with task Lock/Release Transport Tracks incl. Role Types

Select the system types for which the tasks should be released and confirm.


30/129


February 2012 24

After leaving the task list you get directly back to the SAP Solution Manager Project definition. There you can

see the successful defined SAP Solution Manager Project which can now be used with Change Request

Management.


31/129


February 2012 25

2.5.5Managed System information (IBase)

With the new SAP Solution Manager Release 7.1 major changes in terms of system management in SAP

Solution Manager are introduced. Central component to administrate Managed Systems is the LandscapeManagement Database (LMDB).

As central repository for all managed systems the LMDB provides detailed system information for other

repositories like SMSY. The SMSY is still being used to define i.e. Logical component and to update the IBase

with system information. Both, logical components and the IBase, are used in Change Request Management.

While a logical component helps to define the selection of systems that should be managed within a Change

Request Management Project, the IBase provides a unique identification for any system and/or client. These

way scenarios like Incident Management or Change Request Management can clearly identify and document

the targeted system within their processes.

Details about the technical settings for the IBase can be found at the IMG in transaction SPRO.


32/129


February 2012 26

There you will find information that the IBase will automatically be updated once a system is maintained in

SMSY. This automatic update is bases on the parameter IB_GEN_AUTO (blank no value) in transaction

DNO_CUST04. Since the SMSY itself will be updated by the LMDB is this way ensured that the IBase

contains updated information about all managed systems.

If you set the parameter IB_GEN_AOTO to X the automatic generation will be stopped and entried for theInstalled Bases and components have to be maintained manually.

For more details about system landscape management in SAP Solution Manager go to service.sap.com/rkt-

solmanSAP Solution Manager 7.1 SAP Solution Manager Setup and Operations Operations of SAP

Solution Manager. There you will find a presentation with details about LMDB, SMSY and SLD.

2.5.6Master Data

After the initial configuration of SAP Solution Manager, you are ready to create the master data relevant for the

Change Request Management scenario. It includes the creation of user and business partner as well as the

system information about the managed systems.


33/129


February 2012 27

2.5.6.1 Business Partner and User

For the Application Change Request Management, there are two types of relevant business partners linked to

System Users in the Solution Manager:

Organization: represents companies/organizations

Person: represents companys employees, such as key users and processors

User and Business partners can be created either automatically or manually.

2.5.6.2 Create User and Business Partner Automatically

There are two options to create User and Business Partner (Key User, Message Processor) automatically.

Option 1will create User as well as Business Partner. Option 2can be used to create only Business Partner

for User of Satellite Systems.

Option 1:Report AI_SDK_USER_BP_GEN

With this report, you generate system users and appropriate business partners in one step in SAP Solution

Manager for users of a SAP managed system:

1. Start transaction SE38.

2. EnterAI_SDK_USER_BP_GEN in the Program input field and choose Execute.3. Select the report execution options.

4. Choose Execute.

The next example shows which execution options should be checked, if you wish to:

o create business partners and system users (by using a reference user)

o update existing business partners

o search for users via existing RFC connections between the SAP Solution Manager and managedsystems of type READ


34/129


February 2012 28

o identify users and business partners by e-mail address

o display all execution details

o execute the report in test mode

Either you create this template User beforehand or you take your existing user. New Users will get same

authorizations.


35/129


February 2012 29

If a user exists in more than one managed systems (e.g. based on e-mail address), the report will create a

SAP Solution Manager user with business partner who is allowed to create tickets for each of the

corresponding managed systems.

For more information on AI_SDK_USER_BP_GEN, please refer to the SAP Help online documentation for

SAP Solution Manager 7.1 SP01 athttp://help.sap.com/.

To find the corresponding documentation more easily, use the search term AI_SDK_USER_BP_GEN.

Option 2:Transaction BP_GEN

Via transaction BP_GEN, you generate business partners in SAP Solution Manager for users of managed

systems.

1. ChooseAdd.

2. Select a system from which you want to create business partners. (e.g SD7)

3. Select users for which business partners should be created and doubleclick on it to add the user to

the list of the selected Users

.

4. Choose Create, as shown below.
http://help.sap.com/http://help.sap.com/http://help.sap.com/http://help.sap.com/


36/129


February 2012 30

5. Select Create

6. Check the Status on the bottom of the screen

2.5.6.3 Create User and Business Partner Manually

To create a business partner for an employee, please proceed as follows:

1. Call transaction BP.

2. Select Create Person.

3. Enter name and address data in theAddresstab.

4. Enter an e-mail address in the area Communicationof theAddresstab.

5. In the Identification Numbers page area of the Identification tab, specify for which systems the

employee is allowed to create incidents / support messages. You have to make an entry of type

CRM001for each target system, as shown in the figure below. The identification number contains data

of the target system in the following format:


37/129


February 2012 31

6. Select the BP role Employee.

7. In the Employee Dataarea of the Identificationtab, assign the employees system user to thebusiness partner.

8. Select the BP role Contact Person.

9. In the Namearea of theAddresstab, enter a language in the Correspondence lang.field.

10. Save your settings.

2.5.6.4 Set up an Organizational Model (optional)

The organizational model reflects the functional structure of your company. It consists of organizational units

which represent how the company is structured in terms of functions and positions which specify how

different functions / tasks are assigned to individual posts.


38/129


February 2012 32

An organizational model can be used in various scenarios. For example, you can represent support teams as

organizational units, which is important for the set-up of support team determination.

For more information on how to set up an organizational model, please refer to chapter 4 (Create

Organizational Model) of the guide Support Team Determination via Business Rule Framework plus (BRFplus)

available in SAP Service Marketplace (http://service.sap.com).
http://service.sap.com/http://service.sap.com/http://service.sap.com/http://service.sap.com/


39/129


February 2012 33

3.Additional Configuration

The last step in the setup procedure is the additional configuration. This covers all the additional functionalities

of Change Request Management that might not be used by every customer or in every landscape situation

some of the most common and most important settings are described in the following sections:

3.1Additional Functions

3.1.1CRM Field Customizing

Impact & Urgency

This field customizing is not part of the Change request management specific IMG but is available via

standard CRM customizing IMG.


40/129


February 2012 34

Define the impact, urgency, and recommended priority levels that you assign to a request for change. The

combination of impact and urgency determines the recommended priority of the transaction.

Define Impact:


41/129


February 2012 35

Define Urgency:

Define what combination of Impact and Urgency results in which recommended Priority:


42/129


February 2012 36

CAUTION:

If the Priority Field should automatically take over the value form the recommended Priority field youmust make sure you do not have customized a default priority value in the customizing for Transaction

Types.


43/129


February 2012 37

Mark Business Activity and double click on Customizing header

Make sure the Default Data for the flied Priority is empty

Risk

Customizing of the values that shall be available in the field Risk is also only available via CRM standard IMGand not part of the Change Request management IMG


44/129


February 2012 38

3.1.2Approval Procedures

The new release of SAP Solution Manager Change Request Management supports so called approval

procedures as part of the process for the Request for Change.

The approval procedure is a small process, which is executed in the status To be approved of the Request

for Change transaction. Customers can define multiple approval procedures in their system and select the

correct approval procedure depending on the type of change, the priority etc

An approval procedure always consists of one or many approval stepseach step is assigned to a specific

business partner function, and later also assigned to a specific business partner.

When you create your approval procedure you can also define which steps can be executed in parallel, and

which steps can only be executed when the previous step was done.

Besides the definition of the approval procedure itself, you can also define rules to determine the approval

procedure or the approver for a step automatically, based on values of the transaction. In general there are

two types of rules:

Approval Procedure Determination

Used to determine, which approval procedure shall be used


45/129


February 2012 39

Approval Step Determination rules

Used to determine, which business partner of the transaction shall be entered as approver of specific

step automatically

Creating a custom approval procedureIn the SAP Implementation Guide follow this path:

SAP Solution Manager Capabilities (optional) Change Management Standard Configuration

Transaction Types Approval Settings Define Approval Settings

You have to go through all the steps listed on the left side of the viewstart by creating a new approval

procedure. You need to define a key-value, a description text (used on the UI) and an approval status profile.

The standard profile is IT000003 and has entries for Approve, Reject and Not Relevant.

The next step is to define how long the approval procedure can be changed by the usereither it is frozen

directly after the initial save, or it will frozen once the approval procedure has been started:

In the next step, you will define the approval steps for your approval procedurein this example a 2-person

approval procedure:

Then you need to assign your steps to your approval procedure. You will also assign the default partnerfunction for this step, as well as the rule modeler profileto be able to define rules for this steps:


46/129


February 2012 40

Note: Make sure to only assign a business partner function which is assigned to your transaction type

otherwise you will get a similar error to:

Change Request Management supports two types of Rule Modeler Profile. It is important to assign the correct

rule profile and also use the correct name for the approval policy as indicated in this table below:

Rule Modeler Profile Approval Policy Comments

AI_CM_AP_STEP AI_CM_CR_RFC_STE Used for step determination

AI_CM_AP_PRO AI_CM_CR_RFC_PRO Used for general approval

procedure determination

If you would like to have a specific step only to be executed if another step was already done before, you also

need to customize the Define Previous Step part:

Finally you can define a new approval determination procedure. For each procedure you can define how to

determine the approval procedure: Either via rulesor via default determination defined in customizing. This

approval determination procedure is later assigned to a transaction type.

In case you want to define rules, make sure to assign the correct Rule Modeler Profile and use the correct

name for the approval policy.

If you want to create an own rule modeler profile, please check the IMG documentation of the activity

In case you want to use only the standard determination procedure, you simply need to add another entry in

the table for Assign Default Approval Procedure

Creation and Management of Rules

Rules can be created and edited in the Web Client UI directlythere is no need to go into the IMG after you

have set up your approval procedures in general.

In the SOLMANPRO Role, choose the entry Service Operations Rules Policies and search for rule

policies of Context Approval Management.

Invalid partner function for approval step Z_STEP_02; has been reset to default


47/129


February 2012 41


48/129


February 2012 42

3.1.3Scope Assignment Block

The Request for Change in Solution Manager 7.1 has a new screen area to define the scope. This new area is

the scope assignment block.In comparison to the Change Request of Solution Manager 7.0 its possible to have multiple follow up

documents. In Solution Manager 7.0 the change request scope was defined through the field subject and the

IBase component, and you could only define one follow up.

The Request for Change in Solution Manager 7.1 offers inside the Scope assignment block the possibility for

several follow up documents also of different types. The field subject is obsolete in Solman 7.1 it was replaced

by the change category of the scope assignment block. For each line item of the scope you have to define a

change category and an ibase component.

To define which change categories are valid you can perform the following customizing.

SAP Solution Manager Implementation Guide - SAP Solution Manager - Capabilities (Optional) - ChangeManagement - Standard Configuration - Change Request Management Framework - Make Settings for

Change Transaction Types:

Add Scope Item

Define ChangeCategory &


49/129


February 2012 43

Choose SMCR Request for Change or your corresponding customer specific request for change and then

double click on Copy Control Rules in the left navigation area.

Here you can define which follow up documents (also your own Z & Y Types) you want to allow in the scope

as change category as well as define which information of the request for change shall be automatically

copied. e.g. priority, text, date, attachments, context. For text and date copy you can define separate mapping

rules in case you want to copy to a specific text or date. You can perform that customizing by double clickingin the left area to text ID Mapping and Dates mapping.


50/129


February 2012 44

CAUTION:

The customizing of the copy control rules only work properly for Z & Y Types if before the CRM Copy

control was performed properly. You can find this customizing under: SAP Solution Manager

Implementation Guide - Customer Relationship ManagementTransactions - Basic Settings - Copying

Control for Business Transactions - Define Copying Control for Transaction Types:

Only documents that are target of SMCR (or Z & Y) here will be allowed in the Change management

copy rules.

3.1.4Transport Management Assignment Block

In change transactions connected to the Change and Transport System you can use various functions from

the Transport Management System. These functions allow you to carry out and monitor transports betweenSAP systems.

Features:

Display and creating of transport requests, test transports, and tasks

Releasing of transport requests and test transports

Display of various information on transport requests, such as the status, whether they contain criticalobjects, or whether there are conflicts

Display of tasks for transport requests: When you choose Display Details, the tasks for the selectedtransport request are displayed in a new screen area.

Navigation to transport requests in connected systems Display of the transport log: The connected system is called automatically to do this.

Customizing activity:Adjust Project Field and Scope in Change Request by Status


51/129


February 2012 45

For example you can customize for which status of an Urgent Change it is allowed to create a Transportrequest and Transport Task.

Example: Here (see Screenshot below) in status E0002 which is In development the button to create a

Transport as well as the button to create a Task should be available. and all other status values E0001,E0004, E0005, etc.) its not allowed and with that the button for creations is not available.

You can use the same customizing option to set other actions/fields to be available status dependent perTransaction type.

CLOSE_TSK_LS close task list

CREATE_REQ create request


52/129


February 2012 46

CREATE_TASK create task

IBASE_COMPONENT I base component field

PROJECT_ID Project ID field

RELEASE_COPY release transport of copies

RELEASE_REQU release original request

SCOPE scope assignment block

3.1.5Landscape Assignment Block

The landscape assignment block shows you all systems of the corresponding task list as an overview.

Usually only the system which is flagged relevant is visible, you can extend that view to see all systems by

pressing the Display All systems button.

You can logon to all systems by clicking on action.

In the customizing you can define which system is flagged to be the relevant system depending on the status

of the change document.

SAP Solution Manager Implementation Guide - SAP Solution Manager - Capabilities (Optional) - Change

Management - Standard Configuration - Change Request Management Framework - Make Settings for

Change Transaction Types:

Mark your Change transaction (e.g. SMMJ) and double click on Specify status Attributes


53/129


February 2012 47

Per E-Status you can define which system role type shall be flagged to be the relevant one.

3.1.6Project, Solution, Document & Test management

Assignment Block

The project assignment block as well as the solution, document and test management assignment block are

all available for the request for change as and for all change transactions. Here you can define which context

shall be linked with a request for change or change transaction.

e.g. here the business process step Create Sales Order was linked as context in the solution assignment

block of an change transaction.

Depending on the transactions type and the status of your document different actions are available to be

performed. To customize this please follow:


54/129


February 2012 48

Available context actions are described below. In the customizing view you can define which context action is

allowed at which status for each which transaction type.

ADDPROJECT Add Project in Project Context

SOLN Add Solution in Solution Context

DELETEPROJ Delete Project in Project Context

DELETESOLN Delete Solution Object in Soln. Context

ADDDOCU Add Document in Document Context

DELETEDOC Delete Document Object in Doc. Context

ADDPROJOBJ Add Project structure object

DELETEPROJ Delete Object

ADDTESTDOC Add test plan or test package in Test WB


DELTESTDOC Delete test plan or test package in Test WB

Note: The customizing of this context action per status comes with Solution Manager

7.1 SP5 only. Before you have not updated to support package 5 the use of all availableactions is not restricted, meaning all context actions are available for all status.


55/129


February 2012 49


STATUSINFO Status Info System in Test WB

TESTREPORT Test Report in Test WB

ADDPROJECT Add Project in Project Context

SOLN Add Solution in Solution Context

DIROBJ Add Structure Object in Solution Context

MAINPROJ Add Maintenance Project in Solution

Context

DELETESOLN Delete Solution Object in Soln. Context

ADDDOCU Add Document in Document Context

DELETEDOC Delete Document Object in Doc. Context

STATUSINFO Status Info System in Test WB

TESTREPORT Test Report in Test WB



DELETEPROJ Delete Project in Project Context

3.1.7SAP WebClient UI Configuration & Personalization

There are several possibilities to configure and personalize the SAP WebClient to fit your organization's specific

business needs. For example, you can change the layout and texting of pages, fields, assignment blocks or tables.

For more information:

WebClient UI Framework:

http://help.sap.com/saphelp_crm70/helpdata/en/4d/2ae3f79e1d49d9be306f7768d55fba/frameset.htm

3.1.8Adding Custom Actions to the SAP WebClient UI

You can add your own actions to the Change Request Management toolbar Actions-Menu in the SAP WebClient UI:

To do so, perform the following:

1. Call transaction SM30 (Maintain Table Views).2. Enter AGS_WORK_CUSTOM as the Table/View.3. Choose Maintain.
http://help.sap.com/saphelp_crm70/helpdata/en/4d/2ae3f79e1d49d9be306f7768d55fba/frameset.htmhttp://help.sap.com/saphelp_crm70/helpdata/en/4d/2ae3f79e1d49d9be306f7768d55fba/frameset.htmhttp://help.sap.com/saphelp_crm70/helpdata/en/4d/2ae3f79e1d49d9be306f7768d55fba/frameset.htm


56/129


February 2012 50

4. For each action, add an entry in the following form:

IM_CRM_UI_PPF_

Example:

IM_CRM_UI_PPF_01 Z_CUSTOM_ACTION_FILTER_01IM_CRM_UI_PPF_02 Z_CUSTOM_ACTION_FILTER_02

Ensure that the actions which you enter here are compatible with the SAP WebClient. Actions which

attempt to carry out any user interaction are generally not compatible with the SAP WebClient. For

example, actions which start SAP GUI functions or launch URLs will not work in the SAP WebClient.

Only manually executable actions will appear in the list. Ensure that the actions are correctly maintained in

your incident action profile, and can be manually started by the user.

Youll find an example use-case, descr ib ing how to m aintain the PPF act ion prof i le in sect ion3.3 o f

th is document .

3.1.9TREX Set-up

TREX (Text Retrieval and Information Extraction) is a powerful engine which provides intelligent search and

automatic classification of documents. TREX search engine is used for full-text search within CRM

documents, such as incidents and knowledge articles. TREX search can be performed in the SAP WebClient

and in the Incident Management Work Center.

For further instructions on how to set up TREX search, please refer to the guide Full-Text Search with TREX

available in the SAP Service Marketplace:

http://service.sap.com/instguides SAP Components SAP Solution Manager Release 7.1 6

Additional Guides

3.1.10 Support Team Determination (optional)

Please refer to the configuration guide of Application Incident Management for more information on how to set

up a team determination.

You will find an overview of existing guides and documentations at the end of this document.

3.1.11 Multilevel Categorization

Multilevel categorization enables you to individually design the categorization of business transactions (e.g.

incidents) on up to 4 levels. It integrates functions such as auto completion, item determination based on

categories and search for related problems, knowledge articles and change requests.

For detailed instructions on how to set up and use multilevel categorization, please refer to the guide Multilevel

Categorizationavailable in the SAP Service Marketplace:

http://service.sap.com/instguides SAP Components SAP Solution Manager Release 7.1 6

Additional Guides
http://service.sap.com/instguideshttp://service.sap.com/instguideshttp://service.sap.com/instguideshttp://service.sap.com/instguideshttp://service.sap.com/instguideshttp://service.sap.com/instguides


57/129


February 2012 51

You can use report AI_CRM_CREATE_CAT_SCHEMAto automatically create an example categorization

schema, which you can adapt for your own purposes. Further details are available in the guide Multilevel

Categorization in SAP Service Marketplace.

3.1.12 Publishing of Saved Search

With SAP Solution Manager 7.1 it is possible to create so called Saved Searches however, those Saved

Searches are personalized for a specific user in standard and cannot be re-used by others.

In case you want to enable your users to share those saved searches with other users, you need to manually

activate a sharing functionality.

More information can also be found in this Blog on the SCM:

http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/12213

3.1.13 Create a system wide text Template

In the Request for Change document as well as for all Change documents you have the possibility to maintain

texts with different Text IDs. Every user can easily create its own text template and re-use it for recurring texts.The disadvantage here is that the text templates are personalized and only available for the users account. If

you want to create a system wide text template, that is available to all users, you have to do the following:

1) Transaction SE61 Document Maintenance

Use Document Class General text choose your language and name your template- then press the "Create"

button to create this new document.
http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/12213http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/12213http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/12213


58/129


February 2012 52

Maintain your Text and save the template. (Package and Transport order will be requested)

2) Transaction DNO_CUST04

Maintain the Fieldname with SDK_MSG_PROC_AUTO_TEXT and fill the Field Value with the name of your

Text template.

3) Use template in transactions


59/129


February 2012 53

For example, open a Request for Change and go to the Text assignment block. Press button Insert Text

Templateto open the following web dialog:

Choose System Template and select your Template.

Press Insert Text.

3.1.14 Create customer specific UI configuration

Before you can start to configure anything in the CRM web UI you have to make sure you have enabled the

configuration mode for your user in the personal settings.

Therefore please press the button in the upper right corner of your CRM UI.


60/129


February 2012 54

In the screen opening please press on Personalize settings

Make sure you have configuration mode enabled

As a result you will find 2 new icons in the shape of a little and a huge spanner in the upper right area of your

CRM UI.


61/129


February 2012 55

If you can see these 2 spanners as part of your CRM UI you can start configuring.

As an example we want to have the fields Impact and Urgency to be mandatory when creating a Request

for Change

Open a Request for Change document and press the little spanner

As a result you will find the Request for Change UI in purple color and an icon of gearwheels in the upper right

area of your screen

If you now click somewhere in on that purple area, the configuration screen will pop up.

Before you start changing the SAP Standard Configuration please copy the configuration into your namespace


62/129


February 2012 56

So now you work on your own configuration which is valid for your Role Configuration Key and the Transaction

Type you were using.

3.1.15 How to define mandatory fields

Please make sure you have created your customer individual UI configuration, before you start to make

changes on the UI configuration (see3.1.14).

To start configuration mark the filed you want to change ( Impact filed) and press the Show Field Properties

button


63/129


February 2012 57

Check the Mandatory flag and press apply

Repeat this last step for the Urgency field, press and save your setting to an

appropriately transport order which is popping up

Switch back from Configuration mode to normal mode by pressing the little spanner again.

As a result you will now find the fields Impact and Urgency additionally marked as mandatory.


64/129


February 2012 58

3.2Customer Specific SetupThis chapter describes the standard Customizing settings. If you want to change the customizing according to

your requirements keep in mind to copy the SAP standard into customer namespace first and make your

changes afterwards.

In the transaction SOLMAN_SETUP you will find one optional step where you can start a copy program which

automates the copying of the ChaRM standard transaction types to the customer namespace.

The transaction copy report provides the following functions

Copies a transaction type into customer namespace

o The copy includes almost all relevant entries including

Status Profile

Action Profile

Data Profile

o The usage of an transaction type is not be copied, these settings must be made manual

DNO_CUST04

Usage in SOLAR01/02 and test workbench

Update a already copied transaction type

Display and transaction type

All customizing which is created with the transaction will be stored on a transport request depending on the

client settings (SCC4)

All entries which are created are written to a log, which is used by the update logic and can be displayed by

transaction AI_CRM_CPY_PTYPE_LOG.

More information about the copy report can be found in section2.3 of this document.

3.2.1 Transaction Type

Transaction types are defined as a set of different configuration settings. This set of configuration settings

represents information and functions within a process. Change Request Management contains many different

processes like Request for Change, Normal Change, Urgent Change or Admin Change. Each of those

processe is defined by an individual transaction type. For example for a Request for Change the Transaction

Type SMCR is defined. Find below a picture showing the available processes in Change Request

Management and the according transaction type.


65/129


February 2012 59

A transaction type defines the attributes and characteristics of a CRM business transaction. E.g. the Request

for Change transaction type SMCR defines the whole customizing for partners, status, text and workflow

action which are needed for the Change Request Management.

The following documentation shows as an example details about the transaction type SMCR.

Call transaction SPRO and open the SAP Reference IMG.

In the IMG activity Define Transaction Typesyou make the settings for a transaction type.

Select transaction type SMCR and press the button Details.


66/129


February 2012 60

The standard settings of SMCR are shown in the figure below.

This screen shows the assigned Profiles and number ranges.


67/129


February 2012 61

SAP recommends you to copy the transaction type (incl. dependent customizing, such as partner or

text schema) into the customer naming space which must begin with Z or Y. This will ensure that

changes will not be overwritten in case of an upgrade.

The recommended name for the SMCR copy is ZMCR. This will prevent some additional customizing

effort, such as adaption of actionsschedule conditions.

You have to specify rules for creating follow-on documents. Via the IMG activity Specify Mapping

Rules for Copy Control you define which follow-on documents can be created from the copied

transaction type and which data the follow-on document should contain. For more information, please

refer to the documentation of this IMG activity.

To copy the Transaction Type SMCR into customer namespace Choose Copy as

Enter the customer namespace ZMCR and a description. Afterwards confirm with Return

Save your changes. Now all assigned standard profiles need also to be copied.

3.2.2 Text Determination Procedure

A text determination procedure is a container for text types, such as description, reply or internal note. It is

assigned to a text object. In Incident Management, the relevant text object is CRM_ORDERH. The text

determination procedure must be assigned to a transaction type which will ensure that the text types can be

displayed in documents.


68/129


February 2012 62

3.2.2.1 General Settings

ProfileSMCR0001 is the standard text determination procedure assigned to the transaction type SMIN. It can

be accessed via the IMG activity Define Text Determination Procedure.

Mark the text object CRM_ORDERH and press the folder Procedure on the left side.

Choose from the result list the text profile SMCR0001.

The next figure shows the settings of the text determination procedure SMCR0001.


69/129


February 2012 63

SAP recommends you to copy SMCR0001 into the customer naming space (which must begin with Z or Y).

This will ensure that changes will not be overwritten in case of an upgrade.

The recommended name for the copy is ZMCR0001.

3.2.2.2 Rich Text Formatting

This section explains how to activate the rich text editor in the SAP WebClient. It enables you to edit texts in a more

powerful way e.g. by using fonts (such as bold or italics), copy and paste functions or text alignment.

There are two ways to activate rich text formatting:

via IMG: rich text formatting is activated for all users

via user parameter: user specific rich text activation

To activate the rich text editor for all system users, please do the following:

1. Start transaction DNO_CUST04.

2. Switch to Changemode and choose New Entries.

3. Enter the following data:

Field Name:AI_CRM_TXTEDIT_HTML

Field Value: X

Description: Activation of Rich Text Editor in WebUI


70/129


February 2012 64


To activate the rich text editor for a specific user, please do the following:

1. Start transaction SU01.

2. Switch to Change mode Navigate to the tab Parameters.

3. EnterAI_CRM_TXTEDIT_HTMLas Parameter ID and Xas Parameter value, as shown in the figure below.


After you activated the rich text editor, buttons for rich text formatting should be available for editing texts in incidentsand problems, as shown in the figure below.


71/129


February 2012 65

3.2.3 Partner Determination Procedure

A partner determination procedure specifies which business partners are involved in the business process, for

example, a sold-to party (partner function 00000001). The partner determination is executed separately foreach partner function. The partner determination procedure must be assigned to the corresponding business

transaction to ensure the correct display and processing of the business partners.

The relevant partner determination procedure for the Request for Change is SMCR0001.

SAP recommends you to copy the partner schema SMCR0001 into the customer naming space (which

must begin with Z or Y). This will ensure that changes will not be overwritten in case of an upgrade.

The recommended name for the copy is ZMCR0001.

Via the IMG activity Define Partner Determination Procedureyou define and configure a partner determination

procedure. You specify how a business partner is determined and which partner functions are included in the

schema. Furthermore, you are able to define which partner functions should be displayed in the header data of

incidents in the work center.

The figure below shows the default partner functions for a Request for Change.


72/129


February 2012 66

By scrolling the table shown above to the right you will see further details like an access sequence that can be

assigned to partner function and ensure that partner identifications are determined automatically when

creating or processing a Request for Change.

3.2.4 Status Profile

A status profile is a container of user statuses which specify the individual status of an object, such as a

Request for Change or a Normal Change. For example, a Request for Change could have the status To be

Approved.

3.2.4.1 General Settings

Via the IMG activity Define Status Profile for User Status, you define and configure the Status Profile.


73/129


February 2012 67

The default status profile for the transaction type SMCR is SMCRHEAD. The figure below shows the standard

customizing settings of SMCRHEAD.

By specifying a lowest or highest status number, you can control the transition from one status to another.


74/129


February 2012 68

Example:

The status In Processhas the lowest status number 20 and the highest status number 50. This means,

that when this status is active, only a status with a number between 20 and 50 may be activated, i.e. T

87077245 charm configuration guide

Documents