Skip to Content
avatar image

Back to the Future with SolMan

About 3 years ago, I implemented SolMan 7.1. For this, I had to install SPS04, which was proclaimed more or less unusable, and therefore I had to upgrade it right away to SPS11 to make it work, i.e. to even run the SOLMAN_ADMIN transaction successfully.

Now, I seem to be in a similar situation again. With the End of Mainstream Maintenance: 31.12.2017 for SolMan 7.1, I am installing SolMan 7.2 to be prepared. I tried upgrading my 7.1 installation and splitting the instances as well, but that is another story.

The SolMan 7.2 installer is for SR1 which going by some recommendations might potentially not be the best vintage and therefore needs upgrading to SPS05 before even trying to run the SOLMAN_ADMIN transaction successfully. However this time, I need to upgrade both the ABAP and Java instances individually and make Maintenance Planner convince that I know what I am doing.

I understand why this is needed for customers theat use SolMan heavily with all its features. However, In my mind, I could imagine a lightweight Solution Manager that just connects my SAP systems to Maintenance Planner and further services like the upcoming S/4HANA Readiness Check.

* Please Login or Register to Comment on or Follow discussions.


  • Jun 01, 2017 at 04:20 AM

    Good topic

    question for you...

    Do you need EWA?

    • Jun 01, 2017 at 06:22 AM

      Hello Yogesh,

      Might you imply that there could be a lighter weight SAP Solution Manager deployment option if I did not need EarlyWatch Alerts? In this case I might trade the one for the other ;)

      Best regards


      • Jun 01, 2017 at 02:30 PM

        I think you don't need solution manager at all

        SAP note mention below will solve your question..

        2287046 - How to Generate the System Info XML for Maintenance Planner upload


  • Add comment
    10|10000 characters needed characters exceeded