Show TOC Start of Content Area

Procedure documentation Creating a Development Track  Locate the document in its SAP Library structure


To create one or more software components (SCs), you require a development track.


      You have configured a domain. Applications SLD, DTR, and CBS have been started and can be called.

      You are in Landscape Configurator in CMS on the Track Data screen.


To create a development track, perform the following steps:


       1.      Choose New. All input fields are now empty and ready for you to enter data. Default URLs are entered for DTR and CBS.

       2.      Enter the following information:


If you are working with proxy settings in SAP NetWeaver Developer Studio, you must enter fully-specified URLs in the URL fields of the track configuration. If you do not do this, the Developer Studio cannot communicate with SAP NetWeaver Development Infrastructure (NWDI).

Track Parameters

Parameter Name


Track Template

Type of track that you are creating. Types DTR and XI currently exist. Choose template DTR.

Track ID

Technical key of the track. This track ID can have a maximum of eight characters. You can choose this track ID only when you create the track for the first time. Once you save it for the first time, it can no longer be changed.

Track Name

User-defined name of the track used for the display in the user interface. The track name must be unique within the domain.

The name can have up to 20 characters.

Track Description

Description of the track. This description can include, for example, the function of the track, such as Development of software component (SC) xy, repair track for SC yz.

Final Assembly Track

Select this field if you want to create SC versions in this track and deliver them to customers.


HTTP address of the server on which the DTR is installed.

(Input value: http://<host name>:<port number>/dtr)


HTTP address of the server on which the CBS is installed.

(Input value: http://<host name>:<port number>)

Development Configuration

Name of the development configuration in which you are working in Developer Studio.

To make it easier to find them, the development configurations always have the name of the track and cannot be changed.

Development Configuration Description

Description of the development configuration.

It matches the Description track and cannot be changed.

Development Configuration Path

Hierarchical path used to structure the development configurations when they are downloaded in Developer Studio.

Use the paths to put tracks in groups of development configurations with related content. (Example values:



Connected to CTS

Indicates that the track is connected with the Change and Transport System (CTS) of the Application Server ABAP (AS ABAP). This option is needed if you want to configure transports of SCA files using TMS transport requests. To be able to use this option the NWDI server needs to be configured for CTS integration. More information: Transports in Heterogeneous SAP System Landscape.

CTS Upload System

Indicates the SID of the CTS non-ABAP source system for which transport requests are created. For example JAD.

       3.      In the Software Components (SC)table, choose the Add SC.... function. The Software Components and Usage Dependencies dialog box appears. The table shows you all available SC releases.

You can filter this list and sort the data in ascending or descending order.

       4.      In the table, select those SC releases that you want to develop in the track and choose the correct package type (the default is Source and Archive). You use the Developed column to specify whether the SC is added to the track configuration as a developed or required SC. For more information about the package type, see Package Types.


Required Software Components are SCs on which the new SCs have dependencies. You must define these dependencies when you create the SCs in the SLD. You can also define build dependencies of SCs in CMS itself. For more information, see Editing Dependencies Between Software Components.

Choose Add. The selected SCs are inserted in the table. CMS also checks the dependency relationships defined for the SC in SLD and adds them to the track configuration.

       5.      If required, repeat this procedure for all SCs that you want to develop in this track and then exit the dialog box by choosing Close.


The table allows you to select more than one entry. You can also copy all SCs to the Software Components(SC) table.

       6.      (Optional) If you want to configure runtime systems, switch to the Runtime Systems tab page. For more information, see Configuring Runtime Systems.

       7.      (Optional) If you want to configure build variants and build options, choose the Build Variants tab page. For more information, see Configuring Build Variants and Build Options.

       8.      Choose Save.


CMS generates a track for the development of the specified SCs. This also generates development configurations for both the development state and consolidation state of the SC. You can then download these development configurations in Developer Studio. The different development configurations can be identified by their name extensions.


The DevConf development configuration, for example, is located under the following names in Developer Studio:

       DevConf_D for development

       DevConf_C for consolidation

End of Content Area