Show TOC

Procedure documentationConfiguring Systems for Activity-Based SDA Transports Locate this document in the navigation structure


To be able to use the Activity-based Transport, the following parts of your landscape need to be at level enhancement package 2 for SAP NetWeaver 7.0 at least:

  • SAP NetWeaver Developer Studio

  • Component Build Service (CBS) and Design Time Repository (DTR) of SAP NetWeaver Development Infrastructure (NWDI)

  • AS Java where CM Services run

  • TMS Domain Controller (AS ABAP and AS Java that are used for transporting non-ABAP object, for example, an SAP Solution Manager System)


  1. Create a development configuration for the development system.

    For this you have to set the Create Development Configuration flag when creating a new system in the Transport Management System.

    More information, see Defining and Configuring Non-ABAP Systems.

  2. When creating the first system, enter the URL to a System Landscape Directory (SLD).

    More information, see Defining and Configuring Non-ABAP Systems, step 6.

  3. Configure the development configuration in the Configuration Service.

    For example, here you enter information on the Design Time Repository, Component Build Service, and software components to be developed in the development configuration.

    For more information, see Using the Configuration Service.

    To activate the Activity-based SDA Transport, choose the option Deployable Export in Transport Settings on the Local Settings tab page and select the Activities checkbox.

    For more information, see Managing Transport Settings.

  4. Create an Upload System.

    To be able to execute your development you need archives in the development system that contains basis libraries delivered by SAP. You have to transport these archives to the development system. If you want to modify software delivered by SAP, you also need the sources of all aplication that you want to perform modifications for. You need the same archives that you used when structuring the runtime system.

    For this transport you have to create an upload system where archives can be included in a transport request and then transported on to the development system.

    For more information, see Creating an Upload System.

  5. Create a transport request for the Upload system and add the required archives with basis libraries to the transport request.

    For more information, see Using an Upload System.


You have configured your system for transporting Activity-based SDAs.

When releasing an activity in SAP NetWeaver Developer Studio, the released runtime objects that are based on the released Activity (packaged as a Development Infrastructure Package file - .DIP) are attached to a CTS transport request.

For more information, see Releasing the Software to the Transport System.

The transport request with the attached .DIP file can be imported with the transaction STMS in the follow-on systems. As part of this, the runtime objects that belong to the Activity are deployed on the runtime system.