Show TOC

Using the Export ServiceLocate this document in the navigation structure

Prerequisites

You have called the Export Service. For this you have selected Start of the navigation path Related Links Next navigation step Export Management End of the navigation path in the Configuration Service.

Context

You use the Export Service to export software components (SCAs) or development components (SDAs) from the system.

The procedure is different depending on whetether you export SCAs of a standalone development configuration or SCAs or SDAs of a development configurstion that was created in the TMS.

SCAs or standalone development configurations are put in an outbound directory for exports and can be imported into another development configuration after the export using the Import Service. SCAs or SDAs of a development configuration that was created in the TMS are included in a transport request for an export which can then be imported 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.

Procedure

  1. In the Export Mode step, select the development configuration of the system you want to execute the export from in the list, or select the standalone development configuration that you want to execute the export from.

    If you have selected a standalone development configuration then a new row appears that displayed the path to the outbound directory that was configured in the Configuration Service.

    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.

    Note

    These options cannot be selected depending on which transport settings you have made in the Configuration Service.

    SDA exports are not possible for standabloe development configurations as only SCAs are created.

  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 components you want to export.

    • SDA Export

      From the selection list, first select the software components 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 and the SCAs to be exported are not in the SAP namespace, you can define which Support Package Level and Patch Level you want to use. You can also specify if 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

      Use this option if you do not want to deliver the sources to your customers. This reduces the export and import time considerably in comparison to physical sources. The source pointers are, however, sufficient to be able to work with them internally. If you use multiple design time respositories internally, ensure that these can communicate with each other.

      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. This step only appears if you execute the export for SCAs or SDAs of a development configuration that was created in the TMS.

    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 the topics under Managing Transports of Non-ABAP Objects in the Transporting Non-ABAP Objects in Change and Transport System documentation.

    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 .

    Check the export log when the export is finished.

Results

The following applies for development configurations that were created with the TMS: You can import the exported software components into non-ABAP systems that are connected to the CTS system.

The following applies for standalone development configurations: You can import the exported software components into other systems with the Import Service.