Maintenance Cycle Phase transistion

Hi,
We are using chaRM 4.0, in tx SCMA,we can not able to move the Phase Transistion from 'Created' to 'Development without Release'. When we click on the next phase it is giving the below error . kindly help us.
MsgType Message Class Msg.no. Message text
E /TMWFLOW/PHCNTRL 54 Change transaction
is incorrect
E /TMWFLOW/PHCNTRL 56 Phase transition
from 'Created'
to 'Development
without Release' is
not possible
Rgds,
Jeni.

Please kindly check on the following notes
933986 Phase transition not possible
909236 No phase transition possible after Note 898168
902579 Maintenace cycle cannot progress to next phase
Prakash

Similar Messages

  • Object to change the SCMA maintenance cycle phase in CHARM

    Hi Everyone,
    Can anyone let me know what is the Object which can perform the activity of changing the Maintenance cycle phase in SCMA Tcode in CHARM? i know only the change manager will have authorization to do that. i want to know the Role name and the particular object which will perform this activity.
    thanks,
    Guru

    Hi ,
    You can follow the below steps.
    -> Goto Tcode SUIM
    -> Roles -> By authorization object
    -> object name : B_SMAN_WPL
    -> Execute
    This will give you the list of roles that are holding this object.
    Cheers!
    Veena BJ

  • Urgent plz...CHanging project/maintenance cycle phase

    i have implementation project and activated ChaRM for it.
    the task list and project cycle has been created scuccessfully.
    i created change request and assigned to that task list. when i set status "Development Complete" i need to import the TRs manually (SDMJ), but for that the phase of the cycle should be "DEVELOPMENT WITH RELEASE"
    i can change the task list phase by executing report /TMWFLOW/PHCNTRL_DB_UTILITY and the TR is imported to QAS successfully as well but the project cycle (SDDV) is still in :DEVELOPMENT W/O RELEASE" ???
    and when i try to change the phase (CRM_DNO_MONITOR -> SDDV -> Next phase) it gives error
    Message no. SOCM_ACTION_LOG 090
    Diagnosis
    An exception has been triggered in PPF action processing.
    System Response
    Action processing has been terminated. The status of the transaction is still incorrect.
    Procedure
    You cannot execute the action until the cause of the error has been removed.
    The error messages will be kept until the transaction is next checked for subsequent analysis.
    Procedure for System Administration
    If necessary, analyze other messages in the application log for the incorrect transaction. To analyze the termination, you can activate the breakpoints in the checkpoint group socm_exception.
    Additional Information:
    Exception CX_SOCM_CONDITION_VIOLATED occurred (program:
    CL_IM_CHM1_HF_CHECK_SET=======CP, include:
    CL_IM_CHM1_HF_CHECK_SET=======CM002, line: 327).
    Please Help

    Hasan Sidra wrote:
    thank you Prakhar for ur reply..
    >
    > Prakhar can you plz correct me..
    > when we activate charm, it creates a Task List and a Project cycle. Is it necessary that these two must be synchronized??
    > Means the status (i.e dev with release, test, go live) should be same or we can transport all the TRs only by maintaining Task List??
    yes ..task list and project cycle must be in sync
    > Because i can not change the status of SErvice DEsk Project any means but i can transport TRs by changing Task List status by /TMWFLOW/PHCNTRL_DB_UTILITY..
    >
    > Please help
    there is no service desk project...but a service desk transaction wihch in turn automatically updates the status of task list..this transaction and task list both are attached to corr changes of ur project
    generally the process is to change the status using service desk transaction not using that report that report is used in case of problem occured....therefore used for force closing the cycle.
    Hope it clarifies
    Regards
    Prakhar
    Edited by: Prakhar Saxena on Jan 9, 2012 11:00 AM

  • Maintenance Cycle Next Phase

    Hi,
    We are using chaRM 4.0, in tx SCMA,we can not able to move the Phase Transistion from 'Created' to 'Development without Release'. When we click on the next phase it is giving the below error . kindly help us.
    MsgType Message Class        Msg.no. Message text
    E       /TMWFLOW/PHCNTRL          54 Change transaction
                                         is incorrect
    E       /TMWFLOW/PHCNTRL          56 Phase transition
                                         from 'Created' 
                                         to 'Development
                                         without Release' is
                                          not possible
    Rgds,
    Jeni.

    Hello Jenifer,
    The problem usually is due to errors in the CRM transaction that represents the Maintenance Cycle. You can check it by calling transaction CRM_DNO_MONITOR and entering in the transaction type SDMN then process.
    You will get a list of all Maintenance cycles, select the proper one and double click.
    In the CRM Transaction in the upper/right side you should have a red button if you click it you can find out the reason for the error and correct it.
    Then the Phase change can be performed.
    Just a info for you, you can also perform the Phase Change throught the CRM transaction type SDMN, check the actions button and you will find it.
    Regards,
    Andreia

  • 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

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

  • Error "no link to maintenance cycle" happens after reset to previous phase

    Experts:
    I have a CHaRM project which has successfully transported a few changes into production.
    Then I use action "set to previous phase" several times  to set this project to "development without release".
    Then I create another change request by selecting the maintenance cycle of above project.
    After authorizing and saving above change request, a normal correction is created. However this normal correction
    has an error "no link to maintenance cycle" even its document flow shows the maintenance cycle mentioned above.
    The IBase is the same as previous selected and is verified to be right.
    Could you help decide what else is wrong?
    Thanks!

    Hi
    Please go to your project and PRESS REFRESH button in System landscape-Change Requests Tab
    this update the entries in database then now
    goto this table  /TMWFLOW/PROJMAP
    Check if the Project is still locked in table /TMWFLOW/PROJMAP: If an error is detected during the processing, then the project might be locked in this table.
    The refresh button will help you to get out of this problem and check also if there any other errors.
    Regards
    Prakhar

  • How to take a maintenance cycle out of phase 'Development without Release'?

    Gurus:
    I have a need to take a maintenance cycle out of phase 'Development without Release'.
    I have searched  OSS and SDN but failed to find any solution.
    Would you please help give some hint? 
    I appreciate your precious help.

    Hi,
    If you want to change the phase of you maintenance cycle, 2 solutions :
    Go in t-code solar_project_admin then choose you project. In the System Landscape --> Change Request Tab, then either :
    - click on the Show Tasklist button then click on the Phase button. You can change the phase from here.
    - click on the Show Service Desk transaction which is the cycle and change the phase executing an action.
    Hope it helps.
    Kind regards,
    Stéphane.
    PS : you can use tx /n/tmwflow/proj as well by choosing a project from the left pannel then clicking on the full screen button in the Scheduling tab.

  • SDMJ assignment to Maintenance Cycle is done in wrong phase

    Hello,
    Since Solution Manager SP15 we have the following problem.
    If you Approve the Normal Correction (SDMJ) the system does not ask you to which Maintenance Cycle you want to assign this NC (SDMJ). Before SP15 this used to work !
    Now ... after SP15 the question is asked only at the phase of setting the Normal Correction "Into Development. so one stage too late !
    Now, instead of the Change Manager, the Developer has to decide to which Maintenance Cycle a Normal Correction belongs to. This is unwanted behaviour.
    Are there other customers, having the same problem ?
    With kind regards,
    Rik Vriens
    +31.6.51937336

    Hi
    Please go to your project and PRESS REFRESH button in System landscape-Change Requests Tab
    this update the entries in database then now
    goto this table  /TMWFLOW/PROJMAP
    Check if the Project is still locked in table /TMWFLOW/PROJMAP: If an error is detected during the processing, then the project might be locked in this table.
    The refresh button will help you to get out of this problem and check also if there any other errors.
    Regards
    Prakhar

  • 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

  • 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

  • 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

  • One maintenance cycle?

    Some consultants are stating that it's better to have 1 maintenance cycle per system in solution manager and keep moving the phases back and forward (thus: after go-live the phase is being moved back to "development without release" and from there a new normal correction can start). But can somebody explain to me <b>why</b> this is better than closing a maintenance cycle at the end of a normal correction?
    Thanks in advance!

    Hi!
    I personally wouldn't recommend that but it sounds like an alternative method of handling parallel development for multiple release. At least in the project I'm in, there is a need to handle two or more simultaneous business releases with different go live dates.
    Idealistically there should be only one maintenance project and subsequently one maintenance cycle per system. A release (=maintenance cycle) is planned, executed and delivered. End of story. But in reality this is not the case. Planning and executing next cycle is usually started while the previous has not yet gone live and this is something that is hard to handle when you can have only one maintenance cycle at the time.
    I'm guessing that the idea of going back and forth with cycle phases is to use certain functionality of one phase but still keep the previous phase functionalities and enable parallel development.
    Having two or more maintenance projects and subsequently many maintenance cycles in order to enable parallel development is risky and it doesn't work well. Trust me I've tried. With more project than one in the same system you easily end up with inconsistencies etc.
    Hope this helps even a bit!
    BR
    Auli

  • 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 tasklist (Maintenance Cycle) activation problem

    Hi ,
    When activating a tasklist for maintenance cycle I get the following error message:
    Phase change from 'Created' to 'Development w/o Release' is not possible.
    Details: Change transiton is incorrect.
    Any ideas anyone on how to resolve this.
    Thanks

    Hey Sniper,
    Try this note: 93398: Status Change from Created to indevelopement is not possiible
    let me know whether it works.....
    Reward points or usefull answer....
    Regards,
    Anand....

Maybe you are looking for