One of the biggest projects going on in the SAP admin space right now is the upgrade, or fresh install, of SAP Solution Manager 7.1. Of course, it's being covered extensively here at Admin 2012 in Las Vegas.
In a session this morning on the improved ChaRM features in 7.1, Enowa Consulting's Nathan Williams polled the audience on the solution's adoption -- roughly 50-60% said they had Solution Manager installed but weren't really using it. "That number was 99% a few years ago," said Williams.
Part of the increased adoption is a result of the communication of the improved features of 7.1. A new Web UI, an improved CRM infrastructure, and a better integration of application lifecycle management (ALM) and IT service management (ITSM) have driven this adoption.
But it's not necessarily going to be easy. "There is no automated migration path from 7.0 to 7.1," said Williams. As a result, you need to undertake a phased approach in phasing out old transaction types and converting to new ones. (Tip: Many of the old transaction types were SDxx and are now merely SMxx. Of course, some are all-new as well.)
It's possible to work with some pieces of Solution Manager on 7.0 and some on 7.1, but it isn't a best practice to keep them both running for long. As Williams noted, SAP has only pledged support for 7.0 until the end of 2013 -- so you can't count on having that technology around for years and years. So it's important that you plan for the change now. Craft a strategy, plan out what needs to happen in each phase, and execute it before SAP's support on 7.0 lapses.
If you weren't able to make it to Las Vegas for the conference, you can follow the action using the Twitte
r hashtags #ADMIN2012 and #BI2012 to see what people are talking about. Want to ask Nathan something about 7.1? Check him out at @Solmanhattan.