Change Request Management during Implementation

[Former Member]

Hi,

Would request suggestions regarding Change Request Management usage during Implentation.

We are using Solman 4.0 during implementation of ECC 6.0.

Thanks & Regards

Mrutyunjay

[Former Member]

Can you be more specific about your concerns? Overall there is documentation that supports Solution Manager use of ChaRM during Implementation to include how to use it. A common issue with using Solution is that it may not work well with home-grown processes and procedures. Additionally there are development pratices that do not work well during implementation in conjunction with ChaRM but these are usually overcome with the integration of Solution Manager - Project Management.

Thanks and please be specific about what your concerns are - the more that we know, the more we can answer your questions and get a proper match for your implementation.

[Former Member]

Hi David,

Very much thankful for your response.

Would request you to please guide towards the documentation which explains usage of Change request Management during implementation.

I have came across documents where in it was mentioned that in a project life cycle Change request management comes during optimization / Maintenance.

During implementation the blue print carries justification for all the customizations consultants do . Following that blueprint only customization is done. And during customization there is no integrated tool in solution manager to raise change requests.

Would appreciate if any experiences are shared.

Thanks & Regards

Mrutyunjay

[Former Member]

Solution Manager follow a SDLC that does not manage change but issues / risks during implimentation (PMBOK) Change management starts when system goes into production. Why would you need change management during implimentation?

[Former Member]

Hi,

Change Management is usually involved from Dev to Production all the way. If you setup Change Request Management you have to assign Dev, Qas and PRD.

Change Request Management requires to have Service Desk implemented as well and both implementations are large project implementations in Solman.

One options is to use CTS+ (CTS Enhanced) and Service Desk. You would have to define the processes how you use Service Desk in relation to Change Management as 'methology'. CTS+ gives you traceability not only in regards to ABAP transports as well with EP and PI for example.

If you want to implement Change Request Management, you should consider to use one sandbox with 3 clients presenting each system DEV, QAS and PRD and ideally use a DEV Solution Manager. Change Request Management may not suit everyone's needs. It involves a lot in regards to document tasks.

The SAP Press book SAP Solution Manager by Marc O. Schäfer and Matthias Melich is a good book to understand different functionalities, but it won't explain to you how to implement or use them from transaction to transaction.

Regards,

Markus

[Former Member]

Very much thankful for the responses and your time.

We are not using Change request management during implementation.

Thanks & Regards

Mrutyunjay

[Former Member]

It works fine. The change is based on ITIL change management. Have a look at the roadmaps for implimentation you can have most of your docs in the project even change docs

[Former Member]

During implementation consultants will have to generate lot transport requests and for each of them would they be raising a change request.

Is this is the process that is followed ?

I have used Change Request Management during support but during implementation has any one used it.

Please suggest.

[Former Member]

I am under opine that Change Request management will come into picture during support only.

During implementation first we align the business and during support we manage changes to it through ChaRM.

Would appreciate any suggestions regarding.

Thanks & Regards

Mrutyunjay