Skip to Content
Product Information
Author's profile photo Ankur Gupta

How to move transports to multiple quality clients/systems in ChaRM


Change Request Management (CHARM). When should you perform the steps provided in this document?

  1. If you are adding a new Quality system to a Landscape.
  2. If you want to add/remove a Quality client in an existing system of a landscape.
  3. If you want to update the Logical Component Groups.
  4. if you want to Redefine your landscape.

NOTE: *Modifying Logical Component Groups or Changing TMS while a ChaRM project is active can be very impactful for all charm changes. Please consult ChaRM expert before making any changes.


Add/remove a Quality system from a landscape

All below stems must be performed in the given order:

Step1: Adjusting the TMS so that Dev System is feeding into two quality systems

Step2: Update the Logical Component Groups

Step3: Redefining the Landscape

Step4: Update the Batch Jobs


Step1: Adjusting the TMS so that Dev System is feeding into two quality systems.

I will discuss two examples here. One related to adding an additional quality system and second example will be of adding multiple clients within the same system.

Example1: DR4 system wants to feed data into two Quality systems QR4 and QR8 and finally Prod PR4 wants to collect data from QR4 system.

Detailed TMS View for Example1


Example 2: DRN Dev system wants to feed data into multiple clients within QRN system i.e. (QRN:900,910,920)

Detailed TMS View for Example2



Step2: Update the Logical Component Groups

  1. SLAN
  2. Select the solution corresponding to your environment. In this scenario we are using “main solution”.
  3. System Landscape > Assign Technical Systems
  4. Search and Select the Logical Component group of the project for which you want to do the modification and add the new Quality system and click OK. (if you don’t see or have a different system type then use Tcode: /nmaint_roles to defined the new system type as Quality Assurance System 2 )


Step3: Redefining the Landscape

  1. Go to the Phase Cycle in Edit mode and Click Redefine Landscape.
  2. Everything should be green on the next screen for “Check Prerequisites”. If not then first fix those errors.
  3. Click Next
  4. Add/Keep by clicking the checkbox, the new additional Quality system/clients as target from Dev boxes.
  5. * Uncheck the Development Workbench system only if shown as a target from customizing client (DR4:400 > DR4:410 in this scenario). This option comes if in TMS you have defined Workbench client as target client for customizing.
  6. Click Next. Validate all details are looking good on next screen and click ‘”Confirm”.

NOTE: *Please notice that all the projects in Charm that are using above modified logical component Group will be affected by this change and you will have to Redefine the landscape for all those projects. It is not necessary to add this extra quality box for all those projects and you can uncheck this Quality box when Redefining if not needed.

Step4: Adjust the quality transport import jobs from the task list.


Step 5: (OPTIONAL) Use report RSCTS_OBJ_TRACK_REMOVE_SYSTEM. If needed you can remove this newly added quality system for CTS Transport tracking. This way you will not receive DGP errors related to this additional Quality system.



In 7.2 SAP has made it extremely simple to modify logical components while change cycle is still open. In 7.1 it was extremely difficult to perform these activities and in certain scenarios it was not possible at all.

During step redefine a landscape :

You are allowed to remove only quality systems and clients from a change cycle in motion.

You are allowed to even switch the quality system with another quality system but transport movement up to that moment would be manual or by a system copy.

SAP doesn’t allow to modify the development or production system when a change cycle is active. See Note below for exception to this scenario: 2587310 – Remove Development and Production systems during redefine landscape

Additional Info:

The transport tracks overview contains the following elements and functions:

  • Tiles represent systems connected by transport routes.
  • Dotted lines represent connections between retrofit systems and their source development systems.
  • Select the checkbox in a system tile to select or deselect a system in a transport track. After deselecting a system, all follow-on systems that cannot be reached anymore are automatically deselected.
  • When the application calculates the transport tracks, the source systems must be the ones defined in the logical components of the branch. All other systems on the transport tracks must be in scope of the entire logical component groups under the change control landscape or the solution that is assigned to the cycle.
  • A valid transport track must have one development system and at least one production system. If deselecting a system makes the whole transport track invalid, all the systems of the track will be automatically deselected. Keep at least one valid transport track for creating a task list.
  • When redefining a system landscape, you are not allowed to deselect existing development or production systems in the task list and if you add or remove target systems you have to take care of the consistency of the import queue and transport status of the relevant systems by yourself.
  • Retrofit systems cannot be added or removed in the overview. Edit them in the retrofit systems table.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Oded Dagan
      Oded Dagan

      Great Blog Ankur!

      Very clear and good examples.


      Oded Dagan

      Author's profile photo Ankur Gupta
      Ankur Gupta
      Blog Post Author


      Thanks Oded Dagan.

      Author's profile photo Vinayak Budapanahalli
      Vinayak Budapanahalli

      Self-explanatory. Thanks Ankur.

      Author's profile photo Hardeep Bajwa
      Hardeep Bajwa

      Thanks Ankur for writing knowledgeable article. Is it possible to define

      two clients in development system ( Customizing and Development) and single Change Document having Customizing  and Development TR's in respective clients ?

      Author's profile photo Ankur Gupta
      Ankur Gupta
      Blog Post Author

      Yes, Hardeep that is definitely possible.

      In fact, it is part of the out of the box normal change functionality where the one Normal change can have both customizing and Workbench request, both belonging to their respective clients with the same charm.

      Although if you are working on an urgent change you can create your customizing and workbench transport(1 each) only in a single development client at a time. Urgent changes choose the fastest path to production. Also, please notice that if you have multiple quality clients then these transports will also only go to the primary quality client. If you have multiple quality clients then charm will not process movement to those clients.

      Author's profile photo Roy Derek
      Roy Derek

      Hi Ankur,


      Thanks for this post. Is there any scenario where we can have the TR auto-imported to all QA clients? Right now, as you mention, it only gets auto-imported to primary QA client.




      Author's profile photo Preeti Ghate
      Preeti Ghate

      Hi Ankur,

      I have created to added two additional client in QA (100 220 along with 200). For that I have created new continual cycle for urgent change( while creating new cycle it is showing as QA 100,200,220) but my transport is not getting import into QA100 and QA 220. While checking the details of Task list i can see only one QA client (QA200) but in the next tab (Configuration) i can see all the QA Clients.

      Author's profile photo Harish Desai
      Harish Desai

      Hi Ankur,

      We have Java systems with CTS+ configured. Now we have multiple Prod systems for different regions. Is it possible to have Delivery routes to multiple prod systems from QAS.