Skip to Content
Technical Articles
Author's profile photo Wolf Hengevoss

Better Manage SLD Exports and Imports Using CTS+

SLD Data Distribution in the System Landscape

A typical SLD topology in a landscape can be described as follows: There are three main landscape areas with an SLD system of their own:

  • One SLD in the non-productive area
  • One SLD in the productive area
  • One SLD for the SAP Solution Manager, which manages systems in the landscape

The following figure shows the SLD systems in such a landscape:

SLD systems in_a landscape and their mechanismsof sychronization

SLD systems in the landscape and the main pathes of data exchange between them. The “selective transport” from design-time SLD of the development area to runtime SLD in the production can be improved by using CTS+

You may also have additional instances for backup, as sandbox systems or to distribute the work load. For details, please always refer to the SLD Planning Guide on the System Landscape Directory (SLD).

SLD systems in the landscape share information with each other. Typically, there is forwarding of technical systems data from the productive SLD to all the others, there may be Demo: The Full Automatic Sync Feature in the SLD of SAP NetWeaver 7.1 when an How to Ensure that SLD Data is Available during Maintenance is used, and – very important for SAP NetWeaver Process Integration – the export and import of SLD data. The latter specifically is needed to transport content used by the SAP NetWeaver Process Integration from development to production. When transporting manually developed SLD content from the development into the productive SLD, full control of content and point in time when it is shipped makes the export / import procedure the appropriate mechanism to distribute information.

When and Why Use CTS+?

However, this is a manual procedure; therefore many steps are not explicitly handled by the SLD – e.g. the storage and transport of the export file. However, with SAP NetWeaver 7.0 SP 12 the Change and Transport System (CTS) learned to transport Non-ABAP content also, and is therefore often referred to as “CTS+”. It is now the preferable transport mechanism for many types of SAP content and further on SAP will add support for new applications. You will find an overview of transport options with CTS+ in the SAP Help Portal.

As of SAP NetWeaver 7.0 SP 14 SLD content is also integrated with CTS+. Things run in a more controlled way when using this transport landscape:

  • Exported file(s) is (are) directly attached to a transport request
  • Transport routes clearly define source and target systems
  • Logs clearly show the state of each request for developers and administrators
  • Imports are shown in the CTS+ system with all other requests
  • Imports can be triggered, scheduled, and monitored centrally

SAP NetWeaver Software Change Management can be found in the SDN.

One hint might be helpful when using CTS+ in this scenario: Import of business systems does require that software components and technical systems used in the imported business systems are available in the target SLD. Usually the technical systems are available in the SLD of the production area (see SLD Planning Guide). This is not the case for the freshly software components developed. If anything is missing in the target SLD all required content can be transported in one transport request. If you choose this option, make sure to add the different export files to the transport request in the correct sequence: first add the objects that are a prerequisite for the import of the other.


In the scenario two SLDs are used. The CTS+ system is fully configured and so are the SLD systems, including settings needed to use CTS+ for SLD transports: The source SLD has got a connection to the CTS+ system, and both source and target SLD have been made known to the CTS+ system and connected with a transport route.

This is a possible scenario:

  • In the 1st SLD – let’s say the development SLD business systems have been created.
  • These business systems are exported. When exporting them a transport request has been created automatically, to which the export is attached.
  • The developer checks and releases the request in a Web UI.
  • In the CTS system source and target SLD are shown.
  • In the target system the import is triggered by the system administrator.
  • When checking the content of the target system, the business systems that have been exported from the source SLD are shown.

For a documentation of Transporting SLD Data Using CTS.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Igor Baylychev
      Igor Baylychev

      Please, upload demo in different format.

      Author's profile photo Wolf Hengevoss
      Wolf Hengevoss
      Blog Post Author

      Dear Igor,

      thanks for letting me know that this is not working any longer. Please refer to the documentation, instead: Transporting SLD Data Using CTS  (

      Best Regards,

      Wolf Hengevoss