Skip to Content
SAP Solution Manager

FAQs on the Enhanced Change and Transport System

This frequently asked questions document answers questions on the enhanced change and transport system, how it is integrated with the existing transport system of the SAP NetWeaver AS ABAP and where you can find additional information.


Basics

What is CTS+?

CTS (Change and Transport System) is the transport capability of the SAP NetWeaver AS ABAP. This capability has been enhanced and now, the transport of non-ABAP objects is supported as well. The ‘+' or ‘enhanced' has been added to express this.

Where can I find information on CTS+?

The Change and Transport System here on SDN provides basic information and links. The documentation on CTS+ can be found on SAP Help Portal. Use the following path to find the documentation: http://help.sap.com/NW70 -> SAP NetWeaver 7.0  -> -> SAP NetWeaver Library -> Key Capabilities of SAP NetWeaver -> Key Capabilities of Solution Life Cycle Management -> Software Life Cycle Management -> Software Logistics Change and Transport System -> Change and Transport System - Overview (BC-CTS) -> Transporting Non-ABAP Objects in Change and Transport System

What are the prerequisites for using CTS+?

CTS+ is available with AS ABAP and AS Java from SAP NetWeaver SPS 12 onwards (both stacks are needed). We recommend that you start using CTS+ with SPS 14. This is the requirement for the system which is used for transporting. The applications that are to be used with CTS+ have very different requirements. Especially, if you are willing to use loose coupling, it is also possible to use CTS+ with older releases of applications. Please make sure that note 1003674 is installed on your CTS+ system.

What are the important SAP notes?

1003674 Enhancement for non-ABAP systems in CTS
1145268 CTS+: Changes from NW 7.0 SP12 -> NW 7.0 SP13
1146170 CTS+: Changes from NW 7.0 SP13 -> NW 7.0 SP14

What do loose coupling and close coupling mean?

Loose Coupling and Close Coupling (or tight integration) describe the relation between the TMS system and the application on the export side.

  • Close coupling means that you can find mechanisms within an application (e.g. SAP NetWeaver Portal or SAP NetWeaver Development Infrastructure to attach a transportable object (e.g. epa, sda,...) to a transport request on the CTS system.
  • Loose coupling means that the application does not provide a direct integration mechanism. You would start an export within the application, download the export result and attach it manually to a transport request via the Transport organizer Web UI by uploading it again.


In most cases, the import is done automatically. This means that when importing a queue TMS calls the deployment tool of an application and hands over the files. The import is done automatically; no administrator's interaction is required. In some cases, the exported file is delivered to a designated destination and the import itself needs to be done manually. This is the case for a KM Documents' import by today. SAP Master Data Management plans to offer a CTS+ integration with MDM 7.1 as well - this integration also requires a manual import.

What is CTS_Browser / the Transport Organizer Web UI?

CTS_Browser is an ABAP Web Dynpro application which is delivered starting with SAP NetWeaver 7.0 SPS 13. CTS_Browser is a Web UI for the transport organizer. You could integrate it into an application (e.g. as an iView into the Portal). The Transport Organizer Web UI is also used e.g. in the case of close coupling to provide an option to users to create new transport requests or release an existing one. The Transport Organizer Web UI can be called via the following URL: 'Protocol'://'server':'Web AS Port'/sap/bc/webdynpro/sap/cts_browser?SYSID='SID of Development System as Configured in TMS'

System Landscape

How should my landscape look like?

You can find a How-To guide containing recommendations for a system landscape on SDN.

Which Applications are supported by CTS+?

You can find a list of supported objects on the SAP Help Portal. Use the following path to find the list: http://help.sap.com/NW70 -> SAP NetWeaver 7.0  -> -> SAP NetWeaver Library -> Key Capabilities of SAP NetWeaver -> Key Capabilities of Solution Life Cycle Management -> Software Life Cycle Management -> Software Logistics Change and Transport System -> Change and Transport System - Overview (BC-CTS) -> Transporting Non-ABAP Objects in Change and Transport System

Do I have to use a Dual Stack System for CTS+?

We recommend that you use the SAP Solution Manager for CTS+. But it is also possible to use an SAP NetWeaver AS ABAP and an AS Java of separated systems.

Does the CTS-System have to have the same SP level as the application?

Not necessarily. We recommend that you start using CTS+ with SAP NetWeaver 7.0 SPS 14. If you would like to use close coupling, please take a look at the release notes to find out which release of the application is required to be able to use CTS+ in close coupling mode. There might also be some pre-requisites on the SP level of the CTS. The release notes are provided on the SAP Help Portal. 
If you would like to use loose coupling, the variety of possible SP levels is much bigger. Please have a look at question ‘How does CTS+ work within the different applications?' on this page to find out more.

How does CTS+ work within the different applications?

There are several How-To Guides and sections on SAP Help Portal which explain how CTS+ works and what is the scope of the transports. You can find the how to guides on SDN by searching for CTS+ and the application name. Please make sure that the guide you are using fits with your release.

  • SAP NetWeaver Portal (EP)
    Close coupling is described on the SAP Help Portal and is available since SAP NetWeaver 7.0 SPS 13. A How-To guide describes the configuration steps.
    Loose coupling possible from SAP NetWeaver 2004 SPS 9 onwards.

  • Knowledge Management (KM)
    Close coupling for Documents is available since SAP NetWeaver 7.0 SPS 14
    Lose coupling for KM documents is also available for SAP NetWeaver 7.0 SPS 13 if you use the Transport of KM Content provided with SAP NetWeaver 7.0 SPS 13. 
    Close coupling for KM Configurations is provided with SAP NetWeaver 7.0 SPS 14. This delivery contains a small bug and works only with a fixed user. Take a look at SAP Note 1291022 to learn about the patch that you need for your SP to fix the issue. Loose coupling with earlier releases is only possible via file system transport and would require a manual import.

  • SAP NetWeaver Exchange Infrastructure (XI / PI)
    Information on functionality and appropriate releases is provided on SAP Help Portal.
    Here on SDN, you can find a HowTo Guide for SPS 14 and a HowTo Guide for SPS 13 of PI.

  • System Landscape Directory (SLD)
    Integration of CTS+ in SLD is available since SAP NetWeaver 7.0 SPS 13. Check SAP note 1101844 for details on features and limitations for specific Service Packs.

  • SAP NetWeaver Development Infrastructure (NWDI)
    Integration of CTS+ in NWDI is available  since SAP NetWeaver 7.0 SPS 14.

  • SAP NetWeaver Master Data Management (MDM)
    Loose coupling is planned to be provided with SAP NetWeaver Master Data Management 7.1 and SAP enhancement package 1 for SAP NetWeaver 7.0 for the CTS system.

  • SAP NetWeaver Business Intelligence (BI)
    If you would like to transport BI objects, this is either a question of transporting Portal content or ABAP objects. There is no special guide for BI available, so please take a look at the objects that you'd like to transport and use the appropriate guide or help pages.


Troubleshooting

I have trouble using CTS+. Where can I find hints what might be wrong?

SAP note 1172252: CTS+, 'attach file': Troubleshooting Guide
SAP note 1155884: CTS+, configuration 'close coupling': Troubleshooting guide
SAP note 1170359: Tracing the Deploy Proxy

I am using CE, there the Deploy Controller is used, not SDM – can I use CTS as well?

Starting with SPS 14, you can use CTS+ for CE as well. Just use the option ‘SDM' and change the system settings of the target system (for example the port needs to be set to 50004 instead of 50018 and an engine user with deployment rights has to be specified). These settings are automatically generated when you create the non-ABAP system in transaction STMS. Open the details of the system after having finished the wizard and make your changes.
You can't run the deploy web service on your SAP NetWeaver Composition Environment 7.1 system. The same is valid if you are using enhancement package 1 for SAP NetWeaver Composition Environment.
The recommendation is to use the SAP Solution Manager as CTS system and to make use of the deploy web service on this system.

Which user do I have to enter in the Pop-up 'Set User and Password for Deployment SDM' when creating a non-ABAP system?

If you chose the deployment method SDM when creating a non-ABAP target system, you will be asked for password for this deployment method in the next step. Enter the user name SDM and the SDM password. If your target system is an SAP NetWeaver Composition Environment (CE) System, the deploy controller is used for deployments. In this case, you have to enter an engine user. Take a look at the previous question for details about using a CE system as target system.

Which permissions are required to import SLD objects?

The user that you enter for 'SLD User / Password' has to have the role SAP_SLD_ADMINISTRATOR on the SLD. This permission is also required if you use the SLD on the PI server. You could enter different users in TMS for the SLD and the PI deployments. If you decide to use the same user for both deployments, then this user has to have permissions for both PI and SLD deployment.

Handling Transports

How is a transport request created? Can I influence the behavior?

You can define a transport strategy to define e.g. whether a new transport request is generated automatically and if it should also be released automatically. Have a look at the SAP Help Portal to find out more about the configuration.

How can I handle (create / release) transport requests?

If close coupling is provide for the application that you are using, you can define different parameters to influence the behavior of the CTS for creating transport requests and releasing them.
If loose coupling is used, the parameters for creating and releasing transport requests automatically are not relevant.

Can I transport any file type via CTS+?

Yes, you have to configure a file share where files types that are not automatically deployed can be stored. This means that the import has to be done manually. Make sure that the file type foreseen to be used for manual import is not used for automatic deployment within your landscape.

Which deployment tools are used?

When creating a non-ABAP-System in TMS, you can choose the deployment method. SDM is one of them. In addition, you can choose XI, SLD or File. In case of File deployment you have to specify certain tp parameters (deploy_outbox). All files to be deployed will be put there. Starting with version 372.04.22 of tp it is possible to specify that only files of type ‘File' go to the deploy outbox. The configuration is described on SAP Help Portal

How can I release a transport request?

Use the Transport Organizer Web UI. There you can mark a certain Transport Request and release it.

Functionality

Does CTS+ provide a change recording?

CTS+ is responsible mainly for the logistics of transports. If the application does not provide change recording, CTS+ does not add this functionality. The Change Recording used within ABAP (e.g. when editing objects in SE80 or changing customizing) can not be used for non-ABAP objects.

Which functionality is provided in which release?

Have a look at the guides and links provided in question ‘How does CTS+ work within the different applications?'. They will help you finding out what is relevant for the application that you would like to use.

Can I use SE09?

SE09 is made for ABAP transports. You have to use the Transport Organizer Web UI (the ABAP Web Dynpro Application CTS_Browser) to create transport requests for non-ABAP objects and should use it for all other functionality as well. You can use SE03 for displaying purposes.

How can I import a transport request – I can’t find this functionality in Transport organizer Web UI

Starting an import is not part of the functionality of the transport organizer Web UI. Log on to your TMS system and use the transaction STSM_QUEUES.

How can the developer / content creator find out about the status of his transport?

The developer / content creator of an application does not have to learn how to use the administrative tools of AS ABAP. Use the transport organizer Web UI. The tab ‘logs' provides information about the import status for a transport request.

Can I use the Team capabilities that I know from ABAP transports?

With SAP NetWeaver 7.0 EhP1, we provide an option to work in teams. Please use the ‘add user' functionality in the Transport Organizer Web UI. Don't set up a transport request for different users as you know it from ABAP.

How can I restrict the permissions for users in the TMS?

With SPS 16, the role SAP_CTS_PLUS is provided. Make sure that the role is available in the client that you are using for transports and that it includes the profile S_ACTSPLUS. If you are not using SPS 16, you could create a role with the following authorizations: S_ICF, S_RFC, S_CTS_ADMI, S_DATASET and S_TRANSPRT.

Can I transport ABAP and Java objects within the same transport request?

Yes. Depending on the target server type (ABAP, J2EE, Dual stack) only the matching transport objects will be deployed.

How can I make sure that the Java and ABAP parts of my new functionality are transported in a synchronized way?

If you are using a dual stack system, put them in the same transport request. If ABAP and java parts have to be delivered to separate systems, there is no automatic way for synchronizing transports in the moment. It is planned to provide additional synchronization mechanism for the Change Request Management within SAP Solution Manager.

What is SODIS_CORE_WBO?

SODIS_CORE_WBO is the predecessor of CTS_BROWSER. It is the name of the ABAP Web Dynpro Application that was used in SAP NetWeaver 7.0 SPS 12 to manage transport requests. It is only available in SPS 12. Starting with SPS 13, you have to use CTS_BROWSER. Please have a look at note 1003674 for details.

Former Member

No comments