ChaRM for Rollout

Question

Hi All,
We are in process of implementing ChaRM. Currently we have a 5 system landscape for Rollout and ongoing production. Also currently we have multiple Rollouts going on and we are using SolMan for all config and other activities.
The current trasnport movement path is Rollout dev --> Rollout QA --> Support dev --> support QA --> Production.
How can I replicate this transport movement through ChaRM. Also many rollout will be in progress when ChaRM will go live, how to enable ChaRM in between the implementation project.
Also in current Rollout and Support environment we have multiple client in development i.e. for configuration and development separately.
Regards,
Smita

Answer 1

Hi Kumar,
Basically the main feature / funtionality of CHaRM is for Approval Process like creation of any change (like config or workbench) and then movement of transports from one system to another system. Dev --> QAS -->PROD.
these all depends up on the requirement you work.As per my understanding for your rollout project you are doing all the ECC configuration using the Solution Manager.
They are two ways of movement of trasports:
1.Moving the Transport Requests from one system to another system out side solution manager.
2.Moving the Transport Requests from one system to other system with in the solution manager.
If you are following the 2.option, In this case you have to do the following:
1.Create a Maintenance Project
2.Create a Maintenance Cycle
before doing this activity, the Basis people has to set the TMS which plays a vital role.
Please check the rest with your Basis People.
Regards,
Sateesh.Kandula