Steps to Upgrade Support Packages using SPAM

Every support packages may involved multiple teams such as ABAP, FUNCTIONAL and BASIS. So, a proper planning needed to ensure the support package upgrade going smooth. As recommended, the upgrade should be implemented in development, quality before going for production.

1. Verify the current level of support packages from transaction code SPAM. Verify and download the required support packages via MOPZ or SAP Service Marketplace.

2. Check the backup status from transaction code DB12. Ensure the backup is completed successfully.

3. Verify the tp, R3trans and SPAM version are meet the needed requirement. Set the notification message in the system so that users will aware on the upgrade.

4. Copy all the downloaded support packages files into DIR_EPS_ROOT directory.

5. Open the SAP system in client 000. Execute transaction code SPAM. Make sure the system is having the valid maintenance certificate.

6. For performance wise, apply the below recommendations,

• Apply the SAP Note 1127194.

Go to transaction code SPAM > Extras > Settings,

• Under the Import Queue tab, set Never on ABAP/Screen Generation. This option will generate the programs and screens only when called for the first time.

• Under Parallel Import, set the value to 4 (initial value recommended by SAP) for Number of parallel processes per R3trans.

7. In transaction code SPAM, you need to load the support packages via Support Package > Load package > From Application Server. This action will put the files into the import queue.

8. Choose back to initial screen of transaction code SPAM. Click on Display/Define to select the component to upgrade. In this example, the upgrade is only on ST-PI (1 component). If you have multiple components, you may choose All components. Next, press Enter to confirm the queue. Please noted that some of the support package will have SAP Note so that you can read to double check before you are executing the upgrade.

9. If you have any transports to add during the import, you can select Yes, else click No to proceed.

10. Next, go to Support Package > Import Queue. At here, you can select the setting to run the import queue via foreground or background. If the upgrade is consists of multiple support packages, you may need to run in background. Press enter to start the upgrade execution.

11. Now, you can just wait and monitor the import queue phases till completed. Upgrade will take a longer time if the import queue contains multiple levels of support package. During the import queue, you may encounter with SPDD and SPAU which need interventions from ABAP & Functional team.

12. You will get below notification which saying that the import queue is completed. To finalize, you will need to confirm the queue. Go to Support Package > Confirm.