How to Guide, change management, ALM, Solution manager

8/10/2019 How to Guide, change management, ALM, Solution manager

1/67

Change Request Management

How to Guide for ALM RDS Service

Applicable Releases:

SAP Solution Manager 7.1 SP 10

SAP Solution Manager Scenarios:

Change Request Management

Version 1.0

July 2014


2/67

Copyright 2014 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 forerrors 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/67

Document HistoryDocument Version Description

1.0 First version of this guide (10.07.2014)


4/67

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 the

documentation.

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/67

Table of Contents

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

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

1.2 Target Group ................................................................................................................ 1

1.3 Content ......................................................................................................................... 1

1.4 Related Documentation ................................................................................................ 2

1.5 Prerequisites Skill Set of delivery resource .................................................................. 2

1.6 Technical & organizational prerequisites at customer site ........................................... 2

1.7 Organizational Prerequisites ........................................................................................ 3

2. Standard Configuration ...................................................................................................... 4

2.1 Prerequisites ................................................................................................................. 4

2.1.1 Required Activities .............................................................................................. 4

2.1.2 Basic Configuration SAP Solution Manager ....................................................... 4

2.1.3 Piece List Activation ........................................................................................... 6

2.2 Initial Setup ................................................................................................................... 7

2.2.1 Create three clients for demo landscape on SAP Solution Manager ................. 7

2.2.2 Check Prerequisites ........................................................................................... 9

2.2.3 Note Implementations ........................................................................................ 9

2.2.4 Basic Setup of ChaRM ..................................................................................... 11

2.2.4.1 Transport Management System .................................................................. 11

2.2.4.2 Maintain number ranges .............................................................................. 18

2.2.4.3 Activate Integration with Change Request Management ............................ 21

2.2.4.4 Create Template Users in SOLMAN_SETUP (Optional) ............................ 232.2.4.5 Set up Roles and Authorizations (out of scope) .......................................... 23

2.2.4.6 Activate Solution Manager Services ............................................................ 28

2.3 Copy Transaction Types ............................................................................................. 30

2.3.1 Copy Transaction Types via Report ................................................................. 30

2.3.2 Manual Adaptation............................................................................................ 35

2.3.3 Adopt Copy Control Rules ................................................................................ 35

2.3.4 Enhance CRM Copy Control ............................................................................ 36

2.3.5 Specify Status Settings for Predecessor Documents....................................... 36

2.3.6 Specify Required Status Values for Successor ................................................ 37

2.4 Master Data and landscape definition ........................................................................ 38

2.4.1 Create RFC destination to managed systems ................................................. 38

2.4.2 Managed System information (IBase) .............................................................. 40

2.4.3 Business Partner .............................................................................................. 41

2.4.3.1 Business Partner and User .......................................................................... 41

2.4.3.2 Create User and Business Partner Automatically ....................................... 41

2.4.4 Create/ Define a SAP Solution Manager Project and activate ChaRM ............ 45

3. CMA CGM Specific Configuration .................................................................................... 56

3.1 Maintenance Cycle - Status Check before Go-Live ................................................... 56

3.2 Solution Documentation Integration ........................................................................... 583.3 Pre and Post Import Activities (PS0) .......................................................................... 61


6/67

Change Request ManagementHow to Guide

SAP AGS CoE EMEA ALM 1

1.General Information

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

SPS10 at CMA CGM.

1.1 Change Request Management Overview

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 CRM UI 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 and could

be used.

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 CRM UI. 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 Target Group(Technical/ Application/ Support) Consultants who will perform the ALM RDS Service for Change Request

Management.

1.3ContentThis setup guide contains the following activities / configuration steps:

Verify basic config incl. piecelist activation

Create or verify number ranges

Configure basis set up for Change Request Management

Set up RFC Connections in system landscape

create logical components in system landscape

Set up involved systems as I-base

Set up SMI, IMG and CTS Projects

Set up project landscape and activate task list

Set up CRM process flows for

o Urgent correction

o Regular correction

o Admin change

o Defect message

Additional Information for Master Data

Issue related FAQs


7/67



1.4Related DocumentationSAP Documentation

http://help.sap.com/saphelp_sm71_sp01/helpdata/en/4c/3acb82b50843b4e10000000a42189e/content.htm

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

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

available in SAP Service Marketplace.

1.5 Prerequisites Skill Set of delivery resource Training: SOD00 mandatory (E2E200 recommendable)

Knowledge of "SMSY " maintain solution and project (mandatory)

Study of material from Alias /rkt-solman ->Solution Manager 7.1 -> complete chapter ChangeRequest Management (advisable)

One-time joint delivery of a ALM RDS Service with dedicated delivery resource (recommendable)

Study of this document (mandatory)

Knowledge of the IMG nodes for Change Request Management (given structure can be differentdepending on SP level)

Knowledge about CRM UI (definition of business roles)

1.6 Technical & organizational prerequisites at customer

site Customer has installed and configured SAP Solution Manager 7.1 at the latest Support Package.

SAP Component CTS plug at the latest Support Package

Solution Manager Starter Pack and Solution Manager Preparation Service (SMPS) has already beendelivered (basic Settings)

Customers Solution Manager runs at least on a two system landscape, development and productivesystem. (https://service.sap.com/sap/support/notes/952859)

A triple copy of the Solution Manager client was executed in the Solution Manager Developmentsystem so the hard drive of the system must provide enough space. (If the copy was not performedby the customer, please follow the instructions in chapter2.2.1)

Access to 000 client of the Domain controller system of SolMan DEV system

Open SAP remote connection (R/3 support & http) of SolMan DEV system for back office support is

provided

Meeting room for the entire time of the service onsite time

Users with SAP_ALL, SAP_NEW and RFC_ACL authorization in all clients (Solution Managerworking client, 801, 802, 803, 000) is provided.

OSS connection established to load relevant SAP notes

Clarify who should be responsible for implementing SAP Notes (SAP Consultant or Customer)

Wifi or wired internet connection for SAP team to connect with back office

Possibility to open SolMan DEV system logon on SAP laptops or customer Laptop/Desktop available
http://help.sap.com/saphelp_sm71_sp01/helpdata/en/4c/3acb82b50843b4e10000000a42189e/content.htmhttp://help.sap.com/saphelp_sm71_sp01/helpdata/en/4c/3acb82b50843b4e10000000a42189e/content.htmhttp://help.sap.com/saphelp_sm71_sp01/helpdata/en/4c/3acb82b50843b4e10000000a42189e/content.htm


8/67



1.7 Organizational Prerequisites The involvement of members from the customer support organization (recommended: members of

business, members of IT, SAP system administrator, Owner of Change Management processes)during the on-site visit is crucial for the successful know how transfer and has to be ensuredbeforehand with relevant SAP contacts.

During onsite visit technical and non-technical topics will be discussed. Based on this the audiencemight be different which should be taken into account and clarified when discussing the agenda.


9/67



2.Standard Configuration

2.1 PrerequisitesThe steps described in this chapter2.1 should already be finished by the basis team before the ALM

RDS service starts.

2.1.1Required Activities

Implement or verify the correct implementation of central SAP Solution Manager Note depending on the SP

level of the Solution manager system.

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

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 basic

configuration, you set up the connection to SAP, schedule relevant background jobs and activate

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


10/67



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.

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


11/67



2.1.3Piece List Activation

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. This procedure is described in a later chapter.

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/67



2.2 Initial SetupThe following activities need to be done by the support consultant (or together with customer basis team).

2.2.1Create three clients for demo landscape on SAP SolutionManager

Create the clients 801802803 in your Solution Manager System to Simulate a Transport landscape (DEV-

QAS-PRD)

1. Create Client

1.1. Transaction SCC4 to create a new Client1.2. Log off from the system1.3. Logon to the newclient with user SAP*, password PASS

2. Copy Client (Requirements You have logged on to the new client with user SAP*)

2.1. Transaction SCCL2.2. Use the following parameters:

Profile : SAP_CUST (if disk capacity is an issue, otherwise you can choose SAP_ALL)

Source: Client 001

If wanted the existing users can be copied from the working client with profile SAP_USER.

The creation of transport routes and rfc destinations is described in a later chapter.

001


13/67



Create Transport Requests to store/trasport the configuration.7.1 SP10 RDS ITSM-ChaRM


14/67



2.2.2Check Prerequisites

In the SOLMAN_SETUP > Change Request Management > Check Prerequisites, select Execute All.

All checks should be green.

Click Next when completed.

2.2.3Note Implementations

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.

Consider enough time for the note implementation since also manual activities need to be performed.


15/67



Master Notes:

1860446 Master Note for Change Request Management 7.10, SP10

General Notes:

1703391 General note for managed systems in Change Management

1574224 General note for Change Request Management ST 7.1

Review carefully the manual activities and stick to the sequence above!

Download, implement and execute the post-processing activities for the ChaRM Master Note.

Click Next when completed.


16/67



2.2.4Basic Setup of ChaRM

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 five individual tasks

1. Transport Management System

2. Maintain number ranges

3. Activate Integration with Change Request Management

4. Set up Roles and Authorizations

5. Activate Solution Manager Services

2.2.4.1 Transport Management System

Make sure that your transport domain has been configured correctly. (see transaction STMS -> Help ->

Application Help -> Configuring TMS).

The existing TMS configuration for the Solution Manager working client should be available and not be

changed. Only additional entries for simulation clients should be created.

Activating Extended Transport Control

1. Call transaction STMS.

2. Choose Overview-> Systems.

3. Double-click system.

4. The Display TMS Configuration: System screen appears.

5. Select the Transport Tooltab page.

6. If the entry CTCdoes notappear in the Parameterscolumn, enter it there, and then in the Valuecolumn,

enter 1.

7. Save your entries.


17/67



Configuring the Transport Strategy

In the transport tracks where the software distribution is controlled by Change Request Management, you

must deactivate the QA approval procedure in the TMS, since this procedure is incompatible with the approval

procedure in Change Request Management. Additionally, activate the "Single transports" strategy. This

prevents you from accidently executing "Import All". All transports within the system landscape of Change

Request Management must be processed by project imports. Proceed as follows:


2. Choose Overview-> Transport Routes.


4. The Display System Attributesdialog box appears.

5. In the Transport strategygroup box, select Single transports(since only Import Singleand Import Project

Allare used).

6. In the Quality assurancegroup box, deselect Delivery after confirmation.

7. Choose Continue.


18/67



Check TMS Parameters


2. Choose Overview-> Systems.

3. Double-click system.4. The Display TMS Configuration: System screen appears.

5. Check if the Parameters are set as follows.

CTC 1

IMPORT_SINGLE_ONLY 1

IMPORT_SINGLE_STRATEGY 1

NO_IMPORT_ALL 1

WORKFLOW_STRATEGY 0


19/67



Activate TMS Trusted Services for all involved transport domain

Logon to domain controller system client 000 -> Transaction STMS -> System Overview -> Goto -> Transport

Domain -> Go to tab Management -> Security Options -> Set Trusted Services to Active -> Save and distribute

the configuration change

The TMS Trusted Services is used by ChaRM to remotely trigger the transport on managed systems. You

have to activate this service on all domain controller systems which might be involved in ChaRM processes.

If the information from the IMG activity Harmonization of RFC Infrastructure is relevant for your

managed system you do not need to execute this IMG - activity. You can proceed with the next IMG -

activity.

Create Transport Layer

STMS ->Transport Routes -> press display change Button -> Edit -> Transport Layers -> press Create

Maintain Transport layer ZTSTTransport Layer for ChaRM Test


20/67




21/67



Create Transport Route

STMS ->Transport Routes -> press display change Button -> Edit -> Transport Route -> press Create

1. set cursor to entry Transport Routes-> press Create2. activate the Extended Transport Control (pressF6)

3. create Consolidation:

4. set cursor to entry Transport Routes-> press Create

5. activate the Extended Transport Control (pressF6)

6. create Delivery:


22/67



Assign Transport Layer to Client

The Transport Layer you created before has to be assigned to the Development Client (801) of your

Simulation Landscape.


2. Choose Overview-> Transport Routes.


4. The Display System Attributesdialog box appears.

5. Choose the Tab Standard Transport Layer

6. Create new Entry on Client level for 801 and the Transport Layer.

7. Save and distribute


23/67



Setting the Mandatory Project Assignment

Call transaction SE03.

UnderAdministration, double-click Display/Change Request Attributes.

Double-click the attribute SAP_CTS_PROJECT, make sure that in the client specific settingsyou have anentry for 801 (client Numbers of your Development system simulation) and Requiredmarked. Dont activate

this parameter system-wide.

2.2.4.2 Maintain number ranges

If number ranges are already maintained please review and correct them if required.

Call transaction SNUM

1. Specify the object/tmwflow/m.

2. Choose Number Ranges.

3. Choose Change Intervalsand then Insert Interval.

4. For the new interval, enter 01, and use the F4 Help function to select a value for the From Numberfield.

The system returns 000000001 to 999999999.

5. Choose Insert, and then Save.


24/67



6. Repeat these steps 1 to 5 for object/tmwflow/d.

7. Repeat these steps 1 to 3 for object/tmwflow/v and enter 01 for the new interval. Use F4 value help to

choose a value for the field From Number.

The system returns 00000000000001 to 99999999999999.

Also check if the number range object for CRM_SERVIC is setup correctly.


25/67



For CMA CGM the following number ranges have been customized:

Request for Change ZMCR 50000000005999999999

Urgent Change ZMHF 90000000009999999999

Normal Change ZMMJ 60000000006999999999

Admin Change ZMAD 70000000007999999999

General Change ZMCG 70000000007999999999

Defect Correction ZMTM 80000000008999999999


26/67



2.2.4.3 Activate Integration with Change Request Management

Call transaction SPRO and navigate to the basic configuration for Change Request Management

Call the IMG activity Activate Integration with Change Request Management.

Perform the three subtasks.

Task 1: Activate Change Request Management and Set-Up Client

Task 2: Integration Solution Manager


27/67



Task 3: Integration Change Request Management

After finishing all steps you should see the following screen.


28/67



2.2.4.4 Create Template Users in SOLMAN_SETUP (Optional)

The below activities have not been performed for CMA CGM.

SOLMAN_SETUP -> IT Service Management -> Change Request Management -> 3.5 Create Template Users

Create user accordingly in simulated managed system

User SOD / 001 SOD / 801 SOD / 802 SOD / 803

CH_REQ_SOD XCH_DEV_SOD X X X

CH_CM_SOD X X X X

CH_OPRT_SOD X X X X

CH_TEST_SOD X X

CH_ADM_SOD X X X X

2.2.4.5 Set up Roles and Authorizations (out of scope)

The below activities have not been performed for CMA CGM.

Review the documentation for details about standard roles provided. Call PFCG and assign the roles to the

system user.

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

Copy standard PFCG composite roles to customer namespace.


29/67


30/67



Roles Z_CM_DEVELOPER_COMP, Z_CM_CHANGE_MANAGER_COMP, Z_CM_TESTER_COMP,Z_CM_OPERATOR_COMP, Z_CM_REQUESTER_COMP, Z_CM_ADMINISTRATOR_COMP copied.


31/67



Make sure you adopt the content of the roles accordingly to your copy

Include ZXXX, YXXX to the roles:


32/67



Business Roles and Authorizations

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

Solution Manager, SAP provides the predefined business role SOLMANPRO for SAP Web Client

configuration 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 Note Authorization for Service Desk Release 7.1

1436270 Collective Note Authorization Solution Manager Release 7.1


33/67



2.2.4.6 Activate Solution Manager Services

Call the IMG activity or transaction SICF_INST and activate the following services.

SM_CHARM

SM_CRM_UI


34/67



Successful activation

You have now finished the basic setup for Change Request Management.


35/67



2.3Copy Transaction Types

2.3.1Copy Transaction Types via Report

As part of step 3 in SOLMAN_SETUP for Change Request Management there is a link to the 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.

You can also call the copy report directly via SE38. Execute report AI_CRM_CPY_PROCTYPE.

Define source and target transaction type as shown below.

SMCR (Request for Change)

Also change the description of the target.


36/67



Perform the copy for the following transaction types.

SMAD (Admin Change)

Click on Start Copying Process


37/67



Logs should be green.

SMCG (General Change)


38/67



SMHF (Urgent Change)

SMMJ (Normal Change)


39/67



SMTM (Defect Correction)

Overview of Transaction Types copied:


40/67



2.3.2Manual Adaptation

Go to the following customizing path in SPRO:

SAP Solution Manager -> Capabilities (Optional) -> Change Request Management ->

Change Request Management Framework -> Make Settings for Change Transaction Types

Select Transaction Type ZMMJ.

Select the action Define Execution Time of Consistency Checks and add the following customizing.

ZMMJ ZMMJHEAD E0009 60 1 Final Execution TR_REQUEST

ZMMJ ZMMJHEAD E0012 20 1 Final Execution PRELIM_PRD_NOT_IMP

ZMMJ ZMMJHEAD E0013 5 1 Final Execution DGP_CHECK_OK

ZMMJ ZMMJHEAD E0013 10 1 Final Execution PRELIM_TR_IN_PRD_BUF

2.3.3Adopt Copy Control Rules

Go to the following customizing path in SPRO:



Then copy all the TP Types to the Z_Namespace to ensure that the workflow offers the copied transactions.


41/67



2.3.4Enhance CRM Copy Control

To enhance the CRM Copy Control please go to the following IMG path:


Transactions -> Copy Control -> Define Copying Control for Transaction Types

Then copy the Target Transaction Types in a customer namespace (ZNAMESPACE).

2.3.5Specify Status Settings for Predecessor Documents

To accomplish this step, please go to the follow IMG Path:




42/67



Choose the Transaction Type (must be done for all the Transaction Types), Enter in each User Status(e.g.

E0008). Click on Specify Status Settings if there are a Standard Transaction Type, copy it to a Z Namespace

as well the field StatProf.

As in the workflow of Change Request management, follow-up documents status change can influence the

status settings of the predecessor documents this settings need to be adapted from Sap Namespace to

Customer Namespace (Z_Namespace).

Additional Information: The influencing action that triggers this predecessor documents status change is

SET_PREDOC.

2.3.6Specify Required Status Values for Successor

To accomplish this step, please go to the follow IMG Path:

SAP Solution Manager -> Capabilities (Optional) -> Change Management -> Standard Configuration ->


As a Request for change, can have more than one follow-up documents it is necessary to restrict that the

follow-up document does only influence the status of the request for change if all other follow-up documents

that were created in parallel contain a minimum status.

Like this, it is ensured that only the last follow-up document reaching a final status will set the status of the

request for change


43/67



2.4Master Data and landscape definition

2.4.1Create RFC destination to managed systems

The below activities have been performed by CMA CGM as prerequisite for the service.

Call transaction SOLMAN_SETUP

Navigate to the area for Managed System Administration.

Press Configure System

Press the button Next until you reach the point Connect Managed Systems.

Select the client which represents the development system. E.g. 801 and mark the checkbox for READ, TMW

and TRUSTED RFC as shown in picture below.

Maintain the SAP Solution Manager user that you are using for the configuration in the field SAP SOLUTION

MANAGER ADMINISTRATOR and the same one in the field for MANAGED SYSTEM ADMINISTRATOR.


44/67



Ensure that the user in managed system has the authorization object S_RFCACL assigned.

Press button CREATE to generate all RFC destination for this client.

Repeat this procedure for all the other clients including client 000 for SAP Solution Manager.

Now you are ready to create logical components as described within the next chapter.


45/67



2.4.2Managed 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. Navigate to

the Technical Setting and further to the IBase.

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.

Please also check Note 1741109 for IBase generation, if the automatic generation fails.

Task:Go to IB53 (or IB52) and check whether all entries for the SAP Solution Manager or Managed System

are available (all clients should be listed)In case there are entries missing call transaction IB_GEN to generate IBase entries for selected systems.


46/67



2.4.3 Business Partner

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.

2.4.3.1 Business Partner and User

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

SAP Solution Manager:

Organization: represents companies/organizations

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

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

2.4.3.2 Create User and Business Partner Automatically

There are two options to create User and Business Partner 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 partnerso search for users via existing RFC connections between the SAP Solution Manager and managed

systems of type READo identify users and business partners by e-mail addresso display all execution detailso execute the report in test mode


47/67



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

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 SP03 athttp://help.sap.com/.

To find the corresponding documentation more easily, use the search term AI_SDK_USER_BP_GEN.
http://help.sap.com/http://help.sap.com/http://help.sap.com/http://help.sap.com/


48/67



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. For the ALM RDS Service you have

to choose NONE since you want to read data from the SAP Solution Manager itself.

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

the list of the selected Users.


49/67



4. Choose Create.

5. Select Create

6. Check the Status on the bottom of the screen


50/67



2.4.4Create/ Define a SAP Solution Manager Project and activate

ChaRM

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 defined

and 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 LMDB.


51/67



Call LMDB and navigate to Logical Components.

Enter a new Logical Component name and click Create.

Logical components are based on product version. Choose a product by clicking on Maintain.

Assign some Technical Systems.

All clients are defined.

801 Development System, role Source System

802 Quality Assurance System, role Target System

803 Production System, role Production System

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


52/67



Call transaction SOLAR_PROJECT_ADMIN. Press the button Create Project.

For CMA CGM the project CM_ADV_SSC has been created already and will be used.

Find below the generic procedure.

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

Maintain a Title and choose a language.


53/67



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.

Important: Since in this pilot scenario the IMG project will be created at the SAP Solution Manager you

need to create this IMG project manually in order to maintain a different name then the Solution

Manager project.


54/67



Go to the tab IMG project and select the row with the development system. Press the create button at the

lower left corner and maintain a name for the IMG project (e.g. Z_CHR01). Answer the question for the

creation of a transport request with No Later.

After the successful creation of the IMG project you will automatically jump to client 801. Go back and continue

as described in this guide.


55/67



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

Confirm the pop-up window.


56/67



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


57/67



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

The user who performs the creation of a task requires a business partner which is assigned to his system

user.

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

button Create Task List.

Define a name for the Task List and confirm.


58/67



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 the

right mouse button or use the task Lock/Release Transport Tracks incl. Role Types.

Example: Unlock task with right mouse button


59/67



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.

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.


60/67



Before you start using ChaRM you need to ensure that all required master data (Ibase and BP) is available.


61/67



3.CMA CGM Specific Configuration

3.1Maintenance Cycle - Status Check before Go-Live

Use case: How to prevent the Maintenance Cycle to be switched to phase Go-Live unless all the Defect

Corrections (ZMTM) have the status Confirmed?

To enhance the Maintenance Cycle please go to the following IMG path:



Select the SMMN transaction type, then select the menu Specify Status Attributes, select the line to be

modified (status E0006Go Live) and finally select the menu Specify Required Status Values for Successor.

Note: The general SAP recommendation is to copy the standard transaction types to the customer

namespace. However, due to the several technical dependencies with SMMN (Maintenance Cycle), it is

recommended to not copy this transaction type. Thus all the customizing done in this transaction type might be

lost after a new activation of the Piece List (Check 2.1.3 Piece List Activation).


62/67



Add the above customizing entry.

In the activity Assign Consistency Checks, change the behavior of the consistency check for the following line:

E0006 20 SUB_ITEMS SOCM_ACTION_LOG A Cancel E0009

Change the value Warning to Cancel if the check has to be handled as an error and to reset the status to

Preparation for Go-Live (E0009).


63/67



3.2Solution Documentation IntegrationUse case: How to create a Change Transaction directly from the Business Blueprint (SOLAR01/02)?

In the SPRO, go to Implementation/Upgrade > Blueprint and Configuration > CRM Transaction Types >Restrict Business Transaction Types.

Add the required entries.


64/67



Go to transaction DNO_CUST04.

Add the above entry.


65/67



In the SOLAR02, select a business process step, then go to the Service Messages tab, it is now possible tocreate/add a Change Transaction (type ZMCR).


66/67



3.3 Pre and Post Import Activities (PS0)Some customizing activities are non-transportable and thus will need to be performed in the Production

System (PS0).

The following procedure can serve as a basis for the cutover of ChaRM in productive SAP Solution ManagerPS0:

2.1 Prerequisites (all activities)

2.2.2 Check Prerequisites

>>> Import of the workbench and customizing transports with IMPORT_SUBSET (selecting the two

transports and importing together)

DS0K900013 and DS0K900015 - 7.1 SP10 RDS ITSM-ChaRM

2.2.3 Note Implementations

2.2.4 Basic Setup of ChaRM

2.4 Master Data and landscape definition (all activities)


67/67


www sap com

2014 SAP AG or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any

form or for any purpose without the express permission of SAP AG.The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain

proprietary software components of other software vendors. National product

specifications may vary.

These materials are provided by SAP AG 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 with

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

How to Guide, change management, ALM, Solution manager

Documents

Transcript of How to Guide, change management, ALM, Solution manager