Show TOC

Transporting Configuration ObjectsLocate this document in the navigation structure


You can transport configuration objects from the development directory to a consolidation directory, and from there to a productive directory. The following figure shows the usual transport units:


The first sections describe the normal transport path using CMS. In this case, you only transport changes in the development system with the Integration Builder; you control the rest of the transport to the consolidation and productive systems by using the CMS Transport Studio.

The last section deals with exports from the Integration Builder of the consolidation system, which may be necessary in the event of selective changes at short notice.

For more information about other possible transport scenarios, see PI-Transports Using the Change Management Service .


You have created an XI track in the Landscape Configurator and entered the addresses of the development, consolidation, and productive directory. There are no software component versions in the Integration Directory. Therefore, for directory transports using the CMS, you specify the software component version SAP-INTDIR 7.1 (EXCHANGE DIRECTORY 7.1) . This refers to all configuration objects of the Integration Directory.

Once you have made this setting, you can create transport lists for the CMS. The status of the change lists no longer changes to Closed immediately after their release, but first changes to Transportable.


You can deactivate the transport of change lists by using CMS (see also: Deactivating Change List Transports ).

Process Flow

(1) Transporting from the Development to the Consolidation Directory

The transport has two steps: You use the Integration Builder to export your changes from the development directory and then use the Transport Studio to transport the changes to the consolidation system.

Exporting Transport Lists

To release changes to the CMS for transport to the consolidation directory, you use transport lists. The transport sequence is important. To keep the number of units to be transported small and easy to check, you are therefore not permitted to transport using change lists in the development directory (see also: Integration Directory Transports ).


Use an appropriate name for your transport list. The name you use is visible in the Transport Studio later.

  1. In the Integration Builder of the development directory, generate a transport list using the transport wizard (Tools → Export Configuration Objects).
  2. The Integration Builder transfers the change list to the Transport Studio; see below. No further steps are required in the Integration Builder.

Transporting Changes to the Consolidation System in the Transport Studio

A change request for the change or transport list appears in the Transport Studio on the Consolidation tab page.

  1. To transport the changes to the consolidation directory, choose Import on the tab page. Once the CMS has imported the changes in the change request to the consolidation directory, the Transport Studio removes the change requests from the Consolidation tab page.
  2. Unlike in repository transports, the Integration Builder first generates an open change list for each imported transport list. This enables you to check changes before activating them for runtime. Adapt the objects according to the consolidation system landscape and then release the change list(s).
  3. Once the change lists have been released, the Transport Studio adds them to the list on the Assembly tab page, where they have the status Waiting for assembly.

(2) Transporting from the Consolidation to the Productive Directory

When transporting to the productive directory, you transport the change lists that you released after import to the consolidation directory to the productive system:

  1. In the Transport Studio, select the Assembly tab page. This tab page displays a list of those transport lists that have been imported from the development directory to the consolidation directory. They have the status Waiting for assembly.
  2. Choose Assemble component(s).
    • If the consolidation directory is still in the initial status (first import from the development directory), a complete copy of the Integration Directory is created. A dialog box appears, where you can select the assembly options and start the assembly. The complete copy contains all active objects of the consolidation directory, including the transport lists imported from the development directory.
    • If changes have been made in the consolidation directory independently of the imported transport lists and released to the CMS, a dialog box appears, in which you can select which of these changes to transport (for more information, see the following section). You have two options:
      • If you only want to transport these changes, select the change or transport lists that you want to transport in the dialog box (you can select multiple entries by using CTRL and SHIFT), and choose Subset Assembly. Only those lists selected in the dialog box are transported.
      • If you want to make a complete copy of the Integration Directory, including the changes (displayed in the dialog box) and all active objects of the consolidation directory (including the transport lists imported from the development directory), do not choose Subset Assembly.

Assembly Options

Option Use

Subset Assembly

If this option is selected, only the change and transport lists selected in the dialog box are considered in assembly. If it is not selected, a complete copy of the software component version is created.

Assembly Mode

You use the Assembly Mode to determine how the CMS handles unresolved import conflicts in the productive repository.

Stop if a component is inconsistent (Default) Assembly is terminated if there are any unresolved import conflicts.

Assemble consistent component(s) only Assembly is executed for all consistent software component versions. Inconsistent software component versions are skipped.

Assemble inconsistent components too The same as the last mode, except that inconsistent software component versions are also included.

  1. Once assembly is complete, you must confirm or reject the import of the change and transport lists to the productive system on the Approval tab page. Rejected imports are removed from the track and are no longer visible on the Assembly tab page (except in the history). Therefore, you must reimport any changes from rejected imports from the Integration Builder.
  2. Import your changes to the productive directory on the Production tab page.

    Note that in directory transports the sequence of transport, confirmation, and import is relevant in the assembly, approval, and production steps of the Transport Studio.

Selective Exports from the Consolidation Directory

When you transport using CMS, the entire contents of the Integration Directory are always transported. After an initial complete copy of the consolidation directory, you will not usually want to transport the complete Integration Directory each time. To transport changes in the consolidation directory to the productive directory, proceed as follows:

  1. Instead of starting the export using the Transport Studio, export the relevant transport or change lists directly from the Integration Builder of the consolidation directory. The Integration Builder displays the status Waiting for Export for these exports.
  2. The Transport Studio does not display the entries for these exports directly on the Assembly tab page. To use the Transport Studio to transport the transport or change lists exported in the last step, choose Assemble component(s) on this tab page. The following dialog window displays the entries for the exported changes for the selective transport. Therefore, before assembly, choose the Subset Assembly option so that the assembly will only include the change or transport lists shown in the dialog window (the other options are described in the table above).
  3. Once you have started the transport using the Transport Studio as described in the last step, the status in the Integration Builder changes to either Closed or Export Failed.