Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

June 2017: IMPORTANT INFORMATION FOR SAP SOLUTION MANAGER 7.2 SP03-SP05

Implement SAP Note 2468028 - ChaRM&QGM: RFC to client 000 cannot be used explicitly  to avoid errors like  "System  is not valid; configure Organizer client in TMS" when trying to create a transport request through ChaRM.


Purpose

With the following steps you will be able to create a project to practice how to manage a non-ABAP landscape from the Change Request Management in SAP Solution Manager 7.1 and SAP Solution Manager 7.2.
Also I will try to give some tips and tricks for the common mistakes in the configuration of this scenario.
I will work in this example with a TMS landscape for portal systems: XAD->XAQ->XAP.

Step 1- Setting up CTS+ in your environment

With the enhanced Change and Transport System (CTS+) you can transport non-ABAP objects via the CTS. CTS+ is offered starting with SAP NetWeaver 7.0 SPS 12. On the SCN document Other CTS+ resources you can find the documentation and How-to Guides which can help you setting up CTS+ in your environment. CTS+ can be used for different environments like Enterprise Portal systems (Java system), PI systems (dual stack systems), SAP Hana, SAP Business Objects, SAP NetWeaver Master Data Management 7.1 systems, etc... See guide Best Practices for Implementing CTS+.
So the first step is setting up CTS+ in your environment, if CTS+ can be used for your specific product landscape then ChaRM can be used to manage this landscape.
In the Best Practices for Implementing CTS+ guide you can read: For the usage of CTS+ at least one ABAP and one JAVA stack is needed. The recommendation is to use the SAP Solution Manager system, which is a dual stack system. CTS+ does not need any Solution Manager functionality, it is a pure SAP NetWeaver technology. But the Solution Manager system can act as central transport management system for the whole landscape.
The decision where to configure the CTS+ components will depend on the use case (such as PI, EP, NWDI) and the system landscape.
Picture below is an example for a central dual-stack system that acts as domain controller for a non-ABAP landscape. Here all server components are configured within the same system.

 

If the ABAP and Java stacks are implemented on separate systems that run on different hosts, some additional configuration aspects need to be considered, see next picture:

 

From ChaRM point of view the relevant CTS+ components are:

- Domain Controller (ABAP): The domain controller is the system, where the TMS transport systems (ABAP and non-ABAP) with their transport layer and transport route are configured. - TMS Communication System (ABAP): The communication system is the ABAP where the transport program tp is triggered to perform the transport steps. By default the Domain Controller is used as Communication system. But that is not mandatory as any other system can act as Communication system. - CTS Export Client: tight integration of CTS+ in the application of the source system where the non-ABAP objects are created. The Export Client communicates with the enhanced Transport Organizer to fetch a proper transport request and to attach the non-ABAP object directly within the application.
Please follow the Best practises guide completely to setup the CTS+ in your environment.

1.1. CTS+ for SAP HANA

 

Please follow the guide How To... Configure SAP HANA for CTS to find information on how ot use CTS+ for transporting SAP Hana objects., applicable to SAP HANA Platform SPS09 to 12 and SAP HANA Platform 2.0 (for SAP HANA Repository (XSclassic)) v1.3 March 2019.

You can model your system landscape for your SAP HANA systems in Transport Management System (TMS) in the same way as for any other non-ABAP application supporting CTS.

This guide is valid if you use SAP HANA on-premise as well as if you use the SAP Cloud Platform SAP HANA service in the Neo Environment. For the SAP HANA service in the Neo Environment, you will find some special configuration settings in this guide. Note that if you want to use CTS+ for the SAP Cloud Platform SAP HANA service in the Cloud Foundry environment, use the How To... Configure SAP Cloud Platform Cloud Foundry for CTS guide.

The figure above illustrates the process of exporting and importing objects with SAP HANA. The front-end is the SAP HANA Studio or (starting with SPS08) the SAP HANA application lifecycle management (HALM). As of SAP HANA studio SPS05, you are no longer required to export the SAP HANA content to the file system and attach it manually to a CTS transport request. It is now possible to export SAP HANA content and attach it to a transport request in one step (referred to as “Close Coupling”).

You can start the export from within the SAP HANA Developer Studio or SAP HANA application lifecycle management. You should no longer use the option of exporting content to a file  system and attaching manually to a transport request.

The next step is to release the transport request  You can then start the import. This is done on the CTS system.

Starting with SAP HANA SPS09, you can set up CTS+ for SAP HANA without an AS JAVA. This means that your CTS system now only has to consist of an AS ABAP.

The communication between the CTS System and the application (target system) is then based on the HTTP protocol.

If you would like to configure CTS+ without AS JAVA:

  • CTS System: SAP Solution Manager 7.2, SAP NetWeaver 7.4 and up
  • SAP Note 2236955 has to get applied to CTS system.
  • For SAP NetWeaver 7.4 lower than SP10: CTS plug-in SP15 installed on the CTS system (taken from SL Toolset 1.0 SP12 at least – always use the newest CTS plug-in available).
  • SAP HANA Platform SPS09 and up, SAP HANA 2.0 (SAP HANA Repository),  SAP HANA Service in SAP Cloud Platform Neo Environment

 

See also guide How To... Configure SAP HANA Extended Services - Advanced Model (XSA) for CTS SAP HANA Platform 2.0 SP0 v1.0 Nov 2016.

 

1.2. CTS+ for SAP Cloud platform Neo Environment

Please follow the guide How To... Configure SAP Cloud Platform Neo Environment for CTS to find information on how to use CTS+ for transporting applications running on the SAP Cloud Platform (SCP) Neo environment.

You can model a landscape for your SCP Neo sub accounts in CTS like for any other non-ABAP application supported by CTS.

When doing that, you associate logical systems in TMS to the subaccounts you have in SCP Neo, let say: subaccount DEV -> subaccount QUA ->  subaccount PRD.

                    

The representations of the SCP Neo subaccounts in CTS will be called systems (for example, logical non-ABAP system, source or export system, as well as target or import system).

The MTA archives, containing the application running in SCP Neo, are attached to the transport request.

Afterwards you need to release the transport request. You can then start the import into the next logical system from the transport route, which will trigger the import into the corresponding SCP Neo subaccount.

To implement the scenario, you need a physical system where CTS is configured.

-        CTS System: SAP Solution Manager 7.2, SAP NetWeaver 7.4 or higher.

-        If CTS System is on state lower than SAP NetWeaver 7.4 SP10: CTS plug-in taken from the latest available SL Toolset

-        SAP Notes 2236955 and 1160362 must be applied to the CTS system

 

1.3. CTS+ for SAP Cloud platform Cloud Foundry Environment

Please follow the guide How To... Configure SAP Cloud Platform Cloud Foundry for CTS to find information on how to use CTS+ for transporting applications running

on the SAP Cloud Platform (SCP) Cloud Foundry Environment.

You will be able to transport SCP Cloud Foundry applications bundled in Multi-Target Application (MTA) archives to SCP Cloud Foundry spaces.

You can model a landscape for your SCP Cloud Foundry spaces in CTS like for any other non-ABAP application supported by CTS. When doing that, you associate logical systems in TMS to the spaces you have in SCP Cloud Foundry.

The representations of the SCP Cloud Foundry spaces in CTS will be called systems (for example, logical non-ABAP system, source or export system, as well as target or import system).

The following figure shows a sample transport route modeled in CTS+.

 

In order to trigger the transport you have to create a transport request for the first system in the transport route (Dev in the example above) and attach the MTA archives that you want to transport to it using the Transport Organizer tool in CTS.

Afterwards you need to release the transport request. You can then start the import into the next logical system from the transport route, which will trigger the import into the corresponding SCP Cloud Foundry space.

To implement the scenario, you need a physical system where CTS is configured.

-        CTS System: SAP Solution Manager 7.2, SAP NetWeaver 7.4 or higher.

-        If CTS System is on state lower than SAP NetWeaver 7.4 SP10: CTS plug-in installed on the CTS system (taken from the latest available SL Toolset 1.0 CTS plug-in) . SAP Note for installing the SAP CTS Plug-In of SL Toolset: 1665940 .

-        SAP Notes 2236955 and 1160362 must be applied to the CTS system.

 

Step 2. TMS System Landscape Configuration

2.1. Create the systems 

Case1. Non-ABAP systems
With the enhanced CTS a new type of TMS/CTS System is introduced – the non-ABAP System. Logon to the client 000 of the domain controller of the system that you want to use as TMS communication system, then in transaction stms  →  SAP System  → Create  → Non-ABAP System

This system type is needed for all pure AS Java landscapes for example EP and for the other systems like SAP Hana, SAP Business Objects, SAP NetWeaver Master Data Management 7.1 systems, etc...

Create all the systems of your landscape.

For SAP Solution Manager 7.2 ensure that these SAP notes are implemented in the domain controller system of the managed landscape (also in the other systems):

  • 1977240 - Extension of the AS ABAP SLD Data Supplier (RZ70)
  • 2148577 - RZ70 always sets communication client to 000 for non-ABAP system

With this you ensure that the domain controller system is sending the information of the non-ABAP system created to the SLD of the SAP Solution Manager.

Case 2. Dual-Stack systems
Existing systems in the transport landscape that are dual-Stack systems (e.g. use case PI) can now be enhanced with the new Transport Tool parameters for the Java stack to be able to transport non- ABAP objects. Typically the ABAP stacks are already configured and included in the transport domain. To add the CTS+ functionality for transports to the Java stack, the existing configuration for the ABAP systems needs to be extended with the relevant CTS+ parameters. Since SAP NetWeaver 7.0 SP Stack 14 a wizard can be used to add the relevant parameters to existing ABAP system configurations. Logon to the client 000 of the domain controller of the dual-Stack system and call transaction stms → Create →Java Stack:

 

For SAP Solution Manager 7.2 ensure that these SAP notes are implemented in the domain controller system of the managed landscape (also in the other systems):

  • 1977240 - Extension of the AS ABAP SLD Data Supplier (RZ70)
  • 2148577 - RZ70 always sets communication client to 000 for non-ABAP system

 

2.2. Configuration of Source Systems

 

Case1. Non-ABAP systems
Enter the System ID and description and choose the Source System Settings. With the Source System Settings the SAP System ID (SAPSID) of the Communication System and the client on which the Transport Organizer Web UI should run is defined. With the activation of the Transport Organizer for this system, transport requests for that system will be created here. The transport requests will have names starting with the SAPSID of this system.
The following parameters are mandatory for the configuration of a pure non-ABAP source system:
- CTC: 0
- CTS_SYSTEM_TYPE: This parameter is only needed when using CTS+ with Solution Manager Change Request Management (ChaRM)
Depending on the system type we should enter here the following values:
JAVA   *for pure Java systems
MDM   *for MDM systems according to note 1464456
BOBJ   *for Business Object systems, 
HANADB    *for Hana systems
UNSPECIFIC *for technical system type Unspecific ... System
others     *for pure file system deployment
Note: If you are using SAP Solution Manager 7.2 parameter CTS_SYSTEM_TYPE is not required.
- NON_ABAP_SYSTEM: 1
- COMMUNICATION_SYSTEM:  SAPSID of the ABAP communication system (e.g. the domain controller)
- NON_ABAP_WBO_CLIENT: Client of the ABAP stack on which the Transport Organizer Web UI (CTS_BROWSER) is activated and will run.
- WBO_GET_REQ_STRATEGY:TAGGED
  Please notice that preselection step is a mandatory manual step after transport request is created in ChaRM, and before adding objects to this transport request. Therefore when using ChaRM WBO_GET_REQ_STRATEGY=TAGGED, such preselection step is not done automatically. Then to preselect the created transport request from ChaRM as the default request you need to follow these steps:

1. Call transaction "STMS".
2. Press the button "Transport Organizer WEB UI" to start the Browser.
3. Select the system in the popup where the request was created.
4. Mark the request you want to use for the Non-ABAP-Objects
5. Set the marked request as preselected request (button "Preselect Request").
After that the request is available and can be used to add objects.

 
Case 2. Dual-Stack systems
The difference of the two wizards is, that for adding Java stack parameters an existing system is selected and no new system is created. Furthermore no COMMUNICATION_SYSTEM parameter is needed for dual-stack systems, as every ABAP system has its own tp that manages transports.
- CTC: 1
- NON_ABAP_WBO_CLIENT: Client of the ABAP stack on which the Transport Organizer Web UI (CTS_BROWSER) is activated and will run.

2.3. Configuration of Target Systems

 

Case1. Non-ABAP systems To create a non-ABAP target system, the wizard to create non-ABAP Target System can be used. Enter the System ID and description and choose the Target System Settings. The Communication System for a non-ABAP target system has the task to communicate with the transport control program tp running on that system together with the Deploy Web Service Client to trigger the import on the target runtime system. With the Target System Settings the types of import are specified.
The following parameters are mandatory for the configuration of a pure non-ABAP target system:
- CTC: 0
- CTS_SYSTEM_TYPE: This parameter is only needed when using CTS+ with Solution Manager Change Request Management (ChaRM)
Depending on the system type we should enter here the following values:
JAVA   *for pure Java systems
MDM   *for MDM systems according to note 1464456
BOBJ   *for Business Object systems, 
HANADB    *for Hana systems
others     *for pure file system deployment
- NON_ABAP_SYSTEM: 1
- COMMUNICATION_SYSTEM:  SAPSID of the ABAP communication system (e.g. the domain controller)
- DEPLOY_WEB_SERVICE: CTSDEPLOY (Name of the Logical Port) that is created to connect to the Java Web
Service DeployProxy
- DEPLOY_DATA_SHARE: (shared) transport directory (e.g. <DIR_TRANS>\data)
- DEPLOY_URL and/or DEPLOY_SLD_URL and/or DEPLOY_XI_URL and or DEPLOY_OUTBOX
Note: In the case that your non-ABAP system acts like a source system and also as a target system in your TMS landscape ensure that you apply SAP Note
Note: If you are using SAP Solution Manager 7.2 parameter CTS_SYSTEM_TYPE is not required.
Case 2. Dual-Stack systems
 The following Java parameters are added using the wizard in  transaction STMS → Create →Java Stack:
- DEPLOY_DATA_SHARE: (shared) transport directory (e.g. <DIR_TRANS>\data)
- DEPLOY_URL and/or DEPLOY_SLD_URL and/or DEPLOY_XI_URL and or DEPLOY_OUTBOX
- DEPLOY_WEB_SERVICE: CTSDEPLOY (Name of the Logical Port) that is created to connect to the Java Web Service DeployProxy)
 Ensure that CTC: 1.

2.4. Configuration of Transport Routes

Once the systems are created in /nSTMS-> Systems go to configure the Transport routes. Look an example for a Java systems landscape:

 

The transport routes for the non-ABAP system landscape can be configured as described in the standard documentation. No additional or CTS+ specific configuration is needed. Specify the transport layer used for the development system, in this case ZXAD.
More details in:
In ChaRM for non-ABAP systems, notice that we will only use the standard transport layer as they defined in STMS.  So we could only recognize one Q system. In case you have two Q systems, configure a target group to the two Q systems, this will link your D system to the group by using one transport layer, in this way both systems will be recognizable under the same "standard transport layer".

Step 3. Definition of non-ABAP Systems in LMDB/SMSY

In Solution Manager 7.1, SAP has introduced the Landscape Management Database (LMDB) as editor and store for landscape data, which works very closely with the System Landscape Directory (SLD) . With Solution Manager 7.1 SPS10, SMSY is reduced to a read-only store for landscape data (see Evolution of Landscape Data Management – Part II: What’s better with LMDB in SAP Solution Manager 7.1, SPS10? ).

How to get the non-ABAP (technical) systems into the LMDB?
- Some non-ABAP system have their own SLD data suppliers, i.e. the system can register automatically in the SLD. From the SLD they are synchronized to the LMDB.
- Systems without SLD data supplier have to be created manually in the LMDB.

 

How do non-ABAP systems get to SMSY?

- Technical systems of type non-ABAP are not always replicated from LMDB to SMSY, however, product systems are.

- Hence, it is important to assign the non-ABAP (technical) system to a product system in LMDB. The SID of the product system must be the short SID and it must correspond to the SAPSID as defined in the TMS.

- The TMS information must not be entered manually in the LMDB. It will be retrieved by the “Read system data remote” in the communication system or by the “Landscape Fetch” job and made available in SMSY.

 

Important notes for Solman system with component ST with patch level <SAPKITL710: Until this patch level ChaRM is relying on the information in SMSY for the systems managed from ChaRM, so once you have created the systems at TMS level in the domain controller system you need to ensure that this information is updated in SMSY, for that go to SMSY, select the communication system of your non-ABAP landscape and press the button "Read System Data Remote" this will ensure that the information under ABAP Transport System/Client is filled, see that you have the systems also in table SMSY_SYSTEM_OTO with the correct communication system indicated.
For source systems ABAP Transport System and ABAP transport client needs to be filled with the values indicated at TMS level for parameters COMMUNICATION_SYSTEM and NON_ABAP_WBO_CLIENT, for target systems only the ABAP Transport System will be filled showing the COMMUNICATION_SYSTEM value.
Example for a source system:
These two values cannot be maintained manually in SMSY, these values should be retrieved from TMS.
Starting in SAPKITL710 ChaRM will check the system information at LMDB level. For non-ABAP systems don´t try to find this information about communication system/client in LMDB because LMDB is not saving this information, but it is not needed.
However still you need to check that the information of the systems is in table SMSY_SYSTEM_OTO. If this is not the case please run "Read system data remote" in SMSY for the communication system.

 

For SAP Solution Manager 7.2 ensure that these SAP notes are implemented in the domain controller system of the managed landscape (also in the other systems):

  • 1977240 - Extension of the AS ABAP SLD Data Supplier (RZ70)
  • 2148577 - RZ70 always sets communication client to 000 for non-ABAP system

With this you ensure that the domain controller system is sending the information of the non-ABAP system created to the SLD of the SAP Solution Manager.

Then job SAP_LMDB_LDB_0000000001 will detect the SLD changes and will create in LMDB a technical system for the created system.

Some non-ABAP systems have their own solution landscape database (SLD) data suppliers. This means that the system can register automatically in the SLD. From the SLD they are synchronized automatically with the landscape management database (LMDB).

Systems without SLD data suppliers are created in LMDB under the Transport Domains tab where they ae created. However, they are not automatically assigned a technical system. You must therefore assign the technical system explicitly.

 Under Transport Domains tab, select the correct transport domain name for the system where you create the non-ABAP system:

Then under Non-ABAP Systems tab, select the system and assign the required technical system. 

Step 4. Definition of logical components in LMDB/SMSY / Logical component groups

SAP Solution Mananger 7.1
Depending on the patch level of the Solman 7.1 you need to create the logical component in SMSY (System Groups and Logical Components, Logical components ->Right click on Logical Components -> Create New Logical Components -> Enter name and product information) or in LMDB (select the Logical component tab).
You need to put the relevant systems into their corresponding system roles, ensure that the system entered fits with the real TMS landscape that you have.
I mean 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. For non-ABAP system you would define a logical component like:

 

The important remark here is that the logical component contains systems but NO CLIENTS.

In the case that the technical system is called for example BOD_BOE, the related Product System in LMDB will have SID BOD, the same SID than in TMS. Then in the logical component you need to use also the product SID name BOD.

 

For Dual-Stack systems define your logical component as always using system:clients.
SAP Solution Mananger 7.2
For SAP Solution Manager 7.2 you need to create a logical component group into the solution and then assign there the systems. See more details in How to create a solution for Change Request in 7.2.

Step 5. Definition of the ChaRM project /Change cycle

SAP Solution Mananger 7.1
To use Change Request Management ChaRM to manage a non-ABAP landscape, you need to define a project in the Solution Manager 7.1 in transaction SOLAR_PROJECT_ADMIN.
Call transaction SOLAR_PROJECT_ADMIN, choose New Project. Choose tab System Landscape and then tab strip Logical Components, enter your Logical component and save.

Choose tab IMG Project and create the IMG project:

The IMG project is created in the ABAP communication system:client of the development system specified in TMS parameters COMMUNICATION_SYSTEM and NON_ABAP_WBO_CLIENT. Note: don’t forget to create the RFC connections for the ABAP Communication system:client in order to be able to create the IMG project. If there are different non-ABAP development systems sharing the same communication systems, then you should create different IMG projects for each non-ABAP development system separately.

 

Please see point "25. Special considerations for non-ABAP landscapes in ChaRM" in SCN blog: Change Request Management scenario: Usual questions and known errors
For non-ABAP system, the IMG project is created on the communication system and the CTS project will be created "implicitly". That means, you will not be able to see the CTS project in SPRO_ADMIN in the communicationsystem. However if you check in table CTSPROJECT, in the solman system, the correct entry is there looking like "SID/IMG project ID”.
So, please keep in mind that you should NEVER activate the CTS project manually for non-ABAP IMG projects.
For Dual-Stack system, the IMG will be created in the development system:client indicated for the source system.
Choose tab Change Requests and select Activate Change Request Management. Choose Create Task List.

See details about how to create the project in SCN doc First steps to work with Change Request Management scenario in Solution Manager 7.1, section 4.

 

For creating change documents for the non-ABAP landscape don´t forget to create the ibase component for the non-ABAP production system or to check that the ibase component is already created.
In the case of using technical systems with longSID, extended SID, ensure that you have entered in the sort string field of the ibase component the long SID.  Enter it in the sort string value for the father and the child - - - ibase components:
Details for sort string in SAP Note 1795400- ChaRM: IBase cannot be found when creating change document.
Note: For a Java system see the KBA 2022069 - Difference in using IBase and IObject for JAVA systems of Incident management to change mamagement scenario.
You need to use in the ChaRM document the ibase component for the parent entry “<SID> + <installation number>" , don´t select ibase component “<SID> <installation> ---“.
For a Hana system only entry “<SID> + <installation number>"  will be create in IB52, select this ibase component for the ChaRM document, see note 1885728  - Change Management: support HANA managed system.
“Not all systems known in the Solution Manager know both numbers; they are only registered automatically for the system types:
AS ABAP
AS Java
HANA DB “
This means that SLD is getting the system number and installation number for ABAP, JAVA and HANA DB systems, then LMDB will have this information only for these type of system.
So, if you are using systems like SAP Netweaver Master Data Management Server MDM, SAP BusinessObjects Cluster or others technical systems then for these other systems the system registration in SLD does not provide any numbers, the link of the system to both numbers must be carried out manually. I mean only very few systems (ABAP, Java, HANA) know the concept of installation numbers. Other technologies (from SAP acquisitions) are not familiar with this installation number.
So, for ChaRM scenario up to SAP Solution Manager Release 7.1 Support Package 10 we were reading SMSY and in SMSY this information was usually filled from the SAP Service Marketplace. “The manual assignment of the installation number and system number was possible up to SAP Solution Manager Release 7.1 Support Package 5 in transaction SMSY. In Release 7.1 Support Package 5, only the system types that automatically register the numbers are supported with the Landscape Management Database (LMDB). For other system types, you currently have to use a workaround.”
Since SAP Solution Manager Release 7.1 Support Package 10 we are reading the information from the LMDB: “As of SAP Solution Manager Release 7.1 Support Package 8, it is possible to maintain the installation number and system number in the LMDB for all relevant system types. However, the numbers maintained there are not synchronized to SMSY in every case, which means that the workaround described here is not yet obsolete. For the system types AS ABAP and AS Java, the numbers - if they are unique - are automatically transferred from the technical system of LMDB to the product system in SMSY.
As of SAP Solution Manager Release 7.1 Support Package 11, it is possible to maintain the installation number and system number in the LMDB for all relevant system types.”
So in the case that you are not filling the installation number manually, then you need to implement  note  2130165 - ChaRM: no project can be selected when IBase of non-ABAP system is maintained
If the note is implemented even if the system in LMDB is not having an installation number maintained ChaRM will be able to select the correct project for the production Ibase component.
However ensure that the Ibase component for the production system is having in the Identification field the SID of the system, I am saying this because if the installation number is missing in LMDB for a BusinessObject system for example, you will see that the system in IB52 does not appears under the customer number, it appears separately under tree “Cluster SAP BusinessObjects” with an empty Identification field, please enter the BusinessObjects SID in this field manually. Note 2153616  was created to fix this issue.
In the case that you are using a non-abap system that is a virtual system please see the SCN Wiki Page Change Request Management: How to create a virtual system in Solution Manager 7.1.
Pay attention to this paragraph: "Note: If you want to create a virtual system for a non-Abap system take the following into account: strictly speaking there is no non-ABAP virtual system.

 

SAP Solution Mananger 7.2

In SAP Solution Manager 7.2 not projects will be used anymore, ChaRM and QGM will used Solutions and Change Control landscapes.

Solutions and Change Control Landscapes will have branches. Branches will contain logical component groups that will contain logical components for each branch. Inside the logical component groups you will enter your managed systems from each managed landscapes.

Then you need to create a change cycle in sm_crm and  select a solution/change control landscape and a branch for it. Only the branches containing a logical component group with a system with role source are available for selection.

Task list is created now from the change cycle document directly by using a guided procedure when moving the document from Created to Scope for example in a SMIM document.

Ensure that SAP Note 2418691 - ChaRM&QGM: Issue in adding non-ABAP system in transport track is implemented in the Solman system if you are missing the non-ABAP systems when creating the task list and selecting the transport tracks.

When you select a solution- branch for a change cycle document, the source systems in the logical component groups of the branch will be used to draw the Transport Track Overview, all other systems will be based on the whole logical component groups included in the Solution, in all branches. 

Related Content

Related Documents

Resource on CTS+  

Best Practices for Implementing CTS+  

How To Configure SAP HANA for CTS in SAP HANA SPS 09, 10 and 11

How to create a solution for Change Request in 7.2

Related Notes