Show TOC

Function documentationCross-System Object Lock


The cross-system object lock ensures that when an object is changed in a managed system, it is locked in the central SAP Solution Manager system. Depending on the conflict scenario, this prevents changes being made to this object in any other transport request. This applies to all managed systems and clients for which the cross-system lock is active.


The cross-system object lock has been configured and activated in Customizing for SAP Solution Manager under Start of the navigation path Capabilities Next navigation step Change Control Management Next navigation step Cross-System Object Lock and Downgrade Protection End of the navigation path.


  • When the cross-system object lock is active, the system can detect conflicts between objects in different transport requests that have the same production logical system (system and client) as their transport target, depending on the type of object that was changed.

  • You can check at any time whether the cross-system object lock is active or inactive, by running the Cross-System Object Lock and Downgrade Protection Configuration report /TMWFLOW/CONFIG_CSOL and checking the settings on the entry screen. You can use this report to activate or deactivate the lock.

  • When the cross-system object lock is active, you can activate downgrade protection. Downgrade protection cannot be activated if the cross-system object lock is inactive.

  • In the Cross-System Object Lock and Downgrade Protection Configuration report, you can either use the default scenario or the expert mode to configure the cross-system object lock. For more information, see the system documentation in the report.

  • If the system detects a conflict, it displays a conflict message directly after a user has selected a transport request for the object to be changed in the managed development system.

    Caution Caution

    Transport requests that are neither assigned to a Change Request Management project nor to a QGM project, are not taken into account during conflict analysis.

    End of the caution.
  • You can define your own cross-system object lock conflict scenario. You can label the conflict with message types such as Error or Warning, depending on your scenario. The final conflict message to be displayed contains the following information:

    • Conflict type (error or warning)

    • Affected transport requests

    • Owners of the transport requests

    Whether you can continue to change an object depends on the conflict type.

  • If you want to remove cross-system object lock entries, the system needs to fulfill the following prererequisites:

    • The transport request has been imported successfully, or it has been repaired manually.

    • The transport request no longer exists in the import queue of the production system.

    • When the user deletes the object from the transport request in the managed system directly, SAP Note 1895691Information published on SAP site is required in the managed system.

Extended Features
  • The conflict analysis keeps track of objects stored in transport requests using lock entries. Within one transport request and one production logical system, there are records for each object in the transport request.

    Note Note

    In the central SAP Solution Manager system, the cross-system object lock monitor (transaction/TMWFLOW/LOCKMON) provides an overview of all current lock entries. The entries are displayed in table form, and can be selected, if you need to delete them, for example.

    End of the note.
  • You can activate and deactivate the cross-system object lock in each managed system, with the TMW_CONTROL_PROJECT_LOCK report in the managed system. You can also do this in transaction/TMWFLOW/CMSCONF in SAP Solution Manager by double-clicking the value in the Cross Sys. Obj. Lock column for managed development systems.

    Caution Caution

    To execute the TMW_CONTROL_PROJECT_LOCK report, you require change authorization for the Transport Management System, for example, the role SAP_CM_ADMINISTRATOR_COMP.

    End of the caution.
  • You might need to update the central object lock information about a transport request. You can do so by using the TMW_TRKORR_LOCK_UPDATE report. If you are the owner of the transport request, you have the required authorization. Enter the name of the transport request whose object lock information you want to update.

    Note Note

    In case SAP Solution Manager is temporarily unavailable, and you still want to change objects in the development system, use the TMW_CONTROL_PROJECT_LOCK report to deactivate the cross-system object temporarily, and make the change. When SAP Solution Manager is available again, you can activate the cross-system object lock and run the TMW_TRKORR_LOCK_UPDATE report for the transport request in which you saved objects during the inactive period.

    End of the note.
  • With regard to the cross-system object lock, the Workbench Organizer provides the following features:

    • When changing to edit mode for an object, the system displays a warning message, asking the user to save their changes as soon as possible.

    • When you change transport objects manually, that is, you delete, edit, or merge objects, the lock entries in SAP Solution Manager are updated automatically.

    Note Note

    If you want to use these features, you have applied SAP Note 1900560Information published on SAP site to the development systems in your system landscape.

    End of the note.