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 and prevents version conflicts at an early stage.

Regardless of whether you use a separate development system or share the same system for your projects, you must avoid different teams working on the same object concurrently if the changes are to be imported in the same production system. It can lead to inconsistencies. The object must stay locked until it has been imported in the production system.

Prerequisites

The cross-system object lock has been configured and activated in Customizing for SAP Solution Manager calling transaction Solman_Setup. Choose Change Request Management -> step 2.1 Configure CSOL and DGP -> Globally Activate CSOL and DGP (Master Guide).

Features

  • You can activate or deactivate the cross-system object lock.

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

  • 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.

  • You can define your cross-system object lock conflict scenario by choosing between the default mode and the expert mode. The default conflict analysis scenario is cross-cycle (cycle relation Cross) with change type relation Urgent Only. In the expert mode, you define customized conflict scenarios for the cross-system object lock. For more information, see the system documentation of the activity.

  • If you want to get notified about the cross-system object lock conflicts, you can select a Warning Only option. Only a warning message is displayed for all conflicts. You can still save your data. Be aware that when choosing this option, you might run the risk of possible software downgrades when older transport requests overwrite more recent transports containing the same objects.

    Caution Caution

    Transport requests that are assigned neither to a Change Request Management cycle nor to a quality gate management cycle are not taken into account during conflict analysis.

    End of the caution.

  • You can define your own conflict scenario for the cross-system object lock. 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

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

Extended Features

  • The conflict analysis tracks the 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 manager (in the Administration Cockpit) 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 on the Landscape Overview tab in the administration cockpit by setting the CSOL Check checkbox for managed development systems.

    Caution Caution

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

    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 for which you want to update the object lock information.

    Note Note

    If SAP Solution Manager is temporarily unavailable but you still want to change objects in the development system, use the TMW_CONTROL_PROJECT_LOCK report to deactivate the cross-system object lock temporarily and change the objects. 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.

    You can also update the lock entries for a batch of transport requests in the cross-system object lock manager of the SAP Solution Manager system.

    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 and prompts you to save any 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

    To use these features, you have to implement the SAP Notes listed in SAP Note 1900560Information published on SAP site in the development systems in your landscape.

    End of the note.

More Information

Conflict Analysis Scenarios