Hi
We are currently implementing Solution Manager 7.1 (ChaRM) and of the mandatory requirements is to activate Cross System Object Lock.
I have globally activated this in Solman and have gone into /TMWFLOW/CMSCONF to activate for our development client. This is now activated.
A transport has now been created in ChaRM and I login to the above mentioned development system and make a customizing change. I then choose the transport and save change. I am presented with an error:
"Error in RFC SM_DSMCLNT001_BACK to Solution Manager System" (Message No. STMWFLOW025)
I have now been looking at this for a few hours and found OSS Note 824521. However, I have already done all this. From a RFC perspective we have:
SOLMAN:
SM_DSMCLNT001_BACK - works fine in SM59. The assigned user has all the correct profiles.
In transaction SDCCN, the above RFC appears also.
In transaction SM30, table BCOS_CUST, "CHARM_DEST" and "OSS_MSG" are both set to destination NONE.
SATELLITE SYSTEM:
In transaction SDCCN, the above mentioned RFC exists
In transaction SM30, table BCOS_CUST, "CHARM_DEST" and "OSS_MSG" are both set to the above mentioned RFC
The user SMB_DSM for the RFC only exists in Solman and not in satellite system. Don't think this is needed though.
As soon as I deactivate CSOL in /TMWFLOW/CMSCONF in Solman (for development client), I can make changes and the above error (in red) does not appear. However, we needed CSOL working and this error not to appear.
Any suggestions??? 
Thanks
Shaun