Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

CTS+ over CMS??


Is CTS+ mature enough to be chosen over CMS? Can you please share your opinions about it? last time I checked were a lot of bugs to be fixed.

Thanks in advance.

Former Member
Former Member replied


What is CTS+ and why is is introduced:

The Change and Transport System (CTS) is a tool that helps you to organize development projects in the ABAP Workbench and in Customizing, and then transport the changes between the SAP Systems in your system landscape.

The XI use case for CTS+ introduces a new transport handling mechanism that offers tighter integration for the transport of ABAP, Java, and Integration Builder objects (Integration Repository and Integration Directory) using the Change and Transport System (BC-CTS) functionality.

As your XI system requires both the ABAP and the Java stack of the SAP NetWeaver Application Server, the following transport tools are available after installation:


The ABAP transport environment (BC-CTS)


The file export and import mechanisms or CMS integration to transport Repository or Directory objects in your transport landscape

In addition, you might also have to transport Java development objects by using the SAP NetWeaver Development Infrastructure itself.

The enhancements to CTS in combination with the SAP Solution Manager Change Request Management (ChaRM) address the following issues:


Synchronized transports for mixed systems (ABAP & Java)


A unified application for mixed system landscapes


Tracking of non-ABAP transports including Change Request Management

For your XI landscapes there will be one central transport environment with CTS+ where you can manage all XI-relevant transport objects from a single entry point.

This how-to guide describes the configuration settings you must make in the CTS+ system and XI systems. The functionality must be set up according to the release version of the integrated XI system. The two configurations will be described separately:


Configuration setup for releases prior to SAP NetWeaver 7.0 SPS12 (also for SAP NetWeaver 2004 SPS14 and higher).


Configuration setup for release SAP NetWeaver 7.0 SPS12 and higher.

Refer the link for CTS+ step by step method of transport:

CMS is generally used to transport Java development objects. The XI Integration Server uses CMS to transport Integration Server content. When the Integration Server uses CMS to transport XI Content, no Component Build Service (CBS) or Design Time Repository (DTR) is used and can therefore be switched off. If you want to transport Integration Server content and Java developments (Java proxies or adapter modules), the CBS and DTR must be running.

If you transport Java developments, you should keep in mind that deployment of Java code can destabilize the runtime environment. Therefore, it is beneficial to install CMS on a separate server, as described in SAP Note 737368 for NWDI.

In this How-to Guide, CMS is installed together with an Integration Server system in the development environment. The advantage of this approach is that you have fewer steps in user management and CMS cannot influence the runtime of a productive environment.

With the enhancements of the SAP NetWeaver Change and Transport System (CTS for short, or CTS+ respectively, if specifically the enhanced capabilities are meant), available with SPS12 of SAP NetWeaver 7.0, the CTS has been enhanced to handle any type of object that can be transported in an SAP system landscape. Therefore, an administrator of your ABAP system can now also manage the transports for the non-ABAP parts of your system landscape.

You can now use CTS to transport (almost) arbitrary objects in an SAP system landscape with transport orders of the Transport Organizer:


Enterprise Portal archives (EPAs)


Exchange Infrastructure objects (TPZs)


Software component archives (SCAs)


Software delivery archives (SDAs)


Enterprise Application Archives (EARs)


ABAP objects

Development objects will be deployed according to their application type. Objects in a single transport order can be a mixture of all types u2013 however that only makes sense, if both are intended for the same system because transport paths are defined in the transport domain controller system.

CTS+ and usage type PI (SAP NetWeaver Exchange Infrastructure, XI)


If you are not using the Change Management Service CMS of the NWDI, you should seriously consider using CTS+ for your XI transports (CTS+ & SAP NetWeaver usage type PI).


If you are already using the CMS, you should postpone any planned migration to use CTS+ up to availability of SAP NetWeaver 7.0 SPS 13 , where integration will be enhanced futher.


In any case you should evaluate the enhanced CTS options of SAP NetWeaver 7.0 comming with SPS 12 and extensions planned with SPS 13/14 for XI transports u2013 in the mid and long term CTS+ is the best practice recommended by SAP for XI tranports.

Read this to have more details on CMS and it's use with XI

CMS for SAP Exchange Infrastructure

Configuration of CMS in Central NWDI & SLD to transport XI objects

Configuration of CMS in Central NWDI & SLD to transport XI objects

How to Use CMS in XI 3.0.pdf

CMS based transport in XI



0 View this answer in context

Helpful Answer

Not what you were looking for? View more on this topic or Ask a question