Cross System object lock

We have implemented Charm in Solman 7.0 Ehp1. I have activated 'cross system object lock' both globally (report tmwflow/config_services) and in satellite System (tcode- /n/tmwflow/cmsconf). am able to change the same table again which i had edited earlier and stored in TR.
am i missing somewhere.
Thanks

Hello Powai,
Please, check the link below, there you can find good informations about CSOL.
/people/rajiv.jha/blog/2010/08/30/csol-managing-parallel-projects
Best Regards,
Diego Fischer

Similar Messages

Error whiel activating cross system object lock

Hi ,
when I am trying to activate the cross system object lock functionality for developement system in tcode /TMWFLOW/CMSCONF from our solman system , it showing the following error
'Error RFC destination SM_SMDCLNT000_TRUSTED: You are not authorized to logon to the target system (error code 1).
Message no. /TMWFLOW/TRACK_N106'
In the above RFC connection the 'Current user' is provided.
Can anyone please let me know what I am missing in this?

Hi Farzan,
I dont have autorization in Client 000 of SMD system thats why its giving authorization error but when I am trying to activate the object locking for SMD client 321 why the system is trying to logging into the SMD : 000 can we somewhere modify the RFC conection which needs to be used.
Regards,
Amar Kamat

Cross system object lock -how to build up lock entries for existing request

Hello,
we implemented ChaRM for some years and intend to activate cross system object lock (CSOL), now.
But there are a lot of existing transport requests, which have not been imported to productive system, yet.
It would be very helpful to create lock entries for objects, which are assigned to those transport requests.
Does anyone know any standard report for this purpose?
Thanks a lot for any hint.
Best regards
Horst

If anyone else needs that feature:
Report TMW_TRKORR_LOCK_UPDATE (executed in satellite system) will lock the objects of a transport request in solution manager system.

Charm without Cross system object lock

Dear All,
We have requirement for configuration of Charm without cross system object lock i.e. solution manager will be used for documentation but create, release, import request from the development system itself.
Can we make changes in the functionality and use charm for documentation only?
if anyone has the same requirement can you please let me know steps to be followed.
Thanks in advance
Regards
Sushant

Dear Prabhakar,
Thanks for the reply.
Our project has just gone live and issues immediate resolution is being carried. Charm will integrate with system and training is required for that which at this point of time not possible but at the same time without affecting the issue resolution we want to log the changes in solution manager.
We will use the CSOL feature may be some time later.
At present i have not activate CSOL, still the document doesn't flow through. Document got stuck at "In development" phase and doesn't move forward. It doesn't allow to change the status.
Regards
Sushant

Cross System Object Lock with ChaRM Retrofit

Hi-
I need to know if there is the ability to have a cross system object lock while utiliziing Retrofit within ChaRM. For example I am working with an N, N1 landscape. When I release a transport request in N I need the object to be locked in the N, and N1 (after retrofit) landscapes.
Will this be supported with both Workbench and Customizing requests?

I dont believe this is possible at the moment. As you must be already aware, that SAP releases the locks from the objects as soon as the transport request is released from the Development System. Unless, this locking mechanism is extended to various systems first (DEV and QAS) and later to parallel landscapes (eg:- Project landscapes) it would be difficult to bring in this feature.
Rgds,
Abhijeet Bhagat

ChaRM:Cross system object lock:Ovelapping

Hi Friends,
In SE38, while activating the service "/TMWFLOW/CONFIG_SERVICES", i am seeing following conflict scenarios:
Cross-Project, Client Specifi, Ovelapping
Cross-Project, Client Specifi, Partial Ovelapping
What is the meaning of overlapping? In which scenario it can be used?
Thnaks for your input
PSK

Hi
There is a feature call cross object locking in solman it is used for that
you can check below note for all the available modes
Note 981729 - Cross-system object lock: Alternative lock modes
Hope it solved ur basic doubt
Regards
Prakhar

ChaRM cross system object lock

Anyone have any experience with the cross system object lock in ChaRM? If so, can I get your thoughts on how well it works and your likes/dislikes?
I read the help.sap.com page. I'm looking fto hear about people's experiences.
regards,
Jason

bump.

Cross system object lock (CSOL)

Hi there,
I am trying to set up CSOL and in the SolMan-help, they talk about the CSOL monitor in SolMan.
But what report or tx do I need to start it ?
PS SolMan 4.0 SP6
"In the central SAP Solution Manager system, the cross-system object lock monitor provides an overview of all current lock entries. The entries are presented in table form, and can be selected if you need to delete them, for example"
regards
Steven

Hi Steven,
the tcode is called /tmwflow/lockmon.
Regards,
uDo

Cross system object lock after SP24 upgrade

Hi Team,
We have recently updated from Sol Man SP23 to SP24. I have set-up cross system object lock (CSOL) in SP23. It was working perfectly.
When we are in SP23, i have made following settings:
In T.code: u201C/TMWFLOW/CONFIG_SERVICESu201D , i have set he conflict analysis as "Cross-Project, Cross-Client". So i that i will always get "Warning" Messge while processing SDHF and SDMJ correction.
In t.code: /n/TMWFLOW/CMSCONF , the CSOL is active.
Recently we have upgraded to SP24. After SP24 upgrade, the CSOL is not working properly. The configurations are same as earlier.(Before SP24). Now if i process SDMJ or SDHF corrections, the CSOL always gives me "ERROR" message but i want to get "WARNING" message as earlier. I have checked the conflict analysis in t.code u201C/TMWFLOW/CONFIG_SERVICES". It is still "Cross Project, Cross-Client" only.
Any additinal SAP notes to be implemrnted to correct this behaviour.
Your valuable guidance required.
Thanks
Kumar

I dont believe this is possible at the moment. As you must be already aware, that SAP releases the locks from the objects as soon as the transport request is released from the Development System. Unless, this locking mechanism is extended to various systems first (DEV and QAS) and later to parallel landscapes (eg:- Project landscapes) it would be difficult to bring in this feature.
Rgds,
Abhijeet Bhagat

Cross system object locking -Object editor popup does not show in dev sys

Hi ,
we want to use the cross system locking for r/3 system .
we have done all the configuration required for cross system object locking in central solution manager system and also in development r/3 system .
also we observed that object lock information is avaible in central lock monitor transcation but when ever there is object lcok it does not show us the the popup for object editing.
appreciate your valuable inputs.
Regards,
Amar Kamat

We found the problem.
The structure was being locked by a user in the QA system and overnight the M version finally activated after another transport attempt.
The second structure with this problem was only referenced as a local object (even though it had a proper tech name and package assignment) preventing its activation in the QA system. We needed to hack the query tables to make it look like a proper global structure, then re-transported and it activated.

CSOL Cross System Object Lock - RFC error in satellite system

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

Ok, the resolution was to ensure SMB_X82 (in Solman) has the following roles and profiles:
Roles
SAP_SOLMANTMWCOL
Z_SOLMAN_BACK
Profiles
D_SOLMAN_RFC
S_BDLSM_READ
S_CSMREG
S_CUS_CMP
S_SD_CREATE
S_TMW_ADMIN
This resolved my issue.
Thanks
Shaun

CSOL : No window Cross system object lock displayed

Hello all,
We have configured CSOL in Sol Man ChaRM. But when we test this configuration, any window is displayed to warn us or to inform us that a lock has been created whereas in /n/TMWFLOW/LOCKMON there is a long list of customizing locks entries.
Have we forgot to do something ?
Thanks for your help,
Regards.
Edited by: Changerequestmanager on Nov 22, 2011 11:29 AM

Figured out by myself : because my scenario was irrelevant.
We have chosen a Cross client/project specific scneario but create 2 transports requests in a same project, which was wrong.
Thanks for your help !

Locationg source system object transport request number in target system .

Hi,
After the object is pushed from source system to target using SCC1 for cross clients but same systems or STMS for cross-systems, if we want to see the object's source system's transport request number in the target system, how can we see that ?
Regards,
Rajesh.

Hi Rajesh
If my understanding is correct you want to know the source server in the target system( i.e where we have transported).
For cross-system objects, as you know we use STMS to transport them...
In the target system:
1. SE10
2. Click on Transports button.
3. Select the required request and expand the node.
4. You will have the first one which has log only for Export.
The node with only Export log is the source system...
Hope this helps...
Kind Regards
Eswar

Cross System Lock using for roles?

Hi everybody,
maybe one of you can support me or have some experiences in case of using the Cross System Lock. We are checking the possibilty to implement the Cross System Lock (using in ChaRM, Scenario E (/TMWFLOW/Config_Lock).
First of all, we made a successful test in usage of table content.
Example:
You save a table modification in a Transport Request generated in ChaRM. Thus, the Transport Request is buffered in a Change Document. The result is that the table modification is locked in the object-monitor (/TMWFLOW/LOCKMON).
However, you save a role (pfcg) in a Transport Request generated in ChaRM the included objects in this role are not buffered in the object-monitor (/TMWFLOW/LOCKMON)
Thanks for your answers!
Best regards
Joachim Eichner

If you use the report TMW_TRKORR_LOCK_UPDATE against the role transport after saving your changes in it, this will register the role objects in the CSOL.
The Role transport tool does not automatically trigger the FM that registers the objects in the CSOL, just like manually adding objects to a transport doesn't trigger it. Therefore the workaround is to run this report. Only the transport owner is allowed to run TMW_TRKORR_LOCK_UPDATE.
In our experience it is not that CSOL does not support roles and authorizations; for the purpose of retrofit, it is able to detect conflicts reliably if the report is run consistently after saving role changes to transport. If no conflicts exists, auto-import works fine. If conflicts exist, then roles must be manually retrofitted.

Cross System Locks and WebServices

Hi All,
is there a standard way to set cross systems locks using webservices?
My situation is that i have a contract in SRM and this contract has a link to an object in an ERP System. So whenever a user is changing the SRM object I need to lock the ERP object to make sure the data are consistent.
THX,
Christoph

depends what you mean by standard way. If you're looking at configurable/customizing way, I'd say no way.
if you're looking at implementation way and really want to use WS, you could call the bapi that lock the contract in ERP using the web service layer of SRM something like http://<ERP host ip>/sap/bc/soap/wsdl11?services=Z<whatever BAPI changes the ERP contract>&sap-client=800&sap-user=<username>&sap-password=<password>.
for example the Purchase Order can be lock this way using BAPI_PO_CHANGE but you have to create a wrapper to it as BAPI_PO_CHANGE doesn't not commit to DB.

Cross System object lock

Similar Messages

Maybe you are looking for