ChaRM: new challenge with maintenance cycle

Dear colleagues,
I have got the following messages for transaction 8157 SDMJ (created from 8156 SDCR):
Header Data     No maintenance cycle is open for the current system
Item 1     The item category 'SRVP' is not permitted for product 'SUPPORT_HOTLINE'.
My questions are:
1) Is the product maintenance obligatory for ChaRM?
2) how to detour these errors?
Regards,
Artem Ivashkin

Mainly this errors occurs due to locked maintenance cycle so goto solar_project_admin and then unlock by right click on the top or it may be due to wrong ibase other ,possible reasons are
- The IBase is wrong: The IBase/component must represent the production system in the project landscape.
- Lack of authorizations: Assign role "SAP_SOCM_ADMIN" or "SAP_CM_ADMINISTRATOR_COMP" (or equivalent) to the user who would like to approve the change request.
- Project is locked in table /TMWFLOW/PROJMAP: If an error is detected during the processing, then the project might be locked in this table. The customer can unlock it by pressing the refresh button under tab "System Landscape" -> "Change Requests". If there are other error messages shown during the refresh process, the customer must fix those errors beforehand.
P.S. The 'Check' button under tab 'Change Requests' (the same as transaction /TMWFLOW/CHARMCHK) will only do the checking. On the other hand, the 'Refresh' button will do the checking and update the relevant database entries.
/people/dolores.correa/blog/2009/07/22/change-request-management-scenario-usual-questions-and-known-errors
check the above reasons mainly refresh
Edited by: Prakhar Saxena on Jun 3, 2011 5:36 PM

Similar Messages

  • Inconsistency with maintenance cycle and task list phases in ChaRM

    Hi Experts,
    I'm deploying ChaRM with SolMan 4.0 SP09.
    I was testing a scenario where there are more than one maintenance project open for same landscape (different logical components but values are the same). I have been using maintenance cycle document (in crmd_order) to control phase changes both in task list and in maintenance cycle.
    I received an error message stating that the system has reset the status of the maintenance cycle and the end result was that task list phase is one step ahead of the maintenance cycle. This of course causes the situation where certain actions are no longer possible (maintenance cycle in Dev with release but task list already in test => release and import are not possible and reseting phase with task list is prevented by ChaRM).
    My question is how do I restore the inconsistency. I have looked for notes (but of course this is not a notes issue) and the internet for solution.
    I am very greatful for any hints you may give me!
    Kind regards,
    Auli

    Thank you!
    Exactly what I'm trying to do. I'll give it a go and get back to you asap.
    BR
    Auli

  • ChaRM: Change name of Maintenance Cycle

    Dear Experts,
    Once a Maintenance Cycle is created I have no clue how to change this name.
    In the Task List I'm able to change the 'Task Group Name', but this reflect to the MC name in the pop-up when you create a Correction.
    Anybody an idea?
    Thanks
    Roel

    Christian,
    Indeed I mean the M000 and H000 names.
    Maybe they can be changed directly in the DB, but the only thing I found until now is a shortcut '/TMWFLOW/PROJCT' which I'm unable to open in SE16.
    I'm trying to find out how I can find the table name behind this shortcut.
    Roel

  • Problem with differetn phases for one maintenance cycle

    Dear Solman Gurus.
    It has happened several times, tha while working with maintenance cycle from 2 different places - from activity Maintenance cycle and form Task list, that system shows different phases. For example in task list is phase TEST in activity Maintenance cycle is phase Development wit release. And you are not able to correct it. Or at least we do not know how to do it. So we can only close the whole maitenance and start all over again.
    Please help us how to prevent this situation or how to correct it.
    Regards,
    Petr

    Hi Petr,
    You should have a look to SAP Note 933705 that helps with your problem.
    Best regards,
    Stéphane.

  • Not able to closing the maintenance cycle of charm

    Hi Team
    I am not able to close the maintenance cycle of charm.
    I had already tried with the phase utility report, I had checked my all authorizations and it is fine.
    I had gone through most of SCN queries for same, current phase of project cycle is completed however. Not able see the any error logs in SLG1.
    Regards
    Harsh

    Hi Rishav,
    We had resolve the issue as now we are able to close the cycle successfully,
    But new CTS project is not being generated, Any idea, should we need to check this with SAP again.
    B R
    Harsh

  • ChaRM Error - "No maintenance cycle is open for the current system"

    Hello All,
    I am setting up ChaRM in development system after EGI session with SAP support. I have copied standard transactions to custom ones and created Maintenance and Implementation project to run test of all scenarios.
    I now come across error of "No maintenance cycle is open for the current system" after I create a change request and in the change document, I cannot see it link with task list and the error message is displayed. I tried it with custom transaction as well as standard SAP transaction (SDCR) and get the same error.
    What links a document to a maintenance cycle? Where can I see the config of this setup? I am trying to see where it is broken. I am using the correct IBASE number (production client in logical component), I tried to create a new logical component, new projects with correct settings but it still gives this error message. Please advice.
    Thanks and regards,
    Nischal

    Hi
    did you also unlock the maintenance cycle and open for changes in solar_project_admin by right click
    do check this blog
    /people/dolores.correa/blog/2009/07/23/change-request-management-scenario-working-examples
    /people/dolores.correa/blog/2009/07/23/change-request-management-scenario-working-examples-final-points-and-appendix
    Question no 17
    /people/dolores.correa/blog/2009/07/22/change-request-management-scenario-usual-questions-and-known-errors
    Hope it solves
    Regards
    Prakhar

  • Completing / closing Charm Maintenance Cycle

    Hi All,
    I am trying to close the CHARM Maintenance Cycle. But get an RFC related error as mentioned below.
    "Error RFC destination
    /TMWFLOW/TL_COMPL_CHK_TR_WO_TL: New Maintenance
    Cycle M000000177"
    The user id which is trying to close the maintenance cycle in Solman,Is it necessary to have the same user id in Satellite system Development '000' client, with proper RFC connections.
    Regards
    PK

    Hi,
    Regarding the error "Error RFC destination
    /TMWFLOW/TL_COMPL_CHK_TR_WO_TL" when closing the cycle:
    This is usually an issue with the READ RFC user authorizations.
    Please add to the READ RFC users to your DEV system (in all
    clientsincluding client 000) the appropriate authorizations (e.g.
    profile S_TMW_CREATE).
    Please see also point 19 of this SDN blog:
    Change Request Management scenario: Usual questions
    /people/dolores.correa/blog/2009/07/22/change-request-management-scenario-usual-questions-and-known-errors
    Hope this helps.
    Cheers
    SH

  • Charm implementation: No maintenance cycle is open for the current system

    Gurus,
    I'm in implementation project to use charm.
    I've created SDCR using charm_create, and choose transaction type subject "Development (implementation)"
    After approving the change request, so that the status become "Approved", I re-open the request to set into "in development", but there's error:
    "No maintenance cycle is open for the current system"
    I've checked notes and search the forum but not relevant to my subject.
    Please help.
    Regards,

    Hi Cesar,
    I'm facing this issue now. I have followed Dolores blog
    - The IBase is wrong: The IBase/component must represent the production system in the project landscape. RP1 is my production
    - Lack of authorizations: Assign role "SAP_SOCM_ADMIN" or "SAP_CM_ADMINISTRATOR_COMP" (or equivalent) to the user who would like to approve the change request. I have updated all roles and given the users SAP_ALL
    - Project is locked in table /TMWFLOW/PROJMAP: If an error is detected during the processing, then the project might be locked in this table. The customer can unlock it by pressing the refresh button under tab "System Landscape" -> "Change Requests". If there are other error messages shown during the refresh process, the customer must fix those errors beforehand. Refreshed it many times without errors
    I'm on the latest level of Solman 7.1 SP8, I have implemented all the new notes as well.
    I have attached a screenshot
    To me it seems like a bug, but haven't found anything on marketplace. Any help is much appreciated.
    Cheers
    Jimmy

  • Not able to complete Maintenance Cycle in CHARM Maintenance Project

    Hi,
    While completing the CHARM Maintenance Project, getting following error:
    "Error RFC destination
    /TMWFLOW/TL_COMPL_CHK_TR_WO_TL: New Maintenance
    Cycle M000000177"
    Because of this error I am not able to complete  the Maintenance Cycle, i.e. not able to change the status  of Maintenance Cycle to 'Completed'
    Regards
    PK

    hi PK
    please refer the posiblities on
    [cannot close maintenance cycle|Cannot Close Maintenance Cycle in CHARM;
    jansi

  • Assigment maintenance cycle -- system (IBASE) in CharM

    Hello!
    I have the problem to establish CharM functionality.
    When I try to set a urgent correction in status "In Development" I get the following error:
    No maintenance cycle is open for the current system
    My question are:
    - How do this assignment maintenance cycle <--> system (IBASE) work?
    - Is it perhaps possible to execute this assignment manually?
    - Is there some log files that can be analysed for this problem?
    Thanks & regards
    Thom

    Hi,
    About this issue, there is a detail information about this in blog point 6  u201CChanges in the logical components of a project where Charm is already activatedu201D.
    This is the link:  http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/15116
    So, you have to change the transport route accordingly and then close current maintenance cycle and generate a new one.
    Following is the steps.
    1: please import all the transport requests which were associated in the current maintenance cycle task list by STMS manually import.
    1: change transport route from DEV > PREPROD >PROD to DEV > USER > PROD on the domain controller system.
    2: close current maintenance cycle.
    3: change the system landscape to DEV > USER > PROD in solar_project_admin.
    4: generate a new maintenance cycle.
    Thanks
    Regards,
    Vikram

  • Maintenance cycle - Charm

    Dear All,
    I am in process of implementing CHARM and i am facing issue in the process flow for maintenance cycle.
    In normal changes - we create change request and a maintenance cycle (MC) is attached to it. Once we change the status to Dev with release then changes are moved to Test system (transport of copies) and after successful testing (actual transport request is released) we change MC status to Test then changes moves to Test system. Then MC moves to Go live and then changes are imported to production. Now when status of MC is go live then we need to change the status back to dev with release which is not working instead it gets insync with the project phase. Kindly let me know if anyone has faced the similar situation.
    Can you someone please clarify how mc status should work in case of normal changes.
    Regards
    Sushant

    Hi Sushant,
    1. try to change the phase of the project cycle without assigning any Change Document to it .
    2. Number Ranges
    "Before you can begin using Change Request Management transaction types, you must ensure that a number range is defined for these transaction types. The number range interval determines the sequential numbers assigned to newly created transactions. "
    To do so you can use transaction SNUM and enter CRM_SERVIC as the number range object.
    The number range interval which the system uses is defined in the transaction customizing in the Transaction Numbering section.
    Please check the below link for more details in 3.2.7
    https://websmp208.sap-ag.de/~sapidb/011000358700001056012011E.PDF (3.2.7)
    Rg,
    Karthik

  • ChaRM: Several maintenance cycles in one maintenance project?

    Hi!
    We are working with urgent correction within ChaRM and thinking about to implement the normal corrections as well.
    Our ChaRM workflow for normal corrections is characterized by:
    a)corrections with different Life cycle (those who will be processed within 1 week, other with 2 week, etc.)
    Questions:
    1) Is it possible to have several maintenance cycles for one maintenance project to handle condition u201Ca)u201D?
    2) What will happen with all the normal corrections and urgent corrections that have a long life cycle (status: in development, test, etc.) when the charm manager set the status of maintenance cycle in u201CGo liveu201D?
    Thank you  very much!
    H. Thomasson

    Hi Holger,
    Maintenance cycle and SMI project is a 1:1 relationship.
    In status GoLive you will be able to continue developement/work on normal corrections but you will not be able to release any transport requests/create transport of copies so your testings in QA will be limited.
    In phase GoLive you are able to import requests into production.
    Normal Corrections which have not been released yet are not lost. Depending on your scenario you may switch phases back to "in dev with rel." after you imported into production. It is not necessary to close and recreate maintenance cycles if you use one project for daily/weekly maintenance.
    /cheers

  • ChaRM and Maintenance Cycles

    All,
    I am just starting out with implementing the ChaRM functionality on Solution Manager 4.0 SP12.
    I have activated the BC Sets and can see how to customise the Change document behaviours but am struggling to understand and prototype the integration of transports & Maintenance Cycles. 
    I am planning to implement SP15 but until then, I wondered if you could point me in the correct direction for understanding how they work and how to customise the settings for them?
    Ideally, I would like a reference site to view this in an operational sense.
    Any help is appreciated.
    Simon

    Simon,
      Here you go - there is more on the SAP Service Market Place and e-Training, but this link below is also a great source of information on how to get everything working.
      If you have any more specific needs, please don't hesitate to ask - if this answers you question, please set this thread to answered.
    http://help.sap.com/saphelp_sm40/helpdata/en/0c/5b2160f6fa4b83a3674a210b1cdeb0/frameset.htm

  • Moving Change requests to new Maintenance cycle after approval

    Good Day
    I was wondering, is there an easy way to move any give change request from one maintenance cycle to another one. An example would be.
    I have a change request that currently has 1 ABAP, 1 Config and 1 Security transport assigned to our current maintenance cycle. I have been requested to move the change request (along with all the transports) to a future maintenance cycle.
    Is it just a case of re-assigning the change request to the future cycle, ?
    Regards
    Don Newton

    Hi Don,
    It's a very interesting question... I think that a lot of people here need this functionality and SAP finally hear that from us.
    This new functionality came with SP15. You should have a look to SAP notes 1071412, 1134993 and 1141086, it may help you to solve your problem.
    regards,
    Stéphane.

  • Cannot Close Maintenance Cycle in CHARM

    Hi,
    I'm testing CHARM and I'm trying to set the Maintenance Cycle (SDMN) to "Complete", but it's giving me an error.
    Error: "Move to Next Maintenance Phase Rejected"
    I was able to go through all the maintenance phases successfully as part of my testing, but for some reason the system will not let me close the maintenance cycle.
    How can I find the problem?

    Hi,
    Follow this note to 1134993.
    This should solve your problem.
    Feel free to revert back.
    -=-Ragu

Maybe you are looking for