cancel
Showing results for 
Search instead for 
Did you mean: 

ChaRM : Grouping of Change Requests

Former Member
0 Kudos

Hello All,

In a scenerio wherein 2 Transports( 1 WB and 1 Cust) need to be created for some change in functionality. Both these Transports are realted to each other functionally. For example, maybe a Report needs to be created along with a small config change. So 2 TRS are needed.

Now in ChaRM, since 1 Change Request will support 1 TR (either WB or Cust) they will have to create 2 Change Requests.

The first Change Request is created for the WB TR. Then hundreds of other Change Requets for other changes are created. Now, the Change Request for the Cust TR s created.

In this case one has to manually search the CR for WB for reference.

Is there anyway that these 2 Change Requests(or even more for that matter) can be grouped together? So that they dont have to manualy note down the No. of each of the Change Request for reference.

Thanks!

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

you can have both customizing and workbench transport for one change request, or, ot be more precise, for the connected change document.

If you use normal correction, you can even have multiple transport requests for customizing and workbench each, while in urgend correction you can have one open request for workbench and one for customizing.

Regards,

Christoph

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi

i m nt sure about grouping the crs

can you check the scenario and solution stated in the thread

[|]

jansi

Former Member
0 Kudos

Thanks. Looks like grouping of Urg CRs not possible.

1. In which phases of Maintainence Cycle can Urg Corrections move to Quality and then to Prod? Is it possible in Developmnt wo Release

2. All Normal Corrections can move to Quality together only in phase Test and then to Prod together only in phase go Live? What is the action Test Import for? I didnot understand from the link above.

Edited by: LT Consultant LT Consultant on Sep 22, 2010 2:53 PM