Steps to upgrade Support Pack Manager

1) Download the latest Support Pack Manager (SPAM) on the SAP service marketplace


2) Transfer the downloaded file to /usr/sap/trans/EPS/in



3) SAP has extract tool to extract the SAR files.You have to login has adm.Then go to the location where you copied SAR files.Then execute “SAPCAR –xvf ”. Copy all the unextracted file to /usr/sap/trans/EPS/in directory.


4) Login as DDIC. Invoke tcode SPAM and load the extracted files. Support PAckage->Load PAckages->From Application Server

5) Then, click Support PAckage->Load PAckages-> Import SPAM/SAINT Update.

6) Then it will automatically update the Support Pack Manager. You're finished!. You may bump into ABAP Dump. Like me, I bump into LOAD_TEXTPOOL_LOST.

However, if you read SAP note 822379

SPAM/SAINT updates

* Symptom: When you import the SPAM/SAINT update, a range of different runtime errors may occur:

o LOAD_PROGRAM_LOST

o LOAD_PROGRAM_CLASS_MISMATCH

o LOAD_TEXTPOOL_LOST

o SAPSQL_SELECT_WA_TOO_SMALL

o SAPSQL_SELECT_TAB_TOO_SMALL

o SAPSQL_WA_TOO_SMALL

o DDIC_STRUCLENG_INCONSISTENT

o RUNT_ILLEGAL_SWITCH

o CALL_FUNCTION_PARM_UNKNOWN

These errors occur because the source code of the Support Package Manager is modified by the import during the run. CALL_FUNCTION_PARM_UNKNOWN, LOAD_PROGRAM_LOST, LOAD_PROGRAM_CLASS_MISMATCH, and LOAD_TEXTPOOL_LOST occur if the ABAP load or text elements are to be loaded back into the local buffer, and there is a different version in the database.
However, SAPSQL_SELECT_WA_TOO_SMALL, SAPSQL_SELECT_TAB_TOO_SMALL, SAPSQL_WA_TOO_SMALL, DDIC_STRUCLENG_INCONSISTENT and RUNT_ILLEGAL_SWITCH occur if changes are made on the SPAM/SAINT data structures with the SPAM/SAINT update.

Solution: None of these errors will occur again if you restart the Support Package Manager (transaction SPAM) and continue to import the SPAM/SAINT update.