I know it’s been a while I am away from blogging but the credit goes to SAP Solution Manager 7.2 team who has really built the new version so well.
One of the most fascinating tool which is now introduced in Solution Manager 7.2 version of Change Request Management or ChaRM is Admin Cockpit.
It is really a great tool with lot of ease of flexibility of administrators etc. I remember in old Solution Manager 7.1 Change Request Management(ChaRM) people use to complain a lot that we don’t have flexibility, things are slow, transparency is not visible, several transaction codes like SCMA,/tmwflow/reportingn etc.
Now it is very simple in Solution Manager 7.2, just goto Fiori launchpad(or transaction code sm_workcenter) and then click on Admin Cockpit as shown below.
Further on clicking the Admin cockpit tile, it open another link where it provides us plenty of good features like below
Thus, all the old Solution Manager 7.1 SCMA features are available here under Task List where I can access them. i.e
- Continual Cycles
- Phase Cycles
- Release Cycles
- Urgent Changes
But there is another one which is one of my favorites because almost this was a big pain during managed system upgrade when import jobs struck due to missing or old tracking transport information in Solution Manager ChaRM.
As solution to above issues, we do have now Landscape Overview where there is a tab for Reread Transport data into buffer which allows to fetch the tracking information for any cycle from the relevant date.
Another good option which provides a very good transparency in terms of figuring out where is my transport is below one under Transport Analysis.
I just can’t forget how people use to chase to know whereabouts of a their own transport in ChaRM or in the end checking se01 logs in managed ERP systems etc.
Last but the least, don’t forget that it is now not needed to schedule the import jobs from se38 report like Solution Manager 7.1 rather we have the options provided under Task list only where we can schedule import jobs as per required frequency.
Infact, another one of the best options here to select the ignore component version option in import jobs which is really helpful during period of small patching etc done during any managed landscape
I like this option too much because for bigger customers where we have whole bunch of changes goes on daily basis we don’t want to transport job struck due to mismatch of component version, even at a time when we know that this will happen.
Thus, this option provides a whole bunch of easiness/flexibility, when we know that mismatch in the component version is not going to affect usual transport or temporary only in our managed system landscape.
Yes, they are lot so I will not go through each of them but ask you explore or enjoy the new features of it.
I wish everyone Good Luck and share your feedback in using this new tool in your live projects or some experiences as I have shared above in real life situation’s.