How to configure SAP Solution Manager 7.

2 - Change
Request Management with SOLMAN_SETUP

Purpose
Overview
Mandatory Configuration: System Preparation
Mandatory Configuration: Infrastructure Preparation
Mandatory Configuration: Basic Configuration
Managed Systems Configuration
Embedded Search
Change Control Management: Change Request Management
Change Control Management: Managed System Setup
Related Content
Related Documents
Related Notes

Purpose
This document will focus on the different guided procedures and activities that you need to complete to get the Change Request Management
(ChaRM) scenario correctly configured for SAP Solution Manager 7.2.

Screenshots are taken from a SAP Solution Manager 7.2 SP06 system.

Overview
There are several activities in different guided procedures that needs to be performed to get the Change Request Management scenario correctly
configured.

Mandatory Configuration: System Preparation, Infrastructure Preparation, Basic Configuration

Managed Systems Configuration
Embedded Search
Change Control Management: Change Request Management, Managed System Setup

See in bold letters in the sections below the activities that are really important for the Change Request Management scenario.

Note: Add the end of each guided procedure there is a Complete step from you can download in a pdf file the documentation of each activity in each step
of the guided procedure.
Mandatory Configuration: System Preparation
Needs to be performed entirely after the SAP Solution Manager 7.2 system has been installed or upgraded from SAP Solution Manager 7.1.

After installing a new SP/FP it is necessary to update the indicated activities that have “Updates Needed” flagged.

1. Define System Role

Depending of the number of the Solman systems in your landscape decide your role, in the case that you have a single Solman system in your landscape
the above three flags needs to be selected.

2. Check Prerequisites

3. Set Up Connections to SAP

Only 3.1 is required in ChaRM, for using the SAP Note Download SAPOSS, SAP-OSS and SAP-OSS-LIST-O01 are created.

4. Apply Essential Corrections

5. Maintain Technical Users

Mandatory Configuration: Infrastructure Preparation

1. Set Up Landscape Management

Define the connections to system landscape directories (SLD) that are used with SAP Solution Manager.

The LMDB synchronizes with the SLD to collect the following information from the system landscape:

CIM model
SAP software catalog (SAP CR content)
Technical system landscape descriptions

2. Set Up Java Connectivity (Step 2.3 is not required)

3. Set Up SAP BW

5. Set Up E-Mail Communication

6. Configure CRM Basics (Set up of the Installed Base (IBase))

7. Enable Gateway services

Mandatory Configuration: Basic Configuration

1. Configure Basic Functions

Setup Extractor Framework

Activate Piece Lists

After installing a new SP/FP you need to run this activity again to get the latest standard customizing. This piece list contains the default
configuration for Change Request Management. The SAP default customizing will be copied from client 000 to your logon client from where you
call solman_setup and overwrite only SAP customizing. This activity has no effect on customer configuration and has to be run after each
Support Patch import.

Because of this it is VERY IMPORTANT that you copy all change documents transaction types into your own namespace or <Z>, <Y>
namespace using copy report AI_CRM_CPY_PROCTYPE.

If you do not do this your modifications to the standard will be overwritten if you activate the piece list after a support package application.

However for the cycle transaction types the recommendation is to use the standard transaction types as usually these cycle transaction types
are not modified. If you need to modify them use also the copy report but some additional settings are required in the phase modeler to use this
new cycle transaction types.

Activate ICF Services

Work Centers Query Refresh
Generate Business Partner Screen

2. Schedule Jobs
Pay attention to job SM:TMWFLOW_CMSSYSCOL (report /TMWFLOW/CMSSYSCOL2): Program for collecting data of transports, notes and support
packages of each System defined in table /TMWFLOW/CMSCONF using asynchronous RFC-function calls, scheduled daily.

3. Configure Manually

Business Partner for Scenario Users

Schedule Application Log Cleanup
Clear Caches for Launchpad

4. Create Basic Dialog Users

Managed Systems Configuration

With the Managed Systems Configuration, you connect the required systems to SAP Solution Manager, by default you will see the Solman ABAP system
and the Solman Java system:

To configure the Solman system for this test case in the Technical Systems tab select the system and click on System Operations->Maintain system. This
will open the system in LMDB where you can create the RFC connections in Destination-> RFC Maintenance.

For ChaRM scenario you will need to create the RFC destinations from Solman to the systems in your managed landscape where you want to control the
software changes via Change Request Management.

Change Request Management requires a READ, TMW and TRUSTED RFC to every Managed System/Client.

For Change Request Management scenario you don´t need to create any connections from the managed system to the Solman system unless you want to
use CSOL or Retrofit functionalities.
Embedded Search

Change Control Management: Change Request Management

Needs to be performed entirely after the SAP Solution Manager 7.2 system has been installed or upgraded from SAP Solution Manager 7.1.

After installing a new SP/FP it is necessary to update the indicated activities that have “Updates Needed” flagged.

1. Perform Basic Setup

With the settings in this step you could be able to test the scenario.

1.1. Check Prerequisites

This step checks whether the activities required under System Preparation and Basic Configuration have been completed, before you continue to configure
Change Request Management.

Check Solution Manager Central Correction Note

Check Piece List Activation
Check LMDB Configuration
Check Background Jobs
Check Service Activation
Set Client for Change Request Management

Change Request Management can only be configured in one client of the Solution Manager system.

Activate ICF Services

Check and Set Up Number Ranges
Check SAP Connect Configuration
Check Customizing

1.2. Implement Master Note

ChaRM master note contains the most critical known corrections. You should also check the note status in SNOTE periodically so that newer versions can
be downloaded and applied as soon as possible.

1.3. Finalize Step

You can now start the Managed System Setup guided procedure. It guides you through the configuration of a managed system landscape (generally a
sandbox landscape) under the control of Change Request Management. From here, you can begin to test in the WebClient UI (transaction SM_CRM) with
the standard transaction types.

2. Set Up Downgrade Protection and Retrofit

In these steps, you can make global settings for the following extended functions provided by Change Request Management.

Also call the Managed System Setup scenario to locally define the system-specific behavior of CSOL, DGP, and Retrofit in Step Configure Extended
Function.

2.1. Configure CSOL and DGP

2.2. Configure Retrofit

2.3. Finalize Step

3. Define Change Process

In the substeps, you can configure the change processes according to your requirements.

You configure the transaction types that you want to use in Change Request Management.

SAP delivers default Customizing for its transactions types, which could potentially be updated with each new shipment (support package). For you to be
able to customize the transaction types according to your individual needs while remaining independent of SAP shipments, we recommend that you copy
the transaction types (for request of changes, change documents that you want to use in your customer namespace, use always the copy report
AI_CRM_CPY_PROCTYPE.

Note: After installing a new SP/FP you should update the already copied transaction types with newly shipped SAP standard configuration. Only
transaction types that have been created with this copy report can be updated.

You can decide whether the transaction type is to be displayed in the WebClient UI by selecting CRM UI in the Channel column. If you choose None, the
selected transaction type is not displayed in the WebClient UI.

In activity Assign Implementation to Change Transaction Types, you can assign an Implementation Class, specify the Text Object ID used for logging and
the Document type used as search criteria. These values are filled automatically when you have used the copy report AI_CRM_CPY_PROCTYPE.

Note: Don´t copy the cycle transaction types, SMIM, SMAI, SMRE, if you are not making changes to these transaction types as some additional settings
are required to use them.

For testing ChaRM scenario only the activities in step 3.1. Copy Transaction type are required.

In the other Substeps 3.2 - 3.16 all required activities to change this standard are required: copy control, status management, PPF actions, Text
management, Date management, Approval procedures, create customer variants, multilevel categorization, define transport risks, …

Pay attention to:

3.5. Set Up E-Mail Notifications: Mail forms needs to be created and PPF E-mail actions activated

3.6.Set Up Business Partners: A business partner with employee role needs to be created for any user working with ChaRM documents: developers,
testers, IT operators, change managers.. you can use bp_user_gen for this or create the users and business partners manually.

4. Configure User Interface

In this step, you can configure the WebClient UI of Change Request Management according to your requirements.

4.1. Define Shared Memory for WebClient UI

4.2. Define UI Configuration Option

4.3. Copy and Adapt Business Role

4.4. Configure WebClient UI

4.5. Implement Dialogs in WebClient UI

4.6. Adapt Translation of UI Texts

5. Define Settings for Template Users

In this step, you can create and update template users and their authorization roles with the help of an automatic tool. We recommend that you use
template users as a reference or a template when generating Change Request Management users in the SAP Solution Manager productive system.
6. Define Reporting

7. Configure Search Infrastructure

In this step, you configure the infrastructure that is necessary for the users of Change Request Management to be able to search in the Change Request
Management objects.

8. Integrate Additional Functions

8.1. Enable Solution Document Integration

8.2. Integrate Project Management

8.3. Integrate IT Calendar

8.4. Integrate Job Scheduling Management

9. Employ Additional Use Cases

Enable Mandatory Transports

Enable Optional Scope Items

Change Control Management: Managed System Setup

1. Configure LMDB

The systems that you want to managed via ChaRM need to be known for the SAP Solution Manager system, need to be known by the LMDB, so a
technical system is created for them.

Ensure that the systems are registered to the SLD of the Solman system.

2. Select System

Select the system for what you are going to perform the following activities.

3. Check Software Prerequisites

ST-PI is a plug-in in the managed system providing a major application programming interface (API) for interacting with SAP Solution Manager. We
recommend that you patch it with the latest version.

To enable the full functionality of cross-system object lock checks, downgrade protection, white list object checks, critical object checks, and custom
checks, you have installed SAP Note 2402504 and the latest ST-PI onto the managed systems.

General note for managed systems in change management (SAP Note 1703391) provides information about recommended SAP Notes on the managed
systems.

4. Configure Change and Transport System

You need to configure the CTS of the managed system landscape, for example, transport domain, transport layer, and transport routes. All these activities
need to be done in the transport domain controller of the managed system landscape.

In most of the case you have already a TMS managed landscape in place and you only need to ensure that this landscape fulfills the ChaRM requirements.

4.1.Configure Transport Management System

Define Transport Domain Controller

Activate Extended Transport Control

CTC must be 1 for single ABAP stack systems and dual stack systems; for stand-alone non-ABAP systems, set CTC to 0.

Define Transport Routes

- Transports are supported in the standard transport layer of each client. When you configure transport routes, only consolidation routes that
are assigned to the standard transport layer of the relevant exporting client are taken into consideration. For each exporting client, one target
client and one target group are permitted.

- Assign one development system to a production system, and connect these two systems by one transport track.

- If a development system and a production system are connected by more than one transport track, this may lead to transport distribution
inconsistencies. This type of transport configuration cannot be supported by Change Request Management, and may cause inconsistencies in
the tools involved.

- Since client transport control is active for the managed systems, all transport routes must be client-dependent. When building the
consolidation route, choose a transport layer. If you have multiple target systems starting from one source system, you can use the transport
target group, which is also supported by Change Request Management.

- If you have more than one development system/client, please make sure all of the transport layer settings are configured correctly here,
otherwise ChaRM may not be able to calculate the transport tracks based on your STMS configurations

- SAP no longer supports the "SAP” transport layer. For more information, see SAP Note 1401611.

- Ensure that you have defined consolidation transport routes from the development system (source system role for ChaRM project) to the first
quality system (target system role for the ChaRM project), and delivery transport routes from one target system to another and from the last
target system to the production system (Production system role for the ChaRM project).

- If you are using Harmonizing RFC communication infrastructure (see note 1384598 for details), the users triggering the release/import actions
in the Solman system need to exist in the target system:client of the managed landscape with the same name and have trusted authorization
(S_RFC* authorization objects) and release/import authorizations. This user should have at least the authorization profile S_TMW_OPERA; role
SAP_CM_MANAGED_OPERATOR will contain both necessary authorizations.

- If you are not using Harmonizing RFC communication infrastructure, the old infrastructure with domain links will be used (see note 913232),
and then the users triggering the import action to the managed landscape will need to exist in client 000 of the target system with import
authorizations .

Create RFC Destination to Domain Controller

Establish an RFC connection from SAP Solution Manager to the domain controller of a read RFC connection in any client.

Configure Transport Strategy

- Deactivate the quality assurance (QA) approval procedure

- Activate the "Single Transports" strategy

Note: This prevents you from accidentally executing "Import All", full lorry icon will disappear.

Set Project Assignment of Requests as Mandatory

If you required that all transport requests created in the managed development system has a CTS project as mandatory, then make this configuration.

Map Systems in LMDB

Go to LMDB and ensure that under Transport Domains tab you can see the transport domain of your managed landscape.

Also for the ABAP systems tab you need to see your ABAP systems. While ABAP systems are automatically assigned to the LMDB and can be used
immediately, you have to make manual settings for non-ABAP and virtual systems.

Distribute CTS Plug-Ins to Managed Systems

This is required if you want to user Central Change and Transport System (central CTS) scenario to manage non-ABAP system landscape and
Downgrade Protection scenario.

Configure CTS Status Switch

When you create a cycle for a managed landscape, a CTS project is created automatically for each of the development systems and clients that act as
source systems in the landscape. By default, the CTS status switches are closed.

Copy System for Pre-Production System

4.2 Configure Enhanced CTS (non-ABAP)

CTS+ is the prerequisite of using Change Request Management for non-ABAP managed systems landscapes.

Define TMS for Non-ABAP and Dual Stack

Map Non-ABAP Systems in LMDB
Conf. RFC Destinations to TMS Communication System
Install CTS Plug-In in TMS Communication System

4.3 Configure Central CTS

In this step, you configure the central Change and Transport System (central CTS).

4.4 Implement Business Add-Ins

BAdI: Change Short Text for Transport Request

BAdI: Change System When Creating Transp. Requests

5. Select Client

6. Check System Prerequisites

RFC needs to be created to the managed system:clients, this is done in LMDB, •READ, TMW, and TRUSTED RFC are created.

A configuration item, IObject, is required for each managed system:client. This is the master data for representing the managed system in SAP Solution
Manager used in LMDB (Landscape Management Data Base) and all change processes.

7. Create User Master Data

In this step, you create the user master data required for your scenario in both the managed system and the SAP Solution Manager.

7.1. Create Managed System Template Users

7.2. Create Users in Managed System

7.3. Create Users in Solution Manager

8. Configure Extended Function

We recommend that you perform the corresponding global configuration in Step Set Up Downgrade Protection and Retrofit of the Change Request
Management guided procedure to ensure that these local settings will take effect.

8.1. Configure CSOL and DGP

Activate CSOL in Managed Systems

Configure Track-Specific CSOL
Configure Downgrade Protection
Check Cross-System Object Lock RFC Connection
BAdI: Implement CSOL BAdI

8.2. Filter Scope Items

8.3. Configure Retrofit

8.4. Define Selective and Status-Dependent Import

8.5. Define Critical Objects

8.6. Set Up Transport-Related Checks

9. Create Landscape and Change Cycle

 Configure Solution Landscape
Check and Assign Logical System
Create and Maintain Branch
Create and Maintain Change Control Landscape
Create Change Cycle (Change Req. Management Only)
Create Scenario (Quality Gate Management Only)
Set up Release Planning

Related Content

Related Documents
Solman_setup documentation in each activity.
First steps to work with Change Request Management scenario in SAP Solution Manager 7.2
How to create a solution for Change Request in 7.2
How to create a virtual system in SAP Solution Manager 7.2

Related Notes
SAP Note 2316974 - General note for Change Request Management ST 7.2
SAP Note 2402504 - ChaRM: Back RFC Check Support
SAP Note 1703391 - General note for managed systems in Change Management
SAP Note 1384598 - Harmonizing RFC communication infrastructure in ChaRM/QGM