Creating
a Transport Request
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 to other users who may need it
¡ Upload it to the NetWeaver Development Infrastructure (NWDI)
¡ Use the deployment function provided by the Software Deployment Manager (SDM) of the SAP J2EE Engine
· 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.
If you want to
export the transport request to another SAP System, you must have defined an
endpoint alias before. For more information, see
Configuring Endpoint
Aliases.
...
1. In the Administration workset, choose Transport → Create Transport Request.
2. Provide a meaningful technical name for the transported content.
3. Choose Next.
...
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.
...
1. 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.
2. Choose the type of export.
a. If you want to export the transport request to your local computer, set the Export to Local File indicator. 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
b. If you want to export the transport request to an SAP System, set the Export to SAP System indicator. Choose an appropriate endpoint alias by clicking on Select Endpoint.

The system message that indicates that the export was completed successfully also contains the number of the transport request (Request ID). We recommend that you note this number for any possible further processing of the transport request in the target system using the transactions EUPTSP (Prompt for Customizing Request) and SE09 (Transport Organizer).
3. To create the transport request and export the file, choose Export.
The transport request is now available on your local computer or on an SAP System and can be used as required.