Show TOC

Function documentationDual Landscape Synchronization (Retrofit)


In system landscapes in which several releases are processed at the same time, similar changes can be made in different development systems. For example, new developments can be made in the new implementation development system, and errors to be corrected or improvements to be made in a maintenance system for the production system landscape at the same time. The system release levels must be adjusted regularly to ensure that changes are synchronized in parallel across different system landscapes. This synchronzation is called retrofitting.


  • You have applied SAP Note 1468044Information published on SAP site in the managed systems.

  • You have made the relevant settings in Customizing under Start of the navigation path SAP Solution Manager Next navigation step Capabilities Next navigation step Change Control Management Next navigation step Retrofit End of the navigation path. For more information on retrofit parameters, see the Customizing documentation under Define Retrofit Parameters.

    Note Note

    If you want to use cross-release retrofit, you have activated the Cross-Release Retrofit parameter.

    End of the note.
  • The retrofit function is activated in SAP Solution Manager.

    For more information about using an RFC trusted/trusting relationship between two SAP systems, see System Users and RFC Destinations with Trusted Systems.

  • Both managed landscapes that are to be part of the retrofit scenario are in the same domain or both domains are linked via a TMS domain link.

  • You have activated the cross-system object lock in Customizing under Start of the navigation path SAP Solution Manager Next navigation step Capabilities Next navigation step Change Control Management Next navigation step Cross-System Object Lock and Downgrade Protection Next navigation step Configure and Activate Cross-System Object Lock End of the navigation path, globally and for the retrofit system

  • You have set up the following RFC connections in SAP Solution Manager, for each working client specified in the logical components used in the maintenance landscape, and the new development implementation landscape. This includes the 000 clients of the TMS landscape domain controller systems.

    • SM_<SID>CLNT<...>_READ

    • SM_<SID>CLNT<...>_TMW


    • from SAP Solution Manager to the development landscape

    • from SAP Solution Manager to the maintenance landscape

    Note Note

    Additional RFC connections are created automatically when the retrofit scenario is activated in SAP Solution Manager.

    For more information, see SAP Note 1175098Information published on SAP site.

    End of the note.
  • Your user has authorization for the following authorization objects in both development system clients used in the logical components:

    • S_RFC_ADM


    • S_SYS_RWBO

  • A logical component in the SAP Solution Manager project contains at least one (retrofit) system with the role Retrofit System.

  • To specify into which system changes are to be imported, you have executed the task Assignments of Postprocessing Systems to Development Systems in the overview of the task list.

    • When you define retrofit systems, the system only offers you transport requests from the development systems you assigned to the retrofit systems when you started a preprocessing task.

    • If you make no assignments, the system offers you all transport requests from all development systems when you start the retrofit. You can make this assignment as often as required. The assignment is updated each time.

    Note Note

    To process new and ABAP Dictionary objects, the target system for the retrofit must have Basis Release 6.20 or higher.

    End of the note.
  • You have created transport requests for the retrofit in the retrofit system into which you want to import the changes from the maintenance system.


The following retrofit processes are available:


Object Types Supported

Can Be Used For

Automatic import

All object types

Note Note

BW objects are partially supported.

End of the note.
  • Objects without cross-system object lock in the retrofit system

  • Objects that were not changed in the retrofit system

Using the Correction Workbench and Business Configuration Sets as postprocessing tools

  • Correction Workbench: Workbench objects

  • Business Configuration Sets: Customizing objects

  • Objects with cross-system object lock in the retrofit system

  • Objects that were changed in the retrofit system

Manual retrofit

Objects that cannot be imported automatically and that are not supported by the postprocessing tools

All other objects

You can perform retrofits for systems that are on different support package, enhancement package, or release levels (cross-release retrofit). The system performs the following checks to ensure that no downgrade occurs:

  • Check for Customizing objects: If table structures, views, or view structures have changed, the object is set to "manual retrofit".

  • Check for Workbench objects: SAP objects are set to manual retrofit.

  • Check for SAP Notes. They can not be retrofitted.

You can use the following functions to prepare the retrofit:

  • Retrofit status display for transport requests and objects in the Critical Retrofit column

    • Green: Can be imported using the automatic import

    • Yellow: Can be imported using the postprocessing tools

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

  • Object list of the transport request

    Shows the objects included in the transport request that you want to retrofit, including the object types

  • Sequence dependency

    The sequence dependency indicates whether a transport request is dependent on another transport request. For example, transport request A contains object X, which already exists in transport request B. This means there is a sequence dependency between transport requests A and B.

    A transport request can have a sequence dependency to more than one other transport request (different objects are in different transport requests).

    There is just one sequence dependency for an object X between transport request A and transport request B if transport request B is the only request with object X or is the request that was last released.

    There can also be a sequence dependency between transport request B and a third transport request.

    The sequence dependency is based on the objects in the object list for the entire retrofit queue. The sequence dependency is updated or deleted as soon as the retrofit for a transport request is completed.

    If there is no sequence dependency, and some requests have not yet been processed, the system displays a message. You can specify in the Customizing settings whether the message is to be displayed as a warning or as an error.

  • Consistency check

    The system checks whether the retrofit was prepared correctly:

    • Have transport requests been created in the retrofit system into which you want to import the changes from the maintenance system?

    • Has the execution sequence of the transport requests to be imported been observed?

    • Does the transport request contain objects from Notes that could cause conflicts during the import?

  • Display for various logs with messages for the transport requests

  • Display and processing of BC Sets for transport requests that contain Customizing objects

  • Call to the TMS Alert Viewer

    For more information, see Displaying the TMS Alert Viewer.


  1. You start the retrofit directly from your change document.

  2. You check the status of each of the transport requests and the objects in the requests.

  3. You perform the retrofit for your transport requests.