Page tree
Skip to end of metadata
Go to start of metadata


With the following steps you will be able to create a test landscape to practice with the Change Request Management ChaRM scenario in SAP Solution Manager 7.2 without creating interferences with real TMS landscapes.

Also I will try to give tips and tricks for the common mistakes in the configuration of this scenario.

The configurations given are valid for Solution Manager 7.2. The screenshots provided in this wiki are taken from a SAP Solution Manager 7.2 SP06.

Configurations on the Managed Systems

1. Create the test landscape in TMS

Usually you would like to use ChaRM to manage the changes in this kind of system landscapes:

DEV:100 -> QUA:200 -> PRD:300

The test landscape that I am proposing is this one: your SAP Solution Manager is installed in system SMD for example, and you are configuring client 001 for being used as ChaRM client, then SMD:001 is your ChaRM client. 

Create three additional clients in SMD, like local client copy from client 000 with SAP_ALL profile, let say you create clients 100, 200 and 300. 

We assume that SMD:100 is going to be the Development system, SMD:200 the Quality system and SMD:300 is the Production system.

In SCC4 assign the following client settings, roles, etc. to these clients.


Customizing role for SMD client 100, Test role for SMD:200 and Production role for SMD:300.

The indications given for this test case from now on also apply to for your real TMS landscape, to DEV, QUA and PRD system.

Create the logical systems in the managed systems, in transaction SALE -> Basic Settings ->Logic System -> Define Logical System & Assign Logical System to Client -> Save.



2. Configuration of TMS for this scenario according to ChaRM prerequisites

2.1. Key points

Transports are supported in the standard transport layer of each client. When you configure the transport routes, note that only consolidation routes that are assign to the standard transport layer of the relevant exporting client are taken into consideration.

For each exporting client, exactly one target client and one target group are permitted.

We recommend that you assign exactly one development system to a production system, and that these two systems are connected by exactly one unique transport track.

If a development system and a production system are connected by more than one transport track, this may lead to inconsistencies within the transport distribution.

In the SAP Solution Manager system, in client 000, call /nSTMS (the TMS configuration should be done in the domain controller system of your real TMS managed landscape). In our example, SMD is the only system and so it is the domain controller.

2.2. Configure transport routes and transport strategy


Note: SMD client 001 does not need to take part of your TMS landscape.

Select Transport Routes icon:

 Go to Edit mode. 

For this test landscape, initially you have system SMD and none transport route defined (for a real landscape you will have the three system boxes DEV, QUA and PRD and the transport routes already defined). Make double-click on system SMD and fill the following values (or in the box of the development system).

In System Attributes tab: the use of Single transport is a prerequisite for ChaRM for all the systems in the landscape:


Note: These is a prerequisite for using the ChaRM scenario:

  • Deactivate the quality assurance approval procedure
  • Activate the single transports strategy

Because ChaRM has its own approval procedure, the existing quality assurance approval procedure isn’t needed in TMS. Also, activating the single transports strategy will ensure that the Import All option can’t be executed in the TMS.

In Standard Transport Layer tab: ensure you enter the client 100, (client with customizing role for the development box)), you need to configure client-specific transport layer settings for development systems:


Note: Enter the development client number and the transport layer which should be used in ChaRM.

If you have more than one development systems/clients, please make sure that for 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.


Consolidation routes:

Create the consolidation transport routes to SMD:200, transport route must be CLIENT SPECIFIC for the use in ChaRM scenario, this is real important!

From development system to quality system you need at least two consolidation routes, SAP and ZXXX.


Go with the pencil from the system SMD to system SMD and get this pop-up:

I create the consolidation route for transport layer SAP and I do the same to create transport route for transport layer ZSMD (for customer developments).

In case of a real landscape you need to choose from which system and CLIENT to which system and CLIENT, use button Extended Transport Control (F6) to see the client field if you choose create the transport route from Edit->Transport route -> Create option.

Note: You should know that in SAP Solution Manager 7.2 we no longer support “SAP” transport layer, for more information please refer to SAP Note 1401611, this note is also valid for SAP Solution Manager 7.2.


Delivery routes:

I make the same to create the Delivery transport route from SMD:200 to SMD:300, delivery routes are always from quality to production systems.


Finally you will get the following situation:


Save and distribute the changes:



All the previous work has to be done in the domain controller systems in real TMS managed landscapes.

The following TMS parameters are required for all ABAP systems in the managed landscape:

CTC  1 (Extended Transport Control activated)






Note: CTC must be set to 1for single ABAP stack systems and dual stack systems; for standalone non-ABAP systems CTC should be set to 0.

All these settings are explained in the solman_setup Change Control Management: Managed System Setup guided procedure. See in wiki How to configure SAP Solution Manager 7.2 - Change Request Management with SOLMAN_SETUP section Managed Systems Configuration.


Preparations on the SAP Solution Manager System

1. Review of the main configuration points in SAP Solution Manager system

Before using ChaRM scenario please ensure that you have run in solman_setup the indicated activities under Change Control Management: Change Request Management. See wiki page How to configure SAP Solution Manager 7.2 - Change Request Management with SOLMAN_SETUP for the important activities.

2. Check RFC Destinations for managed systems:clients in LMDB

You can use the Harmonizing RFC communication infrastructure as import strategy called, see SAP Note 1384598. It has the following advantages:

  • No named dialog user needed in client 000 is required
  • For imports into the managed system, the RFC destinations created within the managed system configuration are used

If the harmonizing RFC communication infrastructure is not used still you will need to activate TMS Trusted Services and created domain links between the solman and the managed landscape domain controllers, see my KBA 1908411 Harmonizing RFC communication infrastructure: how it works.

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.

Don´t forget that if harmonizing RFCcommunication infrastructure is in used you don´t need to create a RFC destination to client 000 of the managed systems as before, only to the system:clients entered in the logical component used for your ChaRM project.

In LMDB, in Technical Systems tab select the system and for Destination entry select RFC Maintenance, here you need to select the client and then create the required RFC connections from the Solman to the managed systems.


For this test scenario you need to select SMD clients 100, 200 and 300 and created the RFC destinations.


3. Create a solution, branch and logical component group for this landscape

In the wiki page How to create a solution for Change Request Management in SAP Solution Manager 7.2 you will see the steps to create a solution for this test landscape, for SMD system. Change in the wiki page the SID EYE for SDM and you could follow exactly the same steps explained there. 

You need to create a solution first, then a logical component group LCG "Maintain Logical Component Groups", and then assign the technical systems "Assign Technical Systems" to this LCG in the correct branch, Maintenance for Development and quality systems, Production branch for the production system:


Enter in the LCG only the systems that you want to control via ChaRM, it is not required that you create a LCG that contains all the systems in transport routes of the managed systems landscape.

LCG can be regarded as a projection of managed system infrastructure into SAP Solution Manager system, so it must represent the real landscape and the system roles should be consistent to system roles at TMS level. That is, for development system, the Type of Role should be Source Systems; for test systems, the Type of Role should be Target Systems; for production system, the Type of Role should also be Production Systems.

Ensure that there are consolidation routes defined from the source system to the first target system and delivery routes created between target systems and from the last target system to production system.

This will be check during the task list creation, if the systems entered in the LCG are not consistent with the real TMS landscape ChaRM you could not create a task list for the cycle and you will receive the usual errors:

  • No exporting system for system
  • No consolidation system found for


System Roles

When you were assigning the technical systems to a branch you saw that you need to fill a system:client under a column with a name.

Each column name is linked to a type of system role such as source system, target system, production system, etc..

There is no change in the concept of system roles from SAP Solution Manager 7.1 to 7.2, but the maximum number of custom roles has been increased from 10 to 52.

Note: You can use all lower and upper-case letters except A, B, C, D, E, F, P, S, T, V, as well as numbers. This is necessary to assign systems of multiple sites to the same logical component (countries, plants). Use system roles for this purpose, do not create site logical components,

In sm30: smsy_roles you can create new roles, however what it is really important is not the description name of the role, it is the Type of Role linked to it, assign it in transaction /nmaint_roles:



You can create a Change Control Landscape if required.


4. Create a Cycle

In the Solution Manager system in the WebClient UI, /nsm_Crm, create a new change cycle:


Select Phase cycle SMIM (variant SAP0) or Continual cycle SMAI (variant SAP1).

Select the landscape data: Enter under Landscape the solution or change control landscape defined in /nslan


The branches shown for selection are the branches of this solution that contains a development-source system.

Save the cycle. 

Choose Actions -> Set Phase to “Active” or “Scope” (depending on the type of cycle you have selected).

A dialog box appears to decide if you want to create a task list for the cycle or not.

You can now create a task list.


In the Define Scope you could remove transport tracks in case that you have a solution branch which contains more than one LCG.

You could remove also parallel systems and leave only a track following the line from development to production.

In the case that you want to create a cycle with cCTS select the flag “Use Central and Transport System”, this will enable step 3. Check cluster assignment where you can maintain the clusters of the systems in the transport track overview.

If this flag is not selected this step 3 is grey out and skipped.

Retrofit system need to be defined in section Retrofit Systems.

In the last step 4. Complete select Create and a task list for the selected transport tracks will be created:


For managing transport requests via Change Request Management, you need to create a task list.

A CTS project will be created automatically in the development managed system, by default no IMG project is created in Solman 7.2. See SAP Note 2516652 - Assign IMG project to ChaRM change cycle in case you require this IMG project.

For working with this cycle move it to Build phase and Unlock Group for the Track:

The task list contains the transport tracks. For the calculation of transport tracks, only from the selected branch, the source systems, for example development systems, are used as a starting point to identify transport tracks.


You can have a minimum of two systems, source and production systems, for ChaRM scenario but you can have for example 5 systems with different roles in your real landscape.

Note: until four system landscape is supported in the ChaRM standard scenario, if you have more systems you will need to define some additional status, actions...This is not supported in standard.

Once again, always create a LCG that fits with the real TMS managed landscape, if not the ChaRM scenario could no be activated. This point is always the point that more problems gives in the task list creation!!!

ChaRM expects to see consolidation routes from source to target systems, delivery routes between target systems and from the last target system to production system.

 Cycle is ready for working. You can start the creation of request for change and change documents.

In the cycle under More button you can make a cycle check or a redefine landscape in case that the TMS changes in the managed systems landscape:

Related Content

Related Documentation


Related Notes

Ensure that you have applied the latest version of the Change Request Management master note for your patch level.

  • 1384598 - Harmonizing RFC communication infrastructure in ChaRM/QGM
  • 2316974 - General note for Change Request Management ST 7.2
  • 1703391 - General note for managed systems in Change Management 
  • 1401611 - Generating transport tracks with standard transport layer
  • No labels