Patch Administration

Posted on by
PATCH ADMINISTRATION:
A Patch/ Support Package is a collection of error corrections. A patch comes as a part of Online Correction Support (OCS). A patch eliminates an error in an R/3 System. It is made available before the next R/3 release that contains the correction. A patch replaces the objects affected by the error, rendering their old versions obsolete. One can only import complete support package and in a specified sequence. Each correction in a patch is documented in an SAP note.
Support Packages replaced hot packages. Support Package covers only one software component type unlike hot package.
The naming convention for support packages/patches should be as follows:
                                  SAPK
For BASIS—– SAPKBXXXXXXX
For ABAP——SAPKAXXXXXXX
For Applications—–SAPKHXXXXXXX
For HR——-SAPKEXXXXXXX
The Support Packages should be administered in the following sequence: BASIS, ABAP, APPLICATIONS and HR.
Similar patch levels should be maintained across DEV, QAS and PRD.
The following packages types are few among that are available:
1. SPAM/ SAINT update: This update will contain changes and improvement related to SAP Patch Manager and SAP Add-on Installation Tool.
2. Component Support Package: This package is valid for one software component (Viz. SAP_APPL, SAP_BASIS, SAP_HR) and contains corrections to errors in the Repository and Dictionary pertaining to the software component only. In addition to the corrections, support packages for SAP_HR also contain adjustments due to legal changes.
3. Add-On Support Package: This package is valid for add-on with a particular release and contains corrections for this add-on.
SPAM/ SAINT update and patches are applied through the Support Package Manager (transaction code SPAM).
Most of the updates and patches are in the form of .CAR files and these are available for download at SAP Marketplace.
SPAM:
SAP Patch Manager (SPAM) is the customer side of the Online Correction Support (OCS). For applying patches, SPAM is executed in 000 Client of an R/3 system. SPAM lets one to apply the patches in the correct order by creating a patch queue. One has to confirm each successive patch queue before the next one is setup. The tcode SPAM calls for the programSAPMSPAM.
Go through for prerequisites before applying a patch to a software component. All the       prerequisites have to be fulfilled before a patch can be applied.
         
1) Schedule window (off peak time) and download the patches from market place.
2) Check if \USR\SAP\\TRANS\EPS\In directory has sufficient space.
3) Check if the table space has not up to 90%.
4) Check if you have sufficient space at O/S level.
5) Update SPAM version, if needed.
6) Download the .CAR files of the patches to be applied onto the system. Uncar the files (patch) by using cmd prompt and change the path to the directory where you have downloaded the patches. Make sure that the TRANS directory should have asapcar.exe executable, if you don’t have one, copy it from \USR\SAP\SID\SYS\EXE\RUN.
Use the command CAR –xvf >:\ \.CAR. The command CAR is case sensitive.
7) When you uncar the .CAR file, .ATT and .PAT files will be generated and they have to be present in \USR\SAP\\TRANS\EPS\In directory before the process of applying patch is initiated.
  1. Log in 000 client as admin user, execute transaction code SPAM and choose SUPPORT PACKAGE tab. Select LOAD PACKAGES tab and choose either “from front end” or “from application server” option
  2. Confirm the selection by selecting the tick button.
  3. System will read the contents from EPS/in directory, then it will import the contents into queue, then choose DISPLAY/DEFINE button
  4. The total available components like ABAP, BASIS, HR, APPL and add-ons etc., will be shown. Choose the type of component which you have uncarred and confirm the selection.
  5. Now that the selection has been made, the selected component will be displayed in the Queue box as shown.
  6. Select either “import queue” option located under “Support Package” tab or the truck button located on SPAM screen so as to initiate the import queue process. Upon the process completion select the confirm option under the SUPPORT PACKGE tab.
  7. After confirming the package into queue, the import process will run and apply the selected software component to the existing installed software application
ADD-ON:
An Add-on can be defined as a set of software components intended to add specific abilities to a larger software application. An Add-on can also be referred to as Plug-in.
In SAP, Add-ons are installed on to the SAP system using the SAP Add-On Installation Tool. This tool can be accessed by executing the transaction code “SAINT”. Before applying an add-on onto the system, please check for the add-ons already installed on the system. Also check the type of add-on downloaded, whether it is intended for Upgrade or Installation. If it is an upgrade add-on, make sure that the earlier version of the add-on and its related patches has been installed on the system, prior applying the upgrade add-on onto the system.
Add-ons are also in the form of .CAR files like the support packages and these files contain the .ATT files and .PAT files.
Download the .CAR files of the add-ons to be applied onto the system. Uncar the files (patch) by using cmd prompt and change the path to the directory where you have downloaded the add-ons. Make sure that the TRANS directory should have asapcar.exe executable, if you don’t have one, copy it from \USR\SAP\SID\SYS\EXE\RUN.
Use the command CAR –xvf >:\ \.CAR. The command CAR is case sensitive
When you uncar the .CAR file, .ATT and .PAT files will be generated and they have to be present in \USR\SAP\\TRANS\EPS\In directory before the process of applying add-on is initiated.
SAINT:
The SAP Add-On Installation tool was developed to enable users to install the add-ons directly from their standard SAP system.
SAINT will have the following authorizations against it. The tcode SAINT calls for the program SAPLSAINT.
  1. Log onto the 000 Client with administrator privileges
  2. Execute the transaction code “SAINT”.
  1. In the upper half of the screen you see the installed add-ons. The lower half displays the add-on packages to be installed. Click on the required add-on and click on the start button to move ahead in the add-on installation process.
  2. The following screen will be displayed wherein we have to load the additional support packages, if any, located in the /trans/Eps/In directory.
  1. From the available set of support packages located in the /trans/EPS/In directory, choose the support packages that are required for the installation and click continue to finish the installation.

Leave a comment