Show TOC

Procedure documentationRetrofitting Transport Requests Locate this document in the navigation structure


You want to start the retrofit process for transport requests related to an urgent or normal change.


Your change document has the status Authorized for Production (urgent change) or To Be Tested (normal change).


  1. To start the retrofit, choose the Start Retrofit action in your change document.

    The system displays an overview of the transport requests available for the selected retrofit system. You must import in the specified sequence.

    Note Note

    The system only displays transport requests that are released and those for which the retrofit is not yet finished.

    End of the note.

    The type of request indicates whether these are changes to development objects or Customizing settings that are imported using generated Business Configuration Sets (BC Sets). If the objects were not processed in the retrofit system, they are transported to the retrofit system by means of a transport of copies (automatic import).

    The Critical Retrofit column indicates which transport requests contain objects that cannot be imported directly by the tools used. The following applies:

    • Green: Objects can be imported using the automatic import

    • Yellow: Objects can be imported using postprocessing tools

    • Red: Objects have to be transferred manually to the retrofit system

    To obtain more information about the objects in the transport request, choose the traffic light icon in the Critical Retrofit column. The log for this transport request is then displayed. Notes in the transport requests are also displayed, because they are transport-critical, and can cause problems in the target system.

  2. You can filter the transport request list for the retrofit by retrofit status, by choosing Retrofit Filter at the top of the view:

    • Hide Not Processed Transports shows or hides all data records with retrofit status “Process Retrofit” (all yellow data records).

    • Show Processed Transports shows or hides all data records with retrofit status “Retrofitted” (all green data records as well as any data records processed manually).

    • Show Rejected Transports shows or hides all data records with retrofit status “Retrofit Rejected” (all red data records).

  3. You can display the retrofit status for each of the objects in a transport request. Do this by simply double-clicking the request. The color of the row indicates the status of the object. See step 1 of this procedure for more information.

    You can filter the objects according to their status by choosing the icon in the left screen area. You can also compare the objects in the source and target systems.

  4. You can use the Sequence Dependency option to see which transports are dependent on other transports. An icon indicates that a transport request is dependent on another transport request. If you choose this icon, the system lists the transport requests that belong to the sequence-dependent requests. In the object list for a transport request, you can see the dependent transport request for each object.

    If there is no sequence dependency, and some requests have not yet been processed, the system displays a message.

  5. Specify the retrofit request in the retrofit system into which the changes are to be imported, for each transport request.

    The transport request in the target system determines the adjustment.

  6. To check the consistency of a request, select it and choose   Additional Functions   Check Consistency  .

    The system checks that:

    • A retrofit request exists

    • The transport request import sequence is correct

    • There are no note objects in the request, that could cause conflicts during the import

    The result of the consistency check is displayed in the lower screen area.

  7. To transport a request, select it and choose the relevant retrofit method.

    Note Note

    You can transport several requests at the same time.

    End of the note.
    • Retrofit for All Categories: The retrofit is performed for all objects in this transport request. The relevant method is applied based on the object type and status.

    • Auto-Import: The retrofit is performed for the objects that can be imported automatically.

      The system collects all objects that do not have any conflicts in a transport of copies. The system imports them directly into the retrofit development system and copies them to the target transport request, in order to distribute them to the target system landscape.

    • Transfer with SCWB: The retrofit is performed for the objects supported by the Correction Workbench.

    • Transfer with BC Set: The retrofit is performed for the objects supported by BC Sets.

  8. To prevent transport requests from being processed, for example, because the change is no longer required, choose   Additional Functions   Reject Retrofit  . The status of the selected transport request in the overview changes to Retrofit Rejected.

  9. To flag transport requests that have not been processed by the retrofit process tools, as completed, choose   Additional Functions   Retrofit Manual  . The status of the selected transport request in the overview changes to Retrofit Manual. If there are no other transport requests for processing, before this request, in the overview, transport requests with this status are removed from the overview, to keep the list understandable.

  10. Choose List Retrofit-Critical Objects to list all transport-critical transport objects, so that you can process them manually. You can export the objects to the front-end PC in various formats, for further processing (e.g. manual retrofit of transport objects).

    Choose Cancel to close the list and go back to the transport request overview for the selected retrofit system.

  11. The following retrofits may be necessary when importing changes:

    • If an object is not yet available in the development system, you can import it from the maintenance system.

    • If an object is in both system, you can compare their versions:

      • If the system finds an area in the target system into which the change from the maintenance system fits, it imports the object. The area is the same in the maintenance and development systems.

      • If the system does not find an identical area in the target system, you have to edit the object and implement the change manually.

      • You have to implement objects that the system cannot import into the target system, manually. This includes, for example, data elements of type String.

      For more information, see Copying of Changes Using the Correction Workbench and BC Sets.

    Note Note

    You must edit semantic dependencies that are not technical dependencies, manually. The system does not recognize such dependencies.

    End of the note.
  12. Use the retrofit status inquiry to specify whether the retrofit was completed successfully.

    You need to specify this because the absence of object transfer warnings only means that there were no technical system errors. Cancelled procedures do not cause errors, so you must confirm that you have completed the procedure successfully, manually.

    • When you set the retrofit to completed successfully, the transport requests no longer appear in the transport request overview for the retrofit.

    • If you specify the retrofit as not having been completed successfully, the transport requests remains in the transport request overview for the retrofit, and continue to show the retrofit status Process Retrofit.

  13. To leave the retrofit transport request window, choose End.

    The task list overview appears.


The monitored transport from the maintenance system into the development system is completed.

Note Note

In the task list daily overview, the system shows the entry Start Retrofit at the time that you executed the retrofit.

To display the retrofit application log, double-click on Start Retrofit in the daily overview. The log displays all messages for the retrofit steps.

End of the note.