Show TOC

Transport Units for CMS Transports (Integration Directory)Locate this document in the navigation structure

A change list enables a collective release of changes to various objects in the Integration Directory. With regard to transports, it stands to reason that those objects that have been changed are exactly those objects that you want to transport. Transporting on the change list level therefore simplifies the selection of changed objects during development.
Alternatively, you can group transport lists containing object sets that are independent of a change list together in the transport wizard.

For prerequisites, see Transport of Configuration Objects (Integration Directory).


Creating Transport or Change Lists

  • Transport ListsThe Integration Builder creates a transport list when you group objects together by using the transport wizard in Transporting CMS mode. The name of the transport list is displayed later during the transport. Once you have performed all the steps in the transport wizard, the transport list is transferred directly to CMS and is visible on the Change Lists tab page. As usual, the last active version of the objects is exported.
  • Change ListsThe Integration Builder creates a standard change list as soon as an object is saved or deleted by a user who has not yet been assigned a change list. Since you cannot change the name of the standard change list, we recommend that you create your own change list before saving or deleting an object. The name of the change list is displayed later during the transport. Once activated, an open change list has the status transportable. You can then either transfer the change list to CMS (context menu Transport) or close the change list (Close Without Transport) on the Change Lists tab page. In the first case, the changes contained in the change list are exported. This corresponds to the object versions at the time of release of the change list (see the example below).

Status of Change Lists and Transport Lists

The following figure gives you an overview of the different statuses that change lists and transport lists can have:

The different statuses are displayed in the quick info for either the transport or change list, and when searching for transports .

Notes on Status "Waiting for Export"

The following procedure refers to direct exports from the Integration Builder (for Directory transports).

  • Following exports from development systems, the status Waiting for Export is only visible for a short time in the Integration Builder, then it changes to either Export Failed or Closed.
  • Following exports from consolidation systems, the change or transport list in the Integration Builder has the status Waiting for Export at first. Such exports are usually performed for selective changes in the Integration Directory and are possible in addition to the normal transport path in CMS. Following exports from a consolidation system, these selective changes are not displayed on the Assembly tab page. To display them, choose Assemble Component(s) on this tab page in the Transport Studio. For more information about the options provided there, see the table under Transport of Configuration Objects . The status does not change in the Integration Builder until after assembly of the selective changes.

Unlike in the Enterprise Services Repository, in the Integration Directory there are no software component versions. The use of the Change Management Service for directory transports presupposes that, as with repository transports, that an XI track has been entered in the Landscape Configurator that references a software component version. For directory transporte enter SAP-INTDIR 7.1 (EXCHANGE DIRECTORY 7.1)for software component version. You can then, using this XI track, transport the entire content of the Integration Directory, or parts of it, using transport or change lists.

If you release changes in the Integration Directory using a change list then the status in the change list in the meantime becomes transportable. You have the control over this status of when and whether changes are to be transported.

You can make new changes to objects in transportable change lists before transport. The result of this is that different versions of an object can exist in different transportable change lists. The following figure provides an example:

The transportable change list CL1 contains three objects. At the time CL1 was released, both objects Object2 and Object3 had version 1 and Object1 had version 2. After this, the objects Object2 and Object3 were changed using other change lists. You now have the following options:

  • To transport the object versions in change list CL1, use the Transport function on the Change Lists tab page.
  • To transport the current object versions, create a transport list by using the transport wizard.