Step-by-Step Procedure for SPAM Update/patching.

In this Blog we will look at updating SPAM . SPAM or Support Package Update Manager is one of the two (The other being SAINT) primary tools for patching SAP ABAP system . For updating SAP Java systems you use JSPAM . If time permits I will write more about the differences and SAP’s overall release & versioning strategy and JSPAM (or lack of it!).

Updating SPAM is a relatively straightforward and simple procedure. The key thing to remember is that you MUST always update your SPAM before proceeding with any Support Package update. Even if you are simply conducting a review to determine the dependencies of the different support packages and which ones to eventually include in the SP upgrade project, you need the latest SPAM version otherwise you could be working with incorrect or outdates information.

Having  said that, SPAM is not always 100% correct in determining dependencies. I had a experience where it was asking for a secondary dependency which we could find on SAP Marketplace. Eventually after much investigation and logging a call with SAP Support, I was  told to ignore the dependency…so just a warning

Step by Step Instructions

In SAP, you always “uncar” (unzip) your sap packages using the SAP tool SAPCAR

Unpacking SAPCAR archives: Uncar in folder /usr/sap/trans

sapD00:d00adm 42% SAPCAR -xvf /usr/sap/trans/spam/KD70142.SAR -V

SAPCAR: processing archive /usr/sap/trans/spam/KD70142.SAR (version 2.01)

x EPS/in/CSN0120061532_0049370.PAT

SAPCAR: 1 file(s) extracted

Tip: Always uncar in /usr/sap/trans as in will create the directories /EPS/in under this directory structure otherwise it will create the …/EPS/in the whichever directory you unzip

 

Location after expand/Uncar: (must be in this location for SPAM to see it)

/usr/sap/trans/EPS/in

PS: You can also directly import the package from you local desktop.

SPAM Update:

Step 1- Load packages

Log into SAP and call tcode SPAM. It will see the new unzipped packages in ../EPS/in folder

Step 2 – Import Spam update

SPAM Updated Successfully!! (Make sure you see a green light)

Possible Errors: You may get an ABAP Dump at the end. Don’t Panic! Simply restart the SPAM tcode and you should see the green light and to confirm it is updated, make sure it reads the new version e.g in this case 7.01/0042