Show TOC

Procedure documentationUsing the Export Service Locate this document in the navigation structure


You use the Export Service to export software components (SCAs) or development components (SDAs) from the system. When exporting, SCAs or SDAs are attached to a transport request which you can then import into the follow-on systems of your transport landscape.

The Export Service guides you step-by-step through the export process. Choose Next to proceed to the next step. Using pushbutton Back you can return to the previous step.


You have called the Export Service. You selected the DI Export Service link in the Configuration Service for this.

Recommendation Recommendation

If you use the Export Service frequently, you can save the URL in your browser favorites to make it easier to call in future.

End of the recommendation.


  1. In the Export Mode step, select the system ID from the selection list of the system from where you want to execute the export.

    In addition to this, in the Export Mode area, select whether you want to export SCAs or SDAs.

    Consistent software components are exported when performing SCA exports. The deployable units of a development component are exported in an SDA export. You have to ensure yourself that the import is executed consistently. We only recommend the SDA Export mode for experts.

  2. Depending on the selected export mode (SCA Export or SDA Export), proceed as follows in the step Components:

    • SCA Export

      From the selection list, select the software component you want to export. You are not allowed to select more than one software component.

    • SDA Export

      From the selection list, first select the software component you want to export SDAs for. Then select the SDAs you want to export.

  3. In the Options step, select the following options:

    • Enter a patch name for the export software component. The system makes a suggestion that you can change.

    • If you have selected export mode SCA Export, you can specify whether sources or archives, or both, are to be included in the export.

      If you include sources then the transport request also contains editable sources. Otherwise it just contains pointers to the sources.

      Note Note

      If you only include the pointer to the source in the archive, this reduces the export and import time considerably when compared to the physical sources.

      In the following situations it is sufficient to include only the pointers to the sources:

      • Sie möchten die Sourcen nicht zu Ihren Kunden ausliefern.

      • You only want to work internally. If you use multiple design time respositories internally, ensure that these can communicate with each other.

      End of the note.

      If you include archives, then the transport request also contains build and deploy archives.

    • Specify if the system is to stop for errors. Using the Advanced pushbutton you can specify exactly what is to be handled as an error (for example, broken DCs, open request).

  4. In the CTS Request step, the system displays the transport request that is to be used for the export. It depends on the transport strategy you selected which transport request is displayed.

    For more information, see Defining Transport Strategies.

    To modify or select another transport request, select the Transport Requests link.

    You then branch to the Transport Organizer Web UI.

    For more information, see Managing Transport of Non-ABAP Objects.

    If you want to add notes to the transport request, then you can do so in the Notes field.

  5. The Export step lists the settings that are affected in an overview. If all settings are correct, start the export. To do this, choose Export.

    If the export is finished, check the export log.

You can import the exported software components into non-ABAP systems that are connected to the CTS system.