KEMBAR78
Implement Support Package | PDF | Backup | Directory (Computing)
Scribd
Upload
39 views4 pages

Implement Support Package

Support Packages (SPs) are essential updates from SAP for fixing issues and enhancing system functionality. Implementation requires specific pre-requisites, including applying updates in client 000, ensuring adequate transport directory space, and having the right user authorizations. The upgrade process involves downloading, uncompressing, and importing the support packages while checking logs for any issues during the import.

Uploaded by

Ayoub Essadi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
39 views4 pages

Implement Support Package

Support Packages (SPs) are essential updates from SAP for fixing issues and enhancing system functionality. Implementation requires specific pre-requisites, including applying updates in client 000, ensuring adequate transport directory space, and having the right user authorizations. The upgrade process involves downloading, uncompressing, and importing the support packages while checking logs for any issues during the import.

Uploaded by

Ayoub Essadi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

1.

Introduction
Support Packages (SPs) are cumulative updates released by SAP to fix issues, improve system stability,
and enhance functionality. They are essential for maintaining the reliability and security of SAP systems.
( collection of SAP NOTES)

2. Pre-requisites for Support Package implementation

- Support packages should be always applied in client 000.


- Ensure that there is enough space in the transport directory. The transport directory is located
at /usr/sap/trans
- The user to be used for the support package implementation must have authorizations
equivalent to DDIC or SAP*
- Take the necessary backups to ensure data safety (full database backup and the folder
/usr/sap/SYS/exe) and also offline backup of the application Server
- Deactived users access on the destination clients
- Release all modifiable transport requests
- Check : 782140 - OCS: Known problems with Support Packages in Basis
- Check SPAM Version: If your SPAM version is 74, you need to check if a newer version is
available

- Check Support Package Level: System -> Status


- Call the transaction SPAM and see if any previous Support Package import is incomplete. You
can proceed ahead unless the previous support package import is successful.

3. Steps to Upgrade the Support Package


1.1. Download Support Packs
URL : https://me.sap.com/softwarecenter

1.1. Download Support Packs

Download the support packages from service marketplace and save them at OS level in directory
/usr/sap/trans.

Uncompress these files using sapcar executable: sapcar –xvf <support package name>
load the Support Packages into SAP system by choosing :

Import Support package

A SPAM/SAINT Update contains updates and improvements to Support Package Manager (SPAM) and
Add-On Installation Tool (SAINT). There is always one SPAM update for each release. SPAM/SAINT
update is mandatory before any support package upgrade
Defining Queue

Queue contains the Support Packages available for the different SAP Components installed in your
system. This Queue information is derived from the support pack uploaded

Click on Display/define => A list of software components derived from the support pack uploaded

you select the required component, for exemple SAP_HR

If the displayed queue meets your requirements, you can confirm it by choosing Confirm Queue

Importing Queue

Do ‘Import queue’ to start importing/applying that particular selected support pack (as per the standard
SAP process). Then The support package import has been started
Once Queue has been imported, SPAM status becomes YELLOW so after we need to confirm the import

Like this :

Checking logs :

 On the OS Level
o While the support packages are being imported, logs are made into the tmp directory
(path: usr/sap/trans/tmp)
o Once the import process is completed logs can be viewed from the log directory (path:
usr/sap/trans/log)
 On the spam transaction
o Go to–>Action log

You might also like