Anda di halaman 1dari 86

SAP Basis Quick

Troubleshooting
A reference to BASIS Administrators

Contents

SAPGUI Common Problems and Architecture


TCP/IP Ports used by applications
SAP AS ABAP+JAVA Architecture
Start/Stop Process
Profiles Location
SAP System Directories
Important Users
Log files & location
List of error codes
List of common OS commands and tasks
Available Tools for Administration
Support Links
Return to Index

Return to Index

SAPGUI Common Problems


and Architecture
Common SAPGUI
Problems

SAPGUI Technical
Infrastructure

SAP Excel Macro


Settings

SAPGUI Family
and Architecture

Return to Index

TCP/IP Ports Used by


Applications
TCP/IP Ports Used
by Applications

SAP
Communication Ports

JAVA
Communication Ports

JAVA Port number tip*


Use this global rule to access Java engine via browser
http://hostname:5NN0P
https://hostname:5NN01
Where:
NN = Is the instance number, and
P = is the port number described in JAVA Ports
Return to Index

AS JAVA Ports

Return to Index

Installation Options
These are the following installation options for the SAP NetWeaver AS:
ABAP system (with integrated VM Container).
In the graphic these are the components in the blue box on the left.
With this installation you can run ABAP programs and selected SAP
Java applications.
Java system. In the graphic these are the components in the green
box on the right. With this installation you can run Java EE
applications but not any ABAP programs.
Dual stack system or ABAP+Java system. These are all the
components in the graphic below

Return to Index

SAP AS ABAP+JAVA Main


Architecture

Return to Index

Each SAP system can have only 1 Central Instance , 1 Central Services
Instance and only 1 Database instance. It can have any number of additional
dialog instances
Return to Index

SAP AS ABAP+JAVA Main Architecture

Return to Index

In a nutshell
SAP Gateway carries communication from another system to
another. It can be either an ABAP/Dual-Stack or a JAVA system.
Works as a barricade before your physical firewall
ICM is a service to provide WebServices to your same landscape
via web over a Browser. If not enabled, SAP cannot carry
communications over the Internet. Supports HTTP and HTTPS
If you installed more than a application server which is another
Dialog instance into your system for load balancing*, the
Message Server determines the application server to which the
SAP GUI connects.
Enqueue Server is responsible for the Lock Management of the
server.
Return to Index

* http://help.sap.com/saphelp_nw70/helpdata/en/c4/3a644c505211d189550000e829fbbd/content.htm

Lock Management (Enqueue Server)

Return to Index

AS ABAP Architecture

Return to Index

Return to Index

Return to Index

AS JAVA Architecture

Return to Index

Each SAP system can have only 1 Central Instance , 1 Central Services
Instance and only 1 Database instance. It can have any number of additional
dialog instances
Return to Index

Return to Index

Return to Index

Dual-Stack (ABAP+JAVA) Architecture

Return to Index

Return to Index

Start/Stop Process

Return to Index

Start/Stop Process

Return to Index

STANDARD STARTUP
(AS ABAP)

Return to Index

right-click

MMC

<SID>

Start
send message via namepipe

SAP<SID>_00
(service)

sapstart.log

Startup Profile

read

strdbs.cmd
msg_server.exe
disp+work.exe

Start

alert_<SID>.log

DB (if not)
dev_ms

Message Server

dev_disp

Dispatcher

read

Default Profile
Instance Profile

Start
Start
dev_rd

Gateway

dev_icm

dev_w0..w<n>

Start

ICM

WPs
Connect DB

DB

AS JAVA Startup

Return to Index

AS JAVA Startup

Return to Index

Return to Index

Return to Index

Return to Index

Return to Index

Dual-Stack Startup

Return to Index

Further reference

Monitoring Start
and Stop of SAP

Startup &
Operation of AS JAVA

Start/Stop SAP
UNIX Commands

Return to Index

Profiles location

Return to Index

Standard profile tree-structure


directory
profile
SYS
/usr/sap/<SID>

Unix Only
/home/<sid>adm
Example :
/home/devadm

Common shared directory:


/sapmnt/<SID>/SYS/profile
OS Alternative tip*
You can access directly to profile
location typing OS command
cdpro using <sid>adm user
Return to Index

Overview of SAP Profiles

*Prior to SAP NetWeaver 7.3, Start profile got merged into Instance profile so only
1 default profile exists per system and 1 instance profile exists per instance
Return to Index

O.S. User for SAP Instance


UNIX
SAP Admin => <sid>adm
example : devadm
SAP DB tools Admin => ora<sid>
example : oradev

sapdba or
brtools

Windows Server
SAP Admin/ DB tools Admin =>

<sid>adm

example : devadm
Return to Index

JAVA Users

Return to Index

SAP System Directories

Return to Index

Standard SAP Directories for a


Dual-Stack (ABAP+Java) System
(Unicode)

Return to Index

Standard SAP Directories for Java


System (Unicode)

E: A Java System can only be a Unicode System

Return to Index

SAP System Directories in Detail


Directory

Description

/<sapmnt>/<SAPSID> Software and data for one SAP system

This directory and its subdirectories need to be physically shared using Network File System (NFS) and mounted for all hosts
belonging to the same SAP system. It contains the following subdirectories:

exe
This directory contains executable kernel programs. In an SAP system with distributed instances, this directory must be
shared for all hosts with the same operating system.
Note
ABAP (Non-Unicode) + Java system only
exe contains a folder uc with a platform-specific subfolder: <sapmnt>/<SAPSID>/exe/uc/<platform>

global
This directory contains log files. In an SAP system with distributed instances, this directory must be shared for all hosts with
the same operating system.

profile
This directory contains the start and operations profiles of all instances. In an SAP system with distributed instances, this
directory must be shared for all hosts with the same operating system.

/usr/sap/trans

Global transport directory for all SAP systems


The global transport directory is used by the Change and Transport System (CTS). The CTS helps you to organize
development projects in the ABAP Workbench and in Customizing, and then transport the changes between the SAP systems
in your system landscape. For more information, see Change and Transport System.

Return to Index

/usr/sap/<SAPSID>

Instance-specific data, symbolic links to the data for one system


This directory contains files for the operation of a local instance.

There is a subdirectory for each instance. Each instance directory has the name of the related instance.
o

The instance name (instance ID) of the ABAP central instance is DVEBMGS<Instance_Number>, and the
instance name of an ABAP dialog instance is D<Instance_Number>. In a high-availability system, there is
also an ABAP central services instance called ASCS<Instance_Number>

This directory contains files for the operation of a local instance.

There is a subdirectory for each instance. Each instance directory has the name of the related instance.

The instance names (instance IDs) of an ABAP system are as follows:


Primary application server instance: DVEBMGS<Instance_Number>
Additional application server instance: D<Instance_Number>.
Central services instance for ABAP (ASCS):ASCS<Instance_Number>
Enqueue replication server instance (ERS): ERS<Instance_Number>
The enqueue replication server instance is only mandatory in a high-availability system.
Example
For an SAP ABAP system with SAP system ID C11, the instances might look as follows:
Primary application server instance: DVEBMGS00
Additional application server instance: D01
Central services instance for ABAP (ASCS): ASCS02
Enqueue replication server instance (ERS): ERS03

Return to Index

The instance names (instance IDs) of an ABAP+Java (dual-stack) system are as follows:

Primary application server instance: DVEBMGS<Instance_Number>

Additional application server instance: D<Instance_Number>.

Central services instance for ABAP (ASCS):ASCS<Instance_Number>

Central services instance for Java (SCS):SCS<Instance_Number>

Enqueue replication server instances (one for the ASCS and one for the
SCS): ERS<Instance_Number>
The enqueue replication server instances are only mandatory in a high-availability system.
Example
For an SAP ABAP+Java system with SAP system ID C11, the instances might look as follows:
Primary application server instance: DVEBMGS00 (the Java EE Engine is installed
in /usr/sap/C11/DVEBMGS00/j2ee)
Additional application server instance: D01 (the Java EE Engine is installed
in/usr/sap/C11/D01/j2ee)
Central services instance for ABAP (ASCS): ASCS02
Enqueue replication server instance (ERS) for the ASCS: ERS03
Central services instance for Java (SCS): SCS04
Enqueue replication server instance (ERS) for the SCS: ERS05
On a primary application server instance with SAP system ID C11 and instance
name DVEBMGS00, the Java EE Engine is installed in /usr/sap/C11/DVEBMGS00/j2ee.

The instance names (instance IDs) of a Java system are as follows:

Application server instance: J<Instance_Number>

Central services instance for Java (SCS):SCS<Instance_Number>

Enqueue replication server instance: ERS<Instance_Number>


The enqueue replication server instance is only mandatory in a high-availability system.

Return to Index

/usr/sap/<SAPSID>

Example
For an SAP Java system with SAP system ID C11, the instances might look as follows:
(Primary) application server instance: J00 (the Java EE Engine is installed in /usr/sap/C11/J00/j2ee)
(Additional) application server instance: J01 (the Java EE Engine is installed in/usr/sap/C11/J01/j2ee)
Central services instance for Java (SCS): SCS02
Enqueue replication server instance (ERS) for the SCS: ERS03}

Example
The file system structure might look as follows:
On a central instance with SAP system ID C11 and instance name DVEBMGS00, the ABAP dialog instance has the
instance name D01.
o

The instance name (instance ID) of the ABAP+Java central instance is DVEBMGS<Instance_Number>, the
instance name of the Java central services instance is SCS<Instance_Number>, and the instance name of
an ABAP+Java dialog instance is D<Instance_Number>. In a high-availability system, there is also an
ABAP central services instance called ASCS<Instance_Number>

Example
The file system structure might look as follows:
On a central instance with SAP system ID C11 and instance name DVEBMGS00, the J2EE Engine is installed
in /usr/sap/C11/DVEBMGS00/j2ee, and the corresponding Software Delivery Manager (SDM) is installed
in /usr/sap/C11/JC00/SDM
On a dialog instance with instance name D01, the J2EE Engine is installed in/usr/sap/C11/D01/j2ee. No
SDM is installed.
Note
The subfolder SDM is only available for the central instance.

Return to Index

/usr/sap/<SAPSID>

The instance name (instance ID) of the Java central instance is JC<Instance_Number>, the instance
name of a Java dialog instance is J<Instance_Number>, and the instance name of the Java central
services instance is SCS<No>.

The instance name (instance ID) of the central instance is JC<Instance_Number>, the instance name of a
Java dialog instance is J<Instance_Number>, and the instance name of the Java central services instance
is SCS<Instance_Number>.
Example
The file system structure might look as follows:
On a central instance with SAP system ID C11 and instance name JC00, the J2EE Engine is installed
in /usr/sap/C11/JC00/j2ee, and the corresponding SDM is installed in/usr/sap/C11/JC00/SDM.
On a dialog instance with instance name J01, the J2EE Engine is installed in /usr/sap/C11/J01/j2ee. No
SDM is installed.

The directory /usr/sap/<SAPSID>/SYS contains soft links to appropriate directories


in /<sapmnt>/<SAPSID>/ for storing data used by several instances.
SYS is logically shared and available on each host of the SAP system. Its subdirectories contain symbolic links to the
corresponding subdirectories of /<sapmnt>/<SAPSID> on the SAP global host, as shown in the figures above.

Whenever a local instance is started, the sapcpe program checks the executables against those in the logically shared
directories and, if necessary, replicates them to the local instance.
For more information about sapcpe, see Program sapcpe.
Executables located in/usr/sap/<SAPSID>/SYS/exe/run are replicated by sapcpe to the exe subdirectory of the
instance directories.

Return to Index

Log files & location

Return to Index

Log file types


There are only two types of log files for
troubleshooting problems:
Developer traces (dev_*)
Standalone (SLOG*) log files, retrieved
ONLY from ABAP-managed systems

Return to Index

STDERR1: Information about the start process of the database system.


STDERR2: Information about the start process of the message server.
STDERR3: Information about the start process of the dispatcher.
Return to Index

Developer Traces
Component
Dispatcher
Web Disptacher
Work Process

File Name
dev_disp
dev_wdisp
dev_w<n> n is the range from 0 to one less the number of work processes.

Dynp (screen processor)


Roll
Paging
DB interface
ABAP processor
Enqueue (lock)
Logging
Spool
Message server
SAPGUI (presentation)
APPC-server (CPIC gateway)
RFC (Remote Function Call) facility

dev_dy<n>
dev_ro<n>
dev_pg<n>
dev_db<n>
dev_ab<n>
dev_eq<n>
dev_lg<n>
dev_w
dev_ms<n>
dev_st<logon name>
dev_appc
dev_rfc, dev_rfc<n>
dev_rfc traces RFC calls to external functions (written in C or Visual Basic).
dev_rfc<n> traces RFC calls that are executed in R/3 work processes. <n>
is the number of the work process in the server (as shown above). A work
process uses the same log file across RFC calls.
Note: The dev_rfc<n> traces are also traced on the external RFC server.

Gateway
R3trans and tp transport programs
Monitoring infrastructure (test mode only)

dev_rd
dev_tp
dev_moni
In normal operation, you will not see this file. It is used only by test tools of
the monitoring infrastructure. It therefore appears only if the test tools must
be activated during a support session.

Startup (sapstart)

dev_sapstart

Return to Index

Developer Traces (contd)


The following criteria are available:

TRACE=0: No trace

TRACE=1: Write error messages in the trace file.

TRACE=2: Full trace. The trace entries that are


actually written can vary with the SAP program that
is being traced.

TRACE=3: Additionally, trace data blocks.

Return to Index

Error and System Log Entries in


Trace Files
In the files, lines that contain error information
begin with *** ERROR =>. Lines for which
system log entries are written start with *** LOG
<message ID>.
An "error line" contains the name of the calling
function, the operation that failed, the error
number from the host system (if a system call is
involved), and the name of and line in the C
module that failed.
Return to Index

Error and System Log Entries in


Trace Files (contd)
Component Abbreviation in Trace File
M
A
Y
X
E
I
S
N
T
L
B
C
P
R
D

Component (Selection using SM50 or SM04)


Task handler
ABAP Processor
Screen Processor
Extended memory
Lock management (enqueue)
IPC (inter process communication)
Print (spool)
Security
Debug system
Background
Database
Database (DBSL)
Paging
Rolling
Diag processor

Return to Index

Displaying trace files


From SAP:
Choose transaction ST11. Here, you see all the trace files in
the work directory. Double-click on a file to display there. If you want
to save a file locally, choose System List Save Local file.
The following trace types have their own transactions.
From the operating system:
/usr/sap/<SYSTEM ID>/<INSTANCE>/work
Replace <INSTANCE> with the following:
DVEBMGS## = If for ABAP Instance
JC## = If for JAVA Dialog Instance
Return to Index

Displaying trace files (contd)


Component

Transaction

More Information

Work process

SM50

Displaying and Controlling Work Processes

Gateway

SMGW

Using SAP Gateway in SAP System

Message server

SMMS

Message Server Monitor

ICM

SMICM

Monitoring the ICM with the ICM Monitor

SAP Web Dispatcher

You can now use the Web


Administration Interface.

SAP Web Dispatcher

You can also download the trace files onto your local computer. To do
this use the ABAP report RSMON000_DOWNLOAD_TRACES. For
more information see Downloading Trace Files.

Return to Index

The System Log (SLOG)


The System Log
The SAP System logs all system errors, warnings, user locks due to
failed logon attempts from known users, and process messages in
the system log. There are to two different types of logs created by
the system log:
Local Logs
Central Logs
Use transaction SM21 to access the system log output screen. With
this transaction, you can read any of the messages that are
contained in the system logs. You can modify the view to meet your
needs.
Return to Index

The System Log (contd)


Local Logs
Each SAP System application server has a local log that receives all the
messages output by this server. The system log records these messages in a
circular file on the server. When this log file reaches the maximum permissible
length, the system log overwrites it, starting over from the beginning. (The
location of the local log is specified in the rslg/local/file profile parameter.)
Central Logs
We recommend that you also maintain a central log file on a selected
application server. Each individual application server then sends its local log
messages to this server. The server that you designate to maintain the central
log collects the messages from the other application servers and writes these
messages to the central log.
The central log consists of two files: the active file and the old file. (The location
of the active file is specified in the rslg/central/fileprofile parameter; the location
of the old file is specified in therslg/central/old_file.)

Return to Index

Profile Parameters and File Locations


The table below shows some of the profile parameters for the system log along with their standard
values:
Profile Parameters and File Locations for the System Log
rslg/local/file

Specifies the location of the local log on the


application server.

/usr/sap/<SID>/D20/log/SLOG<SAPinstance_number>

rslg/collect_daemon/host

Specifies the application server that maintains


the central log.
Specifies the location of the active file for the
central log on the application server.

<hostname of main instance>

rslg/central/old_file

Specifies the location of the old file for the


central log on the application server.

/usr/sap/<SID>/SYS/global/SLOGJO

rslg/max_diskspace_local

Specifies the maximum length of the local log.

500,000 bytes

rslg/max_diskspace_central

Specifies the maximum length of the central log. 2,000,000 bytes

rslg/central/file

/usr/sap/<SID>/SYS/global/SLOGJ

This is not a complete list. There are additional profile parameters that refer to the system logs; they all begin
with rslg*. However, we do not discuss them all here. You can use the transaction RZ11 to access the rest
of the parameters.

Return to Index

Log Location

Return to Index

Trace files
/usr/sap/<SYSTEM ID>/<INSTANCE>/work
System log files (ABAP-managed only)
/usr/sap/<SID>/DVEBMGS##/log/ or /usr/sap/<SID>/D##/log/
Replace <INSTANCE> with the following:
DVEBMGS## = If for ABAP Instance
JC## = If for JAVA Dialog Instance
(application server in the same instance)
D## represents Dialog Instance
## represents instance no.

Return to Index

JAVA-Managed Systems

Return to Index

JAVA-Managed Systems

Java Managed Systems

Return to Index

Developer traces
Structure
dev_jcontrol
The trace file of the JControl process.
JControl is responsible for starting, stopping and controlling the processes of the J2EE instance.
Use the dev_jcontrol trace file when you have problems starting or stopping the whole J2EE instance.
We recommend that you always check the end of this file for error messages regarding the startup of JControl.

dev_<component name>
The trace file of the corresponding JLaunch process (the <component name> can
be bootstrap, bootstrap_<cluster_element_ID>, dispatcher, server<n>, sdm, jcmon, oricm). For example, the trace file for the bootstrap

process isdev_bootstrap.

std_<component name>.out
The standard and error output file of the corresponding JLaunch process (the <component name> can
be bootstrap, bootstrap_<cluster_element_ID>,dispatcher,server<n>,sdm, oricm). For example, the output file for the bootstrap
process isstd_bootstrap.out. Output and error messages from the Java VM are written to this file.

jvm_<component name>.out
The standard and error output file of the JVM running the corresponding JLaunch process (the <component name> can
be bootstrap, bootstrap_<cluster_element_ID>, dispatcher, server<n>, sdm, or icm). For example, the output file for the JVM running the bootstrap
process is jvm_bootstrap.out.

Java Managed Systems

Return to Index

Types of log and trace files


Startup and control framework logs

Contain information about the startup process. You can check these
files if errors or undesired behavior occur during the startup process.
By default, the data from the last three restarts is kept.
The developer trace files and system output of all the executables
belonging to an instance are located in the
directory \usr\sap\<SID>\<instance name>\work, where <SID> is the
system ID (for example, CE1) and <instance name> is the instance
name (for example, JC00 or SCS01).

AS Java logs

The log and trace files generated by the AS Java process(es) and
the applications running on top of AS Java are stored in the
usr\sap\<SID>\<instance name>\j2ee\cluster\server<n>\log directory.
Java Managed Systems

Return to Index

Log Location

Java Managed Systems

Return to Index

Trace files
/usr/sap/<SYSTEM ID>/JC##/work
Visual Administrator trace files
/usr/sap/<SYSTEM ID>/JC##/j2ee/admin/log
Log viewer* files
/usr/sap/<SID>/JC<Instance number>/j2ee/admin

JC## represents Dialog Instance


## represents instance no.

Return to Index

List of error codes


(General)

Return to Index

List of common error codes

SAP Error Codes

Top 10 ABAP
Dumps

List of CPIC Error


Codes

MESSAGE_TYPE_X
Meaning

Return to Index

List of common OS Commands


and tasks

UNIX Common
OS Commands (SAP)

BASIS Common
Tasks

Guia rapida editor


de vi (UNIX)

SAP BASIS FAQ

Return to Index

Return to Index

Available tools for administration


** Always remember that for Windows administration, you can always
use SAP Management Console (MMC) **

AS JAVA Tools
JCMON (launched from command
Difference
shell)
configtool and visual admin
SAP Netweaver Administrator
(Web-only)
Visual administrator
Config tool
Shell console
Connecting to the
ABAP Transaction SMICM (if dualSAP Web AS
J2EE Engine
stack system)
Tools
Return to Index

SAP Microsoft Management Console


(Windows)
The SAP Microsoft Management Console (SAP MMC) provides a common
framework for system management. It integrates previously separate tools in
a common user interface for centralized system management. Although the
SAP MMC itself does not offer any management functionality, it provides an
environment for incorporating and accessing management tools. Tools are
integrated in the SAP MMC with snap-ins for standardized access to
functions.
SAP has developed the SAP Systems Manager snap-in let you monitor, start
or stop the SAP system centrally from the SAP MMC. SAP recommends you
to use the SAP MMC because it simplifies system administration and
provides many new features.
You can use the SAP MMC for both ABAP and Java systems. If you use a
Java system you can ignore references to ABAP. If you use an ABAP system
you can ignore references to Java.

Return to Index

Features
The SAP MMC offers the following features:
You can monitor and control any number of SAP systems and application servers and ITS
instances with a single tool if they are running on Windows. As of SAP NetWeaver 7.0, you can
also monitor SAP instances running on different platforms.
Once you have configured the console, you can save the configuration in a file and easily
forward it to other users.
The dual DCOM interface ISAPControl of the start service and IITSWatchdog of the ITS
watchdog service let a third party use the functionality - for example from C, Java or Visual
Basic - and let you integrate it into your own tools or scripts without having to use proprietary
SAP mechanisms.
The start service is available on all platforms and offers a new Web service interface, called
SAPControl with better control and monitor capabilities. Some of the new snap-in features
require the new Web service interface. You can access the Web service interface in your own
applications from a Web service-enabled programming environment like C, Java, ABAP or
.NET. The old ISAPControl DCOM interface has become obsolete but is still supported under
Windows.

Return to Index

Features (contd)
The SAP MMC lets you to:
Display all SAP trace files, start profile, instance parameters, the system environment and SAP environment
Display the most serious alerts in the alert tree (ABAP transaction RZ20)
Display the current status tree (ABAP transaction RZ20)
Display and acknowledge current alerts (ABAP transaction RZ20)
Display the SAP syslog for a functioning, offline, or malfunctioning SAP system (ABAP transaction SM21)
Display the ABAP work process overview (ABAP transaction SM50)
Display the ABAP and ICM queue statistics (dpmon)
Display Application Server Java (AS Java) processes, caches, threads, web sessions, EJB sessions, remote
objects, application aliases, and shared memory tables
Display Java virtual machine garbage collection and heap memory information of the Application Server Java
Display ICM threads, connections, caches and proxy connections
Start or stop one or all application servers of a system with a mouse-click. You can restart service without
having to restart the App Server
Log on to an application server
Start analysis tools in the SAP system for nodes in the alert tree
Control Java or ABAP processes
Modify dynamic profile parameters
Remove enqueue locks manually
Create compressed instance or system snapshots for offline problem analysis and problem reporting
Start the following third-party tools, if available, to manage an application server or ITS instance:
o Telnet
o SSH client
o Windows Terminal Server Client
o pcANYWHERE
o Computer Management snap-in

Return to Index

Further documentation
The following SAP Notes provide additional information:.

Note number
927637

936273

Title
Web service authentication in
sapstartsrv as of Release
7.00
sapstartsrv for all platforms

995116

Backward porting of
sapstartsrv for earlier
releases

823941

SAP start service on Unix


platforms

Troubleshooting
SAP recommends you to first check the SAP Notes 877795 and 142100 for
potential problems
Return to Index

AS JAVA Tools

Return to Index

AS JAVA Tools

JCMON (launched from command shell)


SAP Netweaver Administrator (Web-only)
Visual administrator
Config tool
Shell console
ABAP Transaction SMICM (if dual-stack
system)
Return to Index

Return to Index

Use Path: \usr\sap\<SID>\<J2EE Instance>\j2ee\configtool\configtool.bat


Return to Index

Return to Index

Use Path: http://hostname:5NN0P/nwa


Return to Index

Use Path: \usr\sap\<SID>\<J2EE Instance>\j2ee\admin\go.bat


Return to Index

Return to Index

Start/Stopping JAVA-Stack using SMICM Transaction


Return to Index

Support Links
1. SAP Community Network (SCN) http://scn.sap.com
2. SAP Help Portal. http://help.sap.com
Main Page
Security Quick Guide

Solution Manager
http://service.sap.com/solutionmanager
http://wiki.sdn.sap.com/wiki/display/SMAUTH/Home

Solution Manager Main Page


Solution Manager Security and
Authorizations Guide

SAP Market Place Links


SAP Library NetWeaver

http://help.sap.com/netweaver

License Auditing

http://service.sap.com/licenseauditing

Connect to SAP

http://service.sap.com/remoteconnection

Inbox

http://service.sap.com/inbox

Installation Guides

http://service.sap.com/instguides

Download SAP product installation


guides

Product Availability Matrix

http://service.sap.com/pam

EhPs for SAP ERP (ECC)

http://www.service.sap.com/erp-ehp

Find minimum requirements needed


to install SAP Software
Find Information on SAP ERP
Enhancement Packages Easily

License Keys

http://service.sap.com/licensekey

Request New Permanent License Key

Oracle DBA Page


OSS Notes
Patches
SAP GUI

http://service.sap.com/dbaora
http://service.sap.com/notes
http://service.sap.com/patches
http://www.sdn.sap.com/irj/sdn/sap-gui

Page for Oracle DBA Material


Search the SAP Notes Database
Download SAP software patches
SAP GUI SDN Wiki

SAP Library Main Page for NW 7.0


and up
Find information about the License
Measurement Process
Open the OSS connection with SAP
and find more information about it
Read messages from SAP to you

Support Links
SAPRouter

http://service.sap.com/saprouter

How to Configure the SAPRouter

Install SAPCrypto

http://service.sap.com/saprouter-sncdoc

How to install SAPCrypto Libraries

Security Notes

http://service.sap.com/securitynotes

Apply relevant security-related


HotNews and Notes.

To display a list of relevant


security-related Notes run
RSECNOTE in transaction
ST13
Software Distribution

http://service.sap.com/swdc

Download new images of


Installation CDs & DVDs

SSCR

http://service.sap.com/sscr

Register Developers and Changes


made against SAP objects

User Administration

http://service.sap.com/user-admin

Add/Change OSS ID user


information