How to setup Cros…

The cross-system object lock functionality ensures that when anobject is changed in a managed system, a lock entry is created forthis object in the central SAP Solution Manager system. Dependingon the selected conflict analysis scenario, this lock entryprevents changes being made to this object by any other change(transport request). This applies to all managed systems andclients for which the cross-system lock has been activated.

Once the cross-system object lock has been activated, the systemcan detect conflicts between objects in transport requests thathave the same production system or the same production client astheir transport target.

The meaning of the cross system object lock function is to protectyour production system from “passing developments”.

 

Inside a Change Request Management maintenance project all changes(Normal, Preliminary, Urgent and Defect) will consolidate with theproject. As the import method is IMPORT_PROJECT_ALL “passingdevelopments” inside a project can never happen.

 

An exception to this is that Preliminary Changes & UrgentChanges can pass each other within a project. Therefore the use ofCSOL is necessary to protect the PROD system from downgrades.

 

Also if more than one project is available for the same systemlandscape, CSOL can protect the PROD system from downgrades.

 

Automatic Categorization of Objects to retrofit (Auto Import,Retrofit and Manual) is based on the Cross System Object Lockentries in Solution Manager
If the Enhanced Retrofit function does not detect a Cross SystemObject Lock entry for an object of a transport requests that shouldbe retrofitted, the object will be flagged as Auto Importobject.

A change to object A is performed in the DEV system. This change isrecorded in the CSOL table of Solution Manager. Now it happens thatin the PRD system a fix is needed. The fix will be performed in theMAINT system and has to change object A as well. As the CSOL entryblocks the second change (fix) of object A the only solution to goon is to delete the CSOL entry as the fix is necessary to solve theissue in PRD.

If now the transport request in MAINT is released and the retrofitcategorization is calculated the retrofit will not detect an entryfor object A and therefore calculate a green case.

If now retrofit is performed the version of object A in the DEVsystem is overwritten!

 

How can we avoid this behavior?

 

You can customize how CSOL shall behave.

You will find default mode and expert customizing.

We will need to use the "expert" customizing as the default modedoes not protect you 100% from the issue described above.

The "Project Relation" customizing is key for the enhanced retrofitscenario. In default it's set to "cross" which means conflicts fromdifferent projects as well as conflicts within the same projectwill stop the process.

What we want to avoid is exactly that conflicts from differentprojects will end in a termination of the process. Therefore theproject relation has to be set to "Specific". This means that onlyconflicts within the same project will result in a termination andfor different project will only appear as warning.

The other settings do not influence the enhanced retrofit behavior,so Change type relation and object type can be set however youneed. But it's necessary that the project relation is only set to"specific" in the case you have the enhanced retrofit scenarioactive in your landscape.

One exception comes if you can for sure exclude Maintenanceprojects in the DEV landscape. In this case urgent changes cannotbe created (this is only allowed when using maintenance projects)which means the default mode comes back into the play again.

Also possible is the warning only setting which results in that allconflicts will ever be detected as warning only and the process isnever terminated.

In this case it's necessary to also activate the downgradeprotection (DGP). This will ensure that if you get a warning inCSOL you can still not get passing developments as it checks againfor release and every import.

 

So with these allowed settings you will never need to delete anentry from the CSOL list because of Urgent Changes needing to beimplemented to PRD as fast as possible. Also in any other conflictsituation you will never need to delete entries from the CSOL listto go on with your process.

Like this you will never get a wrong "green" retrofitcategorization which will end up in an over write in DEV.

 

Conclusion:

When using enhanced retrofit in Solution manager the use of crosssystem object lock is mandatory for the correct behavior of thetool.
You cannot use the enhanced retrofit without having CSOL setup andactivated for the retrofit relevant projects.
With some of the available conflict analysis customizing settingsin cross system object lock  the danger ofdowngrading your Implementation work appears.

When using the enhanced retrofit, you should only use projectrelation "specific" . Any “cross-project” setting is not allowed,because a terminating cross system object conflict would requirethe deletion of the corresponding lock entry. But that lock entryis required for the correct  analysis of theenhanced retrofit.

 

Summary:

When using the enhanced retrofit scenario make sure your CSOLcustomizing is set to "specific" from the project relation point ofview.

Also "warning only" is a valid setup if on top DGP is activated.The default mode can also be valid for the enhanced retrofitscenario when it's ensured that no Urgent changes can ever becreated in the implementation landscape (DEV).

来源：http://scn.sap.com/community/it-management/alm/solution-manager/blog/2014/12/09/how-to-setup-csol-and-dgp-when-using-retrofit