Support Package Upgrade by using SUM[Software update manager]

What is SP upgrade:

A Support Package contains a collection of error corrections. You can only import complete Support Packages and in a specified sequence. Each correction in a Support Package is documented in an SAP Note. After you have imported a Support Package, you must perform the Modification Adjustment using transaction SPAU. Basis responsiblity to maintain the system at latest level or N-1 level at MAX.


  • Import thing is before start the SP upgrade maintain the kernel at latest level. or skip the kernel part while generating stack for SP upgrade.
  • Make sure to put the maintenance certificate before kick off SP upgrade.
  • Delete the old spool number in SAP system before start the SP upgrade.
  • Maintain minimum 48 GB free in Database to run SUM tool.
  • Here am going to do SP upgrade by using SUM tool. So before start using read the SUM manual for quick action.
  • Note: SUM tool have the option to upgrade both ABAP + JAVA stack at same time.

Step 1:Download SUM[Software update manager] latest version from service market place In my case am using SUM 1.0 SP06. PFB 1 2 Please make a note of HTTP Listening port number. In my case -4239 3 Step 2: How to start the SUM tool? Here am going to share the step by screen shots to open the SUM tool. PFB for your reference. 4 6 Step 3: Here i was done SP upgrade for dual stack. As i stated earlier we can upgrade ABAP+JAVA at the same time to reduce the downtime. 7 Fill the OS level password ie SIDADM password. 8 Step 4: We have successfully generated stack.XML file before start the SP upgrade and put into EPS\In folder and specify as same below.[For how to generate stack.XML file, refer my blog] 9 Step 5:Refer SAP note 1707161 and do the needful i.e update the keyword below to proceed further. 10   Step 6: Complete the initialization part ans click next.11   Step 7:Provide DDIC[000 Client] user password to extract the system information 12 13   Step 8: SPAM version is too low to proceed further so we have imported latest version of SPAM. 14   Step 9:Currently extraction phase running on. Middle of extraction phase SAP recommended notes missing from our system, so first implement the below listed SAP notes to proceed further steps. 15   16   17   Step 10: We have moved to configuration phase, ie very import phase like back bone of our SP upgrade. 18   In this configuration phase we can set the number of parallel process should run during our SP upgrade.   19   20



Step 11:  Currently configuration part running on. it will give the system information.



At this phase, handover the system to developer and capture the SPAU and SPDD correction in transport number and fill the same below as well.


Step 12: Beauty of SUM tool concepts is, create the shadow system and upgrade it first then if successful means copy the same to  our original system




Now here ABAP phase completed successfully. we will go for JAVA part.


Step 13: Provide necessary java admin & SAP* passwords.








java got completed successfully.

Step 14: Likewise checks run for both ABAP+JAVA.

Preprocessing phase-Shadow system to be created end of preprocessing phase.

Execution phase– upgrade the shadow system first and check if SP upgrade is successful?

Postprocessing phase-copy the shadow instance ie upgraded system to our target system.






Finally we have successfully completed SP upgrade by using SUM[Software update manager].

Please let me know in case of any queries.

Thanks & Regards,

Sabarish Vasudevan.

Stack Generation in Solution Manager

What is Stack.XML:

While upgrading you need Stack.XML which contains information about your present level to target level information. ie Solman system compare satellite system with reference of service market place. It contains a list of all patches which are required during the installation or upgrade.


  • Maintenance Optimizer is configured in solution manager.
  • Configured Technical System in SMSY[Solution Manager System Landscape].

Generating Stack file:

Step 1: Tcode: solman_workcenter

Step 2:solman_workcenter again then Change request management – Maintenance Optimizer 






Step 3: Here we are going to generate new stack file, Click new to proceed.



4Step 4:Kindly go with recommended option, it will give you the latest stack level.






Step 5: Select Target stack level. ex. Current level of my system stack 2 to target stack 7





Step 6:Here I don’t want any additional products if you need check below required component.



Select kernel depending on your product version.




Step 7: Select Stack dependent files



Step 8: Selected files successfully added into download basket.Finally you have created Stack.XML files in EPS folder.PFB for more info.



Please revert if you have any queries.

Thanks & Regards,

Sabarish Vasudevan.