Contents

1 Introduction............................................................................................................................. 10
1.1 Objective............................................................................................................................ 10
1.2 Assumptions...................................................................................................................... 10
1.3 Configuration Prerequisites................................................................................................10
2 SAP Solution Manager Architecture......................................................................................12
2.1 SAP Solution Manager Architecture...................................................................................12
2.2 Managedstems.................................................................................................................. 13
3 Change Request Management Setup....................................................................................14
3.1 SOLMAN_SETUP.............................................................................................................. 14
3.2 Step 1: Perform Basic Setup..............................................................................................16
3.2.1 Check Prerequisites....................................................................................................16
3.2.2 Implement Master Note...............................................................................................17
3.3 Step 2: Setup downgrade protection and retrofit................................................................17
3.3.1 Configure CSOL and DGP..........................................................................................18
3.3.2 Configure retrofit......................................................................................................... 19
3.4 Define change process......................................................................................................19
3.4.1 Copy transaction types...............................................................................................19
3.4.2 Define copy control.....................................................................................................22
3.4.3 Define status management.........................................................................................23
3.4.4 Define PPF actions.....................................................................................................24
3.4.5 Setup e-mail notifications............................................................................................25
3.4.6 Setup business partner...............................................................................................26
3.4.7 Define text management.............................................................................................26
3.4.8 Define date management............................................................................................26
3.4.9 Define approval procedures........................................................................................26
3.4.10 Define change request management actions..............................................................27
3.4.11 Make settings for task lists..........................................................................................28
3.4.12 Maintain multilevel categorization...............................................................................28
3.4.13 Define processing log.................................................................................................29
3.4.14 Define risks/impact/urgency recommended prio.........................................................29
3.4.15 Define transport risks..................................................................................................30
3.5 Configure user interface.....................................................................................................31
3.5.1 Define shared memory for WebClient UI....................................................................31

Copyright 2017 - Accenture Proprietary and Confidential 8/10/21

Page 2 of 42
 3.5.2 Define UI configuration option.....................................................................................32
3.5.3 Copy and adapt business role....................................................................................33
3.5.4 Configure WebClient UI..............................................................................................34
3.5.5 Implement dialogs in WebClient UI.............................................................................36
3.5.6 Adapt translation of UI texts........................................................................................36
3.6 Define settings for template users......................................................................................37
3.6.1 Create template users................................................................................................37
3.7 Define reporting................................................................................................................. 39
3.7.1 BW Reporting: Define extraction settings....................................................................39
3.7.2 BW Reporting: Choose transaction type f. reporting...................................................40
3.7.3 Change Request Management reporting....................................................................41
3.8 Configure search infrastructure..........................................................................................41
3.9 Integrate additional functions.............................................................................................42
3.9.1 Enable solution document integration.........................................................................42
3.9.2 Integrate project management....................................................................................42
3.9.3 Integrate IT calendar...................................................................................................42
3.9.4 Integrate job scheduling management........................................................................42
3.10 Employ additional use cases..............................................................................................43
3.11 Complete........................................................................................................................... 44
4 STMS setup............................................................................................................................. 45
4.1 Activate Extended Transport Control.................................................................................45
4.2 Configure Transport Strategy.............................................................................................46
5 CHARM – Managed system setup.........................................................................................47
5.1 Configure LMDB................................................................................................................ 47
5.2 Select System.................................................................................................................... 48
5.3 Check software prerequisites.............................................................................................48
5.4 Configure Change and Transport System..........................................................................49
5.4.1 Configure Transport Management System.................................................................50
5.4.2 Configure Enhanced CTS (Non ABAP).......................................................................55
6 Landscape Definition in Solution Manager...........................................................................57
6.1 Create the Solution............................................................................................................ 57
6.2 Create Logical Component Group.....................................................................................57
6.3 Assign Technical System...................................................................................................58
6.4 Create Change Control Landscape....................................................................................59
7 Change Cycle Definition in Solution Manager......................................................................60

Copyright 2017 - Accenture Proprietary and Confidential 8/10/21

Page 3 of 42
 7.1 Create Change Cycle.........................................................................................................60
7.2 Create Task List................................................................................................................. 61
8 Charm Administration Cockpit..............................................................................................64
9 SAP Roles and Users.............................................................................................................. 66
9.1 SAP Roles......................................................................................................................... 66
9.2 Set Up users and partners.................................................................................................66
9.3 User List............................................................................................................................. 67
10 Transport Request List.......................................................................................................68
11 Additional Functionalities...................................................................................................69
11.1 Schedule Import Jobs........................................................................................................ 69
11.2 Create Virtual Systems......................................................................................................71
12 Appendix TR Import Landscape.........................................................................................72
12.1 Appendix TR Import Landscape.........................................................................................72

Copyright 2017 - Accenture Proprietary and Confidential 8/10/21

Page 4 of 42
Area: Solution Manager

Copyright 2017 - Accenture Proprietary and Confidential 8/10/21

Page 5 of 42
1 Introduction

1.1 Objective

The objective of this document is to describe the steps followed to configure Change
Request Management functionality in SAP Solution manager application.

This guide explains the technical configuration performed to implement Change

request management for Company TTF/TTF charm implementation project.
Functionalities are described in deliverable
AP322_ChaRM_Company_Functional_Design_TTF_TTF .

1.2 Assumptions

This document covers only the steps performed for the configuration of the Change
Request Management.

Following assumptions have been made to implement the configuration:

 Change request management will be used for TTF/TTF project activities.

 Solution Manager 7.2 version will be used
 Installation and post installation steps performed by Company IT team
 TMS transport layer defined by Company IT and Technical Architecture Team

1.3 Configuration Prerequisites

Following activities are prerequisites for Charm configuration and were performed by
Company IT and Technical Architecture teams. Most of them are executed from
transaction SOLMAN_SETUP and are out of the scope of this document since are
performed by other teams:

 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 notes and
web service configuration.
 Infrastructure Preparation: Configuration of the SAP Solution Manager
Landscape and landscape components. In this step, you set up the
synchronization of the system landscape directories (SLDs) and SAP Solution
Manager, to keep the information about the system landscape up-to-date.
 Basic Configuration: 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.
8/10/21

Page 6 of 42
 Managed System Configuration: 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 it is required to execute at
last following steps of the wizard setup:
1. Assign Product
2. Check Prerequisites
3. Maintain RFCs
 STMS Configuration: TMS Domain controllers must be properly defined before
integration with Charm. Specific setup for Charm is explained in a specific
section in this document
 Administrator User: New user as copy of SOLMAN_ADMIN was created by
Company IT team to perform Charm configuration steps.

8/10/21

Page 7 of 42
2 SAP Solution Manager Architecture

2.1 SAP Solution Manager Architecture

Two SAP Solution Manager 7.2 environments were created for this project:

 Development box.
o Used for the build and testing of Charm functionality.
o Connected to all Dev and Test TTF/TTF systems
o System Details:
 SID: AA1
 Application Server:
 Instance Number: 13

 Production box.
o Configuration performed in development box is transported to this
environment.
o Connected to all TTF/TTF SAP systems
o In this environment are generated the Charm objects that will be used
by TTF/TTF project team members to manage SAP Transport Requests
o System Details:
 SID: AA9
 Application Server:
 Instance Number: 23

SAP Solution Manager Transport Route screenshot:

2.2 Managed Systems

SAP Solution Manager systems are connected to Company central SLD, this is
mandatory to keep Systems information in Solution Manager up to date. SLD
architecture is out of the scope of this document.

8/10/21

Page 8 of 42
Company TTF and TTF SAP full landscape picture is as below (it includes more
systems that the ones in scope for this project but useful to have an overall view).
Screenshot extracted from TTF_System_Landscape:

Regression Test environment is not planned at this point, in case of be included in the future
landscape could be added to the Charm TTF and TTF solution without impact in the projects.

Note that for SAP Convergent Mediation and Opentext Document Presentment no CTS+ can be
implemented due to technical incompatibility. SAP best practices for import/export the solution
in this landscape will be followed, Charm Documents type Administrative Changes (will be used
to track all changes performed for this scenario).

8/10/21

Page 9 of 42
3 Change Request Management Setup

3.1 SOLMAN_SETUP

SOLMAN_SETUP transaction is a wizard which allows configuring the system in a

guided and automated way. This tool allows an easy and fast step-by-step
configuration of solution Manager.

It includes Mandatory and optional steps. In this document only the ones executed
have been included.

Some of the configuration steps are transportable, so implemented in Development

environment, saved in SAP Transport Requests and transported to Production. Other
type of changes is in client or manual configuration that must be performed manually in
each environment.

Steps to start configuration:

1- Log on to SAP solution manager in SAP GUI.

2- Start Transaction SOLMAN_SETUP.
3- Access to Change Control Management Section.

Automatic basic configuration consists in follow wizard configuration steps, it is a

graphical guide including most activities within SPRO for Change Request
management configuration.

SPRO transaction  SAP solution Manager  Capabilities (Optional) 

Change Management

8/10/21

Page 10 of 42
3.2 Step 1: Perform Basic Setup

In this step, you lay the groundwork for further configurations that you can define in the
subsequent steps.

Performing the basic setup enables you to execute a dry run and test all basic standard
function of Quality Gate Management (QGM), Change Request Management and
Requirements Management.

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

3.2.2 Implement Master Note

In this step, you download and implement the master Charm SAP Note 2356468. This
SAP Note contains corrections that are implemented both manually and automatically.

Note that the availability and behavior of note implementation actions depends on the
system role that you selected for this SAP Solution Manager system.

8/10/21

Page 11 of 42
Central note was implemented in AA1 and transported to AA9. See SAP Transports
section with the details about transport number

3.3 Step 2: Setup downgrade protection and retrofit

In these steps, you can make global setting for the extended functions provided by
Change Request Management according to Transport Management best practice:

 Downgrade protection (DGP)

 Cross-system object lock (CSOL)
 Retrofit

You can perform these steps early in the setup process as you may want to test or
productively apply these functions in some scenarios without using change processes.

3.3.1 Configure CSOL and DGP

In this step, you configure the cross-system object lock and downgrade protection for
your scenario.

See below screenshot with steps executed, default SAP configuration for CSOL and
DGP was saved:

3.3.2 Configure retrofit

Out of scope

3.4 Define change process

In the following substeps, we can configure the change processes according to the
requirements.

8/10/21

Page 12 of 42
 3.4.1 Copy transaction types

A transaction type defines the attributes and characteristics of a CRM business

transaction. Each process has its own transaction type.
SAP recommends that to copy the transaction types (including dependent customizing,
such as partner or text determination procedure) 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, and also to keep the standard transaction as a reference.
The typical transaction types involved in Change request management procedure are:

Based on the current requirements for Change Request Management configuration

following transaction types will be used and copied:

 ZMMJ For Project Normal Changes as copy of SMMJ – Normal Change

 ZMAD For Project Non SAP Transport Changes as copy of SMAD – Admin
Change

Click on EDIT mode from Step 3 in wizard to navigate to transaction type copy tool.

From the open window, the transaction type to be copied is selected:

For example, SMMJ  ZMMJ

Execute transaction copy and a new popup will appears with all the components that
will be copied:

8/10/21

Page 13 of 42
Copied transaction types have been included in transport request and moved from AA1
to AA9.

Repeat same steps for any Transaction Type that should be copied.

Number Ranges

Number ranges intervals were created and assigned to the copied transaction types
ZMMJ and ZMAD:

3.4.2 Define copy control

In these activities, you configure the required and optional setting for using copy control
in your scenario. You specify valid combinations of source and target transactions
along with the data to be copied.

Steps executed with the default values:

3.4.3 Define status management

In this step, you adapt the status profiles.

A status profile is a container for user statuses that specifies the status of a transaction.

Status Profile ZMMJHEAD updated with the ones defined in deliverable

AP322_ChaRM_Company_Functional_Design_TTF_TTF:

Changes were performed in development environment and transported to AA9 trough

TR.

3.4.4 Define PPF actions

In this step, you control the status changes in change transaction and change cycles
with Post Processing Framework (PPF) actions. Whenever the status of a transaction
8/10/21

Page 14 of 42
changes, certain actions have to be carried out such as “Go to Tasklist”. These actions
are either performed automatically when a change is saved, or you have to carry them
out explicitly.

No change in the default configuration was made

3.4.5 Setup e-mail notifications

In this step, you configure the setting required for e-mail notifications.

 You have activated the following switches in transaction SFW5:

o CRM_IC_CEBP
o CRM_SHSVC

 In Customizing for SAP Solution Manager (SPRO) under Customer

Relationship Management  Marketing  Marketing Planning and Campaign
Management  Personalized Mail  Maintain Attribute Contexts for Mail
Forms, you have selected the following entries:

o Attribute Context: SERVICE REQUEST

o Marketing Attributes: All Marketing Attribute Sets
o Type: SQM Service Request Management

Mail notification no implemented since is not part of the requirements.

3.4.6 Setup business partner

In this step, you configure the settings for partner processing. You can define partner
functions and access sequences, as well as determinate the use of custom partner
functions.

Default SAP configuration, no changes performed.

8/10/21

Page 15 of 42
 3.4.7 Define text management

In these steps, you configure all the settings related to text management in your
scenario.

Default SAP configuration, no changes performed.

3.4.8 Define date management

In the following activities, you define date types, durations and date rules. You assign
the date profile to a transaction type.
Default SAP configuration, no changes performed.

3.4.9 Define approval procedures

You can define approval procedures for requests for change, change documents,
business requirements, and IT requirements.
No implemented since Request for Change functionality is out of scope

3.4.10 Define change request management actions

In these activities, you make the settings for Change Request Management actions
and consistency checks.
Change Request Management actions run the Post-Processing Framework (PPF)
action (HF_SET_STATUS) depending on the user status. Whenever the status of a
transaction changes, certain actions have to be carried out. These actions are either
performed automatically when a change is saved, or you have to carry them out
explicitly.

Default SAP configuration, no changes performed.

8/10/21

Page 16 of 42
 3.4.11 Make settings for task lists

In these activities, you can enhance task lists.

Default SAP configuration, no changes performed.

3.4.12 Maintain multilevel categorization

In these activities, you make the settings for multilevel categorization.

Default SAP configuration, no changes performed.

3.4.13 Define processing log

In this step, you can make the processing log settings for change transactions.

Default SAP configuration, no changes performed.

3.4.14 Define risks/impact/urgency recommended prio

In these activities, you make the setting for risks, impact, urgency, priority and priority
of dates.

Default SAP configuration, no changes performed.

3.4.15 Define transport risks

In these activities, you make the required settings for displaying transport risks on the
Landscape assignment block in the WebClient UI.

Executed with the default SAP values, no changes performed.

8/10/21

Page 17 of 42
3.5 Configure user interface

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

3.5.1 Define shared memory for WebClient UI

In these activities, you define the shared memory for WebClient UI objects.
It confirms that the shared memory area is large enough to allow buffering of the
WebClient UI objects and certain background jobs are scheduled to set shared object
areas.

Steps executed with default SAP values.

3.5.2 Define UI configuration option

In this step, you define the WebClient UI configuration.

If any transaction types have been copied into the customer namespace, the activity
Copy UI Configuration into Customer Namespace has to be carried out as well.
Executing all activities allows you to have a customized UI layout for the transaction
types in your customer namespace.
Background: All transaction types of change request management make use of two
major UI components. In addition, the UI configuration option allows a dynamic display
of various UI layouts for corresponding transaction types.

Steps executed but no changes performed in the configuration since there are no
changes in the Layout configuration. Will use SAP Standard fields without
modifications, no new fields have been created.

8/10/21

Page 18 of 42
 3.5.3 Copy and adapt business role

In this step, you copy and adapt the SAP CRM business roles to your needs.
SAP CRM business roles are the central object to package the main business content,
authorizations, as well as logical and navigations links needed for the end user to
perform a specific job function.
The business role defines which functions and links the end user of Change Request
Management can access via the WebClient UI. We only provide "SOLMANPRO" as the
only standard business role, while in practice, every user role should have its own
predefined role. Therefore, we recommended that you copy the standard
SOLMANPRO business role to several custom roles in your customer namespace and
individually adapt them.
As navigation links or authorizations might be subject to change over time, you should
compare and possibly adapt your business roles to the standard business roles
whenever necessary.

Copied Standard Business Role SOLMANPRO to ZSOLMANPRO, this was executed

in development environment and transported to Production. This business role will be
assigned to End Users to determine Webclient UI that they will access.

3.5.4 Configure WebClient UI

In this step, you configure the display of the WebClient UI.

You can also enhance its performance.

8/10/21

Page 19 of 42
Updated business role ZSOLMANPRO to adapt WebClient UI, the purpose is hide
functionalities not in scope for transport management. For example the ones linked to
Incident Management or Request for Change.

As a prerequisite for the configuration, it is required for the administrators to enable the
configuration mode as described below:

1.On your WebClient UI start screen, choose Personalize.

2.Under Settings, choose Personalize Settings.
3.Select Enable Configuration Mode and choose Save.
4.Result: The system displays two new icons at the top of your screen, Show
Configurable Areas and Configure Page.

SAP Default Webclient UI:

Adapted Webclient UI

3.5.5 Implement dialogs in WebClient UI

In these activities, you make the required settings for implementing dialog boxes in the
WebClient UI.
Steps executed with default SAP values, no changes performed.

8/10/21

Page 20 of 42
 3.5.6 Adapt translation of UI texts

In this step, you can adapt the translation of user interface texts in the SAP system.
The transaction should be used only for custom texts, and with utmost care.
In general, SAP recommends the following:
If you find an incorrect translation in your system, report the error in an OSS message,
using component XX-TRANSL-<language>. SAP will provide instructions on how to
make the correction. The translation will also be corrected for the next Support
Package.

Steps executed with default SAP values, no changes performed.

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

3.6.1 Create template users

In this optional step, you can create standard users in the SAP Solution Manager
system.
If you use BI Reporting, you need additional standard template users in the BW system
/ client. If your BW system is in the same client as SAP Solution Manager, the relevant
roles are assigned to the standard user in the SAP Solution Manager system.
You have the following options:
 Create New User: the system creates the new user and the corresponding
business partner, if necessary, and assigns the relevant copied and SAP roles.
 Provide Existing User: if you update an existing user, the system assigns the
relevant copied roles and SAP roles to an existing user. If you have selected
Accept Manually Created User Without Checking Roles Assignment, roles are
not assigned to the mentioned user.
 Update User Roles: the system assigns the relevant copied and SAP roles to
the selected current user ID.
8/10/21

Page 21 of 42
  Update Password: you assign a new password to the selected current user ID.

In Advanced Mode, the following functions are available to you:

 You can assign a user group to a user while creating or updating the user.
Select User Group and enter a user group. The system adds the user group to
the user in User Maintenance (transaction SU01).
 You can make your own namespace available globally as a default namespace.
 You can create a new user group. Choose Maintain User Group to start
Maintain User Groups (transaction SUGR).

Step executed in Development environment to create Z*roles as copy of the Standard

SAP ones, see security section with the list of roles created.

3.7 Define reporting

In this step, we provide configuration spots for two reporting options (BW reporting and
Change Request Management reporting).

3.7.1 BW Reporting: Define extraction settings

 You prepare BW reporting for Change Request Management in two steps.

 BW Settings

8/10/21

Page 22 of 42
  By choosing Activate BW Content, you trigger a background job to prepare
all BW objects that are required by the BW reports. You need to complete
this step before you continue with the Extraction Settings.
 Extraction Settings
 Enter the extraction parameters and choose Save. This automatically
adjusts the extraction settings.
Step executed with default values:

3.7.2 BW Reporting: Choose transaction type f. reporting

In this step, you specify which transaction types are to be included in the report.
All available change transaction types are listed in the table.
Activated for Z* transaction types in use:

3.7.3 Change Request Management reporting

In this step, you configure the reporting services for Change Request Management.

Executed with SAP defafult values, no changes performed.

3.8 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.
The search infrastructure includes the configuration of the Embedded Search, the
enhancement of the standard search (full-text search) and the setup of TREX.
Not required since there is no TREX connected to SAP Solution Manager.

3.9 Integrate additional functions

8/10/21

Page 23 of 42
Integrate additional functions
In this step, you define the integration of additional functions.

3.9.1 Enable solution document integration

In this step, you can enable the integration of solution documentation.

SAP Solution Manager 7.2 allows you to change and release solution documentation
with the control of change documents. You can perform and release changes in the
software as well as in the solution documentation synchronously.

3.9.2 Integrate project management

In this step, you configure the settings for integrating SAP Portfolio and Project
Management (SAP PPM) with your scenario.

3.9.3 Integrate IT calendar

In these activities, you configure the settings for integrating the IT calendar into your
scenario.

3.9.4 Integrate job scheduling management

In this step, you can manage and document in detail the background processing of
your entire system landscape.

You can:

* Document the jobs of your entire system landscape centrally

* Import jobs with their scheduling parameters from managed systems into job
documentation
* Schedule jobs in managed systems from job documentation
* Configure and document the monitoring of jobs in Business Process Monitoring
* Set up job control for your managed system
You can call the application from the respective work center or SAP GUI.

Steps described in section 3.9 not executed since functionalities are not in scope.

3.10 Employ additional use cases

In this step, the Customizing provided allows you to react to additional use cases and
system upgrades.

8/10/21

Page 24 of 42
You can define settings for the following features:
* Enable mandatory transports.
* Enable optional scope items.

Steps not executed since they are not required for functionality in Scope.

3.11 Complete

Summary of executed steps

8/10/21

Page 25 of 42
4 STMS setup
Mandatory Configuration performed by Technical Architecture and Company IT teams
for the whole SAP Landscape.

Steps in SPRO under transport management System contain information about the
important activities to be implemented in STMS in satellite system. Main steps
performed as prerequisite for Charm implementation:

 Domain Controller Definition

 Add New Systems to Domain Controller
 Setup Transport Parameters
 Define Transport Routes

Notes:

 Consolidation routes must be created between Dev and Test system

 Rest of the routes created are delivery routes.
 In case more than one system or clients are required as target, transport group
is required. (New transport groups can be created in Edit  Transport target
group  Created)
 All routes must be client specific.

4.1 Activate Extended Transport Control

In order to use Charm for Transport Management, Extended transport protocol need to
be activated.

Transaction STMS, systems overview.

1- Double- Click on each system.

2- In transport tool tab, include parameter CTC with value =1

4.2 Configure Transport Strategy

In this activity, following actions are implemented:

 Deactivate the quality assurance (QA) approval procedure

 Activate the "Single Transports" 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

8/10/21

Page 26 of 42
 Management. Additionally, you have to activate the "Single transports" strategy. This
prevents you from accidentally executing "Import All". All transports within the system
landscape of Change Request Management must be processed by project imports.

1- In transaction STMS – transport routes –

2- Double click on each system

 Ensure that single transports option is selected

 In the Quality assurance group box, deselect delivery after confirmation

NOTE: Steps described in 4.1 and 4.2 section must be executed for all the SAP
systems integrated into the TMS layer of TTF and TTF.

8/10/21

Page 27 of 42
5 CHARM – Managed system setup
These configuration steps describe how to integrate satellite systems into SAP Solution
Manager Charm Solution

5.1 Configure LMDB

In this step, we check whether the managed system we need to configure is already
available in the landscape management database (LMDB). How to update LMDB is
managed by Company IT team and out of scope of this document.

It is mandatory that Transport Domain are properly updated in LMDB, they will contain
the TMS configuration:

5.2 Select System

Indicate system for which you need to perform the Charm integration

5.3 Check software prerequisites

In this step, you can check the software prerequisites for the selected managed
system. Especially important that ST-PI component is properly implemented. That
activity is responsibility of Technical Architecture team.

5.4 Configure Change and Transport System

In this step, we configure the change and transport system (CTS) of managed systems.

Although there is only one selected managed system in this guided procedure, you can
configure the entire managed system landscape that you want to connect to Change
Request Management.

If you have already configured the CTS of the managed system landscape as
explained in section 4, you can skip the step.

8/10/21

Page 28 of 42
Example: You usually only need to execute all configuration steps for all managed
systems in the transport domain controller. In general, this is the development system.
As a result, you don’t need to redo it in the quality assurance and productive systems.

NOTE: Configuration steps described in this section must be executed for all the SAP
systems integrated into the TMS layer of TTF and TTF.

5.4.1 Configure Transport Management System

Define Transport Domain Controller

Activity performed as part of installation steps of each new environment. Out of scope
of this document

Activate Extended Transport Control

Activities

 Call transaction STMS.

 Choose Overview -> Systems.
 Double-click each system.
 The Display TMS Configuration: System <system ID> screen appears.
 Select the Transport Tool tab page.
 If the entry CTC does not appear in the Parameters column, enter it, and in the
Value column, enter 1.
o CTC must be 1 for single ABAP stack systems and dual stack systems;
for stand-alone non-ABAP systems, set CTC to 0.
o Save your entries and distribute the configuration change.

8/10/21

Page 29 of 42
Define Transport Route

Activities

 Log on to the domain controller system.

 Choose transaction STMS.
 Choose Transport Routes.
 Go to change mode, and configure the transport routes and transport layers
according to your landscape and requirements.
 Save and distribute the configuration changes.

Create RFC Destination to Domain Controller

RFCs are created as part of Managed Systems Configuration steps by Company IT.

Configure Transport Strategy

8/10/21

Page 30 of 42
In this step we activate the "Single Transports" strategy.

Activities

Proceed as follows:

 Call transaction STMS on the domain controller system.

 Choose Overview -> Transport Routes.
 Double-click each system.
 The Display System Attributes dialog box appears.
 In the Transport strategy group box, select Single transports (only Import Single
and Import Project All are used).
 In the Quality assurance group box, deselect Delivery after confirmation.

Set Project Assignment of Requests as Mandatory

For each system in which you want to create transport requests, you have to set the
project assignment of CTS requests to mandatory.

Activity can be performed in URL indicated in Solman wizard or in transaction SE03 in

the manage system.

Configure CTS Status Switch

Activities

 Choose Change CTS Status Switch.

 For your system, open the CTS status switch and perform the desired action.

5.4.2 Configure Enhanced CTS (Non ABAP)

In this step, we make the required settings for the change and transport system (CTS)
for non-ABAP systems
8/10/21

Page 31 of 42
Define TMS for Non-ABAP and Dual Stack

Activities

For non-ABAP systems, create the system in the domain controller client 000 of the
system that you use as a communication system. Choose transaction STMS → SAP
System → Create → Non-ABAP System.

Conf. RFC Destinations to TMS Communication System

In this activity, we configure the RFC destinations between the SAP Solution Manager
and the TMS communication system of non-ABAP target systems to execute TMS
transports. The configuration is needed as import commands of TMS transports into
non-ABAP target systems are sent to the TMS communication system.

For each non-ABAP target, you need to identify the associated TMS communication
system in transaction TMS of the respective TMS domain.

For each TMS communication system, you need to create the SAP Solution Manager
RFC destinations.

In TTF/TTF scenario have been agreed to use AA9 (SAP Solution Manager Production
system) as communication system for all Non ABAP environments.

Install CTS Plug-In in TMS Communication System

Plug-In installation in AA9 managed by Company IT.

8/10/21

Page 32 of 42
6 Landscape Definition in Solution Manager
Very Important remark: solution, branches, logical component groups, system roles
etc... will represent the TMS Real Landscape, TMS is always the master of this data.

6.1 Create the Solution

The solution should contain the complete customer system landscape, processes, and
solution documentation in a customer's business.

Technically, a solution is the root of a structure that contains all of those objects.

In transaction /nslan we created the solution TTF_TTF_SOLUTION that will contain all
the SAP landscapes linked to Charm functionality:

6.2 Create Logical Component Group

With this object we define SAP landscape that must be aligned with TMS configuration.
With this information and the system role function, it allows to determine the correct
target system, for example the quality or development system.

Will be created one LCG per SAP Solution Landscape and Stack.

6.3 Assign Technical System

For right charm functionality, Logical Component Group always must have a
Development and a Production Environment defined.

Following structure will be created along TTF/TTF project:

NOTE: Since most of Non-development environments are not available yet Technical
Systems required will be created as Virtual Systems in TMS and LMDB. Virtual
systems will be replaced by the real ones once they are available.

6.4 Create Change Control Landscape

A change control landscape is the part of your complete system landscape that can be
controlled by change request management. This is helpful when there is no need to

8/10/21

Page 33 of 42
control the complete solution but only parts of it. The change control landscape
consists of a combination of logical component groups that you can define and
maintain on the Change Control Landscapes tab for your selected solution in the
Solution Administration.

TTF_TTF_SOLUTION_SUB_1 Change control Landscape was created:

8/10/21

Page 34 of 42
7 Change Cycle Definition in Solution Manager
A change cycle is a type of change transaction that defines the system landscape
(change control landscape and branch) and the transport tracks for change documents.
Each change cycle has a defined set of phases, depending on its type. Typically,
Cycles are associated to Go Live projects.

NOTE: Real Change Cycle for TTF and TTF are not created because they are pending
of the approval for Charm Activation in Production. Proposed names are:

TTF Solution

TTF Solution

7.1 Create Change Cycle

Access to WebClient UI or execute transaction CRM_UI. Click on Create-Change
Cycle option. Standard SMIM transaction type is used for Phase Cycle creation

Indicate description, Landscape Solution and Branch. That will indicate SAP systems in
the scope for the Change Cycle being created. Click on Save once done.

7.2 Create Task List

The task list defines which processes can be performed for a change, depending on
the change cycle to which it is assigned. For example create a Transport of copies or
Import a TR. Follow wizard Steps:

Check Prerequisites

Define Scope:

This will indicate SAP Systems in scope for Change Cycle:

8/10/21

Page 35 of 42
Create Task List

Unlock Task List Activities so they can be executed. Use “Lock/Unlock Group” button
for that:

Set Status of the Change Cycle to Build

Now users will be able to use Change cycle created for Transport Management.

8/10/21

Page 36 of 42
8 Charm Administration Cockpit
Administration Cockpit is the entry point to the administrative activities, you can find it
as a tile in SAP Solution Manager Fiori Launchpad in /nsm_workcenter transaction .

It provide access to :

 Task Lists

On this tab page, you can execute operational and background activities for
distributing software in your system landscape, for example, handling change
cycles, task lists, and import scheduling.

 Landscape Overview

You can display information about the managed systems contained in the
logical component groups that are connected to Change Request Management,
and/or Quality Gate Management (QGM), via the solution landscape
(transaction SLAN) or the change control landscape assignment. Each
managed system in the logical component groups is listed along with the
communication systems.

 Critical Objects

You can define and edit critical transport objects.

 White List Objects

You can add objects that are allowed to be saved to a transport request of a
standard change to a white list.

 Cross-System Object Locks

On this tab page, you can manage cross-system object lock entries. You can
display lock entries according to defined criteria, remove them or register lock
entries for transport requests that are managed by Change Request
Management or Quality Gate Management.

 Transport Analysis

You can analyze the transport requests in your landscape in different views.

 Search

8/10/21

Page 37 of 42
 You can search for various objects based on your search criteria. You can also
do a full-text search.

Depending on the type you selected in the Search In field, the system displays
change transactions, transport objects, or transport requests as the search
results.

 Scheduled Import Jobs

You get an overview of all sequent scheduled import jobs independent of task
lists, change cycles, and target systems. You can search the background jobs
scheduled for importing transport requests in Change Request Management.

8/10/21

Page 38 of 42
9 SAP Roles and Users

9.1 SAP Roles

Key guidelines for SAP Roles configuration regarding Charm functinality:

 Specific Composite Role for the different Functional Roles or “Players” will be
defined.
 Single Roles to be mapped to each Composite Role will be defined.
 Single Roles will be copied from standard deployed roles and then named
according to agreed naming convention.

9.2 Set Up users and partners

Every user to use Charm needs to have a business Partner created for Solution
Manager system. This is a mandatory prerequisite

Business partners and new users can be automatically created from transaction
BP_USER_GEN.

From this transaction, we can create corresponding Business Partner using the data
from SAP user (SU01) like first name, mail etc… This is mandatory for all new Solman
users.

Different selection options are available, users per systems, or period of creation of
users.

9.3 User List

List to be consolidated together Technical Architecture and TTF/TTF teams. SAP

Solution Manager Users are managed by Company IT team.

8/10/21

Page 39 of 42
10 Transport Request List
See below list of SAP Solution Manager Request that contain all the transportable
configuration objects implemented:

8/10/21

Page 40 of 42
11 Additional Functionalities

11.1 Schedule Import Jobs

Access to corresponding task list in Change Control Administration Cockpit (from

transaction SM_WORKCENTER)

Expand node with Activities linked to the system where Import Job must be activated:

Execute Activity “Schedule Import Job for Transport Requests” and set corresponding
JOB

Import Jobs created can be managed from “Scheduled Import Jobs” tab in Change
Control Management – Administration Cockpit

NOTE: Import jobs will be schedule once Test Environment are released to TTF/TTF
teams to start testing phase

11.2 Create Virtual Systems

Since most of Non-development environments are not available yet Technical Systems
required will be created as Virtual Systems in TMS and LMDB. Virtual systems will be
replaced by the real ones once they are available.

Steps are very well described in below SAP Wiki document:

https://wiki.scn.sap.com/wiki/display/SM/How+to+create+a+virtual+system+in+SAP+So
lution+Manager+7.2

For Charm functionality it is mandatory generate corresponding Technical System for

each TMS virtual system created.

8/10/21

Page 41 of 42
12 Appendix TR Import Landscape

12.1 Appendix TR Import Landscape

Charm setup must be aligned to TMS configuration, System and client strategy is

8/10/21

Page 42 of 42