Skip to Content
Author's profile photo Veeramalla V

Sum and Sum with DMO


I started the upgrade of 7.3 portal system and sum is expecting <sid>adm password, and due to audit restriction we were not able use the <sid>adm in sum for the upgrade.  I checked couple of documents about sum and I didn’t see any workaround for the same.

I checked one document which talks about  DMO for HANA , observed that there was option where we can skip <sid>adm user/password(by changing the sumstart.conf file) and tried that option  we moved forward but unfortunately started several issues with schema user and  and several other issues(Even though I have given full permission and groups to the user) and ultimately resulted the restart of the upgrade with JSPM with the help of note 1563660 .

I checked with sap and they told that it is not meant for normal upgrade and it’s is only meant for DMO and it was not tested for other scenarios


I spent several hours for investigating the workaround and picking the wrong tool again wasted several more working hours in solving the actual issue. I checked several blogs in SDN and here I would like summarize few points which gives idea when to use sum and sum with DMO  ,   this is not new blog with entirely new content but I would like differentiate both the tools .

Software Update Manager:

    • Release uprade (major release change)
    • System update (EHP installation)
    • applying Support Packages (SPs) / Support Package Stacks
    • applying Java patches
    • correction of installed software information

  SUM is used for all SAP NetWeaver based systems, so systems either based on AS ABAP, or AS Java, or based on a dual-stack system. 


http://<host name>:4239.

SUM with DMO

Database migration option (DMO) is an option in SUM – DMO is not a separate tool and this build is only using the ABAP part of SUM, called SAPup

  1. 1. Although DMO is based on the “standard” SUM, a new user interface (UI) is used – but only for the DMO procedure. The UI is based on SAPUI5, so it’s running in a browser, and offers some comfortable features like checking the log files without having to log on to the OS of the application server.

   2.  Different start procedure

SUM is started in a different way: a browser request to the SAPHostAgent is used to start SUM, instead of starting SUM from the prompt/console. This allows you to start the SAPup process without having an additional server window open

Different UI

   3. SUM shows a new user interface which is based on SAPUI5, which is currently exclusively available for DMO only.

   4. The new UI is currently only available for the DMO procedure, but in the long run, it may become available for other use cases as well.

Where we can use


  • You want to migrate your existing SAP ABAP system to the SAP HANA database
  • Your SAP release needs to be upgraded prior to migration
  • MO for SAP NetWeaver BW and for SAP Business Suite systems
  • DMO is available with Software Update Manager 1.0 SP09, and can be used for systems based on AS ABAP. It can be used for SAP NetWeaver BW systems from 7.0 SP17 (and higher) to migrate to 7.31 (and higher). And it can be used for systems part of the SAP Business Suite 7.0 (and higher) to migrate to a level corresponding to SAP BASIS 7.40 (for example “SAP enhancement package 7 for SAP ERP 6.0”).

How to start SUM with DMO option

Run the command /usr/sap/<SID>/SUM/abap/SUMSTART confighostagent to create the file sumstart.conf in

Start the DMO Frontend with the following URL – (HTTP/HTTPS)



Using proper tools as suggested by sap will save your time And always it is  recommend to use sap prefered tools and follow release notes and guides before planning any upgrade .


1600846 – JSPM/SUM Calls sapcontrol without user credentials

1563660 – sapcontrol, <sid>adm authorization issues (SUM)

SAP First Guidance – migrate BW on HANA with the

database migration option (DMO)

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Andy Silvey
      Andy Silvey

      Hi Veeramalla,

      thank you for publishing this article and describing your experience and your observations on the application of the different tools.

      One of the simple rules in SAP is wherever possible stick to the standard and use the right tools for the job.

      The root cause of the challenge you experienced was that you didn't have access to the sidadm password.

      I have seen this scenario in so many large companies.

      The problem can be solely attributed to weak Management and weak Leadership.

      In the SAP Basis world, where things are complex enough, it simply isn't right that after the enterprise has invested all of this money into the software, hardware, human resources, that the Basis Engineers have to resort to hacking and trial and error simply to attempt to complete the execution of an upgrade.

      Upgrades are complex enough without having to add a layer of complexity around hacking the tools and procedures.

      You should not have had to do that, your Manager/Team Lead should have taken the situation,

           the SUM Tool requires the sidadm password

      to the Security Team and using the process obtained an exception/exemption.

      If the Manager/Team Lead is not having the skills and qualities to achieve that, then he/she is putting the implementation and investment at risk and costing the enterprise more money and time. Time spent hacking, reading, guessing, time spent at every hurdle trying to get the upgrade to execute step by step, time spent solving later fundamental issues caused by the upgrade not being executed with the correct tools.

      To conclude, the article is interesting in as much as it shares differences in the tools and their usage scenarios, however,

      the moral of the story is:

           . There are times when Basis Leads / Basis Managers needs to show Leadership and take challenges like this one, SUM needs to sidadm password, as high as is needed to obtain the desired result

      On top of this, upgrades are a standard routine activity, often on an annual basis and for the whole SAP landscape, and therefore, this scenario is precisely the kind of scenario which needs an exception to the rule, and so, if the Manager / Basis Lead will show leadership and get an agreement with the Security Team on this one, they solve the problem for ever more.

      Best regards,


      Author's profile photo Veeramalla V
      Veeramalla V
      Blog Post Author

      HI Andey,

         Thanks for you comments and i strongly agree with your views, Most of the time  basis consultant  need to  depends on other groups like unix/linux/database/security . Challenging part is that most of the time these groups are supported by different companies  getting the things to be done is some what difficult and it's purely management decision and they need to take it forward .

      As a basis consultant thumb rule is , stick to basic rules like following standard guides and release notes before starting any activity.