How many ways you can apply support packs?

We need to be logged in 000 client for applying support packages. Initially we need to download the latest support packages available in the www.service.sap.com/swdc After downloading we initially need to upgrade the SPAM/SAINT tool i.e. the SAP_OCS component with the latest patches available. For the other layers we need applying the n-1 th support packages of the latest available. One basic rule we need to follow while applying support packs is we need to maintain same patch level for BASIS layer and the Application layer i.e. for the SAP_BASIS and SAP_ABA. Support packs can be applied in two ways: One is from the From Front-End and the other is From Application Server in the Load Packages Option in the Support Packages Menu in Support Package Manager Screen. Flow: SPAM Support Packages Menu Load Packages Option From front-end Or From application server From Front End Process:

Click on the From front-end option in the Support packages Menu Select the support package to be applied, confirm it and Decompress it. After decompression the decompressed files will be transferred to \\hostname\sapmnt\trans\EPS\in Directory. select the new packages option and select the support package to be imported and click on the Queue button. After adding the support package to the queue click on the Import Queue option in the Support Package menu in the in the initial screen of the SPAM. Finally we need to confirm the activity by clicking on the Confirm option in the Support Package Menu.

From Application Server Process: Unpack the downloaded support using the command: sapcar xvf <location:///XXX.CAR> in /usr/sap/trans directory. This command unpacks the files that need to be imported into your SAP instance into the usr\sap\trans\eps\in directory. Select the From Application server option from SPAMSupport packages MenuLoad Packages.

SUPPORT PACKAGES: or Patches / Hot packs / LCP/CRTs Support packages or support stats provides enhanced functionality, changes to the existing data dictionary elements, repository objects like reports programs, transactions etc., Support packages of various types, few of them are: 1) Basis support packages 2) ABAP support packages 3) APL support packages -> SAPKB620050 -> SAPKA620050 -> SAPKH470050

4) HR support packages 2324 -> SAPKE470050 In order to display the current support package level. Go to system + status + click on Magnifier. Then all the package levels will be displayed. Pre-requisites for support packages: There should be 2 Background jobs. The latest SPAM/SAINT versions should be applied on the system. There should be enough space to hold the support packages in EPS/in There should be no aborted packages. Support packages should be applied on this sequence of nos. of support packages level. Upgrade the Kernel version if required. Apply support packages in order of BASIS/ABAP/APPL/HR. Technical and functional consultants needs to be informed while applying support packages because when the system updating DD elements, repository objects functional and technical objects. Functional and Technical team are the right people to advice whether to keep the existing functionality or move on the current functionality which comes in SP. Scheduled down time and inform users. Go through composite note thoroughly before applying support packages. If the support package is more than 10MB, UNCAR the file using sapcar svf <filename>.sar. When we uncar two files are generated with extension .ATT or .PAT. When the support pack is aborted and could not be resolved the final remedy is to delete entries in the these 2 tables. Packages once applied cannot be reverted back. If we want to revert, then contact SAP technical support. APPLYING SUPPORT PACKAGE OR PATCHES 1) 2) 3) 4) 5) Go to SPAM (SAP Patch Manager). Load packages from the Presentation Server/Application Server. Display all the new Support Patches to be applied (Queue). Import the Queue or Display in Define Queue. Support pack starts upgrading the system and it goes into various phases like TP Connect To DB, DDIC import , DDIC activation (all these 27 steps can be found in PAT01) while applying support package, it stops to run the SPDD/SPAU.

SPAD: This is the transaction which is used to update the data dictionary tables which applying SP. This is the phase where functional consultant assistance is required. SPAU: This is the transaction which is used to update the repository objects like programs, reports, functional modules while applying support packages. This is the phase where technical consultants required. Note: If the objects are changed earlier with the help of SAP notes, Now these notes are parts of the support package which are modifying the system, during this scenario each and every object which was modified earlier with the help of the note are popped on the screen whether to keep the original or change to version. KERNAL UPGRADE/PATCHES. Kernel is the heart of SAP system and located in run directory \usr\sap\<SID>/run. If consists of various executables which are required for smooth functioning of R./3 system. Sometimes these executables gets outdated and needs to updated from time to time. The following are the reasons for Kernel Upgrade: 1) During OS upgrade, DB upgrade and OS,DB patches. 2) It is a pre-requisite to upgrade the kernel to certain level before applying support packages. 3) Some of the executables are Msgserver.exe , dispatcher.exe , sapcar.exe , TP.exe , R/3 trans. 4) Kernel upgrade is the process of replacing the existing executables with current executables. Process of Kernel Upgrade: 1) As part of the upgrade, complete Kernel Directory can be replaced or a group of executables or single executable can be placed. Ex:- While import6ing transporting request: 1) TP gets aborted with an error, TP outdated then replace only TP. 2) While uncaring the files SAPCAR may be outdated in this replace only sapcar. 3) DB executables like SAPDBA, BRBACKUP, BRARCHIVE, BRRESTORE, BRCONNECT are grouped to be upgraded.

There are 2 types of executables: 1) R/3 executable with DB dependence. 2) R/3 executable with DB Independent. 1) Go to marketplace www.service.sap.com and download the current version of Kernel. 2) UNCAR files into a directory called newrun. 3) Schedule downtime and inform users. 4) Shutdown SAP DB,R/3 , A Servers. 5) Stop all the services including saposcol. 6) Go to exe directory rename the existing run directory to old run and rename the new run to run directory. 7) Start sap, run SICK any problems it will show. SAP NOTES: SAP maintains a knowledge base of problems and resolutions which are accessed from marketplace. www.service.sap/notes SAP provides resolutions in the form of a note which is a number. Note can be searched on number [if we know] or we can search with the problem code, error number etc., Note provides info. Regarding the problem, as follows: 1) Problem 2) Pre-requisites. 3)Cause of the problem. 3) Solution, Corrections, attachments and note may redirect one or more number of notes. Notes are of 2 types: 1) Informative note: Which consists of details to solve the problem. 2) Corrective note: This provides changes to the data directory elements or repository objects. If there is a repository changes i.e., program code change can be done using SNOTE. If there are any changes in data dictionary elements or customizing (Keying entries) to provides entries manually in tables which are detailed in attachments. To change repository objects we need ACCESS KEY. While correcting the program SSCR key note required. SAP software change request. Applying Snote:

1) Go to SNOTE. 2) Load the NOTE, when we load the note status will be known. 3) Implement the NOTE, while implementing the note status is in process. After NOTE is applied it is completed. Once the implementation is completed Before going live R/3 system needs to be tested for its optimal runtime.
It is always advisable to first verify the SPAM/SAINT version in the system. Check in http://service.sap.com/ocs for the latest version of SPAM/SAINT. The SPAM/SAINT update and support packs files are .CAR files, which need to be unpacked. Supports packs for Applications area (i.e. changes made to the objects of various functional modules of SAP) are also know as HOTPACKS The following procedure is a step-by-step procedure for applying these Support Packs. 1. Download the required .CAR files from SAPNet or SAPServX server 2. Put them in a temporary directory either in /usr/sap/trans/tmp or any other folder which you can create (say, patch) 3. Change to the directory /usr/sap/trans (UNIX) or \usr\sap\trans (NT) 4. Use the command CAR -xvf <path the of the CAR file including the .CAR extension> 5. The command CAR is case sensitive 6. The command CAR will decompress the CAR file and put two files (with extensions .ATT and .PAT in the /usr/sap/trans/EPS/in directory. 7. Logon to the SAP system in client 000 as user DDIC 8. Once in the system execute the transaction code SPAM 9. Depending on what version are you in do the following : For 4.5x : Goto Tools Upload Patch For 4.6x : Goto Support Packages Load Packages From Application Server 10. You will get a pop up box with the list of the patches in the queue. Both the applied patches and the new ones will be listed 11. Hit the Back button to come to the main screen 12. Click on the Display/Define button on the screen 13. You will get a pop up screen with the unapplied patches. 14. Select the patch or group of patched that you want to apply and hit the enter key/icon. 15. The patch number will be defined in the queue box. 16. Again depending on the version, you do the following : For 4.5x : Goto Tools Apply Patch For 4.6x : Goto Support Packages Import Queue or click the apply patch / import queue icon on the application toolbar 17. After the patch is successfully applied, you will have to CONFIRM the patch application. 18. Again depending on the version, you do the following : For 4.5x : Goto Tools Confirm For 4.6x : Goto Support Packages Confirm Or click the confirm icon on the application toolbar

19. The light in the status box should turn green. 20. After the patch(es) are applied, execute the transaction code SPAU. This transaction code will check for the changes made by the patches as well as by the user via OSS notes etc to the system You can compare the changes and decide to keep the changes made to the system via OSS notes or return the objects to original. At times depending on the situation, you may have to reapply the OSS notes after returning back the object to original Before applying the patches, check for the SPAM version. It is always advisable to have the latest SPAM version running on the system. You can download the latest SPAM version from the SAPNet or SAPServx server. There are patches, which require a certain level of SPAM version in order to be applied. Plug-ins are applied on the R/3 side using the transaction code SAINT Before applying the plug-ins check the plug-ins that are installed on your system. Also verify the type of plug-in that you have i.e. if you have plug-in file which is for installation or if it is for upgrade. If the file that you is for upgrade then be sure to have the earlier version of the plug-in and its related patches installed in the system prior to applying the upgrade plug-in. If you are updating the plug-in then verify that the earlier lower version of the plugin and its patched are already installed in the system. For example, 4.6B IDES system comes with PI_1_1999. The plug-in PI_A_1999 is also already applied. If the PI_1_1999 plug-in is not installed then you will have to install it and its two patches first before applying PI_1_2000 plug-in. The following process shows you the steps for applying plug-ins. 1. You should apply the plug-ins in client 000 as any other user other than SAP* or DDIC. Create a user in client 000 with SAP_ALL profile. 2. Log on the client 000 as the newly created user. 3. Execute the transaction SAINT 4. Upload the plug-in by going thru the menu, 5. Once the files are uploaded. You will get two boxes on the screen. The top box will contain the list of Plug-ins already applied in the system. The bottom box will contain the list of plug-in, which are available to be applied. 6. Select the plug-in PI_1_2000 from the second box and click on the Continue button. 7. In the next screen put the cursor on the Plug-in box and click on the Continue button 8. After the plug-in is installed successfully, you will be asked to do SPAU checks or Continue. Click on Continue icon. 9. After that you will get the 4th screen of the SAINT process, click FINISH on the screen that you get. 10. After the plug-ins is installed, apply patches for the plug-in using the transaction SPAM. (The process is described in the previous section). Tell me about Phases in Support Packs/Add On ? The following list explains the phases executed by the Add-On Installation Tool in the order in which they are performed. 1. PROLOGUE Initializes installation 2. CHECK_REQUIREMENTS Checks the Change and Transport System

3. DISASSEMBLE_PATCH Decompresses the OCS packages 4. ADD_PATCH_TO_BUFFER: Creates import buffer for the installation 5. IMPORT_OBJECT_LIST Imports object lists of the OCS packages into the database 6. OBJECTS_LOCKED_? Checks if objects to be imported are in open transport requests 7. SCHEDULE_RDDIMPDP Checks if the job RDDIMPDP is scheduled properly 8. ADDON_CONFLICTS_? This phase exists only when you install or upgrade add-ons (not for PCS). It checks for object conflicts with imported Support Packages that have a higher version than is specified in the import prerequisites for the add-on. If another add-on is already installed, SAINT checks whether there are conflicts between this add-on and any Support Packages that were included as import prerequisites for the new add-on. It also checks whether the new add-on has direct object conflicts with the add-on that is already installed. 9. CREATE_VERS_BEFORE Creates versions for the objects of the OCS packages in the installation queue (if this option has been selected) 10. SPDD_SPAU_CHECK This phase exists only when you install or upgrade add-ons (not for PCS). Checks if an SPDD/SPAU adjustment is necessary 11. DDIC_IMPORT This phase exists only when you install or upgrade add-ons (not for PCS). Imports the Dictionary objects 12. AUTO_MOD_SPDD This phase exists only when you install or upgrade add-ons (not for PCS). SAP Add-On Installation Tool (BC-UPG-OCS) SAP AG 20 November 2001 Checks if Dictionary objects can be automatically copied 13. RUN_SPDD_? This phase exists only when you install or upgrade add-ons (not for PCS). Starts transaction SPDD, if necessary 14. DDIC_ACTIVATION Activates the imported Dictionary objects 15. IMPORT_PROPER Activates and imports all remaining objects 16. AUTO_MOD_SPAU This phase exists only when you install or upgrade add-ons (not for PCS). Copies the automatically adjustable objects 17. ABAP_GENERATION Generates the runtime objects for the imported Repository objects (ABAP source code,screens) 18. RUN_SPAU_? This phase exists only when you install or upgrade add-ons (not for PCS). Starts transaction SPAU, if necessary 19. EPILOGUE Registers the add-on On which Version have u applied support packs? SAP 4.6C,4.7 E.E Have u faced any Issues while Appling support packs ?

 Single Baground process system hang NO Space in Trans/EPS/IN error No Space in DB Sequence Not Maintained Errors More than 10 MB size patch applied in frond end -system hang Conflicts between the support packages and add-ons TP not configured No authorization to apply packs (DDIC authorization required default client 000) Some of the Possible Errors during Support Package Application The solutions provided below may or may not work for you. They worked for me under the circumstances that I got these errors. CANNOT_CREATE_COFILE If while applying a patch, you get an error CANNOT_CREATE_COFILE delete the concerned file of the patch from the /usr/sap/trans/cofile and /usr/sap/trans/data directory. After deleting the files restart the process. The patch application may work EPS in IS IN OLD FORMAT If you are unable to upload the queue and you see a message like EPS in IS IN OLD FORMAT , check for the SPAM version and do a SPAM update. Delete the concerned files (i.e. the .ATT and .PAT files from the /usr/sap/trans/EPS/in directory) and then decompress the .CAR file and continue with applying the support packs. OBJECTS_LOCKED_? There are also times when a patch will fail because an object that it is trying to modify is locked by a change request. In such cases, identify the object and the change request and then using SE03 search for the object. Once you have identified the change request unlock the object and then Continue with the SPAM transaction. Sometimes the SPAM/SAINT Update process comes out with error. In such case just go ahead and start the SPAM update process again and it should go through fine. What authorizations do u require for applying support packs/ add on? DDIC Authorization required. Ensure that apply in 000 client To use all the functions of the SAP Add-On Installation Tool, you require the following authorizations: S_TRANSPRT S_CTS_ADMIN Both authorizations are in the authorization profile S_A.SYSTEM. Assign this authorization profile to the system administrator only. What types of ABAP Dumps do u regularly get in your monitoring ?

TIME_OUT The program has exceeded the maximum permitted runtime and has therefore been terminated. RAISE_EXCEPTION A RAISE statement in the program "--------- raised the exception condition "-----".Since the exception was not intercepted by a superior program in the hierarchy, processing was terminated. CONVT_NO_NUMBER The current ABAP/4 program "-------- had to be terminated because one of the statements could not be executed MESSAGE_TYPE_X

The current application program detected a situation which really should not occur. Therefore, a termination with a short dump was triggered on purpose by the key word MESSAGE (type X). Diagnosis An error occurred during a comparison of the Control Framework data between the SAP Front-end and the application server. This error is very probably due to an error in the front-end software installation or an obsolete version.

Procedure Reinstall your front-end software or inform your system administrator. If the error continues to occur even if the front-end is correctly installed, you should inform SAP, including details of how to reproduce the error. SYSTEM_NO_ROLL Each transaction requires some main memory space to process application data. If the operating system cannot provide any more space, the transaction is terminated. CALL_FUNCTION_WAIT_ERROR "Connection closed" An error occurred when executing a Remote Function Call. There is an error in the communication system. To clarify and resolve the error, contact your system administrator. DBIF_RSQL_SQL_ERROR SQL error 1555 occurred when accessing table Database error text........: "ORA-01555: snapshot too old: rollback segment. What are the different Memories Available in SAP?

Tell me the Extensions of the files generated after uncar of support packs using sapcar? .ATT and .PAT What is the Hierarchy for Appling support packs? Basis,ABAP,Appl.HR