You are on page 1of 13

Support Packages 1. How do you apply support packages? Ans: Support packages are apply through SPAM 2.

What is SPAM? Ans: SPAM is a tool and has its own Version and it is used to applied to fix the bugs, error codes try to fix and provide additional functionality. Suport packages have their own released Life cycles. 3. What are the types of the support packages available? Ans: There are various types of support packages are available which nedds to be applied based on the requirement. These are 1. Basis Support Package which has the naming convension of SAPKB 620005(here KB represents Basis and 620 represents Release and 05 represents support pach no or package no) ABAP Ans: There are various types of support packages are available which nedds to be applied based on the requirement. These are 1. Basis Support Package which has the naming convension of SAPKB 620005(here KB represents Basis and 620 represents Release and 05 represents support pach no or package no) ABAP : SAP KA 620 05 ( KA ABAP, 620: Basis release / Web as release and 05 indicates package/patch no) APPL: SAP KH 470 05(470 r/3 release) HR: SAPKE 470 05

Note: all the above support patches needs to be applied in the same sequence ie BASIS ABAP APPL HR ( first priority for basis, second abap third appl and last hr) 4. Pre requisitions to applying Support Packages and Patches? Login into 000 clnt as ddic Configure TMS Ans: 1. Update SPAM/SAINT version both carry same version (Saint means sap add-on installation tools) 2. Support packages should be applied in the sequence 3. There should not be any aborted/terminated support packages 4. There should be enough space in the Trans/eps/in eps: electronic Parcel services 5. Support packages can be applied either through front end or through application server. 6. If the support packages is greater than 10 MB apply through application Server. 7. If the support package is less than 10 MB apply through GUI 8. Apply the patches in the sequence of Land scape. 9. Download the composite note from sapmarket place known problems related to supportd packaes of release 620/700/47 10. uncar the files the down loaded files are with the extension .CAR 11. . CAR : compressed archive this files needs to be uncared by SAPCAR_XVF, SAKB62051.CAR 12. SAPCAR_XVF 13. Reserve 2 no of background work process. 14.for executes all trans requests automatically TP- works ( ensure that RDDIMPDP is scheduled in 000 client with user DDIC

15.Based on the composite note a group of support patches / packages cab be applied together. 16. Ensure that conflict packages are applied separately SAPKB 62005 SAPKB 62008 62009 620012 62013 Conflict packages ie we should go through note completely. 17. UPGRADE the Kernel based on the recommendations from the composite notes. 18. Functional consultants and technical consultant should be around to apply support packages 19 there should be enough space in the Data Base 20. All the support packages should be applied sequentially ie number sequence should be followed. Ie 1,2,3, 18,19,20 21) SPAM/SAINT can be applied in a orbitary order ie 05,06,07,08,09,10 22) Different packages are related to different transactions respective transactions . Hence support packages should follow sequential manner. II APPLYING SUPPORT PACKAGES: Go to www. Select support packages and patches Go to my components Select the patch to down load 62007 can apply at a time

2. If the size is less than 10 mb download from your desktop else download in application server or down load from nearest source and transfer to application server. 3.Most of the patches come with .CAR extension UNCAR the file using sapcar_xvf 4. After imcar eps\in directory will be created in the current

directory or 5. copy the .CAR file in to usr/sap/trans and uncar it, the files will be uncared into \eps\in directory. 6. Files with extention .ATT and .PAT are extracted into \eps\in directory. .ATT PAT Attributes of patch is patch files.

7. Go through the composite note and define the que ie 05,06,07,08,09,10 are together like bundle and for ex. Conflict packages canot go along this bundle 8. Go to SPAM 9.UPDATE SPAM/SAINT apply support packages. 10. UPDATE: SPAM/SAINT: upload(load the .CAR file using front end always the tool is not more than 5 MB Already downloaded on desktop Load through front end from the file EXECUTE The file is uploaded in to \eps\in directory Select the file in to Que Goto Menu Click on Import SPAM/SAINT update

SAM/SAINT version is updated and the current screen will become blank \n SPAM Apply Support Packages: Go to SPAM Load through application server The files PAT, ATT loaded in to tables PAT01 and PAT03 Select the new support packages and define the Que based on composite note Click on Import Que, the patches sart applying on the system some times the patch stops with traffic signals Red. Go to the Menu Click on Ignore errors and start the Import, Import will start from the point where it stops. Some times patch may stop due to the following errors:Go to Import logs in-------Some of the following are the errors like ORA-1653 and ORA-1654 table space overflow add data file reside data file. RDD*Jobs could not be started (schedule in ))) client user DDIC) Memory insufficient ORA.1631 and ORA1632 Maximum extents reached the table hence, sapcar_xvf KB increase extents. TP- Outdated (need to update TP) Confilict between support packs (apply notes) Conflict between Add-On and support package apply CRT conflict resolution table

Once the issue is resolved, Import the Que again and confirm the Que. Ensure that the light is Green colour not even Yellow.

CRT: Conflict Resolution transports(addons, plugins, very rare all these) CRTs these are released to resolve the conflict between Addon and Support Packs: 1 Copy these CRTs in to the Trans directory 2 Add to Buffer 3 Import.


It is a process of replacing the executables. With newer version executables. Kernal version can be find in system status or disp+work command on a command on a command window gives us the Kernal version Kernal needs to be upgraded / updated time to time based on the requirement Kernal upgrading required in the following circumstances: during the implimentation during the upgrade during the support package application to fiz the bugs in the system during the O/S upgrade or Database upgrade.

Process of upgrade Kernal: Download latest Kernal from\swdc Sapkernal 32 bit 6.40 version Sapkernal 64 bit 6.40 version

There are 2 no of files abavilabel: Database dependent : SAPEXE-DB0809.Sar Database independent SAPEXE0809.sar

Uncar the file SAPCAR_XVF.sapexesar Into a new run directory (date & time) Newrun040607 Usr\sap\sid\sys\exe\run\newrun 040607 1. Schedule downtime 2. stop the system and all the services manually 3. copy existing run to old run (time stamp) now a new directory

4. usr/sap/<sid>\sys\exe\run\oldrun040607 5. copy all executables from newrun to run directory 6. it will prompt to over write the executables clock on OK to continue 7. start the system 8. login to system 9. execute SICK 10. if you could not loin or if the system could not start if the problem resolved with in downtime if not revert back to old Kernal. ADDONs and PLUGINS ADDONs and PLUG-INS are used to provide additional functionality ie addl. Component to the existing system Eg example fo plugins are: ST_PI BI_cont XI-Cont Solution tools pluin for early watch support to provide preconfigural business content and roles to provide preconfigured XI content roles

VIRSASAP Security Compliance tool Fabrication and all Industry specific solutions.

Process of applying ADD Ons Go to Marketplace and download the addon or copy from the DVD in to trans directory And all pre-requisites apply same and load the package through application server. Select the package click on load Select the package click on continue to install the ADD ON

It will stop and request you to read the note and specify request to a password to key-in to continue to install the Add-on It will stop and request you to read the note and specify request to a password to key-in to continue. Get the password /key work from the note and key in the password to continue the Addons. Addons should be displayed in the status Notify the functional consultants to work on the ADDONs Please do not believe other consultants while reading note.

NOTES NOTES provides Bug fixes program enhancements, Information or manual corrections. Notes are of 3 types corrections. Notes are of 3 types 1. Automatic correction of standard programmes without changing the Basic structure and without object Access key / SSCR key Notes can be reverted back because, they insert the new code and comment the existing code, where as support packages over writes the code. Notes are applied through SAP NOTE ASSISTANT; SNOTE is the transaction to apply the notes. This is available by default from R/3 4.7 version onwards but for earlier versions we need to down load SNOTE.

APPLYING SNOTE Go to Download the note to desktop, it is in KB upload the note (select the note and click on upload note) the status of the note is New Select the note and Implement the note, while implementing the status is in processing with note is apply the status is implemented. If the note is outdates the status is obsolete.

Note: When the note cant be applied the status can be inconsistent.

SPDD & SPAU While applying Support packages and patches the phases SPDD and SPAU prompts 1 A+b=25 using the functionality defined my own programs A+b=27 Change related to DATA Dictionary SPDD phase will come ie functional and Basis should present while Appling support packages. 2 /*A+b=25*/ old A+b=27 SPDD Phase: When there is a change in a data dictionary element, this phase needs to be executed in functional consultant needs to decide

whether to keep existing functionality or to enhance to the functionality coming through Supt package. If a note is applied we need to specify to keep the changes which came to the note. SPAU Phase This is similar to SPDD but only for the repository objects and standard programs. Manual corrections: It is used to provide a detailed information related to customizing changes like updating LOGOS, changing table entries, creating table entries like country name, country time etc; INFORMATIVE NOTE: this note provides valuable information and sometimes program resolutions eg: release notes, patch information composite notes, Installation known problems etc. SAP MARKET PLACE: It is portal which is built on sapweb application platform / webas plat form and provides the following services. 1. 2. 3. 4. 5. 6.\notes\swdc for software development course\inst guides\sp-stacks\spsolution manager\sap netweaver 04 s,sr1,sr2 7.\PAM If it is used to generate the following keys 1. Licence Keys 2. Developers keys 3. SSCR key 4. Migration key 5. User data Registering Users: 6. System data : Registering system 7. Rampup Activity 8. Opening connections to SAP 9. Create customer messages 10. Quicklinks 11. Online shop LICENCE KEY: Generation i. Customer no

Installation no Hardware key System host name, instance no, OS/DB Click on generate Licence key

ii. iii. iv.




Developers key: select SID Click on register developer : 4000$ need to pay Name of the developer and register SSCR Key: for each object sap software change registering key, 3 entries we need to give in SSCR key Prog. ID Prog Type Programme<ID,Type,Name> Once the programe is unlocked it is available for all the developers to work on it. Migration Key: Select the source system <SID><><host> Provide the target system: O/S, DB,Kernal,R/3 Version etc Migration keys are required when we are moving or migrating from one operating system to other operating system or one database system to another database system USER DATA: Note: O/S , D/B Migration has to be carried by a certified OS and Data base Consultant 2. 1.SAP provides a super admin when we purchase the software. This super admin is allowed to create additional market place users and also assign authorizations based on the requirements. This is only S user ID 3. System Data: As part of post Installantion activity we need to register our system with SAP, sot that we can generate the keys, create messages for support, create new system >system data> specify system ID, hostname, instance no, OS, DB, R/3 release and version and save. 4. RAMPUP: <Opportunity to work on components before they are released> It provides an opportunity to work on components before they are released (alpha, beta versions)

5. Opening connections to SAP: In order to get remote support from SAP our system has to open remotely provided that SAP routeres configured. Select the system Click on open connection to SAP Specify the date of closing the connection 6. Create customer Message: Click on create customer message Create customer message Enter the message and search for the resolution SAP displays list of notes Click on continue to message Enter the message and select priority(low, medium, high, very high: production down performance/bottlenecks 7. SAVE and SEND it to SAP 8. close the message after resolution QUICK LINKS: It provides an Index Alpha betically so that user can navigate to the functionality in one step. ONLINE SHOP: It is used to order the software and other online products.