What is mean by OSS how to work on that?

OSS are online sap support notes. These notes are available online for solving critical problems in sap system.We may use the already existing notes or may add our own quaries.

In order to apply any OSS note, you have to be authorized by your company and be assigned an OSS ID and password.

For any SAP standard program modification, you are required to login to OSS and request for a repair program Access key.

Access the SAP Support Portal:

http://service.sap.com/

- Keys and Requests

-- Request license key

--- Follow the Steps 1 to 5 of the License keys for SAP Business Suite

--------------

Follow this step to obtain the Program Access key:

Menu Path: System -> Services -> SAP Service (Transaction code OSS1)

Login in with your OSS ID and Password

Click the Registration button

Click Register Object

Double click R/3 Value Contract

Fill in the Object Registration for Installation:

For e.g.
PGMID/Object/Name: R3TR FUGR MIGO
SAP release: 46C

Finished, click the Register button

Select the Key number and use the Copy and Paste short key to copy the Access key

You are now able to modify the SAP standard program.

Finished the modification, do remember to transport it to the production system after all the necessary testing.

What is SNOTE? How to import the OSS notes?

SNOTE (SAP Notes Assistant) is available in SAP 4.6c after a plug-in and is by default from SAP 4.7EE. Using SNOTE transaction code, you can directly install the Recommended Code changes in SAP system. It creates a transport request which can be imported later on in the Quality and Production systems.

The advantage of SNOTE is that you need not get the notes added in the individual systems and can have the change moved in to all the systems as per the guidelines.

There are two ways to import the OSS Note (SAP Notes).

1. Download the Correction to your system and import it.
2. Directly download from SNOTE transaction code (Only available from SAP 4.6c)

Visit the following links:

http://help.sap.com/saphelp_nw04/helpdata/en/b8/3cf839fd35384de10000000a11402f/content.htm

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/7b1d5312-0d01-0010-7bbb-c819a4579f58

I did not find any OSS notes appropriate for my problem or bug. What i have to do?

If the OSS notes displayed are not helpful to solve your problem. You can write to
SAP Service describing your problem. You problem will be answered by SAP
Support team.

How to apply OSS notes number?

Before applying OSS notes number into your SAP system. You need to check
whether it is already implemented in your SAP system or not. If it is not
implemented you can go ahead.

There are some OSS notes, which we should implement manually, that means
we need to change the code in the programs/objects ourselves according to the
steps mentioned in the problem.

What is OSS Notes number?

After entering into SAP notes search, you can search for the problem using
keyword appropriate for your problem. If you have specific OSS notes number with
you, then you can directly enter the OSS notes number and you can see the Notes
explanation.

Where can i access SAP OSS?

Where can i access SAP OSS?
Log on to www.service.sap.com. Under the SAP Support Portal, click on SAP
notes search.


Do i need user ID and password to enter into the OSS?
Yes, you need an User ID and Password to enter into the site. It will be provided by
the BASIS Team in the Project. When they create SAP User ID, they will create
OSS notes ID also. You can also register individually in the site.

WHAT IS OSS

OSS stands for On-line Service System.
What is the use of OSS?
In day-to day business customers who are using SAP software encounters
problem or bugs with SAP software. To resolve the issues faced by customers
SAP has provided an on-line solution.
What? SAP software is having problems or bugs? Yes, any software product is not
100% pool-proof. SAP is continuously updating the versions for better
performance and options.

OSS and SAProuter

SAProuter is a program that functions as an intermediate station between SAP Systems or programs. SAProuter functions as an application-level gateway (proxy) that enables and regulates access to SAP through the SAProuter port. SAProuter allows you to connect to an SAP System without a direct network connection between the client computer and the application server. The SAPGUI connects to the SAProuter that forwards all the packets to the application server or to another SAProuter. This enhances security because the link to other applications does not have to be open. ...more

Apply Support Packs To My SAP SYSTEM

How can I apply support packs to my 4.7 IDES SYSTEM?
SAP"- SAP R3 4.7EE,
DATABASE : ORACLE 8.1.7
OS : WINDOWS 2003 SERVER
What is the step by step procedure and how to apply in r/3?

You have various issues with your setup:

- Oracle 8.1.7 is not supported under Windows 2003
- Oracle 8.1.7 is out of maintenance since three years

During SP application you will maybe run into problems that can't be
fixed since your installation is just too old and unsupported. *-- Markus

As mentioned, it's true that it won't get supported on Oracle 8. The best combination would be with 9i

Any How I have mentioned the steps below to apply for patches.

To Apply Support packs first up all you need to download the patches. When you have the downloaded the file i.e.. (*.car ) patch file then you can extract and apply it in two ways.

1. Go to command prompt through cmd (if you are using windows) and go to the folder where you have download these files ( could be in \downloaded folder\ ) type this command on command prompt without quotes "sapcar -xvf .sar". Now it will create a folder called EPS and a folder called IN inside EPS. Go to this folder and it will show two extracted files with extension " .att " and " .pat ". Copy this two files into yours trans\eps\in folder which could be something like \usr\sap\trans\eps\in folder.Then type spam on your session and navigate to Support Package\Load Package\From Application Server and it will ask for Path confirm it Say " YES"Select the patch imported and double click on it and then click on small truck Icon and it start Import.

2. Type Spam on session then navigate to Support Package\Load Package\From FrontEnd \ and Navigate to path where you have downloaded the *.SAR file of Support Pack.Now it will open a popup window and then click on decompress button ( It is front-End process for extracting or decompressing .sar file in .pat and .att extension ) After that click on Display-Define button on right hand side.) Select the BASIS or ABAP patch ( whichever you are applying *) what ever you are after and import it in queue. After that click on Small truck Icon in menu i.e.. (import Queue) and it Starts importing.
*-- Deepanshu Sharma
* Note :- Basis patch starts with KBxxxx.sar and Abap Patch start with KAxxxx.sar likewise.
* Note :- If you are applying all support pack it may ask you to increase your spam level (SUPPORT PACK MANAGER).

Reporting a Problem to SAP

When I tried to report a problem to SAP using
http://service.sap.com/message url it provided 4 steps to follow:

1) Choose system
2) Prepare Solution Search
3) Find Solution
4) Enter Message

I could do the step 1 but dont know what to do at steps 2, 3 and 4.

SAP changed the customer message screens so you now have to navigate through a search of the SAP Notes before being able to create a message.

We usually search the Notes extensively before we create a message, so we just enter a blank search and then go on to create the message.

Follow the steps, It may solve your problem:

1. Copy following url into web browser : http://service.sap.com/message

It will ask you for your OSS ID and password .
A Screen which contain a push Button Select System displayed .

2. Push the Button Select System .
It will open a sub screen in which there will be a hierarchical structue which looks like

-
-

+
+

Here + indicate that you have a sub tree .
Specific product like SAP R/3 T for Services , SCM , CRM , ERP etc

3. Select the system for which you need to log a message
It will take you to message screen screen.

4. Select you domain for problem for example Basis problem with Database where dataBASE IS oracle then Message type will be BC-DB-ORA
* .
5 Select priority of Message

6 . Write Message and send it to SAP

SAP Transaction code to pre-compile all system program

If I have to run SGEN and have to recycle the server as well for clearing out memory, does it make sense to run SGEN first and recycle afterwards, because SGEN will sort of litter the memory or is it inconsequential what runs first.

SGEN is ued to "compile" ABAP programs. Results are put in database.

So, if you restart SAP, compiled results will still be in the database, so, no need to run SGEN again.

Make use of the transaction 'SGEN' to re-generate all the SAP programs after you change version of your SAP kernel, upgrade SAP system or apply support packages.

Do take care of the table spaces and use SAPDBA to observe them.

Do it during a weekend which is the best or a period of time with very very low users activity.

It will takes about 5 to 8 hours depending on the type of hardware configuration you are using.

How to know the kernel version of a SAP R3 system?

-----Original Message-----
Subject: How to know the kernel version of a SAP R3 system

Hi all

Could someone tell me how can I find the Kernel version of a SAP R3 system ?
example, for those releases
SAP R3 4.0B, 4.5B, 4.6B, 4.6D and so on ....

Thanks for your help

-----Reply Message-----
Subject: RE: How to know the kernel version of a SAP R3 system

From any screen choose System-->Status then click the 'other kernel info' icon (between Navigate and Cancel).
The same information can be found at OS level in the dispatcher trace file: /usr/sap///work/dev_disp.
Regards,

-----Reply Message-----
Subject: RE: How to know the kernel version of a SAP R3 system

Hi,

Goto transaction sm51, and click (not double click) on the the Database
server and then click on release notes. there you will see the SAP R/3
kernel and patch level etc.

Regards

-----Reply Message-----
Subject: RE: How to know the kernel version of a SAP R3 system

You can use the System ==> Status and then Other
Kernel Info button to get the details about the Kernel
Release, Patch levels etc.

Regards,

-----Reply Message-----
Subject: RE: How to know the kernel version of a SAP R3 system

I think an even more convenient way to do this is to use SM51. Highlight
the server you are interested in and click on "Release Information". This
provides you a location to view all servers with out logging on to each
one. The answer below will give you information about the server you are
connected to only.

-----Reply Message-----
Subject: RE: How to know the kernel version of a SAP R3 system

Also try "disp+work -v" on server.

-----Reply Message-----
Subject: RE: How to know the kernel version of a SAP R3 system

go to transaction SM51 -->release information

-----End of Message-----

Useful SAP System Administration Transactions

AL01  SAP Alert Monitor
AL02  Database alert monitor
AL03  Operating system alert monitor
AL04  Monitor call distribution
AL05  Monitor current workload
AL06  Performance: Upload/Download
AL07  EarlyWatch Report
AL08  Users Logged On
AL09  Data for database expertise
AL10  Download to Early Watch
AL11  Display SAP Directories
AL12  Display table buffer (Exp. session)
AL13  Display Shared Memory (Expert mode)
AL15  Customize SAPOSCOL destination
AL16  Local Alert Monitor for Operat.Syst.
AL17  Remote Alert Monitor for Operat. Syst.
AL18  Local File System Monitor
AL19  Remote File System Monitor
AL20  EarlyWatch Data Collector List
AL21  ABAP Program analysis
AL22  Dependent objects display
CREF  Cross-reference
BD64
BSVW  Linkage Status Update-Workflow Event
CMOD  Enhancements
DB01  Analyze exclusive lock waits
DB02  Analyze tables and indexes
DB03  Parameter changes in database
DB11  Early Watch Profile Maintenance
DB12  Overview of Backup Logs
DB13  Database administration calendar
DB14  Show SAPDBA Action Logs
DB15  Data Archiving: Database Tables
DB16  DB System Check: Monitor
DB17  DB System Check: Configuration
DMIG  Start Transaction for Data Migration
DB2   Select Database Activities
DB20  DB Cost-Based Optimizer: Tab. Stats
DB21  DB Cost-Based Optimizer: Config.
DB24  Database Operations Monitor
DB26  DB Profile:Monitor and Configuration
DB2J  Manage JCL jobs for OS/390
DBCO  Database Connection Maintenance
FILE  Cross-Client File Names/Paths
NACE  WFMC: Initial Customizing Screen
OAA1  SAP ArchiveLink: Maint.user st.syst
OAA3  SAP ArchiveLink protocols
OAA4  SAP ArchiveLink applic.maintenance
OAAD  ArchiveLink Administration Documents
OAC2  SAP ArchiveLink: Globaldoc. types
OAC5  SAP ArchiveLink: Bar code entry
OACA  SAP ArchiveLink workflow parameters
OAD0  SAP ArchiveLink: Objectlinks
OAD2  SAP ArchiveLink document classes
OAD3  SAP ArchiveLink: Link tables
OAD4  SAP ArchiveLink: Bar code types
OAD5  SAP ArchiveLink: Customizing Wizard
OADR  SAP ArchiveLink: Print list search
OAM1  SAP ArchiveLink: Monitoring
OAOR  SAP ArchiveLink: Storeddocuments
OARE  SAP ArchiveLink:St.syst.return codes
OS01  LAN check with ping
OS03  O/S Parameter changes
OS04  Local System Configuration
OS05  Remote System Cconfiguration
OS06  Local Operating System Activity
OS07  Remote Operating SystemActivity
OSS1  Logon to Online ServiceSystem
OY18  Table history
OY08  Development Class Overview
PFCG  Activity Group
PFUD  Authorization Profile comparison
RLOG  Data migration logging
RZ01  Job Scheduling Monitor
RZ02  Network Graphics for SAP Instances
RZ03  Presentation, Control SAP Instances
RZ04  Maintain SAP Instances
RZ06  Alerts Thresholds Maintenance
RZ08  SAP Alert Monitor
RZ10  Maintenance of profile parameters
RZ11  Profile parameter maintenance
RZ12  Maintain RFC Server Group Assignment
RZ20  CCMS Monitoring
RZ21  Customize CCMS Alert Monitor
SA38  ABAP/4 Reporting
SAD0  Address Management call
SADC  Address: Maint. communication types
SALE  Display ALE Customizing
SAINT Plug-in Installation
SARI  Archive Information System
SAR3  Customizing Archiving
SAR4  Define Archiving Class
SAR5  Assign Archiving Class
SAR6  Archiving Time Generator
SARA  Archive management
SARL  Call of ArchiveLink Monitor
SARP  Reporting (Tree Structure): Execute
SART  Display Reporting Tree
SB01  Business Navigator - Component View
SB02  Business Navigator - Process flow vw
SBAS  Assignments to Process Model Elemts
SC38  Start Report Immediately
SCAT  Computer Aided Test Tool
SCC0  Client Copy
SCC1  Client Copy - Special Selections
SCC2  Client transport
SCC3  Client Copy Log
SCC4  Client administration
SCC5  Client Delete
SCC6  Client Import
SCC7  Client Import – Post Processing
SCC8  Client Export
SCC9  Remote Client Copy
SCCL  Local Client Copy
SCDO  Display Change DocumentObjects
SCMP  View / Table Comparison
SCOM  SAPcomm: Configuration
SCON  SAPconnect - Administration
SCPF  Generate enterprise IMG
SCPR1 Customizing Profiles : Maintenance Tool
SCPR2 Comparing Customizing profiles
SCUA  Central User Administration : Distribution Model Assigment
SCUG  Central User Administration Structure Display
SCUL
SCUM  Central User Administration Field Selection
SCU0  Table Analyses And Comparison
SCU1  Table Comparison - Export to Tape
SCU2  Table Comparison Against Tape
SCU3  Table History
SD11  Data Modeler
SDBE  Explain an SQL Statement
SECR  Audit Information System
SE01  Transport and Correction System
SE02  Environment Analyzer
SE03  Transport Utilities
SE06  Set up Workbench Organizer
SE07  Transport System Status Display
SE09  Workbench Organizer (Initial Screen)
SE10  Customizing Organizer
SE11  Data Dictionary Maintenance
SE12  Data Dictionary Display
SE13  Maintain Technical Settings (Tables)
SE14  Convert Data Dictionary tables on Database Level
SE15  Repository Info System
SE16  Display Table Content
SE17  Generate Table Display
SE30  ABAP Objects Runtime Analysis
SE32  ABAP Text Element Maintenance
SE33  Context Builder
SE35  ABAP/4 Dialog Modules
SE36  Logical databases
SE37  ABAP Function Modules
SE38  ABAP Editor
SE39  Splitscreen Editor: Program Compare
SE40  MP: Standards Maint. and Translation
SE41  Menu Painter
SE43  Maintain Area Menu
SE51  Screen Painter
SE52  Parameterized screenpainter call
SE54  Generate table view
SE55  Internal table view maintenance call
SE56  internal call: display table view
SE57  internal delete table view call
SE61  R/3 Documentation
SE62  Industry Utilities
SE63  Translation: Initial Screen
SE71  SAPscript form
SE72  SAPscript Styles
SE73  SAPscript font maintenance (revised)
SE74  SAPscript format conversion
SE75  SAPscript Settings
SE76  SAPscript: Form Translation
SE77  SAPscript Translation Styles
SE78  SAPscript: Graphics administration
SE80  Object Navigator
SE81  Application Hierarchy
SE82  Application Hierarchy
SE84  R/3 Repository Information System
SE85  ABAP/4 Repository Information System
SE86  ABAP Repository Information System
SE88  Development Coordination Info System
SE89  Maintain Trees in Information System
SE91  Maintain Messages
SE92  New SysLog Msg Maintenance as of 46A
SE93  Maintain Transaction Codes
SE94  Customer enhancement simulation
SE95  Modification Browser
SEPS  SAP Electronic Parcel Service
SERP  Reporting: Change Tree Structure
SEU   Repository Browser
SF01  Client-Specific File Names
SFAW  Field Selection Maintenance
SIAC1 Web Object Administration
SHDB  Record Batch Input
SICK  Installation Check
SIN1  SAPBPT: Inbox
SINA  SAPBPT: Maintain Standard Config.
SLG0  Application Log: ObjectMaintenance
SLIN  ABAP: Extended Program Check
SM01  Lock Transactions
SM02  System Messages
SM04  User Overview
SM12  Display and Delete Locks
SM13  Display Update Records
SM14  Update Program Administration
SM21  System log
SM23  System Log Analysis
SM28  Installation Check
SM29  Model Transfer for Tables
SM30  Call Up View Maintenance
SM31  Table maintenance
SM31_OLD  Old Table Maintenance
SM32  Maintain Table Parameter ID TAB
SM33  Display Table ParameterID TAB
SM34  Viewcluster maintenancecall
SM35  Batch Input Monitoring
SM36  Batch request
SM37  Background job overview
SM38  Queue Maintenance Transaction
SM39  Job analysis
SM49  Execute Logical Commands
SM50  Work Process Overview
SM51  List of SAP Servers
SM54  TXCOM maintenance
SM55  THOST maintenance
SM56  Number Range Buffer
SM58  Asynchronous RFC Error Log
SM59  RFC Destinations (Display/Maintain)
SM60  Borrow/Return Objects
SM61
SM62
SM63  Display/Maintain Operating Mode Sets
SM64  Release of an event
SM65  Background Processing Analysis Tool
SM66  System-wide Work Process Overview
SM67  Job scheduling
SM68  Job administration
SM69  Display/Maintain Logical Commands
SMEN  Dynamic menu
SMGW  Gateway Monitor
SMLG  Maintain Logon Group
SMLI  Language import utility
SMLT  Language transport utility
SMOD  SAP Enhancement Management
SMT1  Trusted Systems (Display <-> Maint.)
SMT2  Trusting systems (Display <->Maint.)
SMW0  SAP Web Repository
SMX   Display Own Jobs
SNRO  Number Range Objects
SO02  SAPoffice: Outbox
SO03  SAPoffice: Private Folders
SO04  SAPoffice: Shared Folders
SO05  SAPoffice: Private Trash
SO06  SAPoffice: Substitutionon/off
SO07  SAPoffice: Resubmission
SO10  SAPscript: Standard Texts
SO12  SAPoffice: User Master
SO13  SAPoffice: Substitute
SO15  SAPoffice: DistributionLists
SO16  SAPoffice: Profile
SO17  SAPoffice: Delete Shared Trash
SO18  SAPoffice: Shared Trash
SO19  SAPoffice: Default Documents
SO21  Maintain PC Work Directory
SO22  SAPoffice: Delete PC Temp. Files
SO23  SAPoffice: DistributionLists
SO24  SAPoffice: Maintenance of default PC
SO28  Maintain SOGR
SO30  SAPoffice: Reorg.
SO31  Reorganization (daily)
SO36  Create Automatic Forwarding
SO38  SAPoffice: Synchr. of Folder Auths.
SO40  SAPoffice: Cust. LayoutSet MAIL
SO41  SAPoffice: Cust. LayoutSet TELEFAX
SO42  SAPoffice: Cust.Layout Set TELEFAX_K
SO43  SAPoffice: Cust.Layout Set TELEFAX_M
SO44  SAPoffice: Cust. LayoutSet TELEX
SO70  Hypertext: Display/Maint. Structure
SO71  Test plan management
SO72  Maintain Hypertext Module
SO73  Import graphic into SAPfind
SO80  SAPfind: Free Text Retrieval Dialog
SO81  SAPfind: Free Text Indexing (Test)
SO82  SAPfind: Free Text Retrieval Batch
SO95  Pregenerated Search Queries - Selec.
SO99  Put Information System
SOA0  ArchiveLink Workflow document types
SOBJ  Attribute Maintenance Objects
SOLE  OLE Applications
SOLI  Load OLE type info
SOPE  Exclude Document Classes
SOTD  SAPoffice: Maintain Object Types
SOY1  SAPoffice: Mass Maint. Users
SOY2  SAPoffice: Statistics data collect.
SOY3  SAPoffice: Statistics Evaluation
SOY4  SAPoffice: Access overview
SOY5  SAPoffice: Inbox overview
SOY6  SAPoffice: Document overview
SOY7  SAPoffice: Folder overview
SOY8  SAPoffice: Mass Archiving
SOY9  SAPoffice: Inbox Reorg.
SOYA  SAPoffice: Change folder owner
SP00  Spool and Relate Area
SP01  Spool Control
SP02  Display output Requests
SP03  Spool: Load Formats
SP11  TemSe Contents
SP12  TemSe Administration
SPAD  Spool Management
SPAM  SAP Patch Manager (SPAM)
SPAU  Display Modified DE Objects
SPCC  Spool Consistency check
SPDD  Display Modified DDIC objects
SPHA  Telephony administration
SPIC  Spool : Installation Check
SPRM  Current Customizing
SPRO  Customizing
SQ01  SAP Query: Maintain queries
SQ02  SAP Query: Maintain funct. areas
SQ03  SAP Query: Maintain user groups
SQ07  SAP Query: Language comparison
SQVI  QuickViewer
SSAA  System Administration Assistant
SSCA  Appointment Diary: Administration
SRZL  CCMS
SSM1  Session Manager generation call
SSM5  Create Activity Group
ST01  System Trace
ST02  Setups/Tune Buffers
ST03  Performance, SAP Statistics, Workload
ST04  Select activity of the databases
ST05  SQL Trace
ST06  Operating System Monitor
ST07  Application monitor
ST08  Network Monitor
ST09  Network Alert Monitor
ST10  Table Call Statistics
ST11  Display Developer Traces
ST12  Application Monitor
ST14  Application Analysis
ST22  ABAP Runtime Error Analysis
ST22  ABAP/4 Runtime Error Analysis
ST62  Create industry short texts
STAT  Local transaction statistics
STMS  Transport Management System
STUN  Performance Monitoring
STW1  Test Workbench: Test catalog
STW2  Test workbench: Test plan
STW3  Test workbench: Test package
STW4  Test Workbench: Edit test package
STW5  C maintenance table TTPLA
STZAC Maintain time zone act.in client
STZAD Disp.time zone activat.in client
SUMM  Global User Manager
SU01  Maintain User
SU01D Display users
SU02  Maintain Authorization Profiles
SU03  Maintain Authorizations
SU05  Maintain Internet Users
SU10  Mass changes to User Master
SU11  Maintain Authorizations
SU12  Mass Changes to User Master Records
SU2   Maintain User Parameter
SU20  Maintain Authorization Fields
SU21  Maintain Authorization Objects
SU22  Auth. object usage in transactions
SU24  Disables Authorization Checks
SU25  Imports SAP Check Indicators defaults
SU26  Adjust Authorization checks
SU30  Total checks in the area of auth.
SU52  Maintain own user parameters
SU53  Display check values
SU54  List for Session Manager
SU56  Analyze User Buffer
SUPC  Profiles for activity groups
SUPF  Integrated User Maintenance
SUPO  Maintain Organization Levels
SUIM  Repository Info System
SWDC  Workflow Definition
SXDA  Data Transfer Workbench
TU02  Display Active Parameters
USMM  Customer measurement

SPAU and SPDD

When you apply a package, a large number of objects are changed.

If you have applied any OSS notes to objects in your system, the hot package may overwrite these objects.

SPDD is used to identify dictionary objects

and

SPAU (repository objects), will identify any objects where the hot package is overwriting changes you have made through OSS notes.

You must check all objects identified in SPAU and decide whether you need to reapply the OSS note or reset the code to the original SAP Code.

If, for instance, you are applying hot package 34, SPAU identifies an object where you have applied an OSS note. You must check the OSSs note and see if SAP have fixed that note in a hot package.

If the OSS note has been fixed in hot package 34, then you should reset the object to its original source code. This means that there is no repair flag set against this object again and it is now SAP standard code.

If, however, the object is not fixed until hot package 38, or there is no fix available you have to reapply the OSS note, otherwise users will encounter the problems they had before the note was applied.

You must transport all reapplied notes and Reset to SAP Standard objects after you apply your hot package to your QAS and PRD systems.

Applying SP4 to Windows 2000 Server

You need to download a newer SAP kernel. You will need an OSS ID and password to access http://service.sap.com/patches. And you will need to know what R/3 version, database, and OS you currently use.

Once you are at the patches website, you will need to click in the navigation tree:
R/3 -> R/3 + ?Release number? -> Binary patches ->
SAP Kernel + ?Release number? + 32-Bit -> NT/I386.

Download everything from the database section and everything from the database independent section.

One of the files you downloaded should start with SAPCAR and end with a *.exe.
Rename this file to SAPCAR.EXE and place it in the c:\winnt\system32 directory.
Go to \usr\sap\\SYS\exe\run and backup the entire directory to some other directory -
I usually create a \usr\sap\\SYS\exe\backup_run directory. Make sure SAP is down, the database is down, the TNS listener is down, and the SAPOSCOL is down before you do this.

Uncompress all the files you downloaded by opening a DOS box and typing:

SAPCAR -xvf .CAR

All files ending with .SAR or .CAR must be uncompressed. All the extracted files need to be moved to the \usr\sap\\SYS\exe\run AFTER that directory has been completely backed up.

Once everything has been downloaded, uncompressed, and moved into the exe\run directory, you can start the SAPOSCOL, the listener and the database services again. And then you should be able to start SAP. If there are any application servers for this database instance, the SAP software will update those kernels on startup.

If the SAP instance STILL does not come back up, you can take down everything again and restore the exe\run directory with your backup copy. Nothing will have been damaged.

Upgrading SAP Kernel, Hotpatches and Database Startup

Kernel upgrade is an easy process.

Go to the SAP OSS Site :-

http://service.sap.com/SWCenter-Main
SAP R/3
SAP R/3 4.6C
Binary Patches
SAP KERNEL 4.6D

Download the kernel programs in a temporary folder.

Create a folder and copy the executables /exe/run/ then uncar the downloaded files and replace the executables.

It is recommended to shutdown the R/3 database and all services including saposcol.

Then restart your system.

A couple of important points to remember are :-.

a) Always make a copy of the files you're going to replace. For e.g. Create a directory (oldkern) and copy all the old files
before replacing them (this helps when sometimes the new Kernel has problems, and you can revert it)

b) You have to shutdown SAP and the Database using the OLD kernel file. Again it is good practice to shutdown everything
first.

Refer to this OSS note which is pretty useful :-

102461 - Installation of 4.0B/40B_COM kernel with 4.0A/40B

How do I find out the current patch level in SAP R/3 4.7

You can use either of these two methods:

1: Follow the path

System --> Status --> Component Information (The Magnifying glass button in the SAP System Data section)

2: Use the Transaction code ---- spam

spam(Support package manager) --> package level

Steps to Start Your Database After Kernel Upgrade

Do these steps to start your database:

1. Open command prompt

2. Give command: SQLPLUS "/as sysdba"
If its giving message connected to idle instance then proceed:

3. Give command: startup open
If its giving error that database is already open, shut it down first. Then first check what database process is up and running.

4. Try stopping the database: shutdown immediate.

5. Follow step 3 again after shut down the database.

6. Exit from SQLPLUS

7. Run command on command prompt: R3trans -d
Check the results whether its still giving error or if it completed with 000 return code, then try starting SAP.

Follow the above steps.

Manually Applying OSS note on SAP Standard Program

What is mean by OSS how to work on that?

OSS are online sap support notes. These notes are available online for solving critical problems in sap system.We may use the already existing notes or may add our own quaries.

In order to apply any OSS note, you have to be authorized by your company and be assigned an OSS ID and password.

For any SAP standard program modification, you are required to login to OSS and request for a repair program Access key.

Access the SAP Support Portal:

http://service.sap.com/

- Keys and Requests

-- Request license key

--- Follow the Steps 1 to 5 of the License keys for SAP Business Suite

--------------

Follow this step to obtain the Program Access key:

Menu Path: System -> Services -> SAP Service (Transaction code OSS1)

Login in with your OSS ID and Password

Click the Registration button

Click Register Object

Double click R/3 Value Contract

Fill in the Object Registration for Installation:

For e.g.
PGMID/Object/Name: R3TR FUGR MIGO
SAP release: 46C

Finished, click the Register button

Select the Key number and use the Copy and Paste short key to copy the Access key

You are now able to modify the SAP standard program.

Finished the modification, do remember to transport it to the production system after all the necessary testing.

Apply OSS Notes On My SAP R/3 System

How to apply OSS notes to my R/3 system?

In order to fix one of the problem in R/3 system, SAP will asked you to download an OSS notes which is a ".car" file.

To work with a CAR File do the following at OS Level:

Get into OS as adm

Copy the .CAR file to a Temporary Directory.

Uncompress the file with SAPCAR

Copy the the data file generated in the data transport directory
( ej: = /usr/Sap/trans/data).

Copy the the cofile file generated in the cofiles transport directory
( = ej: /usr/Sap/trans/cofiles).

Run transaction STMS

Upload the support package with SPAM transaction and the support package will show "New support packages".

**********

Examples of CAR command :-

1) UNIX only:

Log on as user adm.
cd /usr/sap/trans
CAR -xvf tmp/.CAR -V

2) Windows NT only:

Log on as user ADM.
cd \USR\SAP\TRANS
CAR -xvf TMP\.CAR

This Will create two(2) FILES

After you run SPAM you MUST run STMS and check the transport queues

**********

As per 315963 note you can direct made the changes in the program or you can apply the support pack.

a) If you want to apply correction then first you need to register the object in SAP, so that you will get the Access key and then you can make the changes.

b) If you want to import the support pack then you need to down load from SAP market-place. and this is in CAR file. and then you need extract the same using CAR utility.
ex: CAR -xvf abc.car

or

you can directly apply the patch from SAPGUI, login to 000 client and then you can load the patch from Presentation server.

Also check what is your current basis patch level?

For example if you want to apply patch 07 and you are having 05 then you need to apply 06 and then apply 07.

**********

Things to take note of:-

It would definitely be better to apply the latest spam/saint spam manager, tp, R3trans and possibly a new kernel patch.

This is not a simple task to complete on the fly. By applying SAP support packs, you may run into problems with SPDD and SPAU adjustments. Also include the fact that the support packages may break one of your transactions. You may want to test this in your sandbox environment, if you have one, before tackling it.

In most situation when you apply support packages, it can takes about 3 weeks to fully test the support packages before you can apply them to the production system.

Do test your "golden" transactions to make sure that they are not broken. If you are not familiar with SPDD and/or SPAU adjustments than do not attempt to load support packages.

You may be better off just to modify the SAP object in question via OSS note.