In SAP Solution Manager 7.1 any changes in the logical components of a project where Charm is already activated would require few manual steps also would cause some outage of ChaRM for the End-Users.
If you would like to add/remove Logical Component to project landscape or to manually adjust systems (change systems and roles) included in exiting Logical Component for active project cycle after the task list generation, you would most likely:
• Close the current project cycle
• Add/remove Logical Component
• Generate a new project cycle
Any change in the TMS configuration, in the transport routes for example, will be handling in the same way.
Now in SAP Solution Manager 7.2, this process has been enhanced to make it less painful and reduced the amount of work involved for landscape changes in ChaRM.
I will show you how adding, removing or changing system(s) in the change landscape looks like in 7.2:
First thing you need maintain you logical components, logical groups and branches to reflect the new changes under “Solution Administration” and possible also some changes on LMDB dependent on what you have changed:
On the “Solution Administration” you can see all the Solutions, Branches, Logical Groups e Logical components part of your change landscapes:
Now we need to make sure the existing cycle(s) will have the new changes reflected, Go To> Change Management on the Fiori launch pad and click on “Administration Cockpit”
The Administration cockpit in Solution Manager 7.2 is a unified interface to maintain all different tools and process in ChaRM.
Select the type of the cycle we want to make changes to:
• Continual Cycle
• Phase Cycle
• Release Cycle
Search for the cycle(s) that have been affected by the changes from the change landscape
Open the cycle
With the Cycle Document open:
-> Click on Edit
-> Go To -> More -> Redefine Landscape
By doing this your cycle will get the current change landscape configuration from the Solution Administration and adjust the change landscape in the cycle. There is no need to close and open cycles anymore for landscape changes; with this process we reduce drastically the outage time for ChaRM maintenances.
The overall ChaRM maintenance in Solution manager 7.2 has been improved to allow more flexibility and reduce effort on day-to-day changes that can occur in the SAP landscape. If you are looking for more information, feel free to reach out to us for a quick demo.
William Perez – Sr. ALM Consultant – CoreALM
