SAP® Documentation

Single view

/TMWFLOW/CONFIG_CSOL - Cross-System Object Lock and Downgrade Protection Settings

BAL Application Log Documentation   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

This documentation explains how to define customized conflict scenarios for the Cross-System Object Lock (expert mode).

CSOL 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 (conflicts) in all the categories, an error message will appear and the object cannot be saved. Any other conflict will be displayed as a warning message, and you need to determine the subsequent action.

Integration

Prerequisites

Features

Selection

Standard Variants

Output

Activities

You can specify what is regarded as an error when a developer tries to save an object, in terms of information about this object, with regard to the criteria "Project", "Change Type Relation", and "Object Type". Only if ALL three criteria have been met by the object attribute, an error message is displayed.

  • Project: 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 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 should be transported as urgent or normal data.
    Note: A QGM Change is treated as an Urgent Change (originally Urgent Correction) on determining the conflict type (error/warning).
  • Urgent Only: Two different 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 will be taken into account.

  • Client-Specific: All objects will be taken into account, including repository (workbench) and customizing objects.

The "Warning Only" checkbox allows the developer to ignore the CSOL error settings. Only a warning message will appear; you can save nevertheless. This option might be used for example in Quality Gate Management or Change Request Management variant SAP1 scenarios. 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.

For more information, see the documentation on the SAP Solution Manager on the SAP Help Portal (help.sap.com) under: Change Request Management and Change Control -> Change Request Management -> Central Configuration Tool of Change Request Management -> Cross-System Object Lock.

Example






CL_GUI_FRONTEND_SERVICES - Frontend Services   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 4173 Date: 20191021 Time: 140920     sap01-206 ( 52 ms )

Our Service

Looking for Support? Questions?

The

Consolut

Callback-Service

Leave us your contact details and we will call you back. Panels marked with * are mandatory.