Cross System Object Locking - CSOL - for ChaRM

[Former Member]

Hello,

I am reading some information in the help.sap.com regarding the functionality of Cross System Object Locking. My customer is looking to apply this for ChaRM to ensure that objects (i.e. programs) are not modified until a previous change request is finished and transported into production.

I would like to get more info how to apply it, which customizing is required (in ChaRM and satellite systems), and advantages and drawbacks of this technology.

Many thanks

Esteban Hartzstein

[Former Member]

Hi there,

I just activated this function in Charm and here's the link that may help.

http://help.sap.com/saphelp_NW70EHP1/helpdata/en/43/7227481a856fcae10000000a1553f6/frameset.htm

Cheers

Eon

[ttrapp]

This is interesting. I recommend to use the transport analyzer tools to look at the transport analyzer tool: http://scn.sap.com/docs/DOC-50311 as well as CharM analyzer tool to find out what object causes the cross system lock. Is the same object in two different transports? Are those transports meant for different systems?

The result could be that someone messed somthing up or that BRFplus does not work mit CHaRM properly and then you should open an OSS message,

Best Regards,

Tobias