Cross System object locking (CSOL)

[Former Member]

Hi,

I want to know, if we activate Cross System object locking (CSOL), then do we need to wait till chnages to that particular object is delivered in production ?

I mean other chnages which involve same object changes, do they need to wait till exiting locked object moved to production.

Regards

PK

[Former Member · Accepted solution]

Hi PK,

This is depends how you customize it.

You can do :

• Send warning message - this means object can saved and imported even if older transport exist and not yet imported to PRD
• Send Error message - here is not possible to save object till old transport imported to PRD

By the standard customizing:

• save 1 object in 2 parallel Urgent Change - error message
• save 1 object in 1 NC and parallel UC - warning message
• save 1 object in 1 NC and parallel NC - warning message

And also you need to consider lock monitor, even if UC is imported to PRD you need to delete locks manually or make project import buffer to PRD, this will refresh all locks.

Rg Dan

[Former Member · Accepted solution]

Hi Dan,

Thanks. Is there any configuration document for CSOL (Cross system object locking).

Regards

PK

[Former Member · Accepted solution]

Hi PK,

Just use SPRO

CSOL Error Conflict Scenario Configuration

Definition

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

Use

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 which has already been saved, and is to
  be saved again, 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 of the
  same type.

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

• Change Type Relation: How to deal with an object which 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 a Normal Change (not as an Urgent Correction).

• Urgent Only: Two different transport requests, which include the same
  object, belong to different urgent changes. For example, two Urgent Corrections
  in Change Request Management.

• Partial Overlapping: At least one of these two transport requests, which
  includes 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 which 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.
Caution: You must be aware of the risk when you choose this option.

After this activate CSOL for your dev system and client

Rg Dan

[Former Member · Accepted solution]

Thanks Dan.