SAP R/3 BASIS

Training

SAP stands for Systems Applications & Productions in data

processing

Sap has two main products in the business software market

Mainframe System R/2 & Client server system R/3 .
R stands for REAL TIME
History of SAP Software
1972 SAP R/1
Innovation = Standard Software and Real Time Computing
1983 SAP R/2
Innovation = Integration of Applications (Mainframe-based)
1989 SAP R/3
Innovation = Relational Database, Client-/Server-Architecture,
Platform Independence
SAP has no plans for R/4 today .

SAP Layers
Three tire client server architecture of the R/3 system separated
system layers .

into three

DATABASE Layer (handles database services)

APPLICATION Layer (process business logic & all other services)
PRESENTATION Layer (SAP Graphical User Interface SAPGUI)
Presentation
Central System

Distributed System

2-Tier System

3-Tier System

Application

Database

Homogeneous SAP Systems

Where Database server & Application server are running the same
O.S. Like Win NT & Unix , presentation are running on windows
workstation.
Heterogeneous SAP Systems
Database server running on one O.S. (Unix) & Application server
running on different O.S (Win NT) ,& presentation server running on
Windows-based workstations.

SAP Layers

R/3 User

R/3 User

Presentation Components
ABAP
Workbench

R/3 Basis R/3 Application 1

System
Kernel & Basis Services
Database Management System
Database

R/3 Application n

SAP R/3 Communication Protocol

Communication among the three tiers server types is accomplished with the use
of standard protocol services,such as one provided by TCP/IP or CPIC .

TCP/IP Transmission Control Protocol /Internet Protocol

At the OS level TCP/IP protocol used , Mainly to communicate with database,
application & presentation layer

CPIC Common Programming Interface Communication

AT the programming level ,R/3 system uses the CPIC protocol for program to
program communication and also includes support for Remote Function Calls
(RFC).

Installation of SAP R/3

1.

INSTALL
INSTALL DATABASE
DATABASE SOFTWARE
SOFTWARE ON
ON DATABASE
DATABASE SERVER
SERVER

2.

INSTALL
INSTALL SAP
SAPSOFTWARE
SOFTWARE ON
ON APPLICATION
APPLICATION SERVER
SERVER

3.

UPLOAD
UPLOAD DATA
DATATO
TO SAP
SAPSYSTEM
SYSTEM (Main
(Main database
database creation)
creation)

4.

SUPPORT
SUPPORT PACKAGE
PACKAGE (PATCH)
(PATCH) LOADING
LOADING

5.

POST
POST INSTALLATION
INSTALLATION Steps
Steps

6.

READY
READYFOR
FORUSING
USING

SAP R/3 Supported Platforms(1)

The key of SAP R/3 success was the strategy of making open solutions ,
in which the applications can run on multiple operating systems ,
databases ,and communication technologies.
OPERATING SYSTEM LEVEL :
AIX
COMPAQ TRU64
DG-UX
DYNIX/PTX
HP-UX
NCR UNIX
SNI DC/OSX
WINDOWS SERVER 32-BIT
RELIANT
SOLARIS/SPARC
LINUX/INTEL
OS/400
DATABASE LEVEL :
ORACLE
SQL SERVER
DB2
ADABAS
INFORMIX

SAP R/3 Supported Platforms(2)

Oracle

Informix

DB2

SQL
SERVER

Adabase D

HP-UX

AIX

Reliant/UNIX

Digital unix

Solaris

NT 4.0 Intel

NT 4.0 Alpha

OS/390

OS/400

SAP R/3 Supported Platforms(3)

SAP R/3 3.1H:
ORACLE 7.3.2
ORACLE 7.3.3
ORACLE 7.3.4
ORACLE 8.0.4
ORACLE 8.0.5
ORACLE 8.0.6

WIN NT 4.0 INTEL

WIN NT 4.0 INTEL
WIN NT 4.0 INTEL
WIN NT 4.0 INTEL
WIN NT 4.0 INTEL
WIN NT 4.0 INTEL

SAP R/3 4.6B:

ORACLE 8.0.5
ORACLE 8.0.6
ORACLE 8.1.6
ORACLE 8.1.7
ORACLE 8.1.6
ORACLE 8.1.7

WIN NT 4.0 INTEL

WIN NT 4.0 INTEL
WIN NT 4.0 INTEL
WIN NT 4.0 INTEL
WIN 2000 INTEL
WIN 2000 INTEL

SAP R/3 4.6C:

ORACLE 8.0.5
ORACLE 8.0.6
ORACLE 8.1.6
ORACLE 8.1.7
ORACLE 8.1.6
ORACLE 8.1.7

WIN NT 4.0 INTEL

WIN NT 4.0 INTEL
WIN NT 4.0 INTEL
WIN NT 4.0 INTEL
WIN 2000 INTEL
WIN 2000 INTEL

SAP support period

Please Upgrade SAP before the mention date

SAP R/3 CORE BUSINESS MODULES

SAP R/3 applications usually categorized in three core functional areas

Financial
Logistics
Human Resource

Application Modules
Financials
Financial Accounting (FI)
Controlling (CO)
Asset Management (AM)
Enterprise Controlling (EC)
Capital Investment Management (IM)
Treasury (TR)
Logistics
Plant Maintenance (PM)
Quality Management (QM)
Production Planning (PP)
Materials Management (MM)
Sales and Distribution (SD)
Project System (PS)
Human Resources (HR)
Personal Administration
Personal Development

INDUSTRY SOLUTIONs (ADD-ON s)

Additionally,SAP actively develops special software packages on top of R/3
,targeted to specialized vertical industries.These packages are known as
INDUSTRY SOLUTIONs (IS) .These packages are fully integrated with the
rest of R/3 applications.SAP has the following IS packages like
IS-B: Sap Industry solution for Banks
IS-H: Sap Industry solution for Hospitals
IS-IS: Sap Industry solution for Insurance,Money,Foreign Exchange
IS-OIL: Sap Industry solution for Oil companies
IS-P: Sap Industry solution for Publishing sector
IS-PS: Sap Industry solution for Public sector
IS-Retail: Sap Industry solution for Retail
IS-T: Sap Industry solution for Telecommunication Sector
These IS-Packages are a collection of specific business processes,set of
transactions,programs,screens,documentation's Which fully integrated
with the R/3 applications.

Other solutions like CRM , SCM , BIW , PUBLIC-SECTOR can

integrate With the sap system .

Basis Software

R/3 BASIS Software is the set of programs & tools which interfaces
with the computer operating system ,database ,Application server &
and the presentation interfaces .

Basis software mainly R/3 common Kernel or R/3 Middle ware

which is the nucleus of a system known as the SAP KERNEL .

The main kernel directory in application server is

\usr\sap\<SID>\sys\exe\run

R/3 WORK PROCESS or SERVICES

In SAP naming convention , a service is a process or a group of work

process .
Computing system i e running the particular Services known as a

server or Application server .

SERVICES in R/3

Standard Work processes

SAPGUI

SAPGUI

SAPGUI

SAPGUI

Dispatcher
D
I
A
L
O
G

U
P
D
A
T
E

E
N
Q
U
E
U
E

B
A
C
K
G
R
O

M
E
S
S
A
G
E

DATABASE INSTANCE

G
A
T
E
W
A
Y

S
P
O
O
L

Dispatcher processes

The SAP dispatcher is the control program which manages

the resources of the R/3 applications.
The main tasks of the dispatcher are as follows:
Balanced assignment of the transaction load to the
appropriate work process
Buffer management in the main memory.
Connection with the presentation level.
Organization of the communication process.

Dialog work processes(1)

Dialog Step:
A dialog step is a sap r/3 screen,which is represented by a dynamic
program(dynpro) .A dynamic program consists of a screen and all the
associated processing logic .
When users are entered something on the screen & press enter ,they are
actually making one dialog step .

The dialog work processes are in charge of interactive

task of the R/3 System . A dialog process performs the
dialog steps corresponding to the user interactive
sessions.
The SAP profile parameter that controls the number of
interactive Dialog Work Process per instance is
rdisp/wp_no_dia

Dialog work processes(2)

Update work Process

The update process is in charge of executing

database changes when requested by dialog or
background work Processes.

Enqueue work Process

The enqueue work process is in charge of lock

Management system. It allows multiple application
Services to synchronize the access to the database
and maintain data consistency.

Background work Process

The background work processes are in charge of

executing ABAP/4 programs submitted for
background execution.
The SAP profile parameter that controls the
number of background work processes per
instance is rdisp/wp_no_btc

Message work Server

The message server is a service used by the

different Application servers to exchange data
and internal messages. The message server
routes the messages between application
servers.

Gateway work Server

The gateway server allows the communication

between the R/3, R/2 and external applications.
This service is a CPIC handler which implements
the CPIC protocol for Communication. This is
commonly known as a gateway.
The function of the SAP gateway is to exchange
larger Amounts of data between application
servers.

Spool work Process

The spool work process is in charge of formatting

the data for printing and passing it to the host
spool system.
The SAP profile parameter that controls the
number of background work processes per
instance is rdisp/wp_no_spo

Setting R/3 WORK PROCESS

Name of the Services

Min Number
of processes

Dialog Services

(D)

>=2

rdisp/wp_no_dia

>=0

rdisp/wp_no_vb,
rdisp/wp_no_vb2

Enqueue (Lock management) (E)

0 or 1

rdisp/wp_no_enq

Background Process

(B)

>=1

rdisp/wp_no_btc

Message Server process

(M)

0 or 1

Gateway services

(G)

>=1

Spool services

(S)

>=1

Update Services

(V)

Taken care by
the parameters

rdisp/wp_no_spo

R/3 WORK PROCESS(2)

Spool Services :
These work processes coordinates all type of print fax requests & services .
Message Services:
This process is for communication between the instances of an R/3 system.

Gateway Services:
Communication between different R/3 Systems
Remote Function Call (RFC)
Common Programming Interface for Communications (CPIC)
Dispatcher process:
SAP dispatcher is the control program which manages the resources of the R/3
applications.
Dispatcher manages the information exchange between the SAPGUIs & the
work processes,enabling users to share the diff work processes available .
Work process (WP):
Work processes are special programs in charge of some specific tasks.These are
mainly service offered by a server and requested by a client.
Dialog Step:
A dialog step is a sap r/3 screen,which is represented by a dynpro .A dynpro ,or
dynamic program consists of a screen and all the associated processing logic.
When users are navigating in the SAP R/3 system from screen to screen ,they
are actually making dialog step .

R/3 WORK PROCESS(3)

Dialog work process
This process is in charge of the interactive tasks of the R/3 system.
A dialog work process performs the dialog steps corresponding to the interactive user sessions .
The dialog work processes execute just one single dialog step at a time and become immediately
free for the next user request .
The dialog work processes can be constantly switching between different user sessions .Due to this
type of mechanism system can manage minimum number of work processes .
A dialog WP can support from 5 to more than 10 simultaneous users each.
Number of WP should be such that user do not wait long time to get free process .
SAP instance parameter rdisp/max_wprun_time =300 defined length of time in seconds that the
dispatcher allows the work process to run . When this value is reached ,the dispatcher stops the work
process and user gets a TIME_OUT .

Background work process :

This process is very useful for submitting programs requiring long processing times,since interactive
execution would exceed the allowed processing time & abort with a TIME_OUT error .
Normally these background jobs are not immediately processed but are when the system reaches the
planned time for execution .

Enqueue work process :

This process is in charge of LOCK MANAGEMENT SYSTEM .In order for the system to run in a
consistent manner ,it ensure that when a transactions dialog steps are handled by different WP ,they
retain the assigned locks until the end of the transaction .
One & only one Enqueue process exists for a single SAP system.

Process Overview

Logical flow of a execution of a user request

1.

User
User enter
enter data
data using
using SAPGUI
SAPGUI

2.

SAPGUI
SAPGUI convert
convert data
data to
to sap
sap format
format && sent
sent to
to dispatcher
dispatcher

3.

Dispatcher
Dispatcher keeps
keeps the
the requests
requests in
in queues
queues && process
process one
one by
by one
one

4.

Dispatcher
Dispatcher allocates
allocates user
user request
request to
to free
free work
work process
process

5.

Real
Real execution
execution takes
takes place
place inside
inside work
work processes
processes

6.

End
End of
of execution,
execution, result
result goes
goes back
back to
to Dispatcher
Dispatcher

7.

Dispatcher
Dispatchersends
sendsdata
datato
touser
userusing
usingSAPGUI
SAPGUI
Time is taken from step1 to step 7 is known as RESPONSE TIME .

Basis Terminology (1)

R/3 System
A R/3 System consists of combination of database server and the application servers .
SAP System Identification
The SAP System Identification, often referred to as the SAPSID, or SID, is a unique threecharacter code that identifies the R/3 System. SAP System Identification codes used are
DEV for the development system, QAS for the quality assurance system, and PRD for the
production system.
Client
A client is a legal and organizational entity in the R/3 System whose business management
data is protected against unlawful access.
In addition, a client:
Has its own set of user data
Is a logical system with separate master records
Has its own set of table data on common table .
System Landscape
The landscape consists of all R/3 Systems (Instances) involved in the implementation
project and client architectures that access (or share) a common transport directory.

Basis Terminology (2)

Customizing
Customizing is the process of configuring the SAP R/3 System such that the R/3
functionality fits the companys needs.

Database Server
This is where the database resides. Main data stores in this server .

Application Server
This is where R/3 application runs. On a 2 tiered system, this would be combined with the
database server.

Instance
An installation of R/3 on a application server .

GUI:
Graphical User Interface. The SAPgui is the software on users computer
or local server that allows to connect to one or more of the SAP
environments.

Disk Space Requirements

To configure a R/3 Release 4.X System, each database will require approximately 20
GB of disk space.
An application server will require approximately 2 GB of disk space .
A client with pure customizing data will require between 700 to 1500 MB.
If the client also contains application data, such as a production system, the storage
requirements can increase to several GB.

The disk space requirements can also be affected by the:

Relational database management system (RDBMS) selected
Number of clients in the system
Number of master data records
Number of transaction data records
Amount of historical data retained

Server Requirement for sap installation (Case study)

DEV

Intel 80686 (Mod 8 Step 3)

Machine Type

PRD

Intel 80686 (Mod 10 Step 1)

Processor

DEV

X86 Family 6 Model 8 Stepping 3 Genuine Intel ~789 Mhz

PRD

X86 Family 6 Model 10 Stepping 1 Genuine Intel ~700 Mhz

DEV

HP Net Server LC2000

PRD

HP Net Server LH6000

Total Physical
Memory

DEV

1GB

PRD

4 GB

Total Virtual
Memory

DEV

6 GB

PRD

12 GB

Disk Space

DEV

60 GB

PRD

130 GB

Server Model

O.S.

Windows 2000 , service pack 2

SAP R/3
Release

46C

Database

Oracle 8.1.7.1.0

SAP R/3 Directory structure (1)

SCM

Thesesap
sap
These
directories
directories
createdby
by
created
sap
sap
installation
installation

DVEBMGS00

The physical parent directory of the whole sap application is /usr/sap

Transport directory is /usr/sap/trans
SAP system parent directory <sapsid> , which is /usr/sap/SCM
If more than one sap system will installed on the same machine then additional
directory will be created under /usr/sap/.. ..

SAP R/3 Directory structure (2)

Sap mount directory is /sapmnt useful for sharing the common files with all
system belonging to the same group .
Mainly /sapmnt/scm indicates the directory /usr/sap/scm
Directory /sapmnt/scm/sys/exe/run it contains all sap runtime programs
this directory also called sap kernel directory.Most of the program files in this
directory are directly used by sap processes
Directory /sapmnt/scm/sys/profile which contains sap profile files like
startup-profile ,default-profile & instance-profile.
Directory /sapmnt/scm/sys/global which contains global or common data
managed by the SAP application & shared by all instances ,all types of logs.

R/3 Client
When Sap installed it comes with 3 default clients with default
users and default password.

Client User

Default
Password

000
000
001
001
066

06071992
19920706
06071992
19920706
SUPPORT

SAP*
DDIC
SAP*
DDIC
EARLYWATCH

R/3 Data(1)
CLIENT
CLIENT

CLIENT
CLIENT

CLIENT
CLIENT

000
000

066
066

001
001

CLIENTIndependent
Independentcustomizing
customizing
CLIENT
SAP
SAP
RepositoryObject
Object
Repository
An R/3 System is subdivided into clients .
In R/3 most of Customer business data in sub groups divided by

clients ,these type of data is client dependent data

When the SAP objects are just accessed by only one client, we
define them as client dependant data.
Some data in R/3 which is shared by all client like R/3
repository data.This type of data is client independent data.

R/3 Data(2)
R/3 database can be divided into two logical components:
R/3 repository object
R/3 customer data
R/3 repository : central part of this is ABAP dictionary i.e. programs,screens,
reports provided by sap or created or modified by sap user .
Customer data : customer data consists of any kind of data entered into r/3
by the customer in time of sap implementation or day to day
business processing .
Customizing data
This data generated when r/3 is configured to meet the particular needs of the
customer through customizing.Most customizing data is client-dependent some
is independent .
Application data
Also known as business data ,which generated day by day business processing.
Mainly master data , transaction data .
User master data
Records of R/3 users password & authorization

System strategies(1)
In time of system setup the question we have to face

How many R/3 systems will be needed ?

What function will be performed by each R/3 system in a

system landscape ?

How many clients will be needed by each R/3 system ?

What role will each client play in the system Landscape ?

Three types of Environment needed for a system strategies

Development environment (DEV)

For development activities .

Quality Assurance environment (QA)

For extensive testing the developed or customized object .Mainly for

integration testing purpose.

Production environment (PRD)

For actual company business transaction.

Combination of all the system is called SYSTEM LANDSCAPE .
Three types of system landscape are

Single-system Landscape

Two-system

Three-system Landscape

Landscape

System strategies(2)
Single-system Landscape
Development client , Testing client , Production Client on a same server .
Advantages
For this type of system , hardware cost & administrative cost is lower .
Disadvantages
Changes to client-independent or repository objects will affect the whole
environment .
The performance of the system affect all clients
Production data is a accessible from development & testing environment
Problems during the implementation of other applications , when some
production is going on .
Problems when modifying standard programs
If the system crashes the all three R/3 systems will be affected .

Most of the disadvantages with a one-system landscape are

associated with client independent changes, repository
changes, & upgrades , that immediately impact the production
environment. These disadvantages are a much greater problem
once the R/3 System is in a productive state.

System strategies(3)
Two-system Landscape
For this case development & QA testing done on same system .
But production on different system .
Advantages
The production system (PRD) containing only the finalized production
environment .
After completing the preparation phase (test, verification, and release), the
parameters and programs can be transported from the development system
(DEV) to the production system (PRD) .
(DEV client QA client PRD System).
Minimal amount of hardware investment.
Minimal system administration and change request management required
Disadvantages
Recommended only for projects with a limited amount of ongoing development
No separate quality assurance system (QAS) for isolated testing
Client-independent customizing activity must be carefully planned so that, it
does not affect other customizing/development activities

System strategies(4)
Three -system Landscape
In this case development ,QA , production take place on different system.
The most recommended system in SAP .
Advantages
New development can start without affecting the production environment.
QA system allows for integration testing of developments before promoted
to production.
Production data is secure, security will prevent access to sensitive data &
client settings will prevent the unauthorized changing of data .
Production performance is not affected by other clients, there is only one
production client .
The general sandbox client (SAND) in the development system (DEV) makes it
easier to become familiar with the new application functions and conduct
suitability testing
Client-independent customizing testing can occur without conflicts
Disadvantages
Requires increased system administration and change management activities
Increase hardware cost

Transport management system

Within the R/3 System Landscape customizing & development changes performed,
in a development client ,has to transfer to QAS client & PRD client .
SAP R/3 enables user to record changes to a CHANGE REQUEST ,which is
distributed to other client or other R/3 system .
When changes to either customizing or repository objects are made,the changed
objects are recorded to a TASK in a Change Request corresponding to a specific
user .
After completion the development ,user release the Change Request & transport
to QAS & PRD system .
Transport Directory \usr\sap\trans

DEV
DEV

QAS
QAS

PRD
PRD

SAP consultants
SAP consultants divide themselves into 3 categories
FUNCTIONAL consultant
BASIS consultant
ABAP programmers

FUNCTIONAL consultant: Experienced people in some business areas

who knows how to customize those modules
to meet the customers need.
BASIS consultant:

Technical consultants who taken care installation

sap administration , database administration.

ABAP programmer: Technical consultant who writes sap programs

& reports for any new requirements in sap by
using ABAP/4 programming language.
Customizing : Once customer buy one sap-kit,it contains all the modules
with all the business processes.the next step is to customize
to suit business needs & practices.
ABAP/4 Advanced Business Application Programming (4GL)
ABAP/4 is a SAP programming language used in the development of all standard
applications included with R/3 .SAP has designed a full purpose development
environment known as ABAP/4 development workbench.

START WORKING ON SAP BASIS

SAP Screen Features(1)

SAP screen has seven main areas: Screen Header, Menu
Bar, Standard Toolbar, Title Bar, either a Navigation
Toolbar or Application Toolbar, Screen Body, and
Status Bar..

SAP Screen Features(2)

Command Field
The Command field is used to enter transaction codes

Standard Toolbar Buttons

The SAP buttons displayed on the Toolbar provide quick access to commonly used
SAP functions.
If a Toolbar button is gray, it is not available for use on that
particular screen.

OPENNING A SAP SESSION using saplogon-pad

Navigation to opening a SAP session

1. Start Programs SAP Fronted SAPLogon
2. Choose any one of the icon SAPlogon or SAPlogon-pad from the desktop .
Choose any server name e.g. SCMA SERVER .
Then the Sap screen will open & connect to the Application server defined on SAPlogon pad

Continue ..

OPENNING A SAP SESSION using sap-session-manager

SAPfront-end
front-endcan
canbe
be
SAP
openusing
using
SAP
open
SAP
SessionManager.
Manager.
Session

ChooseApplication
Application
Choose
serverfirst
first. .
server
EnterProper
Proper
Enter
USERID,ClientID,
ID,
USERID,Client
Password&&
Password
Languagetotoopen
open
Language
thesap
sapsession
session. .
the

FIRST SCREEN ON SAP

EnterProper
ProperClient
Clientidid, ,
Enter
Useridid, ,Password
Password&&
User
Languagetotoopen
openthe
the
Language
sapsession
session. .
sap

Nowstart
start
Now
Working
Working

Start work on Basis

SAP menu Tools Administration

StartBasis
BasisAdminstration
Adminstration
Start
BasisAdministration
Administration
Basis
UserAdministration
Administration
User
ClientAdministration
Administration
Client
TransportManagement
Management
Transport

Navigation Using Transaction Codes

SAP provides a unique multi-character identifier for each system
task. This shorthand
name is called a transaction code which is a navigation alternative to
using a menu
path to get to a system task
Transaction code may contain letters only, or a combination of letters
and numbers.
Used in conjunction with a prefix such as /n or /o .
e.g . SPAM , SU01 .
/n ends the current transaction and switches to the new one without
saving any data
in the current transaction .
/o opens a new SAP session and accesses the new transaction
Command
field
Command
field
without
ending
the
with
with
current one (which will remain open in the background session)
transaction
transaction
Code.
Code.

Transaction Code(1)
Transaction is an operation that lets a user make changes to a database .
In SAP transaction is a sequence of related steps ,are screens in which data
is introduced causing the generation of other events.
The final task of a transaction is to modify the information which ultimately
goes into the database. The database is not updated until a transaction has
finished.
All the transactions in the R/3 system have an associated transaction code.
All available transaction are held in table TSTC .To see the table data we can
use the transaction codes SE16 / SE11 .
We can create user defined transaction code by using SE93 .
The Used transaction code by the user can be monitored using the transaction
code STAT.

Transaction Code(2)
Transaction
Transaction
codeSE93
SE93toto
code
maintainTC.
TC.
maintain

Userdefined
defined
User
TCstart
startwith
withYY
TC
or
Z
or Z

Transaction Code(3)
Transaction
Transaction
codeSTAT
STATtoto
code
monitor
monitor
Transaction
Transaction
codeused
usedby
by
code
anyuser
user
any

System Status
Navigation : Menu System Status

Client Maintenance
Maintain client using the transaction code SCC4

User Maintenance
Create or maintain User
using the transaction code
SU01

Maintain Authorization
Maintain User Authorization using transaction code PFCG

Configure & Maintain Transport Management System

Maintain Transport management system using transaction
code STMS .

Maintain Transport request

Maintain Transport Request using transaction code
SE01 .

Maintain RFC connection

Maintain RFC connection using the transaction code SM59.

Maintain SAP Profile

Maintain SAP Profile using the transaction code RZ10.

Maintain SAP table data

Maintain SAP table using the transaction code SE11.

To monitoring Logon user with R/3

Can Monitor any user working or not using TC SM04.

To maintain the customizing setting within R/3

Create customizing setting by the transaction code SPRO

To upload support package to R/3

Upload the support packages using transaction code SPAM

To monitoring system log messages

Monitor log of the system using transaction code SM21

Database backup scheduling

Scheduling and monitoring database backup using TC DB13

Sending System Message

Send system message to the sap users using TC SM02.

SAP SYSTEM STARTUP or SHUTDOWN(1)

Double click
clickon
onthe
the
Double
iconSAP
SAPSYSTEM
SYSTEM
icon
MANAGEMNT
MANAGEMNT
CONSOLEto
toSTART
START
CONSOLE
SAPMMC..
SAPMMC

SAPMMC
SAPMMC
Whichused
used
Which
tostart
start&&
to
stopsap
sap
stop
application
application
server..
server

SAP SYSTEM STARTUP or SHUTDOWN(2)

SAPMMC
SAPMMC

Rightclick
clickthe
the
Right
applicationserver
server
application
name(scma
(scma
name
here)the
the
here)
start/stopoption
option
start/stop
willcome
comechoose
choose
will
theright
rightone
one
the

SAPMMC
SAPMMC

Whenthe
thesap
sap
When
systemstart
start
system
properlythen
then
properly
msg_server.e
msg_server.e
xe&&
xe
disp+work.e
disp+work.e
xe
xe
willgreen
green&&
will
statuswill
will
status
show
show
Running. .
Running

SAP SYSTEM STARTUP or SHUTDOWN(3)

SAPDBA tool can be invoke from operating system (dos prompt for WinNT) using the
command C:\> sapdba

SAPDBA
SAPDBA

Sapstartup/shutdown
startup/shutdown
Sap
alsocan
canbe
bedone
doneby
by
also
usingSAPDBA
SAPDBAtool.
tool.
using

STARTUP/ SHUTDOWN can be done from operating system (dos prompt for WinNT)
using the commands
C:\> startsap (Starting sap & db )
C:\> stopsap (Stoping sap & db )
C:\> startsap r\3 (Starting sap server only ,when db is running )
C:\> stopsap r\3 (Stoping sap server only, but db will running )
C:\> startsap db (Starting db only ,but sap will not start )
C:\> stopsap db (Stoping db ,when sap already stopped )

Roles of an Basis Admin(1)

Within R/3 :
User administrator
Set up and maintain user accounts
New user setup
Reset a password
Lock or unlock a user
Security administrator
Create and maintain SAP security profiles
Monitor and manage security access and violations
System administrator
Create a system message
Start or stop the system
Maintain the health of the system
Monitor system performance and logs
Transport administrator
Transport changes from one system to another
Manage change requests

Roles of an Basis Admin(2)

Within R/3 :
Batch scheduler
Create and manage the scheduling of batch jobs
Backup operator
Schedule, run, and monitor backup jobs of the SAP database and any required
operating system level files
Disaster recovery technical manager
Create, test, and execute the SAP disaster recovery plan
Programmer
Apply Online Service System note fixes to programs
Data Dictionary (DDIC) manager
Change the Data Dictionary (when applicable)

Roles of an Basis Admin(3)

Outside R/3 :
DBA for the specific database on which the system is running
Manage database specific tasks
Maintain the databases health and integrity
Operating system administrator
Manage the operating system access and user IDs
Manage operating system specific tasks
Desktop support
Supports the users desktop PC
Maintenance R/3
Changing system profile parameters
Applying hot packages or legal change patches
Upgrading the kernel
Client copy (create, copy, and delete)
Transporting objects from system to system

SAP Today
4th largest software vendor in the world
30+ years of business experience
7,500+ customers in 90+ countries
13,000+ R/3 installations
1,400+ R/2 installations
~13,000 employees
Worldwide presence in over 50 countries outside Germany

SAP WORLWIDE HEADQUARTER ADDRESS :

SAP AG Germany
Neurottstrass 16, D 69190 Walldorf ,Germany
Phone : 06227 34 0
Web site : www.sap.com

www.sap-ag.de