Show TOC

Transporting Non-ABAP Objects in Change and Transport System Locate this document in the navigation structure


The enhanced Change and Transport System enables you to transport Java objects and SAP-related non-ABAP applications in your system landscape, alongside ABAP objects. You can also administer non-ABAP systems in a CTS transport domain in SAP NetWeaver Application Server ABAP.

The aim is to have one transport tool that supports all development workbenches and applications with one tool. The tools for creating applications and content remain the same. The different workbenches of the applications offer options to attach your objects to a CTS transport request. The level of integration depends on the particular workbench.

In this way the enhanced Change and Transport System provides a unified transport tool and makes the work of administrators easier when executing imports. You only need access to one tool to execute imports for different backend systems. The deployment tools are called automatically. CTS allows you to monitor imports and analyze errors. The queues and history in CTS give an overview of imports that have already been executed or which are planned.

Transportable Objects

You can use CTS to transport the following additional objects:

  • Content objects of the System Landscape Directory (SLD) (products, software components, technical systems, and business systems)

    More information: Transporting SLD Data Using CTS

  • Modifications to repository metadata of SAP Master Data Management 7.1

    More information:   MDM 7.1   Setup and Use the MDM Change Transport with CTS+  

You can transport these objects together with ABAP objects in a single transport request. When you run imports in Transport Management System (TMS), the system performs the appropriate deployment step automatically.

Best practices, and any exceptions or constraints to this information are documented in SAP Note 1003674.

Implementation Considerations

The enhanced CTS functions are available as of SPS 12 of SAP NetWeaver 7.0. For an overview of the functions provided by each SPS, see the Release Notes.

You need an SAP NetWeaver Application Server ABAP and an SAP NetWeaver Application Server Java for the CTS system. We recommend that you use a dual-stack system (such as an SAP Solution Manager system) as the domain controller.

Note Note

You can also use the Java components of the enhanced CTS on the SAP NetWeaver Application Server Java of a different SAP NetWeaver system. You only need the SAP NetWeaver Application Server ABAP as the domain controller in this case.

End of the note.


The enhanced functions are integrated into Change and Transport System. The UIs of the associated applications have also been enhanced.

You can connect the following SAP applications closely to CTS, that is, non-ABAP objects can be attached to transport requests directly from the SAP application:

  • SAP NetWeaver Development Infrastructure (NWDI)

  • SAP NetWeaver Developer Studio (NWDS) (only valid in connection with CM Services for NWDS with status 7.0x)

  • SAP NetWeaver Portal

  • Process Integration (PI)

  • System Landscape Directory (SLD)

If you use NWDI then as of enhancement package 1 for SAP NetWeaver 7.0 you have the following options for executing transports:

  • You can still execute your transports with the Change Management Service (CMS) of the NWDI.

    For more information, see Scenarios and Recommendations on Using CTS and NWDI.

  • You can execute transports using CM Services (Change Management Services) that are delivered as part of SAP NetWeaver Application Server Java (AS Java).

    You can use this current version to manage development configurations in Transport Management System (TMS) and to transport both SDAs that are based on released activities (.DIPs) and versions of a development component (SDA) as well as an entire software component (SCA) in transport requests.

    More information about CM Services, see Using CM Services.


In some scenarios, you need to perform some manual actions when you add objects to transport requests. Some object types require you to perform manual actions after the deployment as well. Refer to the individual application's documentation for more information.

Even if you only want to use enhanced CTS for non-ABAP systems, you still require an SAP NetWeaver Application Server ABAP for the domain controller.

Only Unicode systems are supported as communication systems where the Transport Organizer Web UI runs.

You must use Transport Organizer Web UI for the creation and administration of transport requests for non-ABAP systems. Transport Organizer Classic UI (transaction SE09) is only suitable for ABAP-only systems and dual-stack systems. We recommend that you use the Web UI for the non-ABAP objects of a dual-stack system as well.