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

Similar Messages

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

  • 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

  • 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

  • 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

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

  • 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

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

  • 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 (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

  • 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 !

  • AE 5.2 cross system risk analysis with CC 4.0

    Hi,
    We have an unique situation.
    We have CC 4.0 (central) set up in ECC system where the rules and risks are defined for systems such as R/3, HR and SRM
    We need AE to use this central CC system to do the risk analysis when an access request for HR or SRM is submitted in AE 5.2. Right now for a request to a HR system, risk analysis is being done in HR system where there are no rules and hence no risks are identified.
    Environment :
    CC 4.0 in  ECC 5.0 with VIRSANH RTA 520_640 Level 3 and VIRSAHR RTA 520_640 Level 2
    AE 5.2 JAVA in NW 7.0 SP level 2
    Risk analysis for Access requests to ECC system is done with out any issues and the connectors in AE are defined as well as CC 4.0 configuration for cross system is enabled.
    Please give your suggestions and also tell me if this below scenario is possible.
    Use CC 5.2 Java stand alone system and define logical/cross system to connect to multiple systems such as HR and SRM and use those specific rules to do the risk analysis.
    Thanks

    Hi RM,
    You can setup Risk Analysis inside AE Configuration.
    You can identify the level of risk analysis and specify the Compliance Calibrator version for processing risks.
    See the details from the AE Configuration Manual
    In the Select Compliance Calibrator Version pane, from the Version drop-down list, select the version of Compliance Calibrator.
    In the URI field, enter the appropriate URI address for the web services.
    In the User Name field, enter your User ID. Your User ID must have security access
    to web service.
    In the Password field, type your password.
    Select the Perform Org Rule Analysis option to perform org. rule analysis at risk
    analysis time.
    Note: There are two selectable versions of Compliance Calibrator. If you select 5.0 Web Service, three additional fields appear (URI, User Name, and Password). For the URI field, you need to navigate to the
    SAP NetWeaver Web Application Server Home page > Web Services Navigator > CCRiskAnalysisService > WSDLs > Standard link of Document, where you will see a list of all web
    services in the server. Select the desired URI address.
    If you select Compliance Calibrator 4.0, there is no need to connect to a URI address
    So the answer is YES, you can connect AE  5.2 with CC 4.0 for Risk Analysis.
    Hope this helps,
    Regards,
    Kiran Kandepalli.

  • Object locking in Charm

    In testing Charm functionality, I am finding that objects are not being locked and 2 developers can make customizing changes in a table at the same time and one transport can overwrite the others changes with no notification!
    This seems very dangerous.
    Is there any way to lock these objects?
    Thank you!

    Hi Randy,
    I am not aware of any functionality to help you here. You use the same development processes you used before to avoid this.
    You could use the Solution Managers Business Process Structure and the Development tab to maintain a status for all of your objects. You would have to instruct the developers to go to Solution Manager, assign the object to themselves, set the objects status to "In development" (or whatever custom status you come up with), double click the object to open it up and make changes, and when done set the status back to "complete" and remove their name. This also provides an audit trail.
    Hope this helps.
    regards,
    Jason

  • 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

Maybe you are looking for