Show TOC

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


To be able to use the Activity Transport, the following parts of your landscape need to be at level enhancement package 1 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 development configurations for non-ABAP systems.

    You have to create a development configuration for every runtime system in your landscape. 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 Transport, choose the option Source 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.

    Since changed sources are transported with Activity Transports, you have to perform a re-build for development components (DCs) in every system of the landscape. To make the Re-Build possible, archives that contain basis libraries delivered by SAP are required in every system where a re-build takes place. These archives must be transported into all systems. If you want to modify software delivered by SAP, you also need the sources of all applications that you want to perform modifications for. You need the same archives that you used when structuring the runtime system.

    Note Note

    You can only modify the applications delivered by SAP if the archives contain the required sources and they are released for modifications.

    End of the note.

    You have to create an Upload system for the transport for which you have to create a transport request where you can include the archives.

    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 activities.

When releasing an activity in SAP NetWeaver Developer Studio, the released activity (changed sources packaged as a Development Infrastructure Package file - .DIP) is 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. In this way the modified sources are integrated into the related workspace in the Design Time Repository. A re-build is executed for the affected Development Components and the deployable development components are depoyed on the runtime system.