Skip to end of metadata
Go to start of metadata

Purpose

Starting with SAP Solution Manager 7.1 SP 10 you have the option to use the central Change and Transport System (cCTS) infrastructure when setting up projects in Change Request Management (ChaRM) or Quality Gate Management (QGM). New features are available in ChaRM and QGM if cCTS is used, for example, a very flexible (re-)assignment of changes.

The purpose of this page is to troubleshoot when working with ChaRM projects with cCTS functionality activated.

In addition, I will try to give tips and tricks for the common mistakes in the configuration of this scenario and how to work with clusters and collections.

May, 2019: SAP note 2706928 - cCTS: Adjust import entry retrieval API is mandatory when working with cCTS cycles in SAP Solution Manager 7.2

Overview

Central Change and Transport System (central CTS or cCTS) enhances the classic CTS with functions for complex heterogeneous system landscapes, which allow you to control transports within a transport landscape centrally. This means you can combine multiple systems of your transport landscape into system clusters. You can bundle transports between these clusters using transport collections. A transport collection is a combination of the transports from the different systems of a cluster.

SAP Solution Manager represents the central CTS server that is responsible for the central management of the transport landscape. You can control transports into the managed systems from the central CTS server.

You can find more information in SAP Help Portal: Central Change and Transport System

Preparation - how to set up a cCTS landscape

Please get the guide How To... Set Up cCTS for ChaRM and QGM for 7.1.

For 7.2 use this updated guide: How To... Set Up cCTS for ChaRM and QGM.

I will use the same landscape as the one indicated here:

 

Step 1. Preparations on managed systems - Create TMS landscapes

You have to create the TMS landscapes as always:

ABAP landscapes

Follow SCN doc: First steps to work with Change Request Management scenario in Solution Manager 7.1

Section Configurations on Managed Systems

1. In E07:000, Domain Controller (DC) system, ensure that you have created these transport routes: N14:100 -> E07:200 -> Z06:300

2. In ERD:000, DC system, ensure that you have created these transport routes: ERD:101 -> ERQ:201 -> ERP:301


Non-ABAP landscapes

Follow SCN doc: Change Request Management: Configuring CTS+ in SAP Solution Manager 7.1

Sections:

Step 1- Setting up CTS+ in your environment

Step 2. TMS System Landscape Configuration

In the domain controller system of the communication system, client 000, you will need to create these transport routes. In this case, imagine that the communication system is the Solman system CSM:

BOD -> BOQ -> BOP

Step 2. Preparations on SAP Solution Manager System – Managing system

If you have several Solman systems ensure that you configure cCTS in the domain controller of the SAP Solution Manager landscape and then create the ChaRM cycle also in the domain controller SAP Solution Manager system.

Note: In the indicated guide "How To... Set Up cCTS for ChaRM and QGM"  section 3. Prerequisite you can read:  "All managed systems need to be part of the SAP Solution Manager domain or the domain(s) of the managed systems need to be linked to the SAP Solution Manager domain using an domain link."

So in SAP Solution Manager 7.1 is mandatory to establish a domain link between the solman domain and managed system domains is mandatory to use ChaRM projects with cCTS functionality.

The whole process including distributing plug-ins, creating clusters, transport collections and starting imports into other systems are executed in the managing system.

Follow SCN doc: First steps to work with Change Request Management scenario in Solution Manager 7.1

Section Preparations on SAP Solution Manager System

1. Review of the main configuration points in Solman system

2. Check RFC Destinations for managed systems in LMDB

For ABAP systems create the RFC destination for the working clients; in our example, this means:

N14:100, E07:200, Z06:300, ERD:101, ERQ: 201, and ERP:301

For non-ABAP systems ensure that the system is created in LMDB as indicated in section Step 3. Definition of non-ABAP Systems in LMDB/SMSY in Change Request Management: Configuring CTS+ in SAP Solution Manager 7.1

Create the RFC destinations for the communication system:client indicated in the BOD TMS parameters; this is CMS:001 following our example landscape. 

3. Create the Logical components in the Solman system LMDB

You need to put the relevant systems into their corresponding system roles, and ensure that the system entered fits with the real TMS landscape that you have.

To clarify, 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 checked during the task list creation. If the systems entered in the logical component are not consistent with the real TMS landscape, ChaRM will not be activated for the project and you will receive the usual errors:

•No exporting system for system

•No consolidation system found for

You need to create these logical components:


Logical component

Development (source system role)

Quality (target  system role)

Production   (Production role)

LC1

N14:100

E07:200

Z06:300

LC2

ERD:101

ERQ:201

ERP:301

LC3

BOD

BOQ

BOP


Up to this point, you have done the same steps that you would do for working with a ChaRM project not using cCTS functionality. 

Step 3. cCTS customizing is set to on? 

Starting with CTS_PLUG 200 SP10, cCTS is automatically active on your SAP Solution Manager.

The CTS Server plug-in is automatically installed during the installation of SAP Solution Manager with the update/upgrade to Solution Manager 7.1 SP 05 or higher. The CTS Service plug-ins should have been distributed to the managed systems using the central CTS Configuration UI.

The managed systems will need to have a minimum the SAP_BASIS patch level indicated in note 1665940.

See section 4. Details on CTS_PLUG on the guide How To... Set Up cCTS for ChaRM and QGM.

 

Step 4. Clusters are configured?

Follow section 5 Step-by-Step Procedure of the guide How To... Set Up cCTS for ChaRM and QGM

“The setup of the system track is done in the following order:

1. Enable cCTS UIs (central CTS Configuration UI, CTS Transport Log Viewer)

2. Create favorites for the cCTS UIs

3. Use central CTS Configuration UI to validate systems and perform the recommended steps

- Define TMS parameters

- Distribute cCTS Service plug-ins

- Create clusters and assign systems

  • Create the development cluster (CDV)
  • Create the quality cluster (CQS)
  • Create the production cluster (CPD)

- Define RFC destinations

  • Deploy destinations

4. Connect the clusters

5. Define import targets for clusters

6. Distribute configuration changes”


From ChaRM point of view these are the important points:

  • See cluster created in Solman system domain controller:/nstms-> systems: CDV, CQS, CPD


Clusters are needed for each system role so that you can bundle systems with the same role from different application landscapes. So you could, for example, create a development cluster containing the ERP, the BW, and the BO development system, a test cluster containing the ERP, the BW, and the BO test system and a cluster containing the respective production systems.

Clusters are represented by an SID in TMS like any other system, but it is not a real system that you have to install. You have to ‘invent’ an SID consisting of three letters which does not yet exist in your landscape. You can then add the systems to this cluster.

Pay attention to the icon used:

  • In /nSZENCONFIG: Central Change and Transport System; in the Solman system, select the systems of your clusters and click “Validate”, Status and Distribution Status should be Green.

Real managed systems are usually assigned to clusters according to their system roles.


  • Check the transport routes between clusters are created: CDV-> CQS->CPD

 

Double click on the target and production systems and ensure that in Import Targets tab you get the correct target system:clients:

 


However, pay attention that in target and production clusters the Request Source is always the source, development systems. 

Operations using the CTS plug-in are blocked with an error message if the CTS plug-in was not installed on a managed system or if the plug-in on a managed system had a lower version than the plug-in on the CTS server (SAP Solution Manager).

In SAP Solution Manager 7.2 with the implementation of SAP Note 2555809 "Report CTS plug-in client checks as warning for CTS plug-in outdated in managed systems" and later the behavior varies depending on whether the CTS plug-in is not yet installed or the plug-in on the systems is out of date. If the plug-in on a system is out of date, you can still perform operations that use central CTS or downgrade protection.

Create a ChaRM project using cCTS functionality

Now that the cCTS infrastructure is configured, you can use it for your projects, cycles, in ChaRM and QGM. This Project, cycle, needs to be created also in the domain controller SAP Solution Manager system where the cCTS configuration was done.

In SOLAR_PROJECT_ADMIN create the project, enter the logical components created for the managed “real” systems like LC1, LC2 and LC3.

Create the IMG projects.

See all details in section "4. In Solution Manager go to transaction SOLAR_PROJECT_ADMIN" of SCN doc First steps to work with Change Request Management scenario in Solution Manager 7.1 if you are using ABAP managed landscapes. Check "section Step 5. Definition of the ChaRM project" of SCN doc Change Request Management: Configuring CTS+ in SAP Solution Manager 7.1 if you are working with non-ABAP managed landscapes.

Then go to tab ‘System Landscape’->’Change Management’ and choose the checkbox ‘Activate Change Request Management’.

Here you need to be careful because you could miss the activation of cCTS. A pop up will come up asking you if you want to activate ChaRM with or without the central Change and Transport System.

Select the Checkbox that you want to use the central Change and Transport System Infrastructure and continue.

Afterwards a pop up will come up where you have to assign the transport cluster and domains to the listed systems. 

1. In the upper area of the pop up the logical components are displayed

2. In the area below the System view for logical components the TMS and Cluster checks status are displayed as well .

3. If there is a maximum cluster which is common to all the logical components assigned, these Clusters will be automatically assigned by default.

Use the button ‘Cluster Configuration’ and you will be brought to the WebUI where the clusters and systems are displayed and can be configured if you have the appropriate authorization.

Use the button ‘Reset Cluster Assignment’ and the cluster assignment should be reset.

Use the help button to display further information to the cluster assignment.

4. Save.

A new button will appear in tab ‘System Landscape’->’Change Management’ called “Maintain system cluster assignment”. You should be brought to the same pop up.


In case the landscape was changed after cluster assignment, but before the task list creation, you still have a chance to change the clusters. Once the task list is created, the cluster assignment can’t be modified any more.


You can now generate the task list. You will see that the task list contains a new node for clusters, where an additional transport track is generated containing the cluster landscape. Cluster actions could be carried out just once in the cluster node, while system actions are done in the system node:

IMPORTANT INFORMATION: SAP Note 2513191 Fix for persisting collections with GUID-based request list is a mandatory note to be implemented in the SAP Solution Manager system.

Working with Change documents: Hints and Tips

Now you can work with this project and create your request for change and change documents.

A change document utilizes one collection, and one collection contains several transport request.


Requester will create a Request for Change to request a change in a production, this change could imply to make a change in the two different landscapes, for example in the ERP landscape and also in the EP landscape. The business needs require to get the changes and the transport requests imported “synchronously” in the involved system of both lanscapes.

These two transport requests, the one for the ERP development system and the one for the EP development system, should be combined to one entity, a Collection, that will be moved from cluster to cluster until production.


The Change manager will assign to this Request for Change a project with cCTS functionality and will create the required change documents and assign them to the desired developers.

The Developer will use the change document to create the transport request that he needs for both development systems.

From the developers point of view, the creation of a collection for grouping the transport requests is “transparent”; this means the developer is still working at transport request level in each real development system.

When requesting the creation of a transport request, a collection will be created.

Ensure that you have check SAP Note 2285667 - Failed to create cCTS collection - Could not add invalid attribute in case that the collection is not created.

If you create a second transport request this will be also added to the same collection.


To see the collection and the transport requests included in the collection you can use these ways:

  • In the task list, M* of H*, in the log for step Create Transport Request you will find the transport request number created and the collection.

Example: Request BODK9001P5 is created in collection CDVK90025C for change 8001459885

  • In the Solman system go report SCTS_SEARCH_FOR_COLLECTION  enter the transport request and you will get the collection number.
  • In the Solman system in /nszentms (CTS Transport Manager) -> Tra: here we can see the collections and which TRs are included in the collection.
  • In the development system where the real TRs are created you will see the project for the TR linked to a collection is Project SAP_CCTS.


When the development passes a change document to To be tested status:

- for a normal change document a Test collection will be created, so real TOCs will be created and exported in the development systems.


The IT operator is the unique user that will need to work with clusters and collections; the IT operator in the task list needs to decide now to trigger the import of the TOCs from the cluster track to get all TOC imported synchronously in the quality systems or to trigger the import from each quality system separately as always.


Note: In case that the IT operator decides to make the import for each single system, the release or the import of the collection will be completed when the last transport requests included in the collection is released or imported.


-  for an urgent change the collection will be released and imported into the next system so the associated TRs will be released and imported. 


Note: If you get this error message when working with a change document containing a collection:

Failed to create cCTS collection. Message No. /TMWFLOW/TRANSPORT 309
Could not add invalid attribute. Message No. SCTS_DIST_CTL_ORGNZE 032
Error in handling of request. Message No. SCTS_DIST_CTL_ORGNZE 002

Request attribute SAP_CTS_PROJECT is mandatory Message No. PU665

Check in the Solman system, usually acting as central CTS server that the CTS project attribute is not set as mandatory for the client where the collections are created.

You can check this in se03: Administration -> Display/Change Request Attributes, parameter SAP_CTS_PROJECT should not be flagged for Obligatory attribute. As this would affect to all clients and the client where the collection is created can not have this setting as mandatory to avoid this error.


Reassigment of released transport requests

From solman 7.1 SP10, a released transport request can be assigned to a change document belonging to a Change Cycle that has Central CTS (cCTS) enabled. Otherwise, you can only assign changeable transport requests.

More information in the SAP Help Portal Assign Transport Requests.


Related Content

Related Documents

How To... Set Up cCTS for ChaRM and QGM

Community Blog DGP – Downgrade Protection for CTS

First steps to work with Change Request Management scenario in Solution Manager 7.1

Change Request Management: Configuring CTS+ in SAP Solution Manager 7.1 

SAP Help Portal: Central Change and Transport System

SAP Help Portal: Assign Transport Requests.

SAP IT Service Management on SAP Solution Manager -> Events

http://wiki.scn.sap.com/wiki/display/SAPITSM/Events

Related Notes

SAP Note 1665940 - Installing/Updating SAP CTS Plug-In 2.0

SAP Note 1688276 - Distributing CTS plug-ins to managed systems

SAP Note 2555809 - Report CTS plug-in client checks as warning for CTS plug-in outdated in managed systems

SAP Note 2285667 - Failed to create cCTS collection - Could not add invalid attribute

SAP Note 2231041 - Collective Note: central CTS with SAP Solution Manager 7.2

SAP Note 2407837 - ChaRM&QGM: Virtual system validation error in cCTS configuration

SAP Note 2513191 - Fix for persisting collections with GUID-based request list



4 Comments

  1. Former Member

    Hi Dolores,

    first of all thank you for keeping on posting those great and helpful Blogs and Wikis. I think I might have added nearly all of them to my favorites bar by now, since I come back here regularly.

    I have two specific questions that might be worthwhile to include in your post, although I think I might have the answers for one of them already:

    Towards the end of this blog you make the following comment:
    QUOTE:

    The IT operator is the unique user that will need to work with clusters and collections; the IT operator in the task list needs to decide now to trigger the import of the TOCs from the cluster track to get all TOC imported synchronously in the quality systems or to trigger the import from each quality system separately as always.

    Note: In case that the IT operator decides to make the import for each single system, the release or the import of the collection will be completed when the last transport requests included in the collection is released or imported.

    Now let's say not the IT-Operator is doing the import into QAS, but an automated job as described in KBA  1897163.

    Then in case of Option 1 we would have the same situation as in " the IT operator decides to make the import for each single system," I would assume.

    For Option 2 the same, although I do not favor option 2 in the KBA at all.

    For Option 3 in the KBA we would have the choice again what we want to do (although we would have the limitation that we need to schedule a whole lot of jobs).

    Is that right?

    The main question that I tried to find and answer for but couldn't find is the following:

    We are currently running KBA option1 using  /TMWFLOW/SCHEDULE_IMPORT with 5 steps (1 step for each system). As far as I can tell the job creates a new import job for each system that then run independently. Thus if step 1 is for ERP and step 2 being for BW, the job for BW might (and often will) start before the imports in ERP have finished and activated. If we had a change document containing an ERP extractor and the follow on processing in BW, we ideally would have the BW import waiting for the ERP import to finish.

    Alternatively, if I run the import job for the cluster, how could I do a sequencing that would follow the logic above, or how does ChaRM sequence the systems within the transport collection - if at all?

    I thought about utilizing CPS Redwood to get more control over the jobs, but since the created import job "/TMWFLOW/SCMA_TRORDER_IMPORT/000" finishes with the start of the import (and not the successful finish) I cannot find a way to set up this scenario. I couldn't find any recommendation either, but think it would fit nicely in here.

    I beg your pardon for "hijacking" this great wiki to post my question here, but I think it would be a really valuable addition if this scenario could be included.

    Thanks a lot again for all of the great content you posted.

    Markus 

     

    1. Hi Markus. If all the transport requests belong to the same collection, you do not need to worry about their sequence. Because during import of collection cCTS will handle them always together. In the end all objects will be correctly imported. This is the essential design of cCTS.

  2. Former Member

    Hi Markus Mueller

    Were you able to get an answer for your questions  above? I have the same question!

    Thanks,

    William P.

    1. Former Member

      Hi William, unfortunately I didn't.

      In case of that scenario my client does it manually, like in the good old times (smile)

       

      Cheers

      Markus