Solman Change Request Management Issue - about create task list

Dears,
    We are now using Solman ChangeRM. I have created a maintainance project and maintained its logical component and IMG project. when I want to create a task list for this project, a message"The project is not released. Hence cycle can not be created" poped. The message no. is /TMWFLOW/CONFIG_UI017. Where can I release the project?
Thanks
Roger

Hi,
Pls click the check button(next to activate button)
see the SLG1 log generated remove the errors shown in red.
One it is done u press the refresh button & thn u cn create the task list
chk
https://websmp202.sap-ag.de/~sapdownload/011000358700000657692007E/ECTS_CHARM_SP12.PDF
/people/dolores.correa/blog/2008/07/26/first-steps-to-work-with-change-request-management-scenario
http://help.sap.com/saphelp_sm32/helpdata/en/0c/5b2160f6fa4b83a3674a210b1cdeb0/content.htm
Regards
Prakhar

Similar Messages

  • Change Request Management  "There is no task list for this project"

    Hello!
    I would like to use the functionality of CharM in SOLMAN 4.0.
    When I enter the Tcode /n/tmwflow/proj I receive the waring/error "There is no task list for this project" (/TMWFLOW/TRACK_N114)
    If I create my own task list via Task list --> create
    I get the warning "You cannot change task lists in the SAP namespace"
    What are the steps to define task list for my project?
    Do I need to configure SPRO ... --> Extended Configuration --> Schedule Manager?
    The second warning I get: "NO CTS projects created yet" or
    "The Solution Manager project does not have an active CTS project yet".
    How can these warnings/errors be corrected?
    Thank you very much!
    regards

    Hi,
    Pls click the check button(next to activate button)
    see the SLG1 log generated remove the errors shown in red.
    One it is done u press the refresh button & thn u cn create the task list
    chk
    https://websmp202.sap-ag.de/~sapdownload/011000358700000657692007E/ECTS_CHARM_SP12.PDF
    /people/dolores.correa/blog/2008/07/26/first-steps-to-work-with-change-request-management-scenario
    http://help.sap.com/saphelp_sm32/helpdata/en/0c/5b2160f6fa4b83a3674a210b1cdeb0/content.htm
    Regards
    Prakhar

  • Creating a New Task in SOLMAN Change request Management

    Dear all,
    We are using SOLMAN 4.0 and scm functionality.In the change request screen we have a create follow up task(+ icon on top left).What is the use of this task,can we asign a task to some particular person?for example can i assign task to tester?If the task has not completed the task,while closing the correction will it give error?
    Please give your suggestions.
    Thanks in advance,
    Avinash.

    Hi,
    Pls click the check button(next to activate button)
    see the SLG1 log generated remove the errors shown in red.
    One it is done u press the refresh button & thn u cn create the task list
    chk
    https://websmp202.sap-ag.de/~sapdownload/011000358700000657692007E/ECTS_CHARM_SP12.PDF
    /people/dolores.correa/blog/2008/07/26/first-steps-to-work-with-change-request-management-scenario
    http://help.sap.com/saphelp_sm32/helpdata/en/0c/5b2160f6fa4b83a3674a210b1cdeb0/content.htm
    Regards
    Prakhar

  • SOLMAN- Change Request Management

    we have a request from one of our customers a big insurance company, to use the "change request management" out of the SOLMAN for non-SAP solutions.
    is it possible ? what are the advantages and disadvantages?
    thanks
    Amnon

    Hello Amnon,
    SAP Solution Manager as the name suggests is for managing the whole gamut of SAP and Non-SAP solutions in the IT Landscape of an organisation. It provides you the tool, content and gateway to create, operate, manage and monitor your solutions over time.
    Please use the following links which may help you in a better way....
    Manually registering a non-SAP system in SMSY
    http://www.sappro.com/downloads/NonSAPsystems.pdf
    SAP Solution Manager Ready
    SAP Solution Manager Ready
    A General overall discussion on Solution Manager http://www.sap.com/platform/netweaver/components/solutionmanager/index.epx
    Hope it helps.
    Cheers,
    Satish

  • Change Request Management--Create Transport Request from Service Desk

    Hi Experts,
    What are the right steps to create a change request via service desk message and keep following the process until import to PRD.
    Regards.

    Hello Jorge,
    You can create Change Request using two ways.
    You can create a Change Request from a Service Desk Message using the action "Create Change Request" or you can create a Change Request directly in transaction CRMD_ORDER.
    Please, check the links below where you can find more information about Charm.
    /people/dolores.correa/blog/2009/07/23/change-request-management-scenario-working-examples
    /people/dolores.correa/blog/2008/07/26/first-steps-to-work-with-change-request-management-scenario
    Best Regards,
    Diego Fischer,

  • How to deactivate Change Request Management workflows task

    We are in a situation where we are switching external SAP service
    organisation and we cannot at this stage introduce any new procedures
    regarding sceduling-tasklists/TMS/etc. Our ChaRM implementation project
    must be set back in to a possision where we can maintain our normal
    system maintainance processes without using a fully implementated
    CharRM functionallity. The implementation of CharRM has to be realized
    in 2 steps:
    a) activate only ChaRM documentation system/flow as an extention of
    servicedesk, implement this in our organisation
    b) activate fully ChaRM functionality with interaction with
    SLD/TMS/tasklists/etc after we have switched service organisation
    Needs:
    1) How to deactivate ChaRM IMG setting SAP Solution Manager-
    >Configuration->Scenario-Spesific Settings->Change Management->Change
    Request Management->Standard Configuration->General Activities-
    >Activate Integration with Change Request Management and related
    settings.
    We had in an earlier stage the total service process/documentationflow
    up and running and with possibilities to interact/respond on
    servicemessages for these roles: User, Servicedesk, Change Manager,
    Change Advisory board, Developer, Tester, IT Operator equal to ChaRM
    process.
    2) Ensure availability to use ChaRM as a extention to servicedesk
    regarding administration and documentation of SAP changements.

    Hi,
    Find the guides : on help.sap.com
    Change Management:
    http://help.sap.com/saphelp_sm40/helpdata/en/0c/5b2160f6fa4b83a3674a210b1cdeb0/frameset.htm
    Service Desk:
    http://help.sap.com/saphelp_sm40/helpdata/en/45/51fbdbd4941803e10000000a1553f7/frameset.htm
    Regards,
    Siddhesh

  • Solution Manager 3.2 SP 8- Change Request Management Configuration Problem

    Hi friends,
    We are in process of implementing SOLMAN 3.2 SP8 in our landscape.I am facing  problem in configuring change request management.
    When the developer is working on an urgent correction document we are facing a problem.The steps we are following are here under provided.
    Step 1 :
    Selected Action "In development" - > it created the transport request in the dev system.
    Step 2:
    Action "Log into System" -> made correction attached to the transport request manually and released the task.
    Step 3:
    Action "Release transport requests" -> The transport request in the development was released.
    Step 4:
    Went for action "Pass to correction" -> I am facing exceptions which conveys
    Status was reset by system
    A condition is not satisfied because of an exceptional situation
    Not all transport requests yet released
    And we would be thankful if you provide the authorization required for the different roles in the change request management.I have followed the help file of SOLMAN 3.2 and create the users as under
    User - Role
    SOCM_RQSTR - ZSAP_SOCM_REQUESTER
    (Derrived from SAP_SOCM_REQUESTER)
    SOCM_DVLPR - ZSAP_SOCM_DEVELOPER
    (Derrived from SAP_SOCM_DEVELOPER)
    SOCM_CHNGNGR - ZSAP_SOCM_CHANGE_MANAGER
    (Derrived from SAP_SOCM_CHANGE_MANAGER)
    SOCM_CHNGNGR - ZSAP_SOCM_IT_OPERATOR
    (Derrived from SAP_SOCM_IT_OPERATOR)
    Even then I am facing problems while developer creating transport requests and while logging into development system.
    I tried adding S_RFC,S_RFCACL auth objects to their roles but did not help.
    Pl. suggest.
    Thanks & Regards
    Mrutyunjay
    Message was edited by: Mrutyunjay Rao Dora

    Hi all,
    We are trying to implement the Change Request Management piece in Solution Manager 3.2. 
    We are facing the following issues which I think relate to the same reason:
    1)We have created a Maintenance Project in SOLAR_PROJECT_ADMIN and assigned it a logical component, which consists of our two system landscape (namely DEVàQAS). We have also created the IMG project in the DEV system and have distributed that IMG project to both the Solution manager system and the DEV system. Now we have to make the maintenance cycle and task list for that maintenance project, but as we select the project and click on “create project cycle” it shows the message "The project is not released. Hence cycle can not be created". It is showing the status of project as locked .How can we open or unlock the project to remove the error?
    2) Also after selecting the SMI project when we click on the button “CTS status switches” or “project specific Transport route” it responds with the error "Project landscape not configured; set the project status to "open" first ".
    3)When we click on “synchronize single project” it prompts for the login of connected system (Development System) and after login, it gives an error "Warning, problems during synchronization of the system Landscape".
    For Error resolution, we have checked the system landscape and it does not give us any errors. We have done that, both from the solution manager by going to the transaction SOLAR_PROJECT_ADMIN -->  >system landscape tab>selecting our logical component and doing a check by clicking the "Check system Landscape" button. It returns with "no Errors". We also did a check on the TMS configuration by logging directly on to the TMS domain controller system and checking the Transport routes. We have checked the RFC connections without any errors.
    Any help would be greatly appreciated.
    Thanks
    Abhi

  • Help me configure Change request management !!!

    Dear friends,
    I am Going to Configure Change request Management, so just to ensure that the configuration is not erronous, i would need Expert advise..
    Just want to know Clear few things before i proceed..
    I am also refering SPRO and related notes
    Scenario :
    I have two SYSTEMS SAP ECC 6.0 with System id R03 and Soluiton manager with SYSTEM id SOL,
    R03 has 3 clients, 300 600 700..
    In R03 300 is the development client, 600 is quality client, 700 is the production client.
    SOL has 2 clients, 100, 200
    With 200 as the production client.
    Q.1) <b>Do i have to configure CHARM in both the client (100 and 200 of SOLMAN).</b>
    Q.2) Initially I had tried to set CHARM in client 100 of solman, but later on realized that it has to be set up in client 200.
    When i logon to client 200 and  Execute IMG activity Spro-> sap soltion manger->basic settings-> sap solution manager system->activate integration with change request management.
    Then by default it take the previous client ( client 100) as the change request management client.
    ( as we know there are three steps in the above activity ), the other activity are executed properly, only prblem being that the default client is always set to 100, which should not be the case).
    I do get the prompt saying ( "The change request clent is set to clent 100, do u want to change to client 200, on clicking yes, still it is always set the same client 100 as charm client ")
    <b>Plz let me know what do i do to set the change request client to 200??</b>
    Q.3) Regarding TMS, we have local domain controller in solman and local domain in R3.
    We are planing to establish domain links between the two systems( ie both the domain controllers) ??
    Is this the right strategy ??
    <b>Any other method that u can recommend  ??</b>
    Q.4)One of the IMG activity says, Generate Destinations to client 000 of all the domain controllers..
    Whenever i do this these, destinations are created with errors, i am not able to create trusted RFC destinations without errors.
    When i logon to satellite domain controler and excecute sm59 there are 2 destinations created Trusted and BACK.
    These destinations works well,
    but when i logon to Solman, got to sm59 , when i test the TMW and TRUSTED rfc destinations  i test these destinations using Remote Logon i get error,
    " no authorization to logon as trusted system"
    I went thru one note which recomended Kernel upgrades to solve the problem,
    I r3 my kernel relaese is 700 with patch level 56, the note recomends to apply patch 80, did u have these problems??
    <b>what is your kernel patch levels in sateliite and solman systems.</b>
    Q.5) TO be able to raise tickets from R3 to solman we create RFC destinations.
    We also create RFC destinations to client 000 of all the sateliite system,
    <b>dont u think these RFC destinations might interfere with each other??</b>
    Q.6) Is there anyone who has successfully configured CHARM. Can you plz share the  configuration documents with me..
    Please note :
    <b>All the contributors would be handesomely rewarded with points .</b>

    Hi,
    Check this
    Note 128447 - Trusted/Trusting Systems
    For your Q4.
    Q3.)
    Establishing Domain link - That's the right way. Go ahead.
    These are the steps.
    <b>1.Define Transport Routes for System Landscape</b>
    assign exactly one development system to a production system, and that these two systems are connected by exactly one unique transport track. If a development system and a production system are connected by more than one transport track, this may lead to inconsistencies within the transport distribution. This type of transport configuration cannot be supported by Change Request Management, and may cause inconsistencies within the tools involved.
    <b>2. Activate Extended Transport Control</b>
    The CTC parameter should be '1'
    <b>3.Configure Transport Strategy</b>
    Deactivate the QA Approval.
    <b>4. Activate Trusted Services.</b>
    5.Activate Domain Links.
    You have to activate domain link between systems.
    6. Generate RFC Destinations to Client 000
    Hope this helps.
    feel free to revert back.
    --Ragu

  • Change Request Management in Implementation projects or not?

    Hello guys,
    We are starting a Change Request Management project at a customer.  We discuss  in the blueprint phase whether we should be using it only for maintenance activities, and not for implementation projects.  We have some people that can be working both in maintenance and also in projects at the same time.
    We want to understand whether that scenario is possible and also whether is advisable.  We want to have control over the process, and therefore we should be restricting the creation of Transport Orders through SE01 so that we know that transport requests are created only by change document action.
    What are the drawback, difficulties, considerations you may consider in making that decision?  Is it logic to work that way or is it better just to implement it for the whole installation, including implementation projects?
    Esteban Hartzstein
    Edited by: Esteban Hartzstein on Jan 20, 2010 3:37 PM
    Edited by: Esteban Hartzstein on Jan 20, 2010 3:39 PM

    We want to have control over the process, and therefore we should be restricting the creation of Transport Orders through SE01 so that we know that transport requests are created only by change document action.
    this you can do either via SE03 / Display/Change Request Attributes  / SAP_TMWFLOW     Request created using Change Manager          X          X / Defaul for all client = Mandatory
    or
    you can achieve this by just activating the CHaRM in SolMan ( solar_project_admin / system landscape / CHARM)
    Nesimi

  • Change request management in solution manger release 7.1 or 7.0

    Hi All,
    Can any body please explain me how to configure change request management in solman release7.1 and if it is possible please send document to my below maild Id.
    And please let me know what are the steps needs to be done satellite systems, we have EP7.0 landscape also there .do we have to do any additional configuration for that in solman side?
    I appreciate for your prompt response
    Thanks in advance
    My Id: haritechies gamil.com
    Regards,
    Hari Prasad . L

    Hi
    Adding more to it
    Use the following link,
    /people/dolores.correa/blog/2008/07/26/first-steps-to-work-with-change-request-management-scenario
    https://websmp202.sap-ag.de/~sapdownload/011000358700000657692007E/ECTS_CHARM_SP12.PDF
    Regular correction
    https://websmp202.sap-ag.de/~sapidb/011000358700000086572008E.sim
    Later login to solman enter tcode SPRO and goto scenario specific Change Request management node and start configuring by
    going through the IMG Help and as per requirement.
    Create a maintenance project and Activate Charms
    https://websmp202.sap-ag.de/~sapidb/011000358700005479242006E.sim
    Regards
    Uday

  • How big effort it is to setup Change Request Management?

    We are interested in implementing Change Request Management into our Solution manager 7.0.
    What size of an effort in mandays it actually is and what kind of professional roles are required to set it up? Some background information for your responses:
    implementation project is already there in Solman (SOLAR01/02) and is already live
    satellite system connections within SMSY are already active
    no central CTS/CTS+ is currently in use
    when having CHARM it is assumed that also CTS+ should be used
    So, I guess we are in a typical situation where implementation project has ended and live and support organisation and tools are being setup. There we need CHARM and CTS+.
    I have read lots of SDN threads and blogs, but did not get a clear picture how big effort setting up CHARM is. Please note, I not looking for config guides now, just your experiences. Even if am not interested in config guides, could you at least describe the main steps that are necessary in setting up CHARM?
    br Kim

    Hi
    Adding more to it
    Use the following link,
    /people/dolores.correa/blog/2008/07/26/first-steps-to-work-with-change-request-management-scenario
    https://websmp202.sap-ag.de/~sapdownload/011000358700000657692007E/ECTS_CHARM_SP12.PDF
    Regular correction
    https://websmp202.sap-ag.de/~sapidb/011000358700000086572008E.sim
    Later login to solman enter tcode SPRO and goto scenario specific Change Request management node and start configuring by
    going through the IMG Help and as per requirement.
    Create a maintenance project and Activate Charms
    https://websmp202.sap-ag.de/~sapidb/011000358700005479242006E.sim
    Regards
    Uday

  • Change Request Managment setup for Solution Manager 4.0

    Hi guys! Can someone help me on how to setup the Change Request Management in Solution Manager 4.0? I have already have checked the SAP Marketplace for any documentation about this topic but found none. I am configuring the two test servers (1 prod and 1 dev) in tcode SMSY. I have also configured the system role for each server. When I try executing /TMWFLOW/CMSCONF in SE38, no clients appear in the CRITICAL OBJECTS pane. Did I miss a required step in the implementation? I hope you guys can help me. Thanks in advance...
    Regards,
    Ronald Navarro

    Hello Ronald,
    Following the spro configuration will setup the Change Request Management scenario, each spro point has associated the corresponding documentation.
    Also in service.sap.com/rkt-solman>solman 4.0>CCC profile you will find valuable information about how to use this scenario.
    Hope this helps,
    Dolores

  • Intergrating Change Request management with satellite systems

    Hi,
    We are using SOLMAN with SCM functionality.We have integrated it r/3 and now integrating with XI.I have created the logical componenet for the system and added to the maintenance project.But when i enable the project for change request management it gives a warning and when checked in SLG1 it shows error message as no consolidation system for XS1(Developement sys) and no export system for XP1(production sys).All the configurations to be done in the TMS are done as per the instruction in the configuration guide and R/3 is configured in the same way which is working fine.Please give your comments on this.
    Thanking you in advance,
    Avinash

    CLOSED

  • Change Request Management without Transport Managment System

    Hello,
    we would like to use the Change Request Management but without using the Transport Managment System (TMS). Means, we do not want that transport request are created automatically, we do not want that it is possible to log on to the satellite systems via the Solution Manager and we do not want to integrate the transport track into the Solution Manager.
    What effort do we have to estimate for such a change? Does anybody already use a process like this? We would be grateful for any idea or solution.
    Many thanks in advance.
    Jenny

    Hi Jenny,
    you can do this with the following activities in your custom Business Transaction (BT):
    - remove un-useful actions from your action list (TA: CRMC_ACTION_CONF)
    - remove the action from the actions depending on user status (TA: starting from SPRO)
    - unlock the switches from your SMI Project CTS Switches (TA: SOLAR_PROJECT_ADMIN)
    The effort, for copying a standard BT and remove the actions and testing it, is about 5 days, if you already know how to customize a ChaRM BT... last but not least if one of the standard flows is what you really need.
    Please let me know if you need more details, otherwise please reward the forum points
    Regards ,
    Giampaolo

  • Change Request Management - Transport Request reimport

    Hello,
    I have read in a forum on SDN about the following behaviour of Change Request Management  in case of a Maintenance Project: after completing import to production environment through Normal correction, when the same maintenance cycle
    is used again, ChaRM reimports all the TP's imported in the previous run.
    In case of an Implementation Project with Normal correction I guess that this can not happen for an import to Production environment, because it's not possible to use again the same cycle, is it right?
    But if we consider the import to Test environment: for example, during a Project cycle, transport request TR1 is imported to Test environment, then cycle status is set again
    to "In development" and a new transport request TR2 is created. Is TR1 re-imported, when TR2 is imported to Test?
    Thansk a lot,
    Stefano

    Hi,
    Whenyou import a normal correction as per the recommedations from SAP they are asking to de select keep for further imports options,so that when we import other request it will not import the older request.
    Please revert for any clarifiaction,
    Thanks and Regards,
    Avinash.

Maybe you are looking for