Support Package Upgrade by

using SUM[Software
update manager]
Posted on April 29, 2013 by Sabarish Vasudevan

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.

Prerequisites:
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
 Plea
se make a note of HTTP Listening port number. In my case -4239
 Ste
p 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.
 Ste
p 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.

Fill
the OS level password ie SIDADM password.
 Ste
p 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]

Ste
p 5:Refer SAP note 1707161 and do the needful i.e update the keyword
below to proceed further.
 St
ep 6: Complete the initialization part ans click next.

St
ep 7:Provide DDIC[000 Client] user password to extract the system
information
 St
ep 8: SPAM version is too low to proceed further so we have imported
latest version of SPAM.
 St
ep 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.
 St
ep 10: We have moved to configuration phase, ie very import phase like
back bone of our SP upgrade.
 In
this configuration phase we can set the number of parallel process should
run during our SP upgrade.
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.