Change Request Management in Implementation projects or not?

[Former Member]

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

[Former Member · Accepted solution]

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

[prakhar_saxena]

Hi

Technically you can;'t create any Urg corr in implementation project but you can do so in maintenance project.

so decide as per ur requirement and scenario rest is same ;normal cor exists in both so it is fine in that case.

Regards

Prakhar