Creating a Transport Request 

Use

Whenever you need to transport Guided Procedures (GP) content created in your system to other systems, you have to create a transport request first. A transport request collects development objects and categories for export to your local computer or to an SAP transport system.

Creating a transport request comprises three steps:

...

...

       1.      Basic Data: entry of the basic data

       2.      Select Objects: selection of the objects to be exported

       3.      Export: selection of the export type and creation of the transport request

You may choose from the following types of export:

·        Export to local computer

The transport request is exported to your local computer in the file format .sda (Software Deployment Archive). You can then forward this transport request by e-mail, for example, to other users who may need it or upload it to the NetWeaver Development Infrastructure (NWDI) to make it available for general access.

●      Export to an SAP system using an RFC destination

By connecting to SAP systems, you can directly export the transport request to these systems and make it available for general access.

Prerequisites

If you want to export the transport request to an SAP system, you must have created an RFC destination before.

More information: Maintaining RFC Destinations

Procedure

1. Enter Basic Data

...

       1.      In the Administration workset, choose Transport  → Create Transport Request.

       2.      Provide a meaningful technical name for the transported content.

       3.      Choose Next.

2. Select Objects

...

       1.      On the Select Objects screen, choose Add… to add content to the transport request.

       2.      From the Select objects for export list, select the folders or development objects you want to transport.

The list contains only activated objects (including deprecated ones).

       3.      Choose Add to List.

The system exports all development objects and categories related to and relevant for the objects that you have selected. For example, if you select a process template, all its blocks, actions, callable objects are added to the transport request.

In addition, all e-mail templates used in the callable objects that you export are automatically included in the transport request.

       4.      To continue with the Export step, choose Next.

       5.      Enter a name for the translation contact person.

By default, it is the currently logged user but you can also specify any other name. This is the person who needs to be contacted in case of questions concerning translations.

Whenever you create a transport request, all translations of GP objects (such as titles, descriptions and so on) included in the request, are exported with the .sda archive. Translations, together with the contact person name, reside in .xlf files.

       6.      Select the type of export and follow the procedures below depending on your choice.

3a. Export to Local Computer

...

If you want to export the transport request to your local computer, set the Export to Local File indicator.

       1.      Choose Export.

The system stores the export file in the following directory: <home_directory>\usr\sap\<server_name>\JC<instance_ID>\j2ee\cluster\server0\<file_name>.sda

c:\usr\sap\F21\JC30\j2ee\cluster\server0\transport1234567890123.sda

       2.      You can download the .sda file to your local computer by clicking the link provided.

The transport request is made available in other Java systems using the deployment functionality provided by the SAP NetWeaver Development Infrastructure (NWDI) and the Deploy View of the SAP NetWeaver Developer Studio (NWDS).

More information:

Transporting GP Content Using NWDI

Deploying Applications

3b. Export to an SAP System Using an RFC Destination

...

...

If you want to export the transport request to an SAP system, set the Export to SAP System  indicator.

       1.      Choose Select Endpoint to browse for existing RFC destinations.

       2.      From the Available Endpoint Aliases dropdown box, select the RFC destination you created previously and choose Add.

In case ABAP forms are included in your transport request, the RFC destination that is configured for ABAP-based forms is prefilled.

       3.      In the ABAP package field (available only if the request includes at least one ABAP-based form), enter the ABAP package to which form objects have to be assigned at the time of initializing the transport request.

At design time, the forms are created as local objects in the ABAP back end without any package. However, for such forms, the ABAP package is a necessary transport prerequisite. In case the back-end system is an SAP system, the package has to be in the SAP namespace; in case it is a customer system, the package has to be in the customer namespace. Local packages cannot be used for transport.

       4.      Choose Export.

For further processing of the transport request in the target system you use transactions EUPTSP (Prompt for Customizing Request) and SE09 (Transport Organizer). For this purpose, you may need the technical name of the request that you specified in step 2, or the number of the request (Request ID) in the system message indicating that the export was completed successfully.

For more information about importing transport requests from the SAP system to target Java systems, see Importing Transport Requests.