Importing Transport Requests 

Use

This procedure describes how to import transport requests for GP objects that you created in an SAP System before.

If you want to import local objects instead, you must use the Software Deployment Manager.

Note that the system transports only those objects, which exist as an active version in the GP design time (including those with status deprecated).

Importing a transport request comprises the following steps:

●      Selecting the source system and the corresponding RFC destination (Select Source System)

First you determine an existing connection to the respective source system in which the required transport systems are available. You can choose from all RFC destinations that you have created in NetWeaver Administrator.

More information: Maintaining RFC Destinations

●      Importing the transport requests (Import Requests)

○       The system displays an overview of all transport requests you have created.

Column title Technical Description: the system shows the technical names that were used internally when the respective transport requests were created.

More information: Creating a Transport Request

○       You can choose Display Check Results to view the check results of the change request.

It is at this point at the latest that you must check the change requests yourself: Check (Request Consistency) in the Transport Organizer (transaction SE09) of the transport system.

○       You can import the transport requests.

●      Adjusting the existing object permissions (Edit Permissions).

○       If required, you must confirm or edit the permissions of the objects imported.

Prerequisites

You must create an adequate RFC destination before importing transport requests from SAP Systems.

Procedure

1. Select Source System

       1.      Use the following fields to choose an adequate RFC destination.

○       Endpoint Alias Type – Endpoint Alias for Remote Function Call (RFC)

○       Available Endpoint Aliases

       2.      Choose Test to check the connection.

       3.      Choose Next to display the view Import Requests.

2. Import Requests

...

       1.      If required, define the transport in the transport system.

You must carry out this step at this point at the latest. In many cases, you may have completed this step before.

                            a.      Call the program GP Content Transport (transaction EUPTSP) in the transport system.

                            b.      Assign a Customizing request to the transport request.

                            c.      Select the transport request by its request number.

                            d.      Save your settings.

The transport request handled is now displayed in the current view Import Requests.

       2.      If required, check this change request in the Transport Organizer (transaction SE59). Choosing Display Check Results now allows you to view the results of this check for each transport request at any time.

       3.      Select the transport requests you want to import.

       4.      To start the import, choose Next.

When the transport was successful, the system issues the following message: Transport request <technical name> imported from system BXI.

3. Edit Permissions

You must now confirm or edit the permissions of the imported objects as follows:

...

       1.      In the hierarchy List of Objects, navigate to an object.

       2.      In the overview Set Permissions, revise the existing permissions if required and save your settings.

       3.      Repeat the steps 8 and 9 for each imported object.

       4.      Choose Release Import to complete the import process.

4. Import Failed Content Deployments

Deployment problems such as the deployment of missing callable object types (types that are not registered on the system), are displayed in the transport queue. These callable object types can be registered by the administrator and imported again. As a result, the transport package is no longer displayed in the transport queue and the content deployment is successful.

...

       1.      In the Administration workset, choose Retry failed content deployments in the Transport section of the overview.

       2.      Choose Import to retry the import procedure.

If the problem persists, check whether you have registered all callable object types.

More information: Implementing and Registering Callable Object Types

Result

The imported objects are now available in the GP design time.