SAP Support Package

The Steps to Upgrade SAP Support Package

/0 Comments/in , /by

Hope sometimes we need to update our SAP Support Package for bug fixing or regular maintenance.

If we  check our current SAP Support Package Level from transaction SPAM –> Package Level or System –> Status , under Component Version click the glass icon.

It will show your current SAP Support Package of each component.

Before we upgrade it, make sure we have downloaded necessary SAP Support Package.

SAP Support Package

Step by Step Configuration

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

sap support manager 1

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

Step 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.

sap support manager3

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

sap support manager 4


Step 5: To Click Support Package->Load Packages-> Import SPAM/SAINT Update.

sap support manager 5

Also See: SAP Support Project Handling Tickets

Step 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.

sap support manager 6

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:

LOAD_PROGRAM_LOST

LOAD_PROGRAM_CLASS_MISMATCH

LOAD_TEXTPOOL_LOST

SAPSQL_SELECT_WA_TOO_SMALL

SAPSQL_SELECT_TAB_TOO_SMALL

SAPSQL_WA_TOO_SMALL

DDIC_STRUCLENG_INCONSISTENT

RUNT_ILLEGAL_SWITCH

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, andLOAD_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.

Also See: SAP Support & implementation – Go live an Overview