Skip to Content

SAP Solution Manager 7.2: Simplified Upgrade and Migration to SAP HANA

This blog post introduces a new, simplified upgrade and migration procedure for customers upgrading from SAP Solution Manager 7.1 to SAP Solution Manager 7.2.

Details on SAP Solution Manager 7.2 can be found here.

If you want to upgrade your SAP Solution Manager 7.1 system running on any database to SAP Solution Manager 7.2, you have to consider that SAP Solution Manager 7.2 is based on SAP NetWeaver 7.4.
There, no dual-stack systems are supported any longer.

As a consequence, your existing SAP Solution Manager system has to be split as part of the procedure – that is, the Java part gets extracted into a standalone system, next to the persistent ABAP system.

This is also a good opportunity to migrate your database to SAP HANA or SAP ASE as part of the upgrade project, since all customers with a valid SAP maintenance agreement can use SAP HANA or SAP ASE as database for SAP Solution Manager without additional licensing costs.

The standard procedure, which is documented in SAP Note 2227300, comprises the following basic steps to upgrade your SAP Solution Manager 7.1 system to SAP Solution Manager 7.2 and migrate the database to SAP HANA or SAP ASE:


Current Procedure.png


  1. Upgrade your SAP Solution Manager system to version 7.2
    with the Software Update Manager (SUM).
  2. Perform a Dual-Stack Split with the Software Provisioning Manager (SWPM)
  3. Migrate your AS ABAP system to SAP HANA or SAP ASE by performing a heterogeneous system copy with the SWPM.
  4. Migrate your AS Java system to SAP HANA or SAP ASE by performing a heterogeneous system copy with the SWPM.
  5. Configure your new SAP Solution Manager 7.2 system using SOLMAN_SETUP

With the standard procedure, you also have the option to use SAP Solution Manager 7.2 before the migration to SAP HANA or SAP ASE (for example, to have a separation of concerns or to get two separate downtime windows/an interim phase of production usage).
If you want to do this, you can perform the configuration (using SOLMAN_SETUP) after the
Dual-Stack Split procedure, as depicted below.


Interim Production Use.png


However, if you already decided to migrate to SAP HANA or SAP ASE with your new SAP Solution Manager 7.2 and if you do not need the option to use SAP Solution Manager 7.2 before the migration step, there is another technical path, which might be interesting for you:
A simplified upgrade and migration procedure incorporating the Database Migration Option of the SUM and the combined split and migration in SWPM.


Simplified Procedure.png


The graphic shows an overview of this simplified procedure, which consists of the following basic steps:

1. Upgrade your SAP Solution Manager system to version 7.2 and migrate your AS ABAP system to SAP HANA or SAP ASE in one step with the Software Update Manager (SUM).




Technically, this step is a dual stack upgrade with Database Migration Option (DMO), which efficiently combines system update, Unicode conversion and database migration.
If you want to find out more about DMO, the blog post Database Migration Option (DMO) of SUM – Introduction is a good starting point.

The newly introduced Dual Stack UI of the SUM guides you through the upgrade steps of the ABAP and Java parts of the dual stack, taking care of the synchronization between the ABAP upgrade and the Java upgrade.


DMO Dialog.png


The DMO option migrates the ABAP part of the system to SAP HANA or SAP ASE as part of the upgrade, which makes a heterogeneous system copy of the ABAP stack superfluous.

This step has the potential to reduce the business downtime, since the old SAP Solution Manager 7.1 system can be used in parallel while the SUM is already upgrading and preparing the migration of the system.
Parts of the migration can be performed during the uptime processing of the SUM.
The downtime of the SAP Solution Manager system and the switch of the connected agents in the maintenance mode can be delayed until the technical downtime of the ABAP part starts in the SUM.
Additionally, there are several ways to optimize the DMO migration performance, as described in the blog post Optimizing DMO Performance.

Watch the demo video:

The result of the dual-stack upgrade with DMO is an SAP Solution Manager 7.2 dual-stack system with the APAB stack already running on SAP HANA or SAP ASE and the Java part still running on the old database.

Afterwards, a Dual-Stack Split is required, since dual-stack systems are not supported anymore for systems based on SAP NetWeaver 7.4. The Dual-Stack Split will separate the ABAP stack and the Java stack into two SAP Systems.


2. Perform a Dual-Stack Split and migrate your AS Java system to SAP HANA or SAP ASE with the Software Provisioning Manager (SWPM).




The database migration can be done as integral part of the Dual-Stack Split.
The outcome is equivalent to the classic way, where a heterogeneous system copy procedure has to be performed after splitting the dual-stack system into a separate ABAP system and a Java system.
The main benefit here is that there are less steps to perform, which reduces the complexity and the possibility of user errors during the procedure:


a) Export the Java stack from your source database.

Dual-Stack Split 1-a.png

Watch the demo video:

b) Install a new Java system on the target database using the export file you just created.

Dual-Stack Split 2-b.png

Watch the demo video:

c) Remove the Java stack from the old dual-stack system on the source database.

Dual-Stack Split 1-c.png


The removal of the Java stack is part of the follow-up activities, which are described in the
Dual-Stack Split Guide, which is available on -> System Provisioning -> Split Option.
In chapter 6.1 of this guide, you can also find a checklist for these activities.

Watch the demo video:


3. Configure your new SAP Solution Manager 7.2 system using SOLMAN_SETUP.

Finally, the new SAP Solution Manager 7.2 system needs to be configured and some post steps have to be performed, which are described in SAP Note 2227300.
This is common with both procedures, for which also variants are possible.


Migration Paths

The following matrix gives an overview of the benefits and considerations of the migration paths described above.


  Upgrade to SAP Solution Manager 7.2 and migration to SAP HANA or SAP ASE

Migration path


Value proposition


Standard procedure

  • First upgrade your dual-stack system, then
  • split the ABAP stack and the Java stack and
  • optionally migrate one or both stacks to SAP HANA or SAP ASE.
  • Interim production use is possible after the Dual-Stack Split
  • Longer downtime and more steps than other procedure

Simplified procedure

  • First upgrade and migrate the ABAP stack of your dual-stack system with DMO of SUM and then
  • split and migrate the Java stack to SAP HANA or SAP ASE.
  • Reduced complexity of the procedure
  • Reduced downtime for migration
  • No interim production use possible, since the split and the migration of the Java stack is integrated into one step.
  • After the upgrade with DMO of SUM, the ABAP part is already migrated.



The simplified procedure is recommended by SAP, if no interim production use is necessary, since it comprises a simpler usage and has the potential to minimize the business downtime.


The simplified procedure is general available for all customers as of SL Toolset 1.0 SPS 19.
Download links and related information about SUM 1.0 and SWPM 1.0 can be found here:

You must be Logged on to comment or reply to a post.
  • Hi,

    We are currently running on MS SQL only. SAP Solution Manager 7.2 has a "free" SAP HANA license. If i look at the PAM i see only the ABAP stack. Means that the HANA license is related to ABAP stack only?

    And as far as i know if you have a HANA license for ERP, you are allowed to use ASE for free.

    So can we use ABAP on HANA and JAVA on ASE for free with 7.2?



  • Hello Stefan,

    Nice blog on solman. SAP is generally recommending to implement fresh 7.2 on HANA rather migrating due to big effort involved of upgrade/split/migrate etc. particularly on HANA. Correct me here?

    Besides we'll get solman response time improvement on HANA overall but which particular scenarios are focused particularly running solman on HANA as per SAP?

    Best Regards,

    Amit Lal

  • Hello Amit,

    thank you for your comment.

    I am not aware of a general recommendation to implement SAP Solution Manager 7.2 fresh on HANA instead of upgrading and migrating. Where did you find this information?

    The SAP Solution Manager 7.2 upgrade guides, which can be found at describe the standard upgrade and migration procedure and with the simplified procedure it is even less effort.

    You may want to consider a new installation if

    • Your SAP Solution Manager system is outdated, e.g. 7.0 EhP1
    • Main purpose is generating keys and downloading Support Packages
    • None of the data contained needs to be preserved

    You can upgrade to SAP Solution Manager 7.2 if

    Regarding your second question, please have a look at

    Get ready fo SAP Solution Manager 7.2 - Lifetime Support by SAP

    There you will find the video "SAP Solution Manager 7.2 is perfect for SAP S/4 HANA" as well as the SAP Solution Manager 7.2 roadmap.

    Best regards,


    • Hello Stefan,

      Thanks for your wonderful inputs.

      This should help as high level technical deciding factors.

      One last point, There is no dedicated quicksizing program/link available for Solman 7.2 on HANA, though I can see its available for solman 7.1 on HANA

      I did checked ==> Sizing Decision Tree but nothing is specifically mention for Solman 7.2 (From Master guide of 7.2)

      I did checked Master guide suggesting 'cases 0-7' for appropriate sizing estimates on section 4.1.9 and also it recommending to use same

      SAP Note 1872170 - Suite on HANA - S/4 sizing report for Solman 7.2 sizing further.

      Please provide some input on this topic as well.

      Thank you again,

      Amit Lal

      • Hi Amit,

        According to my knowledge, the SAP HANA Memory Sizing report for SAP S/4HANA (attached to SAP Note 1872170) is valid as first estimation for SAP Solution Manager as well.

        Best regards,



      Hi Stefan,


      Thanks  for this useful blog.

      Regarding ST-TST - it's not a problem to upgrade with St-STS component installed in SM7.1 if you upgrade to SM 7.2 SP03 and higher.

      Here is a note that might be helpful for those who are checking how St-TST component behaves during SM7.2 ugrade:

      Title: Additional info about the component ST-TST and ST-OST for upgrade from Solution Manager 7.1 to 7.2 release

      Kind Regards,


  • Hi Stefan,

    thank you for an excellent blog.

    I am interested in the simplified upgrade and dmo migration strategy.

    We have SolMan 7.1 and we are planning to go to 7.2 and possibly with HANA (MDC with ABAP and Java db's in the same HANA system).

    Old Skool we assumed the path would be...

    1) Upgrade Dual-Stack SolMan 7.1 ABAP+Java to SolMan 7.2

    eg mini project 3 months with testing etc

    2) Dual Stack Split

    eg mini project 3 months with testing etc

    3) Migrate ABAP and Java db's to HANA (MDC Tenants) using classical SWPM (or ABAP stack could be done with DMO and only upgrade the ST/PI STA/PI)

    3 months with testing etc (we already have MDC and are familiar and content with migrating and operating it)

    Optimistically, this is three projects, with optimistic durations, probably it would end up being 12months work, divided into 3 pieces with for example 3 x the testing effort

    How to make it shorter ?

    We wondered, if this would be possible:

    1) Dual Stack Split ABAP & Java

    2) Upgrade and Migrate to HANA in one step

    ABAP using DMO

    Java do an SP Upgrade and then SWPM Tools to migrate to HANA

    This would mean two Projects and only two sets of testing, step 2 would have a longer downtime, but the whole would be completed in a shorted period.

    But alas, this is not possible because as OSS Note 1797362 - Dual-Stack Split for Systems Based on SAP NetWeaver, says, the procedure is not supported for SolMan 7.0 and 7.1 🙁

    So, question, you have proposed an approach:

    1) Using the SUM tool's new Dual-Stack functionality, do a Dual-Stack Upgrade and HANA DMO in one go/run

    If I understand this, in one step we will:

    Upgrade and DMO the ABAP Stack onto HANA db

    Upgrade the Java stack on the existing AnyDB

    The system is still DualStack !  I am curious/interested how the Dual Stack system with each Stack on a different db can function, obviously, hopefully even in the Dual Stack the ABAP Stack has it's own unique DB integration/connectivity and the Java Stack has it's own unique DB integration/connectivity

    The result as you said is, ABAP is on HANA and Java is on AnyDB, both ABAP and Java are on SolMan 7.2 and it is still a Dual Stack

    2) Dual Stack Split

    Ok, in this step "we" would Dual-Stack Split the Java stack into it's own SID - and for us, migrate the DB to a HANA Tenant.

    Ok this is all clear.


    In your example,

    are Step #1 Upgrade ABAP and DMO to HANA, Upgrade Java


    Step #2 Dual Stack Split

    all completed during the same downtime as one big project,


    would we do Step #1 Upgrade and DMO ABAP onto HANA , Java upgraded and remaining on AnyDB, and then run Productively with SolMan 7.2 ABAP on HANA and Java on AnyDB

    and then later, do a new Project to do the Dual Stack Split ?

    I mean, in between the Upgrade+DMO and the Dual Stack Split can we run productively ?

    If we could run productively after Step #1, then we could "leave" the dual stack split until we are really forced to, eg, the next upgrade cycle.

    And this way, we get SolMan onto 7.2 with HANA in one step 🙂

    Long question, if it's not clear, let me know.

    Best regards,


      • Hi Andy,

        yes this is correct: You cannot run productively before the Split.

        A Dual-Stack Split is required, since dual-stack systems are not supported anymore for systems based on SAP NetWeaver 7.4

        However, you could run productively after the split and before the migration(s) in the standard procedure.

        In the simplified procedure the split-migration is the last step anyhow.

        So you can always run productively after the split.

        Best regards,


    • Hi Andy,

      using DMO, we can upgrade+migrate to 7.2 directly on HANA, and perform the dual stack split, and put the java schema under the same abap tenant.. something like mcod in a tenent?

  • Hi Stefan,

    In SAP HANA I will be able to perform the same process automation (SAP GUI Scripting API) that I already realize with SAP GUI for Windows?

    I ask because I develop applications in parallel (JavaScript, VBScript, VBA) for SAP applications.

    And I believe that the company I work in the near future plans to move some business modules for SAP HANA.

    Thank you.

    Sincerely, Jerônimo.

  • Hello Stefan,

    If we decide to discard the JAVA, what will be the impact directly or indirectly to our Solman 7.2? It is mandatory to have JAVA in Solman 7.2?



  • Hi Stefan,

    Informative post.

    I saw the 7.2 upgrade using DMO - (Page 11) it refer to this SCN.

    We have some queries for Solman 7.2 upgrade:

    We are planning to upgrade our Solution Manager 7.1 system and need information about the best practices and recommendations on the target landscape setup.

    Source:SAP Solution Manager 7.1 SP12



    Standard Installation

    Target:SAP Solution Manager 7.2 SP03

    Suse Linux SLES12


    Distributed Installation

    Please suggest best practices for the below:

    1) Is it recommended to upgrade to 7.2 before we split the ABAP & Java stacks (or) split the stack first before starting upgrade to 7.2?

    2) When we split the stacks for target, is it recommended to have both SAPSR3 & SAPSR3DB database schemas in one database or should each have their own dedicated database on target servers?

    3) When we split the stacks for target, is it recommended to have both ABAP & Java Stacks running on the same host with two different Instances/SIDs or should they run as two different instances on two different hosts on the target.

    We need Some recommendations on these for us to better plan the upgrade.



    • Hi Karthik,

      a lot of what you are asking is answered in this OSS Note:

      2227300 - Further Upgrade Information for SAP Solution Manager 7.2

      and the pdf attached to it.

      As the Note states:

      1) Upgrade is executed before the split

      2) SAP recommends to have both DB Schemas in one DB

      3) SAP recommends to have both JAVA and ABAP on the same host - personally I won't be doing that when we upgrade to 7.2

      Best regards,


  • Hello,

    We have completed the upgrade of Solution Manager with DMO, and are now attempting to split off the Java stack and migrate it to HANA. We could extract the Java stack fine, but get an error when we try to install the new Java system on HANA:

    Also, if you take a look at this presentation and go to slide 8, it states that when performing the Dual-stack split, the OS and DB stay the same. This appears to directly contradict what you have stated in this blog.

    Please advise, Thank you.

    • Hello Jason,

      You need to select „Perform an OS / DB migration during the dual-stack split“ during the DSS Export of the Java stack:

      If you did not do this, please repeat the DSS Export of the Java stack with this option.


      • Thanks Stefan, we got it working now.

        It’s important to note that this option is only available in the newest SWPM version (18) which was just released last week. If you attempt to export the Java stack with an older version (we used 17) you will not encounter this screen. Without selecting this option the dual-stack split will fail.

        Seeing as how this is critically important, it is probably worth mentioning this in SAP NOTE 2227300 or this blog.

        Kind regards,


  • Hello Stefan, Will you let me know who created the videos you have included here? I would like to use these for social media content. Thank you, Lisa Arroyo

  • Hello Stefan,

    Please can you share more information on Generally availability of SUM tool with Simplified Approach for Upgrade/Migration to SAP Solution Manager 7.2

    Many thanks,

    • Hello Jitendra,

      we are planning to make this procedure general available with SUM SP19 (Note: This information is subject to change).


        • Hello Mario,

          the procedure has been added to SUM SP19, which is expected to be released mid-February.

          All customers will then be able to use the simplified approach with DMO without the need to register or to set additional parameters.

          Best regards,

      • Hi Stefan,

        SUM SP19 is available now, I think you can adjust this blog now 🙂



        BR, Eric Li

  • We have all our portal on NW 750 so I assume it should also be possible to upgrade solman 7.20 to NW 750 as well.

    How about Upgrading this NW 7.4 to NW 7.5 for solman 7.2?Does it work like any other upgrade or there has to be some upgrade path for this ?


  • Hi,

    Are below upgrade options (to 7.2) supported for SOLMAN 7.1 (source release) running on ASE (as MCOD):

    • using DMO to move ABAP stack to HANA, while JAVA remains on ASE
    • using SUM to upgrade ABAP+JAVA to 7.2 (this will still be MCOD on ASE!) and then immediately split JAVA stack (move DB). Both ABAP and JAVA should stay on ASE.

    thanks & Regards,

    Ajay Patil


  • Hello Stefan! This is a wonderful post!!

    Is the Simplified procedure still valid for upgrade + migration to SAP Cloud?

    I'll appreciate a lot your input.



  • Hi Stefan

    We have some critical Scenario here :

    We have Our Primary Application server & Additional application server on SUSE Linux Operating system , Our DB oracle Instance ,ASCS,SCS and ERS Instances are on AIX Platform .

    Can I use the Dual stack split tool for my Heterogeneous system .and Can you please give me path for the sap best practices in my scenario ,we are not going to migrate HANA db we need to use same Oracle DB.




  • Hello stephan ,

    thanks for the post , we have charm in our Solman, can you please point to any document where I can understand what extra steps are required when I move to HANA and also split the JAVA stack ?



  • Hello Stefan,

    Nice blog , eagerly waiting to explore new approach.

    Is it possible to use system move option with DMO for dual stack scenario ?







    I am in the process of preparing solution manager upgrade from 7.1 to 7.2

    As per the upgrade guide

    In SAP Solution Manager Configuration (transaction SOLMAN_SETUP) check the status of the scenarios System Preparation, Basic Configuration and Managed System Configuration. Perform outstanding activities, if needed.

    We are starting with the Sandbox system, my question is " is it mandatory to complete System Preparation, Basic Configuration and Managed System Configuration.before we start with the solman 7.2 upgrade ?
    ​As this is a sandbox system and no one is using it we are thinking to complete the upgrade and then do the System Preparation, Basic Configuration and Managed System Configuration along with the 7.2 post upgrade activities.
















  • Thanks Stefan,

    It's nice blog explaining different scenarios for Solman upgrade/migrate.

    We have Solution manager 7.2 SP5 on Oracle DB and we are using it after upgrade from last 10 months for Charm, QGM, Test Suite, TechMon.

    Now we are planning to migrate it to HANA database, will we need to do content activation again after DB migration.

    Can you shed some light on this please.





  • Nicely put up article. Thanks.!


    We are already on solman 7.2 SP8 and we are planning to migrate to HANA.

    Can we do it with SUM ?. DMO without upgrade.

    And if the ABAP SID is migrated to HANA , what happens with my JAVA SID ?.