Show TOC

Function documentationCross-System Object Lock Locate this document in the navigation structure


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   Capabilities   Change Control Management   Extended Configuration   Cross-System Object Lock and Downgrade Protection  .


  • 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. In the Cross-System Object Lock Configuration area, you can select Cross-System Object Lock Active or Cross-System Object Lock Inactive to activate or deactivate the lock.

  • In the report, you can either use the default scenario or the expert mode to configure the cross-system object lock.

    The default conflict analysis scenario is cross-project (project relation Cross), change type relation Urgent Only, object type Client-Specific. If you want to use a different scenario, run the /TMWFLOW/CONFIG_CSOL report. Here, choose Expert Mode and select the relevant scenario from the Define Customized Conflict Scenarios screen section.

  • 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

    The system can only detect a conflict if the selected transport request was created in change request management or Quality Gate Management. If the transport request was created locally, the system does not track changes in it.

    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.

Expert Mode Configuration

The cross-system object lock provides the following categories to classify customizing error conditions. This keeps transport objects reliable and consistent in your development landscape and transport process. If an object to be saved violates the categories, an error message is displayed and the object cannot be saved. Any other conflict is displayed as a warning message, and you determine the subsequent action.

You can specify what is regarded as an error when a developer tries to save an object, with regard to the criteria Project Relation, Change Type Relation, and Object Type of the object. An error message is only issued if all three criteria are met by the object attribute.

The Cross-System Object Lock and Downgrade Protection report enables you to use the following settings:

  • Project Relation: How to deal with an object that has already been saved in a transport request, and is to be saved again in another transport request, with regard to the project it belongs to.

    • Cross: The system ignores the type of project to which two transport requests belong.

    • Specific: Projects to which two transport requests belong should be the same.

    • Different: Projects to which two transport requests belong should be different ones.

  • Change Type Relation: How to deal with an object that has already been saved, and is to be saved again, with regard to its change type. You must decide whether it is to be transported as urgent or normal data.

    Note Note

    A QGM change is treated as an urgent change on determining the conflict type (error/warning).

    End of the note.
    • Urgent Only: Two transport requests which include the same object belong to different urgent changes. For example, two urgent changes in change request management.

    • Partial Overlapping: At least one of these two transport requests, which include the same object belongs to an urgent change.

    • Overlapping: The system ignores the type of change to which two transport requests belong.

  • Object Type: How to deal with an object that has already been saved, and is to be saved again, with regard to its type, depending on whether it is a client-specific or a cross-client object.

    • Cross-Client: Only repository (workbench) objects are taken into account.

    • Client-Specific: All objects are taken into account, including repository (workbench) and Customizing objects.

  • The Warning Only checkbox allows the developer to ignore the cross-system object lock error settings. Only a warning message is displayed, you can save nevertheless. This option can be used, for example, in variant SAP1 scenarios for change request management .

    Caution Caution

    When choosing this option, you must be aware of the risk of possible software downgrades when newer transport requests overtake older transports containing the same objects.

    End of the caution.
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 (if you change the object list of the transport request manually, for example).

    Changes that are made to the object list of a transport request by the list editor for a Transport Organizer object, are not recorded in the central lock management. Objects can still be locked across multiple systems, if Transport Organizer authorizations are used. The authorization object required to change a transport request object list with the Transport Organizer, is S_TRANSPRT (Transport Organizer), request types CUST (Customizing), DTRA (Workbench), TASK (task), activity 23 (maintain).

    If you are the owner of the transport request, you are authorized to update the central object lock information, using the TMW_TRKORR_LOCK_UPDATE report. 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.