Cycles in solution Manager 7.2

[rahul_yedapally]

Solution Manager 7.2 has Replaced Project with Maintance Cycle (continuous cycle ,Phase Cycle, Release Cycle)

continuous cycle can be Used for CHARM Process existing RFC & CD of Cycle

Release Cycle Can be used for new Releases & Same time Can we used for Upgrade Projects

Our Plan to Drive Upgrade Project with ALL Test cases , Solution Documentation, Transactions With help of Single Release Cycle or Do we need to go with PPM Projects

Cheers,

Rahul Yedapally

[former_member694235]

hello sir ,

can you please tell me how to close a solman phase cycle which is in 'being completed status'.

[rahul_yedapally]

Dear Pooja,

Check Cycle is associated with sap0 or sap1 variant ? if sap0 variants exists then project has migrated from 7.1 to 7.2

Thanks,

Rahul Yedapally

[pooja_rajurkar]

Hello Prakhar,

We are working on Solman 7.2 Upgrade project. We have created maintenance cycle and respective branches. However in ChaRM, while releasing RFC for development I am getting error as 'Request for change has no cycle.'

Could you please guide on the same.

Thanks

Pooja R.

[rahul_yedapally]

Dear Prakhar,

it-approved-via-business.pngit-req-via-new-business-req.pngppm-it-task.pngThanks for the clarification . How do we Track New Business Requirements via PPM? I agree once Business Requirements Approved only IT Requirements will be created? But same time VIA PPM we have an option for IT Requirements when we Release task IT-Requirements will be automatically created & Recorded as Transaction In PPM project further Reference? Attached Document for Reference

Thanks,

Rahul Yedapally

[prakhar_saxena]

Hi Rahul Yedapally

this is not something new and ITPPM was also available in solman 7.1. So transaction getting created out of ITPPM is nothing new but it was ChaRM SMCR earlier.

However it is all as per your requirement you need to setup the system accordingly.

It is all good but you need to understand the REAL customer requirement whether they would like to go for which and then how can address it.

Thanks

Prakhar

[rahul_yedapally]

Dear Prakhar,

I think your assumption is wrong let me put in detail even we have Cycles in 7.1

1) Solution Manager 7.1 has Tcodes: Solar_project_Admin, Solar01, Solar02 where its called as Project creation & All Documentation which can be Stored Via Documentation tab & Test Scripts , Transaction, Process was Defined

For CHARM We Were using Projects if you old RFC (Request for Change) SM_CRM Screen there was name called Project Tab where assignment was done based on list available in Solar_project_Admin

2)Now when we talk about Cycles We have an additional Functionality of Release Cycle from 7.2 but I mean to say Continual and Phase cycle where used in place of Project TAB Assignment in 7.1 while creating new RFC from SM_CRM

Yes I am aware about Release Management Major and Minor Release for new Planned upcoming Releases

Challenges in Current phase

1)Integrated PPM With CHARM & Requirement Management

Created new PPM Project in 7.2 & Assignment of Phases with Resource allocation budget planned go live release dates as project portfolio

New Request for change Can directly create PPM task associated with Cycle

New IT Requirements can be Directly created task from PPM Project when Phase status while be on Released

All this Transaction RFC & IT Requirements can be linked to PPM Projects for Reference Tab TRANSACTION

The Challenges which we have when User Creates new Requirements from Solman_workcenter- Requirement Management Fiori App this Request will go for Approval & Once approve IT Requirements will be automatically created with new Reference id linked for Requirements Transaction id

The Transaction id for IT Requirement which was created via New Requirements Fiori Apps is not linked with PPM Projects Task id? Both IT Requirement Transaction id has different when we Compare with PPM Task & Requirements via FIORI App

Hope its clear now

Thanks,

Rahul Yedapally

[prakhar_saxena]

Hi Rahul Yedapally

if your problem is below

The Transaction id for IT Requirement which was created via New Requirements Fiori Apps is not linked with PPM Projects Task id? Both IT Requirement Transaction id has different when we Compare with PPM Task & Requirements via FIORI App

this is correct behavior because users create Business Requirement(uniq ID) via the Requirement Management app and not IT requirement...IT requirement is created later as per workflow from IT requirement.

Further, it is not mandatory to link everything like you mentioned above i.e. Project with Soldoc with ChaRM with Release Management. My comments was to help to first understand the need in more detail and then proceed accordingly.

I hope above helps if not please clearly mention the error or screenshot where you struck.

Thanks

Prakhar

[prakhar_saxena]

Hello Rahul Yedapally

I think you need to read more...:)

Solman 7.1 Projects are not replaced by 3 cycles in solman 7.2 instead just 2 cycles i.e. Continual and Phase cycle.

Continual means no Phases and you can use for Normal /Urgent /admin/standard etc. type of changes where there is no phase restriction is required...read below

https://help.sap.com/viewer/8b923a2175be4939816f0981b73856c7/7.2.06/en-US/669d8815a46e4273be05e41fbb...

Phase cycle is obviously phased approach like earlier and goes step by step...read below.

https://help.sap.com/viewer/8b923a2175be4939816f0981b73856c7/7.2.06/en-US/19e72646492f4824be967962d2...

Release Cycles are a different and new functionality which wasn't there in 7.1 ...it is RELEASE management which is a separate functionality itself.

https://help.sap.com/viewer/8b923a2175be4939816f0981b73856c7/7.2.06/en-US/10dad8533eb2492ae10000000a...

Hence read the documentation to understand them in more detail and then only proceed accordingly as you need to identify and understand in too much of detail beforehand. 🙂

Hope it helps

Thanks

Prakhar