What is Support Packs in SAP:
SAP releases Support packs, which are a collection of advanced corrections.
Types of Support Packages are listed below:
HR Support Package
ABAP Support Package
APPL Support Package
Basis Support Package
Add-on Support Packages
These are available for download directly from the SAP Service marketplace at below link
SPAM package download: service.sap.com/patches
On demand the Support packs available are sent in form of CDs to SAP’s customers. The system should be update by the designated personnel as early as possible. The support packages have certain dependencies and the same is to be checked on. Basis and ABAP support packages can be loaded independently whereas special care is to be taken while loading application support packages to include the CRTs of addon packages otherwise some conflict can arise and system can go to an unstable state.
How to apply Support Packs (SPAM package) to SAP :
After collecting the required information on CRTs and the like, the Support packs can either be downloaded from the SAPNET or uploaded from (Support packages) CD into the usr/sap/trans/EPS/in directory. The CAR files will also have to be extracted to the same directory.
Login to the system on client 000 – With any user-id other than SAP* or DDIC. The login-id should have SAP-ALL and SAP-NEW authorizations.
Run transaction code SPAM to invoke the SAP Patch manager. You can choose the upload button to upload data directly from /usr/sap/trans/EPS/in directory on the server or from a path on your local Front end.
Execute the “SPAM” transaction again. You will now be able to see the support packs window. Use the drop down box menu to verify the queue. The support packs will be in the queue followed by their corresponding CRT’s for the different add-on. Press the consistency check button to verify the queue is okay.
Go to the Menu Option settings on the SPAM screen and change the settings from ”S” to “T” (Standard to Test mode) The queue may be applied in test mode to check if it has conflict with any object that is already modified in the system. If there are any modifications to the program that the hot pack is also affecting, then the hot pack will create versions for the same. It will make the program delivered by it to be the current request the active version. Transaction “SPAU” (SAP Adjustments) will need to be run to make the required adjustments. If CIN programs are also affected, please check with SAP India.
Make sure that you have applied the latest SPAM update before you apply any other patches.
Always apply patches to your test system before you start to apply them to your production system!
Only the system administrator should be able to download, apply, confirm, or reset the status of patches. To use all the SPAM functions, you require the authorizations.S_CTS_TR_ALL and S_CTS_ADMIN. You can find both of them in the authorization profile S_A.SYSTEM
Ensure that you are logged into client 000 with the proper authorizations. If you log into another client, or do not have the correct authorizations, you can only use the display functions.
Make all the users log off before you apply patches in scenario ‘S’. During the patch application steps, the R/3 system must not be in use, i.e. only the system administrator is allowed to be logged on. Otherwise you risk program terminations.
Shut down all application servers except the central one for the duration of the import. Otherwise, buffer synchronization problems with program terminations, and possibly data inconsistency, may result.
You cannot have any incompletely applied patches in your system. To check this, under Directory choose Aborted patches and then choose Display. No patches should be displayed. Under the section Patch, the status should display a green traffic light.
Check the logs before confirming the patch application.
Never apply patches directly with tp. You will lose all of your modifications and overwrite your Add-On, if you have installed one. If you have made a modification adjustment for the Patch Queue in your test system, ensure that you do not import the resulting modification adjustment transport into further systems until you have applied the same patches to these systems.
While a patch is being applied the session is blocked. Open a second session before you apply the patch to avoid logging on again.