SAP Full Notes Latest

BUSINESS APPLICATION SOFTWARE FOR INTEGRATED SOLUTIONS
(BASIS)
SAP:
Systems applications products for data processing.
Developed in Germony.
Its an ERP
ERP: Enterprise Resource Planning.

Planning the resources in an organization is called ERP.
What are the functionalities in a company?
A company is having different modules like
- Sales
- Finacials
- Purchasing
- Production
- Human Resources
Integrationof all the modules done by ERP – SAP.
Basics to startup with BASIS Administartion
Computer
A computer is a machine for manipulating data according to a list of instructions or an
electronic device for the storage and processing of information or a programmable
machine which runs with two principal characteristics as
1
It responds to a specific set of instructions in a well-defined manner.
It can execute a prerecorded list of instructions (a program).
Software
Written coded commands or set of instructions that tell a computer what tasks to perform
or Computer instructions or data. Anything that can be stored electronically is called as
software. The storage devices and display devices are hardware.
Software is often divided into two categories:
systems software : Includes the operating system and all the utilities that enable the
computer to function.
applications software : Includes programs that do real work for users. For example,
word processors, spreadsheets, and database management systems fall under the category
of applications software.
Program
An organized list of instructions that, when executed, causes the computer to behave in a
predetermined manner. Without programs, computers are useless.
A program is like a recipe. It contains a list of ingredients (called variables) and a list of
directions (called statements) that tell the computer what to do with the variables. The
variables can represent numeric data, text, or graphical images.
Computer Hardware
Hardware is the physical medium built with electronic technology lies between input and
Output.
As an example objects that you can actually touch, like disks, disk drives, display
screens, keyboards, printers, boards, and chips.
In contrast, software is untouchable. Software exists as ideas, concepts, and symbols, but
it has no substance.
The distinction between software and hardware is sometimes confusing because they are
so integrally linked.
Computer Hardware devices
Random Access Memory (RAM) – The temporary storage device and part of CPU which
is used for program execution and short term data storage, so the computer does not have
to take the time to access the hard drive to find the file(s) it requires. More RAM will
normally contribute to a faster PC. RAM is almost always removable as it sits in slots in
the motherboard, attached with small clips. The RAM slots are normally located next to
the CPU socket.
Motherboard – It is the main component inside of a computer designed using electronic

technology with all circuits internally within it. It holds the processor, memory, and any
2
add-in boards. It's inside the case and is the component that all of your peripherals plug
into. It is also called the "mainboard," or, "mobo," for short.
Processor - The exact term processor is a sub-system of a data processing system which
processes received information after it has been encoded into data by the input sub-
system. These data are then processed by the processing sub-system before being sent to
the output sub-system where they are decoded back into information.However it is
usually termed as the microprocessor, the brains of the modern day computers.
Hard disk – Its is a permanent storage area of a computer and a hardware device part of
CPU which can store anywhere from 20MB to more than 200GB. Hard disks are also
from 10 to 100 times faster than floppy disks.
It is physically a round plate, Magnetic or Optical, on which data can be encoded.
Operating system
It is what is needed to run the programs on a computer. It makes the link between
programs and hardware.
Computer Network
It is combination of multiple computers connected together using a telecommunication
system for the purpose of sharing data, resources and communication. For a while, a
home computer network may consist of two or more computers that share files and a
printer using the network. The size and scalability of any computer network are
determined by the hardware used as well as which protocols are being implemented.
Or a network consists of two or more computers that are linked in order to share
resources (such as printers and CD-ROMs), exchange files, or allow electronic
communications. The computers on a network may be linked through cables, telephone
lines, radio waves, satellites, or infrared light beams.
The three basic types of networks include:
Local Area Network:
A Local Area Network (LAN) is a network that is confined to a relatively small area. It is
generally limited to a geographic area such as a writing lab, school, or building. Rarely
are LAN computers more than a mile apart.
 A local area network (often called a LAN) connects two or more computers in a house
or an office.
Wide Area Network:
3
Wide Area Networks (WANs) connect larger geographic areas, such a Solar Soft ,
Ameerpet , the India, or the world. Dedicated transoceanic cabling or satellite uplinks
may be used to connect this type of network.
 A corporate network enables communication among various offices of the same

organization.
In fact, two computers connected over the Internet is not considered a computer network.
Some basic types of computer networks include:
 An "internetwork", sometimes called a Wide Area Network (because of the wide

distance between networks) connects two or more smaller networks together. The largest
internetwork is called the Internet.
Computers can be part of several different networks. Networks can also be parts of bigger
networks.
If we consider as the local area network in a department store is usually connected to the
corporate network of the parent company, and may have privileges with the corporate
network of a bank. Any connected machine at any level of the organization may be able
to access the Internet, for example to demonstrate computers in the store, display its
catalogue through a web server, or convert received orders into shipping instructions.
Where in the network technology, there are two different computers existing, known as
Server Computer - A computer that delivers information and software to other computers
linked by a network
Client Computer - A computer that recieves information and software from server
computer linked by a network
OSI Model
The OSI (Open System Interfconnection) model serves as a logical framework of
protocols for computer-to-computer communications. Its purpose is to facilitate the
interconnection of networks. It is the seven-layer Reference model was developed by the
ISO subcommittee and defined as below…
The 7 Layers of the OSI Model
4
The OSI, or Open System Interconnection, model defines a networking framework for
implementing protocols in seven layers. Control is passed from one layer to the next,
starting at the application layer in one station, proceeding to the bottom layer, over the
channel to the next station and back up the hierarchy.
Application (Layer 7) -This layer supports application and end-user processes.

Communication partners are identified, quality of service is identified, user authentication
and privacy are considered, and any constraints on data syntax are identified. Everything
at this layer is application-specific. This layer provides application services for file
transfers, e-mail, and other network software services. Tiered application architectures
are part of this layer.
Presentation (Layer 6)- This layer provides independence from differences in data
representation (e.g., encryption) by translating from application to network format, and
vice versa. The presentation layer works to transform data into the form that the
application layer can accept. This layer formats and encrypts data to be sent across a
network, providing freedom from compatibility problems. It is sometimes called the
syntax layer.
Session (Layer 5)- This layer establishes, manages and terminates connections between
applications. The session layer sets up, coordinates, and terminates conversations,
exchanges, and dialogues between the applications at each end. It deals with session and
connection coordination.
Transport (Layer 4)- This layer provides transparent transfer of data between end
systems, or hosts, and is responsible for end-to-end error recovery and flow control. It
ensures complete data transfer.
Network (Layer 3)- This layer provides switching and routing technologies, creating
logical paths, known as virtual circuits, for transmitting data from node to node. Routing
and forwarding are functions of this layer, as well as addressing, internetworking, error
5
handling, congestion control and packet sequencing.
Data Link (Layer 2)- At this layer, data packets are encoded and decoded into bits. It
furnishes transmission protocol knowledge and management and handles errors in the
physical layer, flow control and frame synchronization. The data link layer is divided into
two sublayers: The Media Access Control (MAC) layer and the Logical Link Control
(LLC) layer. The MAC sublayer controls how a computer on the network gains access to
the data and permission to transmit it. The LLC layer controls frame synchronization,
flow control and error checking.
Physical (Layer 1)- This layer conveys the bit stream - electrical impulse, light or radio
signal -- through the network at the electrical and mechanical level. It provides the
hardware means of sending and receiving data on a carrier, including defining cables,
cards and physical aspects. Fast Ethernet, RS232, and ATM are protocols with physical
layer components.
What is a Protocol?
A protocol is a set of rules that governs the communications between computers on a

network. These rules include guidelines that regulate the following characteristics of a
network: access method, allowed physical topologies, types of cabling, and speed of data
transfer.
What is IP Address ?
IP addresses
 are unique, 32-bit addresses which are correspond to connections, not hosts
(generally, move connection == change IP address) & are referenced by humans
via dotted decimal (or dotted quad) notation, one number per 8 bits (1 octet or
byte), e.g., 128.192.6.7 which consist of three primary classes A, B, and C (class
D is for multicast) of the form [netid,hostid]
Class formats
Subnet Mask (netmask)

 32-bit value generally used to subdivide (subnet) a given IP class network into
smaller (sub)networks and Netmask determines which portion of an IP address is
the network address and which is the host address
 An IP address bit is a network address bit if the corresponding netmask bit is 1
 An IP address bit is a host address bit if the corresponding netmask bit is 0
6
 "Natural netmask" has all netid bit locations = 1 and all hostid bit locations = 0
(e.g., 255.0.0.0, 255.255.0.0, and 255.255.255.0 for class A, B, and C networks,
respectively)
 Netmask example:
Netid and hostid conventions:

 Network addresses have hostid with all bits = 0 (e.g., 128.192.0.0 with
netmask=255.255.0.0 and 128.192.6.0 with netmask=255.255.255.0)
 Directed broadcast addresses have hostid with all bits = 1 (e.g., 128.192.255.255
with netmask=255.255.0.0 and 128.192.54.255 with netmask=255.255.255.0)
 "Limited" broadcast has all bits = 1 (e.g. 255.255.255.255)
 Loopback address 127.xxx.yyy.zzz used for internal testing, no traffic generated
(typically 127.0.0.1)
IP network ranges by class:

 Class A == 1.0.0.0 - 126.0.0.0
 Class B == 128.xxx.0.0 - 191.xxx.0.0
 Class C == 192.xxx.yyy.0 - 223.xxx.yyy.0
 Class D == 224.xxx.yyy.zzz - 239.xxx.yyy.zzz (multicast IP)
What is Database and uses:
1) Storing data in an organized way

2) Duplication of data avoided.
3) Indexing for fast retrivals or access.
4) Normalisation
What is Normalisation:
It is the process removing duplication by splitting tables into different parts.
Difference between i) On site and ii) Off site
What is Data Centre?
7
Data centre is the server room, where all the data of the company will be stored.
Different OSs:
1) Windws 2) Unix 3) Linux 4) Solaris 5) AIX
Databases:
1) Oracle 2) SQL server 3) DB2 4) Sybase 5) Informaix

3) MAX DB - It is installed on memory.
If system restarts or shutdown all the data will be lost.
End users:
People who are using for productive work for the company are called as end
users.
High Availabiligty: for HDs
1) Mirroring.
2) RAID – Redundant Array of Independent Disks
3) SAN – Storage area network.
4) Clustering - (In case of Overload)
5) Stand by server – Incase of Disaster Recovery
i) Log shipping
ii) Replication
6) Backups.
Mirroring:
It is used in case of operating system as well as database log files. If one hard disk
fails another hard disk will take care.
In this technique data is written to two duplicate disks simultaneously. Using this way if
one of the hard disk fails the system can initially switch to another disk without analysis
of data or server.
RAID: (Redundant Array of Independent Disks)
Storing the same data in different place on multiple hard disks.
If any one of the hard disks fails the data will store automatically in a disk called hotspare
by RAID.
8
SAN:
If we are having 5 applications for each application here we are having 5 servers.
Maintaining 5 servers is tough. So here SAN came into scenario, where we will store all
data in a common place.
SAN is also having mirroring. So there is no chance to lose of data.
5) Clustering (In case of Overload):-
-Here when the load is more on CI (central Instance) automatically it will transfer
the transactions to DB directly is called as clustering.
 In other words connecting 2 or more computers together in such a way they
behave like a single computer which is also called as clustering.
 Clustering is used for parallel processing.
 If any one of the above server fails another server will take of user.
5) Stand by servers (In case of Disaster Recovery)
In case of any disaster/calamatees…there may be chance of nor working of server. If

one server is not working aother server will take response an will give service for the
users.
a) Log shipping :- It is time consuming.

If server is slow we have chance of lose of our data
b) Replication:- It will directly done at database level.

Exact copy will pass to all related server, wherever the servers were
located. So there is no chance of lose of data.
9
6) Backups:
a) OFF line Backups: -

During offline backup we shutdown the server and we will take back up. It is
also called as cold backup.
b) ON line backup:-
When the system is up and running then we take the backup which is called as
ON line backup. It is also called as HOT backup.
Connectives:
1) HUB
2) SWITCH
3) ROUTER
Advantages of SAP:
1) Rich set of modules.

2) Data Integrity.
3) Data Sharing between modules is easy.
4) Easy administration.
5) Only one databse.
6) It will support all the available databases and os.
7) Upgrade from time to time.
8) 24X7X365 Global support.
9) User Friendly.
10) Security.
11) Supports interface to other SAP/non-SAP systems
12) SAP supports multilanguages available using UNICODE
Unicode :- It is R/3 software provides access to almost all languages in the world.
It uses 2 bytes.
Non-Unicode:- It is the version of R/3 which supports only few languages in the
world.
13) One GUI for all R/3 systems.
14) Common Programming Language which supports OOPS and ABAP.
15) SAP supports JAVA.
16) Easy Add-ons
----- To add funtinality to existing system.
10
Hour Glass State:
When the user con’t navigate from one screen to another screen that situation is
called as hour glass state.
Hardware Sizing:
To analyse the business requirements of an organization level depending

upon the users data will allocate the hardware resources.
We can give over business time, standby time, legacy data, o/s and DB
version, data archiving.
There are 2 types of Hardware sizing.

1) User Based 2) Object based / through put
1) User based: In this again of 2 types i) Named users i) concurrent users.
Names Users:
Low Normal 0-480 dialog steps.

Medium Transactional 480-4000 ds
High Power Users 4000-14,000 ds
Dialog step:-
User communicating with system through application server & database.
* Who are logged into the system is called as Named users.
Concurrent Users:
 Users who are creating more load on the system is called concurrent users.
 These are also Named Users.
11
 These are also called as High Users.
12
Steps for Hardware sizing:
1) Contact SAP
2) Get OSSID (Online SAP Service ID)
3) Login to www.service.sap.com/qsizing (It is sap official site)
4) Go to Quick Sizer Tool
5) Enter project name/Customer Number
6) Create Project
7) No. of Users (Low/Medium/High Activities)
8) Amt. of legacy data.
9) No. of modules.
10) I) user based ii) object based.
11) Select operating system of SAP
12) Select database and its version.
13) Select the peak load time.
14) High availability.
15) Data Security[Mirroring/Raid/Clustering ….etc.,]
16) Save the details.
17) Calculate the Results.
Output:
1) Disk size.
2) Memory requirement in MB
3) CPU requirement in SAPS [System Application Benchmarks for Performance
standards]
 SAPS are calculated based on the usage of processors.

 Analysis says that each 1500 saps we require one CPU.
SSCR: SAP Software Change Registration.
13
Architecture of SAP R/3:
Presentation layer/tier/server:
It is the interface to a user. This is the only layer from where users connect to the
SAP system. DIAG (Dynamic Information Active Gateway) is the protocol which is
used to communicate b/w user and SAP system. Using this we can have
I) Our own font settings

II) Our own langnguage settings.
III) It is user friendly.
IV) With the help of message server which identifies favourate server and
logs onto it.
V) It is intelligent server.
VI) It is operating system & db independent.
14
Presentation layer is nothing but SAP GUI: SAP GUI is to facilitate users to log into R/3
system. This logon can be used to all the components of SAP (CRM,APO,BW,XI etc.,)
Types of SAP GUI:
1. SAP GUI for Windows.

2. SAP GUI for HTML.
3. SAP GUI for JAVA.
SAP GUI for Windows: It is for the windows environment. Support platforms
includes windows 98,windws NT4, Windows 2000 and
windows XP.
SAP GUI for HTML: Front end requires only a web browser, an ITS is necessary
to conver the presentation into HTML.
SAP GUI for JAVA: It is used only where java is supporting.

It supports Windows 98,windws NT4, Windows 2000 and
Windows XP
MacOS 9
MacOS x
Linux, HP UX, Solaries, AIX
OS/2.
R/3 Version GUI Version
3.1i 3.1i
4.6C 4.6C
4.6D 4.6D (BASIS)
4.7 EE 6.00 SAPWEBAS (BRTOOLS)
ECC 5.0 6.40 SAPWEBAS
SAPGUI version: GUI versions are released from time to time based on the
component releases. Upto 4.6D version it is following the release of the R3
component. From 4.7D onwards it following the release of SAPWEBAS.
GUI initialization: GUI is initialized by the following INI files.
1. saplogon.ini
2. sapmsg.ini
3. saproute.ini
4. sapdoccd.ini
1. saplogon.ini : This files consists of the system details like name of the
server, SID and instance umber. When we click on new tab in SAP GUI to
15
enter description of the new server after saving it will be entered into this
file. Without this file we cannot logon into the system and there will be no
entries to logon from SAPGUI.
2. sapmsg.ini: This file is used to identify least loaded server in the logon
group, if logon load balance is configured. This file consists of message
server details.
3. saproute.ini: This file is used to communicate with SAP systems over the
saprouter.
4. sapdoccd.ini: This files is initialized when the library is accessed. It

contains the path of library.
16
Application layer/tier/server:
It is used to :
i) Provides business areas
ii) Configure work process
iii) Reduce traffic on DB.
iv) Configure memory areas.
v) Business logic & presentation logic handled.
It consists of dispatcher, work processes, memory areas, buffer areas and interpreaters,
Dispatcher: This represents an instance, there will be only n e dispatcher per instance.
This is used to handle the user requests. Dispatcher receives the users request and keeps
them in the queue (dispatcher queue) based on the available free resources, user request
will be assigned with work process on FIFO basis. Dispatcher runs by an executable
disp+work.exe. This can be monitor by using a command line tool dpmon(It listens on
the port 3200+instancenumber.
Work process: Dispatcher assigns the user request to a dialog process, dialog is the only
process which will handle user request.
Dialog process: It is used for handling generation of reports, updating the temporary
tables, updating the spool tables, updating the background tables so that update, spool
background processes reads those tables for execution.
Dialog work process runtime is restricted to 600 sec. Which is manipulated by rdisp/
Dialog work processes should be 1:5 to 1:10.
Update work process: This process is used to update the database initially update
requests are handled by dialog work process as they couldn’t execute within the specified
time. The task has been moved to update process. It is also the reason for obtaining the
transaction consistency because dialog process handles starightfull request. Dialog
process updates the temporary tables. Update process reads the temporary tables and
update the database.
Enque process: Enqueue process is used to lock and unlock SAP objects. It will update
the database and takes the users request. In order to handle this mechanism SAP has
defined enqueue and dequeue (unlock) modules. Enqueue process will issue locks to
message server to all the dialog instances. That is dialog communicates with message
server & message server in term talks to enqueue to get the lock.
 Dialog process communicates with the message server and message server
communicates to enqueue
 Dialog processes on central instance can communicate with enqueue directly
to obtain locks.
17
Background Process: The long running, time consuming and expensive reports or
updates will be used to schedule in the non-dialog mode using the background process.
Dialog work process receives the background request & updates background request &
updates background job tables. Background work process reads the job tables for every
60 sec & executes them
Message Server: Message server is used to communicate with all the available
dispatchers. If logon load balance is configured, message server identifies the least
loaded server in the logon group. It is run by an executable msg_server.exe. This is also
used to communicate with enqueue to issue locks to the work process coming from dialog
instance.
Gateway: There will be one gateway work process for each instance. Gateway is used
to communicate with external system. It listens on the port 3300 + instance no.
Spool Process: Spool process is used to output the documents to the printer, fax, email,
pager and sms. Dialog process receives the spool request and updates spool tables or
stores spool data at OS level. Spool process reads the spool tables or spool data and
output to specific device.
Note: All the work process runs with executable disp+work.exe
Memory Areas:
In order to define a work process we should have enough resources at the rate of
75mb to 150mb for each work process. When the user request is assigned to a work
process, work process requires certain amount of memory to execute the user request.
Ex: Roll memory, extended memory, heap memory
Buffer Areas:
There are two types of buffer areas
1. User related buffer (user specific)

2. R/3 buffer (non-user specific)
User buffers are nothing but user context.
User Context: User context is the area where user logon attributes, parameters,
authorizations and earlier accessed content are stored. These are valid until the user
session. User logout, buffers are lost.
18
R/3 buffers: Frequently accessed contexts like programs, tables, fields, currencies,
calendar, measurements are stored in R/3 buffers.
The data which is frequently accessed and rarely changed is eligible for buffering.
These buffers are accessed by all the users. These will remain until the restart of the
instance. If the instance is restarted, buffers are lost.
Interpreters:
1. ABAP Interpreter: This is used to interpret the ABAP code embedded in the
user request
2. Screen Interpreter: This is used to interpret the screens.
3. SQL Interpreter: This is used to interpret SQL Statements in the ABAP
program.
Note: Task handler which is a part of work process handles the interpreters.
Dispatcher: It receives user request and assigns work process or keep user request in
dispatcher queue.
Task Handler: It is the agent which process the user request by segregating into screen ,
abap, SQL interepreters. As it consists 3 interpreaters. context
User Context:
The user context is the buffer area where it stores user logon attributes,
authorization parameters.
Despatcher Queue: It is the queue where user exists when work processor is busy. It
follows FIFO.
Database Layer/tier.
It is the layer where database is hosted. It has its own memory areas, buffer
areas, work processes etc., A central RDBMS realizes the database layer of an SAP R/3
systems. Communication between the application and the database layers occurs
exclusively over SQL. SAP R/3 work processes typically use only the Open SQL
interface.
Processes:
Dialog : Dialog work processes fulfill all
Installation:
19
Pre-Requisites:
5. Proper hardware is received according to H/W Sizing.

6. Verify SAP Software.
7. Installation document from SAP  www.service.sap.com
8. Read the document and highlight the steps involved inst. guides.
9. Internet connection to resolve the runtime issues.
10. Get the known problems in installation [ECCS] from SAP Market place
[www.service.sap.com/notes].
11. Install o/s and patches [h/w vendor
12. Get a static IP address from N/W team
13. Install db & patches (SysDBA, Basis)
14. Specify an entry in \etc\hosts
15. Dump the s/w into server
16. Setup Virtual Memory
17. Install current version of JAVA because SAP Installation too requires
JAVA Runtime Environment [JRE]
18. Set the environment variable JAVA_HOME & Path
19. Set the Ethernet Card/LAN/ for mass file sharing.
[Landscape : Arrangement of systems.]
There are 2 installation tools:
1. R/3 setup <= 4.6C

2. sapinst =4.7 EE
Services:
1. saposcol.
2. SAP<SID_instace<number
3. oracle services.
4. osservices.
SAP Installation consists of 3 Types:
1. Centrol Instance:
2. Database Instance:
3. Dialog Instance:
Centrol Instance: This is the instance where all the services are configured and it
manages all the instances through message server. CI is named as
“DVEBMGS”00&instance number. The services of instance number are as follows:
20
D - Dialog
V - Update
E - Enque
B - Background.
M - Message
G - Gateway
S - Spool
4. Go to dump
NT/386/sapinst.exe
5. Select centrol instance.
6. Specify the <SID and instance number.
<SID : System Identifier which is of 3 character and it should be
unique in the landscape. It should not be either SAP , ERP or other
reserve words. The main objective of <SID is used to identify the
Instance.
7. Specify the host name.
8. Specify the ORACLE home path.
9. Assign 60% of memory to CI. (for productive 70%(CI)+30%(DI))
10. Specify the path for usr directory C:,D:, or E….
11. Specify passwords for <SIDADM,SAPSERVICE<SID..
<SIDADM: Is R/3 system administrator which is used to start & stop R/3
systems and has administrative previlieges.
SAPSERVICE<SID: This is a service user which is used to run all the SAP
services like SAPOSCOL, SAP<SID_instancenumber.
12. Specify kernel path.
13. Specify the Dispatcher/Gateway/Message server port numbers.
14. Continue installation.
Database Instance:
1. Select Database Instance.

2. Specify SID,host name and Instance number.
3. Specify the installation on new database or use existing database.
4. Specify the database, SchemaID (SAP<SID)
SchemaID : It is the owner of the database.
5. Specify the memory 40% of physical memory.
6. Specify the log files location.
i) Mirror logA, OriglogB - 1 disk
ii) OriglogA, Mirror Log - 1 disk
Log files contains the changed data.
7. Specify the path of Kernal Directory.
8. Specify the path for SAP directory
21
[sapreorg, spacheck, sapbackup, saptrace, saparch, oraarch]
9. Specify the path for data directory.
[sapdata1,….sapdata2]
10. Specify the export DVD/dump path.
11. Specify passwords for <SIDADM and SAPSERVICE<SID.
12. No. of parallel processors to expedicate the installation process.
13. Select MNLS [Multi National Language Support].
14. Specify passwords for system,sys,DB etc.,
Dialog Instance: This is an additional application server which is to install and to

provide more number of work processors to cater more number of users. [Provides
additional memory and CPU).
1. Select the dialog instance.

2. Specify the CI. (Host name)
3. Specify the DI (Host name) (This is where data is stored).
4. Specify the host name and number
D<Instance number
D01, D02……
5. Specify the kernel path.
6. Specify the passwords.
Installation of GUI:
1) If users are minial:

(10-15) users goto user desktop & install.
2) If we have more number of users. Copy the GUI installation CD into a file server.
Share the folder to every one.
3) Write a logon script to network system administrator to trigger during the user
logon user login.
4) Using a 3rd party tool like Microsoft monitoring server where all the users
desktops are monitored centrally.
Check CI installation:-
1. Check the services.

a) Saposcol : SAP Operating system collector. This is only one SAPOSCOL
in the system.
b) sap<SID_00: It is an instance service whichis used to start the SAP
instance.
c) oraTNSlistener:
d) oraService_SID: This is oracle service user <SID which is used to start
oracle.
2. Check users: <SIDADM and SAPSERVICE<SID and DB users.
22
OP$<SIDADM and OP$SAPSERVICE<SID
To see them connect system/mananger
SQL select * from dba_users.
OP$ mechanism: It is used to logon on to the database by O/s users without

prompting a password.
3. Logs:
i) syslog in MMC
ii) Application system logs in Event Viewer.
iii) sapint.log
iv) aler<SID.log
v) Developer traces in work directory.
R3trans –d : It generates a trans.log in home directory where command is executed.
Note: sapstartsrv.exe : When we were not getting MMC. Type details of the SAP system
which is asking.
4. Directories:
i) \\usr\sap\trans
ii) \SID\sys\exe\run\sys\profiles
iii) Check al lthe sapdata…
iv) Check all the folders in /oracle/SID
Starting R/3 system.

Stopping R/3 system.
Profiles:
Profiles are used to configure various system parameters. For R/3 system we
have 3 types of profiles.
1) Startup profile.
2) Default profiles.
3) Instance profile.
Startup profile: - START_DVEGMGS00_hostname.pfl
It is used to start i) database database startup executable- strdbs.cmd

ii) Start message server. msg_server.exe
iii) start dispatcher : disp+work.exe
Default profile:- ( Default.pfl)
23
It consists of global parameters which will be applicable across all the
instances in an R/3 system. It consists:
SAPSYSTEMNAME = S47
SAPDBHOST = lolla
rdisp/mshost = lolla
rdisp/sna_gateway = lolla
rdisp/sna_gw_service = sapgw00
rslg/collect_daemon/listen_port = 37
rslg/collect_daemon/talk_port = 13
rdisp/bufrefmode = sendoff,exeauto
ms/http_port = 8100
dbs/ora/tnsnames = S47
Instance profile:- This profile is sued to set the parameter for an instance.
<SID_DVEGMGS00_hostname.pfl
SAPSYSTEMNAME = S47
INSTANCE_NAME = DVEBMGS00
SAPSYSTEM = 00
rdisp/wp_no_dia = 7
rdisp/wp_no_btc = 2
rdisp/wp_no_vb = 5
rdisp/wp_no_vb2 = 2
rdisp/wp_no_enq = 1
rdisp/wp_no_spo = 1
SAPGLOBALHOST = lolla
PHYS_MEMSIZE = 1222
DIR_TRANS = D:\usr\sap\trans
icm/server_port_0 = PROT=HTTP,PORT=8000,EXTBIND=1
DIR_ORAHOME = D:\oracle\ora92
The naming conventions for the profile:
1) START_DVEBMGS00_HOSTNAME.pf; - CI
24
START_D01_DVEBMGS00_HOSTNAME.pfl - DI
2) Default.pfl
3) <SID_DVEBMGS00_HOSTNAME.pf; - CI
<SID_D01_DVEBMGS00_HOSTNAME.pfl - DI
DVEBMGS : Specifies centrol instance i.e., all the work processors are configured here.
Note: Here there is only one Default.pfl which Global.
Startup profile in DI consists of startup of dispatcher.

Instance profile in DI will be same as Instance profile of CI.
The parameters which are configured in default profile will be overridden by

Instance profile.
Client Copies: There are 3 types of client copies.
1. Local Client Copy (SCCL).
2. Remote Client Copy (SCC9).
3. Client Export(SCC8) and Client Import (SCC7)
1. Local Client Copy : This is a client copy which is used to perform

within the sam SAP system.
Ex:
Client copy From D47(000) to D47(111).
Procedure :
Pre-requisite: Create a new client D47(111).
Procedure :
1. Login into newly created client 111 in D47 with sap* and password pass.
2. Goto SCCL.
3. Give the below details:
SAP Profile : SAP_ALL

Source Clinet : 000
25
Source UMR : 000
4. Select Scheduled background job, schedule job, continue, immediate,

check, save, continue.
5. Goto SCC3 and monitor the client copy log.
2. Remote Client Copy (SCC9) : This is a clietn copy which is used to

perform between two different system.
Ex:
Client copy form Q47(111) to D47(222).
Note : We require RFC (Remote Function Call) between two different System.
Procedure :
Pre-requisite: 1) Create a new client D47(222).

2) RFC must be created between 2 systems.
Procedure :
1. Login into newly created client 222 in D47 with sap* and password pass.
2. Goto SCC9.
i) Target Client : 222

ii) Selected Profile : SAP_ALL
iii) Source Destination : RFC Name
iv) System Name : Q47
v) Source Client : 11

5. Goto SCC3 and monitor the client copy log.
3. Client Export(SCC8) and Client Import(SCC7):
This is a client copy which is used to perform within the same system
26
or between 2 different systems using TMS.
Ex: Users from D47(111) to D47(222) or Users from Q47(500) to D47(111).
Procedure:
1. Login into D47(111)

2. Goto SCC8.
1. Selected profile :SAP_USER

2. Tartget system :D47
4. Then it gives 3 transports:
KO -- Cross client
KT -- Client specific --
KX -- Client Specific texts.
Procedure Import(SCC7):
Then we login to target system D47(222)
1. Import the transprt (KT)

2. Goto SCC7.
4. Then users comes from D47(111) to D47(222).
Profiles in SAP system:
During the SAP installation following 3 profiles will be created at OS level.
1. Default Profile
2. Startup Profile
3. Instance Profile
Default Profile:
This profile is used to add/modify global parameters like

instance, buffer
27
and security parameters. The parameters whatever we add/modify in
default profile which effect comes to
all the applications servers. Only 1 default profile will be there for
one SAP system.
It is represented as DEFAULT.PFL.
2.Startup Profile:
This profile is used to start i) database ii) message server iii) dispatcher.
One each startup profile per instance/server.
It is represented as START_DVEBMGS<in>_HOST.PFL.
3. Instance Profile:
This profile is used to add/modify parameters to application server

like instance, buffer and security parameters. The parameters whatever
we add/modify that effect comes to the particular isntance only.
One each Instance profile per instance/server.
It is represented as SID_DVEBMGS<in>_HOST.PFL.
Ex:SID = S47 IN = 01 HOST=NAVIN Then profiles are:
1. DEFAULT.PFL
2. START_DVEBMGS01_NAVIN.PFL
3. S47_DVEBMGS01_NAVIN.PFL
Assignment:
1. Difference between Default profile and Instance profile.
Default profile is global.

Instance profile is local to particular instance.
2. If there are 3 application server/instance ( 1CI and 2 DI's) then

how many profiles will be there.
28
Ans:1DF+3SP+3IN = 7 profiles
3. if there 4 application servers then 9 profile.
4. All the profiles are location in /usr/sap/SID/SYS/profiles.
5. Startup sequence of the profiles.
1. Startup profile.
2. Default profile
3. Instance profile.
SAP Instance Management:
We can management instance using following 3 ways with profiles.
1. RZ10
2. RZ11
3. Os level.
ALL PROFILES ARE AVAILABLE AT /usr/sap/S47/sys/profiles
RZ10: It is used to add/modify static parameters, if we modify any

parameters using RZ10 then we must have to restart the sap system to see
the effect.
Procedure to increase dia workprocess by 2:
1. Login into SAP system in any client(111).

2. Goto RZ10.
3. Select the instance profile, extended maintenace and click on change.
Increase the parameter:
rdisp/wp_no_dia = 4
4. Select copy, back, SAVE, Yes, Continue.
5. Restart the sap system to see the effect using SAP MMC.
29
2. RZ11 : It is used to add/modify dynamic parameters, if we
add/modify any prameters using RZ11 then we no need to restart the SAP
system but if we start the SAP system then we lost the effect of the
changes.
RZ11 is also used to see the documentation of the parameters.
How to know static or dynamic parameters:
1.goto rz11
2.type paramenter
3. select display
4. then we get DynamicallySwitchable is tick then the parameter is dynamic.
3. OS level : We can add/modify parameters at os level also using

profiles. If we add/modify any parameters at os level then we must
have to restart the SAP system but the problem with parameter changes
using os level is we dont have version management.
Procedure: (increase BTC by 1) using os level.
1. Goto Profiles./usr/sap/S47/sys/profiles.
2. Open the instance profile.
3. increas the parameter by 1
rdisp/wp_no_btc = 3
How to check this at SAP level: GOTO SM50 ( work process overview )
What is the difference between changing the parameters at os level and

using RZ10.
In RZ10 we have version management whereas at os level we dont have

version management.
Quesion 1. What is the difference between RZ10 and RZ11.
Assignment:
Question 2. Change the default client as 111.
30
Change the parameter login/system_client = 111 using RZ10 or at level.
31
Startup problems:
1) Check all the services.

2) Check for syslog in MMC.
3) Check for applicationlog, system log in even viewer.
4) Check alert<SID.log
5) Check memory.
6) Check all the environment variables.
7) Check all the executables.
8) Stderr0,1,2
7 & 8 files are available in
\usr\sa\p\<SID\DVEBMGS\work directory
9) Enough space is not available.
10) Archive stuck
11) Changes in profile parameters.
12) Tablespace overflow.
13) Check n/w connective between CI/DB.
14) Kernal executable corrupted.
Post – Installation Activities:
1) SICK / SM28 (SAP Installation Consistence CheK)

2) Slience (Used to install saplicense) Get hardware key - saplicence –get
Goto to SAP market place get license key with the help hardware key.
3. SE06 - Click perform-post installation
4. SR13
5. SMLT :- Perform any additional language installation.
6. RZ10 :- Utilities - import profiles of all the active servers.
7. SU01- Create super user and change passwords of sap* and ddic and lock them.
8. STMS
9. SCC4 - Client creation.
10. SCCL - Local client copy.
11. SPRO - Allow for customizing. SE38 and SE80
SAP GUI problems:
Reason: User couldn’t logon to the system First, ask the user to send the screenshot of
the error msg.
1. Network Interface problem.

2. N/W connectivity b/w GUI & SAP system.
3. Check the entries.
4. GUI showing special characters.
32
33
ASAP Methodology:
It stands for Accelerated SAP.
1) Preparation.
2)
3) Business Blue print.
4) Realisation.
5) Pre-go-live.
6) Go-live & support.
Transaction codes in SAP Basis:
SUPPORT PACKAGES: or Patches / Hot packs / LCP/CRT’s
Support packages or support stats provides enhanced functionality,

changes to the existing data dictionary elements, repository objects like reports programs,
transactions etc.,
Support packages of various types, few of them are:
1) Basis support packages - SAPKB620050

2) ABAP support packages - SAPKA620050
3) APL support packages - SAPKH470050
4) HR support packages 2324 - SAPKE470050
In order to display the current support package level.
 Go to system + status + click on Magnifier.

 Then all the package levels will be displayed.
Pre-requisites for support packages:
 There should be 2 Background jobs.

 The latest SPAM/SAINT versions should be applied on the system.
 There should be enough space to hold the support packages in EPS/in
 There should be no aborted packages.
 Support packages should be applied on this sequence of nos. of support
packages level.
 Upgrade the Kernel version if required.
 Apply support packages in order of BASIS/ABAP/APPL/HR.
 Technical and functional consultants needs to be informed while applying
support packages because when the system updating DD elements, repository
objects functional and technical objects. Functional and Technical team are
the right people to advice whether to keep the existing functionality or move
on the current functionality which comes in SP.
 Scheduled down time and inform users.
 Go through composite note thoroughly before applying support packages.
34
 If the support package is more than 10MB, UNCAR the file using
sapcar –xvf <filename.CAR
When we uncar two files are generated with extension .ATT or .PAT.
 When the support pack is aborted and could not be resolved the final remedy
is to delete entries in the these 2 tables(PAT01 and PAT03).
 Packages once applied cannot be reverted back.
 If we want to revert, then contact SAP technical support.
How to update the SPAM:
Updating SPAM from 16 to 20.
1. Download required SPAM level 20 (KD62020.CAR).
2. Uncar the car file.
sapcar -xvf KD62020.CAR
3. Then we will get 2 files .ATT and PAT and copy thes in /usr/sap/trans/EPS/in
4. Login into SAP level in 000 client with DDIC type of user.
5. Goto SPAM
6. Select Support Package -- Load packages -- From application

server. Click BACK.
7. Select Support Package -- Import SPAM/SAINT Update
8. Continue.
10. If any problem comes, then follow 7,8 th steps until success.
How to apply support packages:
Applying BASIS from KB62041 to KB62042.CAR
1. Download required Support Package Level 42 (KB62042.CAR).
2. Uncar the car file.
35
sapcar -xvf KB62042.CAR
3. Then we will get 2 files .ATT and PAT and copy thes in /usr/sap/trans/EPS/in
4. Login into SAP level in 000 client with DDIC type of user.
5. Goto SPAM
6. Select Support Package -- Load packages -- From application

server. Click BACK.
7. Select Display Difine , All Components, Calculate Queue, Confirm queue.
Observe the required patch in the queue.
8. Select Support Package -- Import Queue
9. Import
10. If any problem comes, then follow 8,9 th steps until success.
Errors During Support Package Manager Phases

If an error is recognized during a phase, Support Package Manager
stops the import process until the error is corrected. You can get
information about the reason the SPAM transaction was stopped and in
which phase by choosing Queue ® Status.
Error Types
Support Package Manager displays the following types of error messages:
...
1. Support Package Manager Security Checks
A typical example is the OBJECTS_LOCKED_? phase. Support Package

Manager stops the import process if objects that need to be
overwritten by the queue are still locked in requests.
2. Error messages from programs tp and R3trans
You can always find the cause of the error in the relevant transport
log. A typical example is the TEST_IMPORT phase. This step checks
whether there are unconfirmed repairs to objects that need to be
overwritten by the queue. The objects in question are listed in the
test import log.
36
3. Incorrect configuration of the Change and Transport System
Errors here often include not having the relevant authorizations for
accessing files in the Change and Transport System, or using old
versions of the tp or R3transprograms. Check the configuration of the
transport tools by choosing Utilities ® Check transport tool.
A typical example is the DISASSEMBLE phase. If <sid>adm does not have

write authorization for directory /usr/sap/trans/data (UNIX), Support
Package Manager stops at the DISASSEMBLE phase with
CANNOT_DISASSEMBLE_R_DATA_FILE.
Support Package Manager requires the Change and Transport System to be

configured correctly.
For more information on known problems, see the OCS Notes referred to
in SAP Note 97620.
Known Errors
PROLOGUE
In this phase, a dialog box prompts you to confirm the import of the
Support Package. If you are not authorized to use Support Package
Manager, or if the current queue has not yet been confirmed, Support
Package Manager stops with a message to this effect.
CHECK_REQUIREMENTS
This phase checks various requirements for importing a Support

Package. It may terminate for the following reasons:
○ TP_CANNOT_CONNECT_TO_SYSTEM: tp cannot log on to the database

of the system.
○ QUEUE_NOT_EMPTY: The tp buffer contains incompletely processed

OCS requests. Use the following tp command to display these requests:
tp SHOWBUFFER <SID> -D SOURCESYSTEMS= TAG=SPAM
You can only continue to import the queue after these requests have
been completely processed, or deleted from the tp buffer.
DISASSEMBLE
In this phase, files from the corresponding EPS parcels are unpacked
and stored in the directory /usr/sap/trans/data (UNIX). It generates
the command files (cofiles) from the accompanying files and saves them
to directory /usr/sap/trans/cofiles (UNIX). It may terminate for the
37
following reasons:
○ CANNOT_SKIP_ATTRIBUTE_RECORD: The attributes could not be read

in the EPS parcel. The reason that the file cannot be read is either
because it has been deleted or because your authorizations at
operating system level do not allow this.
○ CANNOT_DETERMINE_EPS_PARCEL: The EPS parcel is not in the EPS

Inbox, because it may have been deleted. You need to download the
relevant Support Package again.
○ CANNOT_DETERMINE_DATA_FILES: The name of a data file could not

be determined, because a profile parameter was not correctly
configured. Use report RSPARAM to check the settings.
○ CANNOT_DISASSEMBLE_R_DATA_FILE: An R3trans data file could not

be unpacked.Possible errors include a missing EPS parcel or a data
file that could not be written to. An error occurred while
transmitting a 20K block from the EPS Inbox to directory
/usr/sap/trans/data(UNIX).
○ CANNOT_DISASSEMBLE_D_DATA_FILE: An ADO data file could not be

unpacked. The reasons are the same as for
CANNOT_DISASSEMBLE_R_DATA_FILE.
○ CANNOT_CREATE_COFILE: The cofile could not be created from the

corresponding data file. One possible error source is that <sid>adm
does not have write authorization for the directory
/usr/sap/trans/cofiles (UNIX). Check whether the data file has been
created. If it has not been created, check that the option Create new
data file is activated in the settings.
ADD_TO_BUFFER
This phase adds the queue to your system’s transport buffer. It may
terminate for the following reasons:
○ TP_INTERFACE_FAILURE: The tp interface could not be called. An

RFC error has occurred.
○ CANNOT_ADD_PATCH_TO_BUFFER: A Support Package could not be

added to the transport buffer. For more information, see the SLOG log
file in the directory /usr/sap/trans/log (UNIX).
MODIFY_BUFFER
38
This phase prepares the transport buffer so that the subsequent import
phases can be processed correctly. It may terminate for the following
reasons:
○ TP_INTERFACE_FAILURE: The tp interface could not be called. An

RFC error has occurred.
○ CANNOT_MODIFY_BUFFER: An unsuccessful attempt was made to

modify the transport buffer.
IMPORT_OBJECT_LIST
This phase imports the object lists for the Support Packages in the
queue into the system. It may terminate for the following reasons:
○ TP_INTERFACE_FAILURE: The tp interface could not be called.
○ TP_FAILURE: The tp program could not be executed. For more

information, see the SLOG or ALOG log files.
○ COMMAND_FILE_IMPORT_FAILURE: The object list for one or more

Support Packages could not be imported. You can find the source of
error in the command file import log.
TEST_IMPORT
This phase checks whether any objects overwritten by the import are
still in unreleased tasks. You can find the source of error in the log
of the test import.
You can skip test import errors and continue the import by choosing
Extras ® Ignore Test Import Errors. However, depending on the type of
error, this may cause the error to reappear with very serious
consequences during the real import. You therefore always need to
check test import errors first, and correct them wherever possible.
OBJECTS_LOCKED_?
This phase checks whether any objects overwritten by the import are
still in unreleased requests. It may terminate for the following
reasons:
○ CANNOT_GET_OBJECT_LIST: The object list for a Support Package

could not be found, since the Support Package does not exist.
○ CANNOT_CHECK_LOCKS: An error occurred when checking the locks
39
for an object in the queue.
○ OBJECTS_LOCKED_IN_REQUESTS: Objects were found that are still

in requests that have not yet been released. Release these requests
before continuing importing the Support Packages.
ADDON_CONFLICTS_?
This phase checks for conflicts between objects in the queue and
installed add-ons. If it finds any, Support Package Manager stops and
prompts you to import the relevant Conflict Resolution Transports
(CRTs). It may terminate for the following reasons:
○ CANNOT_GET_OBJECT_LIST: The object list for a Support Package

could not be found, because the Support Package does not exist.
○ CANNOT_GET_LAST_UPGRADE_INFO: The information about the

component upgrade could not be determined.
○ UNRESOLVED_ADDON_CONFLICTS: Conflicts with add-ons could not

be resolved, because the relevant CRTs are missing from the queue.
SCHEDULE_RDDIMPDP
This phase schedules the transport daemon (program RDDIMPDP). It may

○ CANNOT_SCHEDULE_RDDIMPDP: Job RDDIMPDP could not be scheduled.

Call Transaction SM37 (job selection), enter the following parameters
and choose Continue:
Job name
RDDIMPDP
User name
<User name>
Trigger event
SAP_TRIGGER_RDDIMPDP
○ Parameter ein und wählen Sie Weiter:
Wählen Sie den abgebrochenen Job aus und zeigen Sie das Jobprotokoll an.
Select the job that was terminated and display the job log.
40
○ Problems with the SAP lock mechanism: Call transaction SM12
and make sure that there are no programs listed with the name
RDDIMPDP.
CREATE_VERS_BEFORE
This phase creates versions in the version database of the objects

that you want to import and for which versions can be created (ABAP
coding, screens, and DDIC objects). It may terminate for the following
reasons:

information, read the SLOG or ALOG log files.
If the return code is 0152 (nothing done), check in the configuration

of the transport tools in the Transport Management System (transaction
STMS) whether the VERS_AT_IMP parameter is set as ALWAYS. If it is
not, set this value and continue importing the queue.
○ TP_STEP_FAILURE: tp step CREATE_VERS_BEFORE could not be

performed successfully. To find the exact cause of the error, choose
Goto ® Log ® Queue, and look at the version log.
SPDD_SPAU_CHECK
In this phase, the system checks if a modification adjustment is

necessary (transactions SPDD/SPAU).
DDIC_IMPORT
This phase imports the ABAP Dictionary. It may terminate for the
following reasons:

○ CANNOT_IMPORT_DDIC: The ABAP Dictionary could not be imported.

You can find the source of the error in the Dictionary import log.
AUTO_MOD_SPDD
41
This phase checks whether all modifications to ABAP Dictionary objects
can be adjusted automatically.
RUN_SPDD_?
In this phase, you are prompted to adjust your modifications to the

ABAP Dictionary objects by calling transaction SPDD.
LOCK_EU (only for import mode downtime-minimized)
This phase locks the development environment. It may terminate for the
following reasons:

INACTIVE_IMPORT (only for import mode downtime-minimized)
This phase imports program code and program texts in an inactive

state. It may terminate for the following reasons:

○ TP_STEP_FAILURE: The tp step INACTIVE_IMPORT could not be

executed successfully. The cause of the error is in the relevant log
(SAPBxxxxxx.<SID>). This log is in subdirectory log in the transport
directory. To display this file, run report RSPUTPRT, or call
transaction AL11.
DDIC_ACTIVATION
This phase activates the imported ABAP Dictionary objects. It may


○ TP_STEP_FAILURE: tp step DDIC_ACTIVATION could not be executed

successfully. To view the cause of the error in the activation log,
42
choose Goto ® Log ® Queue.
If you import two or more Support Packages in a queue, activation
errors can result from an incorrect activation sequence for Dictionary
objects. If this is the case, the activation errors disappear if the
objects are activated again. To do this, choose Support Package ®
Import queue.
IMPORT_PROPER
This phase imports all Repository objects and table entries. It may

○ TP_STEP_FAILURE: A tp step could not be performed

successfully. You can find the source of error in the relevant log,
for example, in the import log.
If a tp step 6, N or S is in the termination message, it is a step

independent of the transport request. The corresponding logs are
contained in the log overview under the node Import steps not specific
to the transport request.
You can also find these logs in the following files in the log
subdirectory of your transport directory (usually /usr/sap/trans/log):
tp step 6: P<YY><MM><DD>.<SID>
tp step N: N<YY><MM><DD>.<SID>
tp step S: DS<YY><MM><DD>.<SID>
To display these files, run report RSPUTPRT or call transaction AL11.
PREPARE_XPRA
This phase prepares the execution of the XPRAs and after-import

methods. It may terminate for the following reasons:
○ CANNOT_MODIFY_BUFFER: The tp program could not change the

corresponding buffer file. For more information, read the SLOG log
43
file.
UNLOCK_EU (only for import mode downtime-minimized)
This phase unlocks the development environment. It may terminate for

the following reasons:

AUTO_MOD_SPAU
This phase checks whether modifications can be adjusted automatically.
XPRA_EXECUTION
This phase executes the XPRAs and after-import methods. It may


○ TP_STEP_FAILURE: tp step XPRA_EXECUTION could not be performed

successfully. To find the cause of the error, read the method
execution log. To view the cause of the error in the log, choose Goto
® Log ® Queue.
○ CANNOT_READ_BUFFER: The tp program could not open the

file.

file.
ABAP_GENERATION
This phase generates the runtime objects for the imported Repository
objects (ABAP source code and screens). It may terminate for the
following reasons:
44
○ TP_STEP_FAILURE: The tp step could not be executed

successfully. To view the cause of the error in the generation log,
choose Goto ® Log ® Queue.
Remember that objects delivered in Support Packages have already been

imported completely. If the return code is 0008, all objects without
syntax errors have been generated.
The persistence of syntax errors can be due to one of the following reasons:
■ Systems that have been developed over a long period of time

often contain many objects that are not longer used or maintained.
These objects are still active in the Repository and can reference or
use other objects (such as includes). If these includes are modified,
syntax errors might occur in the obsolete objects. However, these
errors have no effect on the SAP System, and can be ignored.
■ Generated includes or programs can contain syntax errors after

an import. You can usually ignore these errors, since the source code
of the generated objects is generated again when the corresponding
transactions are started (a special generation transaction might
exist).
■ If SAP objects have been modified, or if customer objects use

SAP objects, there are may also be syntax errors in the modified SAP
objects and the customer objects. If this is the case, you must adjust
the modifications or customer developments.
■ Buffer synchronization problems can also cause generation errors.
Generation errors do not necessarily indicate inconsistencies in the

system. However, you should investigate them using the criteria above.
If the errors are non-critical, or temporary, ignore them by choosing
Extras ® Ignore generation errors, and continue the import of the
queue. Choose Support Package ® Import queue.
○ CANNOT_READ_BUFFER: The tp program could not open the

file.

45
file.
RUN_SPAU_?
This phase prompts you to adjust your modifications to Repository

objects by calling transaction SPAU.
CLEAR_OLD_REPORTS (only for import mode downtime-minimized)
This phase deletes obsolete versions of program code and program texts
from the system. It may terminate for the following reasons:

○ TP_STEP_FAILURE: The tp step CLEARREPORTS could not be

performed successfully. The cause of the error is in the corresponding
log (PZ<yy><mm><dd>.<SID>). This log is in subdirectory log in the
transport directory. To display this file, run report RSPUTPRT, or
call transaction AL11.
EPILOGUE
This phase completes the import process. The system checks if the
queue has been completely processed. If it has, there should be no
more transport buffer entries for the queue. It may terminate for the
following reasons:

○ QUEUE_STILL_IN_BUFFER: The queue has not been processed

completely, since there are still incomplete Support Packages from the
queue in the transport buffer.
SPAD:
This is the transaction which is used to update the data dictionary tables which
applying SP. This is the phase where functional consultant assistance is required.
SPAU:
46
This is the transaction which is used to update the repository objects like
programs, reports, functional modules while applying support packages. This is the phase
where technical consultants required.
Note: If the objects are changed earlier with the help of SAP notes, Now these notes are
parts of the support package which are modifying the system, during this scenario each
and every object which was modified earlier with the help of the note are popped on the
screen whether to keep the original or change to version.
47
KERNAL UPGRADE/PATCHES.
Kernel is the heart of SAP system and located in run directory \usr\sap\
SID\exe\run. If consists of various executables which are required for smooth functioning
of R./3 system.
Sometimes these executables gets outdated and needs to updated from

time to time.
The following are the reasons for Kernel Upgrade:
1) During OS upgrade, DB upgrade and OS,DB patches.

2) It is a pre-requisite to upgrade the kernel to certain level before applying
support packages.
3) Some of the executables are
Msgserver.exe , dispatcher.exe , sapcar.exe , TP.exe , R/3 trans.
4) Kernel upgrade is the process of replacing the existing executables with

current executables.
Process of Kernel Upgrade:
1) As part of the upgrade, complete Kernel Directory can be replaced or a group of

executables or single executable can be placed.
Ex:- While import6ing transporting request:

1) TP gets aborted with an error, TP outdated then replace only TP.
2) While uncaring the files SAPCAR may be outdated in this replace only
sapcar.
3) DB executables like SAPDBA, BRBACKUP, BRARCHIVE,
BRRESTORE, BRCONNECT are grouped to be upgraded.
There are 2 types of executables:
1) R/3 executable with DB dependence.
2) R/3 executable with DB Independent.
1) Go to marketplace www.service.sap.com and download the current version of

Kernel.
2) UNCAR files into a directory called newrun.
3) Schedule downtime and inform users.
4) Shutdown SAP DB,R/3 , A Servers.
5) Stop all the services including saposcol.
48
6) Go to exe directory rename the existing run directory to old run and rename
the new run to run directory.
7) Start sap, run SICK any problems it will show.
SAP Notes:
These are used to fix single bugs.

Basically there 3 types of SAP Notes.
1. Informative Notes.
2. Corrective Notes using SNOTE
3. Corrective Notes using Manual.
Informatiive Notes:
These notes provide information about the note for any problem to fix.
Based on the information we will try to solve it.

Whenever we find any problem or issue in SAP system then search for
the resolution, the resolution leads with informative notes sometimes.
By reading the informative notes we will try to fix the bug , issue
or problem.
2. Corrective Notes using Snote:
Sometimes to fix a bug we need to apply notes using SNOTE.
Procedure for Snote:
1. Login into DEV system.

2. Goto SNOTE.
3. Search for the note, if the note is not available in the system.
4. Goto--->Download SAP Note-->Give the Note Number--->Continue.
5. Select Note then it shows a tag which says whether we can implement or not.
6. If the Tag says can be implement the note.
7. Select the Note--->click on Implement SAP Note.
8. It will create transport , once the transport create release it and
import to QAS and PRD.
3. Corrective Notes using Manual Process:
49
Sometimes to fix a bug a note will be given which
provides steps to modify one or more lines of a particular program,
report etc., in the SAP System.
This activity should done with ABAP consultants.
Once we apply then we can revert it whereas once we apply support we

cannot revrt it.
Procedure to revert a note.
1. Login into DEV system.

2. Goto SNOTE.
3. Select the note for reverting and click Reset SAP Note
implementation....which give a transports.
4. Release the transport import again into DEV,QAS and PRD.
50
Adapting the SAP System:
1. Customizing : It is the job in which keying entries in the

system without changing structure of the sap system.
2. Enhancements / Exists : These are provided by SAP to append

to enhance the functionality of the system without changing the
structure.
3. Support packages and Patches : Patch is used to fix bug in

the sap system.
· Support packages are used to enhance the existing

functionality of the SAP components.
· SNOTE also used to fix / correct the single bug in the SAP system.
· Group of notes called Support package.
· Group of support packages called support stack.
· Once we apply note we can revert it but once applied support

packages we cannot revert to do such we have approach SAP or we have
to change manually.
4. Development : If above 3 could not satisfied then the

customer need to go for Y or Z objects(User Created). The development
needs to registered in the market place.
5. Modifications : It is the process of changing the SAP

standard objects by operating object access key.
Transport Management in SAP System:
Change request management :
Whenever a customizing changes or

development changes are initiated it is prompted with a pop-up box to
save the changes to a change request i.e., change requests are
created by project managers or Leads. Change Request / Transports
created using.
51
1. SE01 - Transport Organizer
2. SE09 - Work bench Organizer
3. SE10 - Customizing Organizer
Different types of Transports or Change Request:
Change Request / Transport Types:
1. Customizing change Request : It is used to save the changes

made to client specific objects.
Ex: Company code, sales etc.,
2. Workbench change Request : It is used to save the changes

made to cross-client objects & repository objects.
Ex : Logical system, programs , reports etc.,
3. Transport of Copies : It is used to export the tables and

table contents based on requirements.
Ex: During System Copy.
4. Re-location of objects : The objects which can be transported

(export) to a trans-directory which can be imported later.
Ex : The objects such as programs, transactions function modules.
52
Transport or Change Request:
Its look like SIDK9XXXXX and which consists 2 files.
1. Control file: It contains the control information(executional

steps) of the transport and it is located at /usr/sap/trans/cofiles
Ex: K9XXXXX.SID
2. Data file : It contains the data of a transport and it is located

at /usr/sap/trans/data
Ex: R9XXXXX.SID
Creating Change Requests(Transports):
How many clients:
111 , 222 , 999
3 Transports –creating in 111.
------------------
Creating 3 dummy transports:
Procedure to create a transport:

1. log into 111 with sapuser/navin
2. Goto SE09.
3. Select create, customizing , continue.
4. Give description as Dummy tp1 and select save, then transport will created for you.
5. Then release the task, and request then we will be created data file and cofiles.
53
D47K900026
D47K900028
D47K900030
Importing transports in SAP System:
In SAP there are 3 ways to import the transports:
1. STMS
2. SCC1
3. Os level
1st transport (D47K900026) importing into D47/111 using STMS.
2nd transport (D47K900028) importing into D47/222 using SCC1.
3rd transport (D47K900030) importing into D47/999 using os level.
1. STMS : It is used to transport the objects from one system another

system.
Example : Importing Transport D47K900026 into D47(111) using STMS
EXample : D47(111) to D47(111).
Example 1: Import first transport (D47K900026) into D47/111 using STMS.
1. Login into D47/111 using sapuser.

2. Goto STMS
3. Select import overview, Double click on the system D47.
4. Select refresh, if the transport not found, then select Extras,
other requests, add-then give the transport to imported(D47K900026),
select continue yes.
5. Select the transport , Import Request.
6. Give the client number then select continue and select YES.
2. SCC1 : It is used to import the transports within the same system

from one client to other client.
54
Example : Importing Transport D47K900028 From D47(111) to D47(222).
Procedure to Importing Transport D47K900004 From D47(111) to D47(222).
1. Login into D47/222 (allways you have to login into target system).
2. Goto SCC1 and give the below details:
Source client : 111
Transport: D47K900028
3. Select start immediately or scheduled as background.
4. Now the transport imported into D47(222).
How to check whether transported or not in 222.
1. Goto SE09
2. Select F5 and give transport number and select continue, select
transport click transport log.
Every transport will be given Return Code after importing:
0 - Success
4 - Success with warnings
8 - Programmatical Error
12 - Transport error.
3. AT os level using tp addtobuffer and tp import.
This method is used to import the transport from one system(D47) to

other system(Q47) or from one client to other client in the same
system. Normally this method will be used when the transport is
larger.
Example : Importing Transport D47K900030 From D47(111) to D47(999) using os

level.
55
Procedure to import transport using os level: (you must have login as
sidadm).
1. Goto CMD.
2. Change directory to /usr/sap/trans/bin
3. type the below commands:
tp pf=TP_DOMAIN_S47.PFL addtobuffer S47K900030 S47
tp pf=TP_DOMAIN_S47.PFL import S47K900030 S47 client333 u1
56
Import Process :
When a transport request is imported the

following actions takes place.
1) User initiates transport request import.
2) TP gets initiates to gets the profile parameters from TP_DOMAIN_SID.pfl
3) TP calls r3trans to transport the contents.
4) TP writes all the steps into tables TRBAT and TRJOB.
5) To schedule (RDDIMPDP) is an ABAP program which runs in the

background with user DDIC and client 000.
a. To schedule RDD* jobs to read the contents from the tables (TRBAT
and TRJOB) and executes the steps sequentially.
6) Some of the steps are MOVE NAMETABS, MAIN IMPORT, DD

ACTIVATION, TABLES CONVERSION , SET VERSION FLAGS.
7) At the end of import, TP specifies the return codes
0 - Imported Successfully.
4 - Imported with Warnings
8 - Imported with Errors.
12 - TP Error.
Trouble shooting errors using Transport Logs.
There are 3 types of logs for troubleshooting Transports.
1. Slog file ->It display the each of the activity step by step
during the transport.
2. Ulog file -> It display the change request numbers along with
57
SID, client, date and time of export and import along with UID.
3. Alog file -> It specifies the commands executed by TP during

export and import of the change request.
PROCESS MANAGEMENT SM50/ SM66
Work process list is displayed in SM50/ SM66. Each process has the following
- Serial Number : Starts with 0 (DEV_W0) in work directory

- Type of Process : (DVEBS) Message and Gateway are not displayed
- Process PID : The identifier at OS level. It is used to kill the process at OS Level. They
are displayed as [DISP+WORK] on windows in the Task Manager.
DW - dispatcher work process in UNIX
0 to 11 [12]
And 1 is for dispatcher 13 Total
-status : Waiting, Stopper, Running
Waiting : The process is waiting "Available" to serve the user request.

Stopped : The process is stopped due to an error.
Running : The process is executing the task (SM50 running with our
Userid should not be considered)
On Hold : The user request is on hold by process for waiting certain
Resources on the other systems (RFC, CPIC)
Shutdown : The process is killed/ shutdown but restart mode set to NO
Waiting for
PRIV Mode: The process goes into Heap mode. It will be completed only after the task
completion/ timeout.
SLEEP MODE: The work process goes into sleep mode waiting for resources (RFC
problem)
- Restart YES/ NO : if the process is terminated and it will restart automatically (Yes),
not restart(NO)
- Error : No of times the process is restarted

- Semaphore : The block that hold at OS Level (DISK)
58
- CPU : The amount of time WP spends utilising CPU resources
- Runtime : The amount of time the process spends on the user request.
- Report : The name of the program/ report the WP is executing
- Client : The client number logged in
- User name : Name of the user
- Action : Select, Update, insert i.e. action on the database.
- Table : Name of the table.
SM66 GLOBAL WORK PROCESS OVERVIEW
It displays the processes based on status. It displays the processes belongs to all the
instances.
From SM66 - Click on SELECT PROCESS
The major advantage of this is it displays the memory consumed by work process.
Double click on the WP to display (Extended, Roll and the Heap Memory)
On Oracle execute
PS -ef |grep ora* (lgwr, smon, pmon, dbwr, ckpt, arch)
SM04 : is used to display the logged in users along with the sessions. We can terminate
the session or the user completely using End session or logoff user.
From User Logoff User Local or End the session
BACKGROUND PROCESS SM36
It is used to run the expensive programs, reports that consumes more time in the
background mode. i.e. a job is scheduled to run at a specific time or periodically.
Example: Daily report, Weekly sales report or expensive to run in the peak hours so they
are scheduled to run in the background mode during off peak hours.
Process Flow
1. User submits the request via dispatcher to a WP.

2. The Dialogue work process handles the request and updates the tables
3. Tables TBC* are used to store the BTC Jobs
4. A program SAPMSSYS starts in the dialogue mode at frequency that is defined
in the parameter rdisp\btctime=60Sec
SAPMSSYS - Checks for every 60 sec into the TBTC* table.
59
* To delay the BTC processing increase the time as much as possible.
Example : 100000 seconds 27Hrs
RZ11 (rdisp/btctime)
Refer - BTCTRNS1 from SE38
We can also use BTCTRNS2 to resume the background jobs (Execute the program)
5. BWP looks into the table and identify the jobs which are in the Ready State.
6. BWP runs the job in the Active mode till completion/ Cancelled.
BWP are defined by using rdisp/wp_no_btc=2 (Min 2 per system)
We can increase as many as possible depending upon the resources.
** Note: We can pause jobs by setting the value to 0 zero **
BWP jobs are defined in SM36

Specify Jobname: Daily report
JobClass: C A, B, C (High, Medium, Low Priority)
Class A requires a dedicated BTC of class A which are defined in operation modes.
Class B has medium priority over class C jobs
Class C jobs runs with Normal Priority
JOB STATUS
1. Scheduled: The job is defined but time to execute is not specified.

2. Released: The time to execute is specified
3. Ready: The Time to run the job is reached
4. Active: BWP processing the task
5. Cancelled: The job is cancelled
6. Completed: The job is completed or finished
Execution server - Name of the instance that provides BWP to run the job
Exec Target - Lolla_<SID_00
Click on step
JOB STEPS
We need to specify the following for the JOB Execution
1. ABAP Program
2. External Command
3. External Program
1. ABAP Program - Is a predefined program that will be run in the background with user
inputs as variants.
Variant - Is a predefined value that is populated during the runtime.
Eg: consider RSPO1041 from SA38
60
Goto SA38 and define variant for 7 & 15 days
Prog: RSPO1041
Variant: lolla SAVE
Click on start condition - IMMEDIATE or DATE....
2. External Commands: The job can be executed by external commands which are
defined in SM49/ SM69. These commands are OS commands that will be executed at
command level.
Eg: BRBACKUP, BRARCHIEVE, BRRESTORE, BRCONNECT

Use DB13 to schedule the jobs. The jobs in DB13 uses OS Commands.
3. External Programs:
NAME: Name of the program
Parameter:
Target Host:
Name : Specify the name of the program and the parameters. Specify the name of the
target host.
Specify the start condition
Immediate/ Periodic/ Jobstart, Event (SM62)/ Operation. Modes.
Job Started: When dependent job started this gets triggered.

Event: When an event triggered in SAP it also triggers the job as well.
OPERATION MODES RZ04 SM63
It is the process of switching DIA to BTC and vice versa during the peak hours as we
need more dialogue process and during off peak we need more BWP to run the BTC jobs.
RZ04 Define
1. Instance
2. Operation Modes (Peak and Off Peak)
3. Specify the processes for modes
Goto SM63 to define timing for the modes
RZ04 click on Create [Instance Operation Mode]

Peak_mode
Peak_mode operations
Default
SAVE
Off peak
Off peak Mode
61
Create new Instance lolla28
Start profile
Save.
BACKGROUND JOB MONITORING SM37
rdisp/wp_no_btc = 2
rdisp/btctime = 10
Operation modes - to make use of the resources optimally
SM37 is used for BTC monitoring
Execute SM37
Specify username, date & time, job name, status ----- Execute F8
1. The jobs with status RELEASED indicate the jobs are released with scheduled time
and waiting for their turn/ time.
2. The jobs with status READY indicates the jobs are ready to pickup by the scheduler
Eg: Consider a CAB - might come late
No sufficient CABS
Long time in ready status indicates
1. The existing jobs are running for a long time i.e. expensive programming or sql
statements/ fetching huge amount of data.
2. The configured BTC processes are not sufficient to handle the requests in
Ready status.
3. May be due to heavy load on the system
4. Also due to passing the jobs by extending scheduler time/ making BTC to 0 by
running the program BTCTRNS1.
Action:
62
1. Increase BTC work processes based on the available resources by using the
parameter rdisp/wp_no_btc = 2
2. Schedule the jobs appropriately during off peak hours.
3. ACTIVE BTC in active status (long time recorded)
The job is running an expensive activity like client copy, pay roll run.
Jobs that fetch information from BW systems, annual reports, dunning reports may take
hours together or even days to complete successfully.
Active indicates the following
1. Jobs are expensive and running to fetch the content.

2. Jobs are waiting to be processed by the target system (RFC, CPIC)
3. Jobs are waiting for the locks to update the records.
Reasons and Resolutions ACTION.
1. Some jobs are bound to run for hours and based on history leave them to run.
2. Check the bottle neck on the target system (ERP-BI-EP-SRM-SCM-SRM)
3. Wait until the locks are released/ jobs are completed. Report to SAP in case of
dead locks.
Select the status - Db click - and click on Job Logs
Execute SM37
Highlight the job
63
Click on Job log
Sap takes at most care to avoid dead locks.

4. FINISHED
The jobs are completed successfully but check the log for further information/
completion.
5. CANCELLED
Job status cancelled/ finished but failed in the log.
Reasons for cancellation of Job
1. User and password Issues (Authentication/ Authorization) user lock, userid expiry,
password change, lack of roles etc.
2. File system problems: BTC reads from the file system to update the database. File not
opened, or corrupted, file sharing issues, file came with different characters, file not
found as well.
3. Variants are not properly defined.
4. Dead locks issue (Lock mechanism congested)
5. Update mechanism failed
6. Table space over flow (ORA-1653; ORA-1654)
7. Table space max extent reached (ORA-1631; ORA-1632)
8. Archive struck (ORA-255; ORA-272)
9. The memory is not sufficient and errors

(No Roll Area, PXA (Buffer), Page Errors)
10. Problem in the program and inputs (Indefinite loops like 1/0)
11. Dependent jobs/ events failure
12. Target systems are not available to process the jobs.
Standard Background House keeping Jobs
64
1. As a part of the post installation we need to schedule house keeping jobs in SM36
Execute SM36
Click on "Standard Background Jobs"
Click on "Default Scheduling"
And schedule the BTC jobs with default time.
1. RSBTCDEL - Used to delete the background jobs

Reporting structure "BTC" "DEL"
2. RSSNAPDEL - Delete the old ABAP Dumps
3. RSPO1041 - Delete the old spool logs and files
4. RSMO13002 - Delete old update requests/ logs
5. RSCOLL00 - Collects performance info in transaction ST03.
6. RSPO1043 - Spool Reorganization
Eg: from SA38
65
Click on Execute
And Specify the Days ...
From GOTO Menu Variants SAVE as Variant
SM37 - MONITORING BACKGROUND JOBS.
1. Used to display the jobs based on job, username, date and status
66
2. It displays the job logs
By highlighting a job and click on Job Log
3. Do not kill the active job unless it is permitted by the owner
4. We can repeat the scheduling of the job if required
5. Background job out put is a report to a spool (Printer), fax or email or even updating a
database (Eg. Client Copy)
6. We can move the jobs from one instance to another instance.

From Menu Job Move to different server. (Consider the above screen)
Active jobs can be moved.
There are Third Party BTC Job Schedulers
1. CONTROL-M Scheduler
2. RED WOOD Scheduler
3. TIDEL Scheduler
67
4. SAP Job Scheduler
5. MAESTRO Scheduler / IBM
These Third party schedulers are not specific to SAP but we can customise these to SAP
These job schedulers are intelligent to work based on the status of Predecessors.
The tool defines when to trigger, how to handle various statuses and alert users
accordingly.
Eg. KODAK Runs 14,000 Jobs/ day

HP Runs 20,000 Jobs/day
68
BTC - Business Case
Sony an electronics company communicates with suppliers for the TV Cabinets/ Circuit
boards, Picture tubes, assembling & packing.
Vendors instead of communicating in hand documents they are advised to

communicate in soft documents. SAP also sends soft documents as well.
i.e. the communication is performed electronically.
BTC Jobs performs the following:
1. Run long running reports for an End User
2. Runs payroll for the employees
3. Client copy for the technical consultants
4. R/3 BIW Replication
5. Communication with NON SAP Systems to fetch the data
6. Dunning report for Finance team
7. Weekly, Monthly and Annual Reports
69
8. Runs standard jobs for House Keeping
9. To run Database jobs using external commands DB13 (SM49 provides commands)
NOTE: In table TSTC, we can get a list of all existing Tcodes and which programs are
called by those transactions.
From SE11 - Provide the table name TSTC and execute providing the T-Code to find the
Program
70
No bother of "Schedule/ Released" Will not in our scope
We need to take care about the Status
Ready for longer time
Active for the longer time.
BTC logs are deleted by scheduling RSBTCDEL which deletes the log files from
TBTC* based on the time interval in the Variant SA38.
UPDATE PROCESS
It is used to update the database from Temporary tables. There are three 3 Types of
updates
V1 - Handles High Priority Updates

V2 - Handles low priority updates
V3 - Reserved by SAP (Currently no use)
Updates are defined by the parameter

Rdisp/wp_no_vb=1
Rdisp/wp_no_vb2=2 from RZ11
Technically for every 5 dialogue work process there should be one update of type V1/ V2
Update Flow:
1. User submits the request for an update

(Let us say a Purchase Order)
Eg: Bearers won’t go to the Pantry

Similarly All dialogue won’t go to the.... DB
2. Dispatcher handles the request and provides a dialogue process to it.

3. Dialogue process interprets the request and communicates with enqueue process to
provide a lock to update the record consistently.
4. Dialogue process updates the temporary tables called as VB* asynchronously
VBHDR - To store update header information

VBDATA - To store data that needs to be updated
71
VBMOD - The modules through which the data is updated
VBERR - Update Error Table
And gets a transaction ID from Number Range Buffer (Transaction SNRO and Table
NRIV Number Range Interval Table)
SNRO
NRIV
72
Eg:
Dialogue Updates - Update Releases the lock.
5. Update gets initialized and reads from Temp Tables and updates the permanent tables
synchronously. Update inherits the locks and releases them upon updating permanent
tables. Update updates the record based on transaction-ID using VBMOD Table (Every
update is module based in SAP)
6. When the Dialogue updates the temp tables the record is displayed in SM13 which will
be processed by update.
UPDATE MONITORING SM13
The record that needs to be updated by update process is displayed in SM13 with
status INIT. If the records stays for longer time in INIT status that indicates the updates
are busy or there are no sufficient update processes or update mechanism is deactivate
from SM14.
Update handles the record and change the status to "RUN"
If the update stays long time in status RUN
1. Longer Update
2. Dead Lock (Needs to inform SAP for Program correction)
Updates which could not be updated will be thrown into ERR Status.
73
1. Update deactivated in SM14
2. Programming problems in LUW
3. Table Space overflow (ORA-1653; ORA-1654)
4. Max Extents reached (ORA-1631; ORA-1632)
5. Archive Struck (ORA-255; ORA-272)
BATCH/ BTC/ BACKGROUND
Each SAP transaction is considered as Single LUW (Logical unit of work) which
in turn contains multiple LUW's needs to be committed to commit the SAP Transaction.
If any one of the LUW is failed the entire transaction is rolled back. That is the reason
why dialogue updates Temp Table.
1. User submits the request.

2. Dialogue handles the request.
3. Obtains lock from Enqueue so the data consistency is achieved and the records are
only for display.
4. Updates the request in Temp tables (VBHDR, VBDATA, VBMOD, VBERROR)
5. Gets the transaction ID from NRIV (Number Range Interval Table)
6. Update gets initiated to update the VB* content permanently into the database.
7. Update inherits the locks.
8. Updates the database based on transaction ID.
9. Update releases the lock from the record.
UPDATE Statuses.
The following are the statuses displayed in SM13 Transaction.
INIT The record is waiting to update by an update process.

ERR The record runs in to an Error (Update Error)
RUN The update is executing the record into DB
AUTO The error records are reprocessed after a system restart/ update activation
Automatically.
SM13 - Repeat Update
Used to repeat the ERR updates. The update are terminated or cancelled due to the
following reasons
1. Table space overflow

2. Max Extents reached
3. Archive struck
4. Programmatical Error
5. Update Deactivation (SM14)
74
Running updates during deactivation
DEACTIVATE ----------- THROWS TO ERROR ------------- GOES TO AUTO
At this point of time we need to select the update (put a check mark of the update from
SM13) and click on [Repeat Update]
Refer modules from SM13
The updates can be repeated with status ERR

Rdisp/vbmail = 1 to send email to the users if an update is failed.
Update mechanism can be deactivated by setting the parameter

rdisp/vb_stop_active=0 to deactivate the update mechanism in case of DB errors.
It can be activated from SM14.
rdisp/vbdelete=30 to delete the update records older than 30 days irrespective of the
status.
Rdisp/vbreorg =1 to delete the incomplete update request during a system restart.
Report in SA38 RSM13002
To delete the old update requests.

Deletes the executed update requests. Reorganize the update tables. (Its a background
job)
V1 and V2 updates needs to be defined in the system.

V1 handles critical updates and V2 handles the non-critical updates which are defined by
the programmers.
We can see either V1 or V2 in the standard SAP Program SAPMV45A by executing

SE38
MESSAGE SERVER/ PROCESS
1. There will be only one message server through out the System.
2. It is used to manage all the dispatchers and identify the least loaded dispatcher
and forward the user request to the dispatcher provided logon load balancing is
configured in transaction SMLG
75
Logon Groups SMLG
SMLG Create
Provide GROUP: For Eg: MARKETING
INSTANCE: dewall36_R3I_00
Now from SAP Logon Screen
Click on Groups and Provide SID and Message Server.
We can find the Active servers from SM51 and on db click on the Host name to view all
the Processes.
76
CONFIGURING SMLG
1. Define a logon group from TCode SMLG
2. Assign the instance.
3. Open GUI Select groups and create entry by choosing group.
4. Add an entry in etc/ services

As sampsDEV (Message Server Name) 3200/tcp
Entry should be made on all GUI systems.
Note: The load is calculated based on in ST07
5. create a file sapmsg.ini if not exists from (x:\windows)

Sapmsg.ini open [MESSAGE SERVER]
DEV = <hostname
Mechanism
1. User communicates using GUI.
2. sapmsg.ini gets evaluated and checks the port in etc\services to communicate

with the message server.
3. Message server maintains the details of favorite server and routes the request to
that dispatcher
4. Dispatcher handles the request - Queue - Dialogue
Message server obtains the lock for dialogue process if the request is coming from the
Dialogue instances.
77
SMMS: MESSAGE SERVER MONITORING
ENQUEUE PROCESS / SERVER SM12 Monitoring
Note: Server Naming convention is used because each of the process serving the user
requests (Dialogue, BTC, Update, Enqueue, Message, Gateway and Spool DVEBMGS)
It is also possible to install and configure all the above servers on different instances or
hosts.
ENQUEUE:
It is used to provide data consistency while updating the system. It

provides locks from a lock table before a record gets updated and ensure that the record is
available for display during an update.
There will be 1 One Enqueue process installed during installation. It is also possible to
increase Enqueue processes to more than one depending upon the updates but most of the
customer environments there will be only 1 One enqueue process.
It is configured by the parameter

rdisp/ wp_no_enq = 1
DEAD LOCK
SAP TRANS ------ MULTIPLE LUWS
MM Dept Sales Dept
78
X + Y (LUW1) A + B (LUW1)
Z + M (LUW2) X + Y (LUW2) Dead Lock
Q + R (LUW3) R + Q (LUW3)
Enqueue process the locks and unlock the record during an update.
Enqueue server maintains the lock table on the shared memory of the Central Instance (or
on the instance where it is installed)
It is recommended to increase the Enqueue processes only on the Central Instance.
Technically the Message and the Enqueue should reside on the same instance (It is not
mandatory). If both are installed on the same machine then it will be more comfortable
for message server to communicate with Enqueue process to obtain locks for Dialogue
process that are coming from other instances.
RFC
DIA - MSSG - ENQ - MSSG - LOCK - DIA
TCODE - SM12 (Lock Management)

Enqueue table size is defined by the parameter
Enqueue/table_size=4MB (Earlier 1 MB to 4 MB) in Netweaver systems this can be
increased to 100MB
LOCK MONITORING/ ENQUEUE MONITORING SM12
Shared Mode
Exclusive Mode.
Locks are monitored in transaction SM12. In principle the lock which are older
than one hour should be reported to the escalation manager. If the lock table is filled
(Enque/ Table_size) an overflow occurs in the lock table.
79
1. Check whether the update server is still performing the updates. If the updating has
stopped, then the lock table can quickly become over filled with the locks held by update
requests. We can resolve the problem by restarting the updates. If updating has not been
interpreted, then we must enlarge the lock table.
Note: Enque table overflow is recorded in SM21 and ST22
Eg: Execute SU01 from Shawn user/ 800 and edit shramana user
Execute SU01 from Shawn user/800 and edit shramana user
Following message is displayed
And now execute SM12 which displays the Exclusive Mode lock
2. Enque time is too high

As a part of the response time enqueue time should be 1ms - 5ms for Central instance and
100Ms in case of the request that is coming form Dialogue instance.
Then we can consider the following
1. Lock table is overflow and the locks are held in SM12
2. Update is deactivate (SM14) due to any of the issues in DB. If the update gets
deactivated then the locks are not released.
3. If the Enqueue time increases i.e. there could be RFC issue or Enque wait time is
increasing then consider increasing Enqueue work processes.
4. Dead locks (Usually never occurs, but there is a collision between PP, Manufacturing
and Material Module, so highlight this issue to SAP)
In some instances we may need to release the locks but we need to follow certain
process.
80
Do not release the lock in SM12 (Even though there is an option)
Lock deletion is recorded in SM21.
1. Users complaint that he could not update a record and message pop up stating that the
record is locked by user XYZ.
2. Check the period of lock (if it is older than 1 hour inform to the escalation manager)
3. Get the written B&W approval from the user and terminate the session of that user
using SM04. (Only Terminate or End that session)
All the transaction activities are recorded in CDHDR
Note: Initially 20Kb Mem is given from ztta_roll_first.
We may need to allow some locks for more than one hour or days (Eg. Payroll
update processing) consumes lot of time. We need to ensure that dialogue process should
not held for longer time, but however BTC is allowed.
SPOOL PROCESSING
User request - DIA - (Tables TBT*) BTC---- (TST01, TST03)--SPOOL -- PRINT
User request - DIA-- (TST01, TST03) --- SPOOL ------ PRINT
PROCESS/ FLOW:
1. User request to print a purchase order (or) user schedule to print dunning reports
(LEGAL Notices, Credits, LOANS etc)
2. These print request are processed by the respective Dialogue/ BTC and stores the
content in TEMSE - Temse is a temporary sequential objects that are stored at OS (File
system) or Database level which is defined by the parameter
rspo/store_location=G or DB
(G Means Global Directory \usr\sap\SID\sys\global)

(DB Means - Database tables TST01 and TST03)
Note:
DIALOGUE - Multiplexing
BTC - Single Process
81
The Advantages of TEMSE.
TEMSE size is 99000
Refer:
SU22 - (s_spo_act) - To identify the tcode/ Authorization objects
SP01
SU24
The Temse can be stored in database or OS level. Temse remains in the DB/OS
unless they are deleted explicitly by SAP standard reports.
TEMSE AT OS OR DB (WHICH ONE IS RECOMMENDED?)
OS [G]
1. It is recommended because the print request are printed faster than database. i.e., from
Global directory requests can be converted to output request at faster rate than database.
2. This is only recommended when the requests are small in nature. (Every day 50-100
Docs) if the size increases the search at file level consumes more time as (No indexes at
file system)
3. File system is not backup frequently as Database. File system backup will be weekly,
fortnight, monthly whereas database is hourly (Redo Logs) and daily DB Backup. That is
Temse is not secured at file system.
DB [DB]
1. Consumes more time than Temse at OS when there are less no of records. but shows
the performance by using Indexes when the user grows (Temse can handle 90000
Requests)
2. Backup is a regular activity on database so the Temse is secured. As it is stored in

tables.
Temse is a part of Normal Database (TST01 and TST03) no separate memory is required.
82
DIALOGUE - BTC request - Spool Process OUT PUT
DIALOGUE - [TST01, TST02] - Spool Process REQUEST
FRONT END Spool process comes at our Desktop
Default setting is DB
RZ11 : rspo_location
: rdisp/ btctime
3. The Spool process reads from TST01 and TST03 i.e. the name of the author (USER),
Name of the Printer, No of copies are procured from TST01 and Printable data from
TST03
Spool Process formats or converts spool requests to output requests i.e. Printer specific
format. If the format is performed locally then it is said to be LAN (Local Access
Method). If it is performed remotely then it is said to be RAM (Remote access Method)
Spool processes are configured by rdisp/wp_no_spo (Rdisp indicates instance specific)

There should be at least 1 one Spool process in the entire system.
We can configure as many as we can depending upon the available resources.
It is also possible to have dedicated instances which will provide only spool processes
PROGRAM[ RSPO1041] to maintain TEMSE.
Refer: From SE12
TPFYPROPTY
Flag for changes

Obj_name = parameter Rdisp/time
83
Type T denotes Dynamic
X - Whether Changeable or not.
SAP System
Note: We should not touch the Repository data of name space 'A' to 'X'.
SE11 table name : /* (/ is a customer name space)
TADIR is the repository
TSTC - Is the T-Codes with the program name.
Market place keys & Reqs Development Name space.
Note: STMS System Transport Tool

no_import_all = 0 (No Mass Transportation)
SPOOL MECHANISM
Dialogue - BTC - TBTC* - TS* Tables

Dialogue --------------------- TS* Tables
Spool process reads from TEMSE and convert spool requests to the output requests
(Printer specific requests).
SPOOL ADMINISTRATION TCODE - SPAD
84
LPD - Line Print Demon
Drivers are specific to O/S and not to SAP
1. It is used to define output devices/ Spool servers and access methods
Defining a Spool Server:
The instance with atleast one spool process is referred as spool server. It is also
referred as Real spool server. (Existing)
Logical Spool Server.
This is not existing but pointed to a Real spool/ another logical spool server. This is used
for load balancing the spools.
Note: We can set up a dedicated instance for spool process.
85
CONFIGURING THE OUT PUT DEVICE.
1. Execute SPAD
2. Click on the Spool Server - Display then Change
3. Click on create
Server Name: LOGICAL SP1
Server Class : Mass Printing
Logical Server: Mapping : lolla28_00

Alt server: ......................
DEFINING OUTPUT DEVICE/ PRINTER
1. Execute SPAD
2. Click on output device
3. Click on display
4. Click on change
5. Click on create
86
6. Specify the Output device name
Specify the description : Local Printer
7. Device type: HP Model & Manufacturer

Device type specifies that the output device is recognized by SAP. If there
is no device type available then select SAPWIN. If required write to SAP and try to get
the device type. SAP sends programs in terms of Patches.
SPAD Utilities For device types Import

If the character set is required.
87
Device Class: (Standard, Fax, Telex etc)
Authorization Group : Specifies the access control methods
Model: 2200
Location : 5th floor A wing...
Message : Only used by Pay Roll.
--------------------
Note:
Dialogue --- TEMSE -- Author, Printer, Number of copies

When printer is defined Spool server (LS/ RS) is assigned
In order to print we need the spool process from the assigned instance to convert the
spool request in to the output request.
Spool process uses Access Methods to format the request. (either Local, Front End, Print
server...)
---------------------
ACCESS METHODS
It specifies the process of formatting the spool request to printer specific

output request.
LOCAL ACCESS METHOD
The spool work process and the host spool resides in the same machine i.e. the work
process transfers the spool request to the spool system locally.
Select L for UNIX based system (Local Print Method)

Select C for Windows (which uses direct operating system call)
88
Select F for FRONT END printing
Spool work process goes to the user desktop and format the request based on the printer
that is connected to desktop. This is more expensive, time consuming than any other
methods.
Disadvantages: No user can print in the background because the desktop initiation is not
possible in the background during off peak hours.
Advantages: Check printing, Sensitive docs, label printing.
Restrict the no of work process that can go into front end mode using the parameter.
rdisp/wp_no_spo_fro_max = 2
i.e. two work processes can be used for front end printing. If this parameter is not used
spool congestion occurs.
Specify I for Achieving device (Optical Devices, HSM, Jukebox (stores each copy
(output doc)) Hierarchal storage machine
REMOTE ACCESS METHODS
The formatting by spool work process is performed on remote system.
Specify U for UNIX operating system where formatting is performed on the remote
machine (Print server) using Berkeley protocol.
Specify S for windows operating system. It will transfer the formatting to remote
system using SAP specific protocol SAPLPD
For LOCAL & REMOTE Needs the printer models

For FRONT END SAPWIN
89
When Remote access method is specified we need the following
HOST Printer:
Destination HOST:
i.e. the printer should be configured on destination HOST. It can be a print server.
Note: Front end cannot be scheduled in the background.
SPOOL MONITORING SP01; SP02
The spool requests are monitored in SP01. users can monitor the requests using
SP02.
Spool Requests Output Requests

(Stores in Temse)
90
Note:
Put a check mark [ ] Do not query host spooler for output requests. If this option is
checked, It improves performance. If we need the exact status then uncheck the box.
Output Attributes: Depends upon the company requirements. Tray info is also similar.
-----
The Major advantage of TEMSE is the documents can be displayed even before it is
printed.
SP01 is used to monitor the spool requests based on statuses.
1. Status '- Minus' : Indicates not yet sent to the host system (No output requests exist)
The spool process is busy/ congested, if too many requests with
this Status indicates need for increasing spool WP.
2. Status '+' : Spool request is being generated (Stored in Spool system)
3. Waiting : Waiting for processing by spool
4. In Process : The spool WP is formatting the output for printing
5. Printing : The host spool is printing the output request. If the SAP spool
system does not receive any status information from the host
spool, this status displayed for approximately one minute. The
system then sets the status to Complete (Competed or Error)
6. Completed : The output request printed successfully. In systems where the

spool system does not receive any information about the host
spool , the system changes to complete as soon as the output
request is sent to the host spool.
7. Error : It indicates a server error such as network error. The requests

have not printed and remain in the spool system until they are
deleted or until they reach their expiration date and are deleted
91
during a reorganization.
1. Printer issues like (Page setting issues, cartridge issues, printer not available) paper
out, print server not available) these printer specific issues will be resolved by Network
Team/ Print Team.
2. User complain that they could not print documents to a specific printer.
- Check the availability of the printer, if required we can change the printer and
reprint the document.
From SP01 --- Select the request -- Use Menu "Spool Request and print directly" or
select print with changed parameters.
While changing the parameter we can set the priority between 1 - 10 (1 as High)
3. Spool request cannot be generated
- The TEMSE is full i.e. TEMSE will be full when it reaches 99,000 requests and
log is generated in SM21 (System Log)
- We need to reorganize the spool requests using the SAP standard reports.
(RSPO1041, RSPO1043, RSPO0041, RSPO0043). These are used to delete the old
spool requests based on selection criteria. In general the spool requests which are older
than 14 days will be deleted if standard jobs are scheduled in SM36 they also checks the
consistency of TEMSE periodically.
- We can also use SPAD for reorganization of spool (but the logic is same)
For this
Execute - SPAD Full ADMIN ADMIN Delete old spool requests
Or from SA38 execute the program - RSPO0041
-----------
Refer SM01 - Transaction Codes [Lock/ Unlock]
92
----------
SP12 - SPOOL TEMSE ADMINISTRATION

It is used to monitor the memory allocated for TEMSE
Note: If we need to forward a spool request select the request in SP01 and forward it to
another user where user can print from alternative printer.
SP01 : Spool request Forward

(Client to client) Recipient : DDIC
Use SBWP (SAP business work place) to display the request in inbox.
PRINT QUEUES
Note: Should have enough spool work process to format the requests to printer specific
requests. Similarly we should have enough output devices to avoid the print queues.
SETTING DEFAULT PRINTER
From SU01 we can specify default printer to the user but do not check the box "delete
the request after output immediately" which improves the spool performance.
The printer can be locked during maintenance in SPAD
To process the requests sequentially based on serial numbers

Select the option -- [ ] print sequentially in SPAD from OP devices attributes tab.
Print sequentially consumes time to print in the order. If this is unchecked it prints faster
but sequence is not maintained.
Dialogue
93
2 Min / Instance
75 - 150 MB
5 - 10 Users (Refer ST07)
Handles request Interactively
Multiplexing
Rdisp/max_wp_runtime = 600
SM50/ SM66
wp_no_dia
DPMON
It initiates update, BTC, spool, Message server and enqueue
BTC
Expensive, long running, time consuming

No time limit
Off peak time
Scheduled to run periodically using variants
Statuses
(Scheduled, Released, ready, active, finished, cancelled)
Job step
Program (SA38), OSCommands (SM49, SM69), External Programs (on Tar. Systems)
TBTC* tables
Standard background jobs
Pause(rdisp/btctime, wp_no_btc=0, btctrans1)
Atleast 2 for the entire system
SM36; SM37
Operation modes (RZ04, SM63)
RSCOLL - gathers performance into ST03
BTC communicates with enqueue for locking and spool for print.
GATEWAY WORK PROCESS SMGW
SMGW is used to monitor the gateway process. Gateway is used to communicate

between SAP and NON-SAP systems. There will be only 1 gateway/ instance. If required
we can also install a standalone gateway on a JAVA engine.
Gateway listens on port '3300'+instance number (3300, 3301,3302 where 01, 02 are the
instances).
Gateway provides an interface so that the external system can communicate with SAP
system on the specified port.
When RFC's are defined between the systems they use SAP gateway when (ALE, EDI,
IDOC are transferring they use gateway)
94
INSTANCE MANAGEMENT
Instance is managed by using profiles. Profiles will resides in

(usr/sap/<SID/sys/profiles)
There are three types of Profiles
1. Default
2. Startup
3. Instance Profile
As part of post installation we import the profiles of Active servers from RZ10.
The profiles resides at OS level in the directory (usr\sap\<SID\sys\profile). They can be
managed/ edited using a notepad. But the consistency is not checked (say for eg. if we
modify the instance profile WP DIA=2000 and there is no error message and versions are
not maintained under OS level)
DEV_DVEBMGS00_lolladel.
So these profiles are imported into database management for consistency check and
version management.
Startup Profile
Startup profile consists of startup parameters like
Starting Database
Starting Message Server
Dispatcher + Work.
Do not modify these parameter under any circumstances on OS level.
Default Profile
It is used to provide global parameters for all the instances, buffer

parameters, security parameters (Password, User restrictions), Message server host,
enqueue host)
Instance Profile
This is specific to instance configuration such as work process, timeout

parameters etc.
Starting Sequence
1. Startup profile is read by the system to start the engine by starting database, message
server and dispatcher in Central Instance.
95
2. Startup profile is read by the system to start the engine by starting (DISP+WORK) on
dialogue instance.
3. There will be only one default profile in the entire system which provides global
values.
4. Instance specific profile - This is used to set the instance specific parameters.
Eg. How many profiles are available on a system with 10 Dialogue instances.
Total = 11 (including Central Instance)

11 X 2 per instance (Start + Instance)
22
22 + 1 (Default Instance) = 23
PROFILE MANAGEMENT
Documentation for profiles are available in RZ10

Profiles resides in the table - TPFYPROPTY
RZ11 is also used to change some parameters dynamically without restarting the system
but they will be reset once the system is restarted.
RZ10 changes are permanent
The field type 'T' Specifies the dynamic parameters.
RZ10
There are three types of Administration.
1. Administration data
96
No need to maintain using this option. It only specifies the path of
the parameters.
2. Basic Maintenance:
It is used to maintain the profile parameters without any technical names.

GUI based using mouse
3. Extended Maintenance
97
Used by administrator using parameter names
Specify the input by including new parameters or modify the existing one.
Copy Save and Activate the profile.
The profile changes are updated at OS level and the existing profile is marked as .BAK
and a new profile is created in the profile directory. It will effect only after restarting the
Server.
Profiles are changed on SAP recommendation or based on experience. Do not change any
of the profiles on trail and error method. System will hang and may not restart.
LOGON LOAD BALANCING SMLG
ST07 - Application Monitor: User Distribution

SMLG- Logon groups sapmsg.ini
98
Logon Load Balancing SMLG
It is used to route the requests to the least loaded instance of that group.
Factors to define LLB.
Identify the components along with users. If the users are logging to different instances
the buffers are scattered therefore they are not effectively used.
So for this
* Note: DDLOG is the synchronization table
User A A+B =50

User B A+B =75 Buffer Synchronization
1. Buffers are optimally utilized.

2. Load balancing to avoid long queues
3. Fail over (Logical) (As we are configuring logical system)
Load balancing provides the following logon groups which are defined in SMLG.
SMLG Define the groups and assign the instances.
Mechanism
1. User uses SAP GUI -groups option to login

2. Saplogon.ini is used to display the available entries
3. User select group and click on logon.
99
4. When the user select group. It looks for sapmsg.ini to identify the message server and
etc/services for message server port. saproute.ini, saprfc.ini, sapdoccd.ini (For library),
saplogon.ini
5. Message server communicates will all the dispatchers and identifies the least loaded
server and mark it as a favorite server in SMLG. The request is routed to the favorite
server.
6. The dispatcher process the request normally.
Sapmsg.ini ---- IP Address --- Hostname of the message server

Central instance (but not always)
DATA TRANSFER TECHNIQUES
During the implementation of the legacy system needs to be preserved or used in the
current system.
Example: A customer/ company is running business for the past 30 Years. He is

maintaining customer details, vendor details, supplier details, employees and salaries,
account payables, account receivables and P&L (Profit and Loss). This information is
required by the customer in SAP System. So there is need to transfer the legacy system
data to SAP system.
Example: Customer implemented SAP but the employees who are old cannot make use
of SAP system. They would like to work on the traditional systems. After go live both
systems SAP and legacy travel parallely. The data entered in the legacy system i.e. PO's,
Invoices, Billing, Shipping are to be transferred periodically(Hourly) bi-hourly(for every
4 hrs) or daily
SO --- PO
BI ---- INV
Example: Reliance, Hero Honda [B2B Company to Dealers] not B2C [Distributers to
customers] they communicate with dealers, suppliers, using SAP. But dealers and
suppliers use non-SAP system so it is required to establish communication between SAP
and NON SAP systems and perform the data transfer periodically.
ETL - Extract - Transfer - Load
SAP - Non SAP

Hero Honda XML Dealers
RFC: REMOTE FUNCTION CALL SM59
100
RFC is used to communicate between SAP systems and SAP to Non-SAP systems using
TCP/IP protocol. RFC's are defined in [SM59]. There are 4 types of RFC's
1. Asynchronous RFC
2. Synchronous RFC
3. Transactional RFC
4. Queue RFC
1. Asynchronous RFC - (Like a post card). The sending system may or may not receive
it. i.e. there is no acknowledgement from the receiving . The transmission is not reliable.
2. Synchronous RFC - It is not like ARFC. It gets an acknowledgement from the target
system. (like a register post).
If the receiving system is not available the process goes into RFC/
CPIC/ Sleep mode and waits until it is wakened by the target system. Target system/
Receiving system may be busy i.e. all the resources are used up. This is reliable but time
consuming and expensive (Client Copy) the job should get finished.
Note: SAP uses CPIC protocol SAP specific (Common Programming Interface for
Communication) to communicate between system.
Berkley UNIX PRINTER

CPIC SRFC
3. Transactional RFC - TRFC - It is an advanced version of ARFC and SRFC. The

request goes to receiving system if it is not handled a Transaction ID is generated by the
source system. A program RSARFCSE is scheduled in the background to run for every
60 seconds.
Transaction SM58 is used for Transactional RFC. It is used to document
all the transactional ID's and ensure that they are received by the recipient system.
This is consistence and reliable.
Example : Central user administration.
A user is created in the parent client and transferred to the child client when they are
available?
101
4. Queued RFC - It is an advanced version of TRF and ensures that the transaction is
committed based on FIFO/ Queue. It ensures transaction consistency of LUW and
reliability of data transmission.
SMQ1 - to monitor the outbound queues of a sending system refer SCOTT for FAX...
SMQ2 - Provides interface to monitor Inbound queues.
DEFINING SYSTEMS - SALE
SAP systems consists of more than one client - technically 1000 client can be created in
one system. So we need to identify which client is the business client. Preciously SAP is
client based (A mandatory field while login)
Each client is defined with a logical system name that is defined in SALE. (Sap System
linking and enabling). Each system is identified by SID, client by 3 digit number. So,
Logical system number should be <SIDCLNT<CLNT_Number
Eg. DEVCLNT900
To identify the systems easily by name

1. Goto SALE Basic Settings Logical System
2. Define Logical System (<SIDCLNT009)
3. Assign logical system to the client.
There should be unique SID in the Landscape.
Defining RFC Connection - SM59
1. SM59 - Provide the name of the logical system

2. Select the connection type '3'
3. Description about the connection
4. Technical settings (Host name and Instance No)
5. Logon Security (Client, UID, PWD, Logon Language)
6. Save the connection, Test Connection, Remote logon
Perform three times to add 3 systems.
Central User Administration SCUA
Goto BD64 or SALE To define the sending systems and receiving systems
Or
Use the SAP standard moral for that application.
Example: To configure central user administration SCUA Tcode is used.
From 000/ Sapuser
102
Execute SCUA / - model : lolla Create
(The logged in system is treated as Sending system)
We need to define recipient/ receiving systems
DEVCLNT001
DEVCLNT000
DELCLNT001 save to configure CUA
Goto back end systems

Try to execute SU01 and create an user .. It wont allows us to create because the
receiving systems will become a Child system.
SCUM is performed only in the Parent System
Eg: Consider a Scenario
- Being in parent create an user assigning profile SAP_ALL

- define systems and SAVE
- Stop the other systems
- Execute SM58 (Transactional RFC)
Users are distributed to the child client using TRFC(SM58) and if the client system is not
Available the record hangs in SM58 and ensure that is updated in the child client.
To delete : Execute report : RSDELCUA or SCUA select the client and delete.
EDI - Electronic Data Interchange
It is used to communicate between SAP to NON-SAP systems.
ALE - SAP to SAP only.
IDOCS (Intermediate Documents) are used to transfer the data. It will be in the
Understandable format of both sending and receiving systems. SAP - NON SAP.
WE05 is the Tcode to monitor the IDOCS

SCUL to check the logs
WE05 Status
103
0 to 49 - are the outbound IDOCS
50 and above are the inbound IDOCS
52 - States that the application document not posted fully.
53 - states that the document is posted
02 - states that there is error in the port
07 - states there is a syntax error.
Tcode IDOC to check the consistency

WE21 to identify the ports for IDOC processing.
SYSTEM MONITORING
Gateway is a port that listens on 3300.

It is used to monitor the health of systems in terms of storage, memory and CPU
technically.
Status (Killed, Ended, Free... Instance is down)

But on SAP front we need to monitor the process utilization, pending updates, dead
locks, system logs, database logs, system dumps, btc failures, RFC failures, Failed spool
requests, work load on the system (Users, Reports, Transactions, Programs)
PROCESS MONITORING SM50 (INSTANCE)/ SM66 (GLOBAL)
104
Monitor the instance specific processes in SM50 and Global Specific Process
overview based on status in SM66.
Monitor the processes with status(reasons) running, hold, stopped, sleep, RFC/
CPIC, PRIV.
Identify the user, time, client, Action.
If BTC is running for longer times check whether it is permissible as per the
process document.
Dialogue process should not consume more than 1-2 seconds for normal tasks. It
will be automatically down (Killed) by system in 600 Seconds. If it is not killed the
process might be occupied by dedicated resource and uses heap memory with status
PRIV. The process has to complete the job or Heap Memory should exhaust, so that
process comes out. We may need to kill the processes with status PRIV using DPMON,
Task Manager or Kill -9 Command on UNIX.
If more number goes into PRIV we may need to restart the instance.
Refer : select MANDT, Count(*) as Total from DEV.USR02 group by MANDT.
Note : Rdisp/gui_auto_logout = 900 sec
---- Example ---

User pwd forgotten and all the users are locked if SAP* is deleted. It will be created with
Password pass. Do not change the status of users in the USR02 Table.
Select MANDT, BNAME, UGLAG from USR02

128 - Self Locked
64 Administrator Lock never becomes 0
-------------------
Refer
SM12 - Select Lock Entries

SM13 - Update requests
SM14 - Update program Administration (Deactivate)
SM36 - To define the Back ground Job
SM37 - JOB monitor
SM21 - System Log
ST22 - ABAP Dumps/ Runtime Error
RZ04 - Maintain Operation Modes
SM63 - Display/ Maintain Operation Mode Set
SP01 - Output controller - Spool
Standard Jobs
105
- RSBTCDEL - Deletes the batch job logs
- RSSNAPDL - Delete Old ABAP Dumps
- RSPO1041 - Delete Old spool logs and files
- RSMO13002- Delete old update request logs
- RSCOLL00 - Collects performance info in Transaction ST03
- RSPO1043 - Spool Reorganization.
DPMON - When the user could not login to the system (Experience Hour glass)
Process the list @ OS Level
DPMON
K
Provide SR. Number
Provide PID.
SM59 - RFC Destination

SM50 - Process Overview
SM51 - Active SAP Servers
SM66 - Global Work Process overview
WE05 - IDOC List
SMQ1 - QRFC (outbound) queue
SMQ2 - QRFC (Inbound) queue
SM04 - User List.
106
WORK PROCESS MULTIPLEXING
(Consider Restaurant Activities).
Each user transaction may be served by one or more processes with out restricting to the
user similarly each work process serve multiple users with out restricting the user. (No
dialogue process remains ideal)
Each process can serve 5 - 10 users and Each SAP transaction consists of multiple
(LUW - Logical unit of work) Each LUW contains task which should be completed/
rollback as a group. Each LUW is a commit or rollback (no intermediate stage ... which
makes the system inconsistency)
SYSTEM MONITORING
SM51
SM50/ SM66
SM13
SM14
SM37
SP01
SM04/ AL08 : Used to identify the number of users logged on to the instance. Identify
the users who are consuming more memory and also identify the transactions and identify
why it is consuming more time. This TCODE is also used to logoff the user session if
required.
AL08
SM04
107
SM21: System logs specific to the instance. We can also identify the logs of other
instances.
System log Remote system
It is used to display the logs for the following activities.
108
1. System Startup/ Work process log
2. All ABAP dumps are documented
3. When we delete SM12 the locks are logged.
4. All the database related errors like Space issues, Segment Management, Archive Stuck.
5. Illegal attempts and user locks
6. Session Termination due to network failures.
As a part of monitoring we need to identify the messages with color red.
7. Time out errors
Identify the error message from the log and search in the market place.
8. It displays the logs based on date/time, user, t-code & problem class.
ST22 ABAP DUMPS
When ever a SAP Program (ABAP program) could not be executed due to an error it will
be thrown out from the GUI- Screen and a dump is recorded in ST22.
ST22 recovers the following
1. Divide Error 1/0

2. Update (Lags in Memory)
3. Infinite Loops.
1. TIME_OUT error: The program requires more time than the time defined in
rdisp/max_wprun_time
2. Memory related issues with error message PXA, SWAP, PAGE, OUT OF MEMORY.
This error requires memory corrections to the parameters.
3. Program Corrections: The problem is with SAP standard program for which SAP
provides a correction through notes (The correction can be applied through SNOTE)
4. Customer defined programs ('Y', 'Z') consumes more memory, endless loops,
improper select statements etc. The program need to be corrected by the developer.
5. Enqueue Table Overflow: SM12
6. Update Deactivation : SM14
7. Database issues like table space over flow, max-extents reached, archive stuck.
8. Illegal time: (Day light savings) - During day light savings the system date and time
has to be changed. Stop the AS and change the date if not, the above error occurs.
Note
109
TSTC - Holds the transaction and the Program name
TSTCT - Holds the description/ text of a T-Code.
PERFORMANCE TUNING ST02
This complete journey should be completed within 600 Milli seconds on an average or
goes up to 600 Seconds Max.
110
1. Front End Time/ GUI Time : Time taken by the user to reach the dispatcher is called
as Front end time. The GUI time should not exceed more than 200 M.Sec. If it exceeds
this consider the following.
1. User desktop is slow

2. If this is same with all the users, network might be congested.
3. The user request is expensive (FI and basis will logon to the central instance.
Rest of all the users are allowed to login to Dialogue instance)
Note: GUI response time is not considered as a part of the Dialogue response time
because the request is not received by the dispatcher.
2. Wait Time: The amount of time the user request sits in the queue. Generally it should
not be more than 50 M.Sec or 10% of the response time. If the time exceeds, consider the
following.
1. The work process are not sufficient to handle the user requests. (1:5)
2. There are sufficient processes but the existing process are held with expensive
request.
Login/disable_multi_gui_login.
3. Roll in Time: The work process copies the Roll in User context into WP task handler.
The time taken by the work process to copy the context (Roll In) is referred as Roll in
time. Generally it should not be more than 50 M.Sec. If it is more than this consider the
following.
1. The user context is heavy to Roll in (User might having more authorizations,
parameters)
2. Minimize the authorizations.
4. Roll Out Time: The time taken by the work process to copy the information from its
local memory to Roll Area/ Roll File/ User context/ Roll buffer and it should not be more
than 50 M. Sec.
5. Roll Wait Time: During the processing when a dialogue process communicates with
RFC's and waiting for the response at this time the user context is copied/ rolled back to
BTC ---- RFC --- Target system.

Roll wait time Sleep
Note: Roll wait time is not considered as a part of response time. If the roll wait time
increases consider there is a bottle next on the RFC communication.
6. Processing Time: The time taken by the work process to process the user request
using interpreters. The processing time should not be more than 200 M.Sec. If the
processing time is more we can consider either ABAP program is expensive, screen is
expensive or SQL statements are expensive.
111
7. CPU Time: When the request are processed using interpreters an amount of CPU is
utilized to process the request using CPU resources is referred as CPU time.
As CPU time is included in processing time it is not calculated in the response time.
CPU time should not be more than (40% of the Dialogue response time - Wait time). If
CPU time is more consider tuning ABAP Programs Refer to ABAP development team
(Also Refer SE30 ABAP Run time Analysis, ST05 Performance Analysis)
8. LG Time: Load and Generation Time: Time required to load the objects such as
source code, GUI info, screen info from the database and generate these objects.
(Refer LC10 : Live Cache). It should not be more than 200 M.Sec.
Run SGEN tcode after patch application, upgrade, new installation or when there is a
mass change in the programs.
9. Enqueue Time: The time taken by the process to communicate with enqueue for
obtaining the lock while updating a record is referred as Enqueue time. Enqueue time
should be 5 M.Sec. on a Central instance and 100 M.Sec on a Dialogue instance. If it
exceeds more than this time we can consider that the enqueues are not sufficient or
Enqueue table overflow. or WP waiting for a lock.
10. RFC or CPIC Time: The time taken by the process to communicate with external
interfaces is referred as RFC time. It should be as minimal as possible. (Communication
between any BW/ CRM/ SCM system). There wont be any threshold value as it depends
on External system.
11. Database Time: The time taken by the process to reach the database and process the
request. Generally it should not be more than 40% of (Response time - Wait time). It is
similar to the CPU time. IF DB Time is more consider the following.
1. The DB statistics job is not scheduled in DB13.

2. The DB resources are stake(CPU and Memory Utilization) i.e. Resource bottle
neck on DB.
3. The DB Buffers are not sufficient.
4. Missing indexes in DB02.
12. Dialogue Response time: The time taken by the Dialogue process to process the
request which includes [Wait time ........ To ......... Roll Out Time]
[Wait time + RI + RO + PI +LG + RFC + DB +ENT]
Note: Team Viewer is the Remote Desktop support Software

BOMGAR.
Ф Indicates - Average Time

# Indicates - Total Time
112
WORK LOAD ANALYSIS ST03
ST03 It is used to calculate the work load analysis. Select Expert Mode to identify the
expensive programs, transactions, reports and users.
While calculating the average consider the number of dialogue steps of the
transaction user. If the response time is more and dialogue steps of fewer 1 or 2 then the
average response time could not be worked out. The response time should be worked out
only when there are atleast 10,000 dialogue steps.
MEMORY
Physical Memory: The memory that is available or the memory that is configured on the
instance using the parameter PHYS_MEMSIZE.
* PHYS_MEMSIZE: This parameter restricts the usage of memory by that instance.
Virtual Memory: The physical memory and SWAP memory/ Pagging Memory on the
disk
The physical memory will not be sufficient to provide the users for temporary work area/
Calculations/ so a part of the disk which is configured for SWAP is used.
On UNIX during installation assign atleast 20GB of SWAP. On windows assign atleast
3*RAM size/ 20 GB which ever is higher.
Shared Memory: The memory that is used by all the applications (OS, DB, R/3)
Extended Memory: The memory that is used by SAP work processes is referred as
Extended Memory.
Local Memory: The memory that is assigned to work process is referred as Local
Memory
Roll Memory/ Roll Buffer: The memory that is used by work process to store the user
context information is referred as Roll memory.
Private/ Heap Memory: The memory that is used by work process exclusively by
restricting itself.
MEMORY ALLOCATION

2. Dispatcher assigns the WP
113
3. WP requires memory to Roll -In the user context.
4. WP gets memory from local memory which is defined in the parameter
ztta/roll_area. It gets only a part of it which is defined by parameter ztta/roll_first
(20KB)
5. If the allocated memory is not sufficient then it gets allocated from Extended
memory ztta/roll_extension.
6. If that is also not sufficient then it uses the remaining ROLL Area.
7. If that is also not sufficient then it uses HEAP/ PRIVATE Memory and the WP
goes into PRIVATE Mode.
8. Heap memory is defined by the parameter
Abap/heaplimit=4GB
Abap/heap_area_dia
Transaction ST02 provides the memory utilization

9. Each dialogue uses abap/heap_area_dia and non dia uses
abap/heap_area_nondia both process should not exceed abap/heap_area_total.
Memory : RAM is the first Memory. Out of this we don't want to allow SAP to utilize
the whole memory.
Virtual Memory: Pagefile.sys
User --- Dispatcher --- WP --- Rolls Its Memory
114
Requires Memory to Roll In to the Task Handler
Ztta/roll_first - 20KB
Extended Memory is used by all the Work Processes.
20 KB ztta/roll_first through ztta/roll_area
Extended Memory ztta/roll_extension : 512 MB
Come back to local Memory
If all the memory is consumed it cant come back so goes to the Heap/ Private Memory.
CASE STUDY
We have configured 20 WP in the Instance and we know pretty well that each user
request consumes a minimum of 25MB of Memory
WP MEMORY 4GB 8GB STATUS

Roll_first Roll_extn Roll_Area Heap
1 20KB 512MB 19.980MB 2GB PRIV
2 20KB 512MB 19.980MB 2GB PRIV
.
.
8
9 20KB 0MB 19.980MB 5MB PRIV
Rdisp/max_priv_time
When the process uses Heap Memory it is used in Heap/ Private mode.
The processes which are in PRIV Mode cannot be timed out by
Rdisp/max_wprun_time
Rdisp/max_priv_time
So configure so that the process is timed out after this time (600 Seconds/ 10 Minutes)
when the work process goes into PRIV mode it will not listen to
rdisp/max_wprun_time=600sec. It will be released only after the task completion or
Memory is exhausted(Abap/heap_area_dia)/ timed out by rdisp/max_priv_time. This
situation is referred as Hour Glass Mode or WP Congestion. At this situation we can use
DPMON or SM04 to terminate the user session. If not kill the process at OS level based
on PID.
Q. The user complains that he could not login to the system - Hour Glass Mode?
A. 1. WP into PRIV Mode
2. ARCHIVE STUCK (The user could not update any record and results in hour
glass mode)
BUFFERS ST02
115
The frequently used content and less frequently modified is eligible for buffering.
Company Name, GUI, screens, calendars, table definitions, programs etc are eligible for
buffering.
Data such as Exchange Rates, Transactional Data(PO, Sales Order, Invoice,

Billing) are not eligible for buffering.
Buffering is specific to instance. Each buffered element is stored in the memory

of the instance in terms of Directories and Space.
Eg. Programs can be stored up to 150000 KB, 150 MB in 37,500 directories. If the
directories/ size is full then Buffer Swaps occurs in ST02.
When SWAP occurs the content needs to be fetched again from Database which
increases the response time.
RAISING A REQUEST TO SAP FOR A SAP ROUTER
From the Market Place www.service.sap.com

click on SAP Support Portal.
From Help and Support Tab
click on Report a Product Error
From Here Provide

Customer : Company Name
Installation :
System ID : JOD
Next
Search Term : SAP Router
Or Go with Message
Select the system & select the component
Raise a request as follows:
Dear SAP,
116
We have installed solution manager and 3 ERP systems in the landscape. Before
we start implementation we would like to establish connecting with SAP using SAP
Router.
Name of the Server : JOMLSOLMAN

IP Address : 213.210.213.197
(This is where our SAPRouter is going to be configured)

We are using dedicated public IP Address
SID : JOS
INSTANCE NO : 00
Please send us certificate details.
{ Open the connectivity, How many hours it needs to be opened; Provide Userid and
password/ Client }
Provide your name R. Shunmugam

Phone No:
Hit SEND
Note: from Market Place My Profile Maintain Single Sign on Certificate Specify
Password.
From Market place Check the email.
SAP : 213.210.213.197
JOLSOLMAN
194.39.131.34
----------------
Earlier from the Back End system say for eg: SOLMAN system
001/ DDIC Login to the SOLMAN system
Discontinued from 2006 -
TCODE OSS1 (Online SAP Service)

From Menu Parameter Technical Settings
Hit Change
SAPRouter at SAP
Note: Instance 98 ( Is for SOLMAN Diagnostic Tool), 99(SAP Router)
All kind of services can be acquired from OSS1
117
Over the web using DIAG protocol. (It is discontinued)
----------------
4 systems in the landscape
SAP Router is a software program which is used to restrict to access the customer
systems using the table SAPROUTTAB.
SAPROUTTAB is a text file with out any extension in the router directory with prefix P,
D and S (Permit, Deny and Secure sometimes)
STEPS TO CONFIGURE SAP ROUTER
1. Create a directory with name saprouter in usr\ sap\directory.

usr\sap\saprouter
Ensure that the folder has full (Read + Write permissions)
Note
SAPRouter is an executable in the kernel directory (usr\sap\SID\sys\exe\uc\NTi386).
Nipping is an executable to ping to the router. This two executables needs to be copied to
the router directory. However we can also download from market place.
On Windows Check whether the SAPRouter service is running or not to make sure
whether the SAPRouter is already configured or not.
2. From Market Place My Company App Components

Look for SAPROUTER700
Windows server X64
Click on Add to download basket.
3. Login as <SIDADM
4. Create a sub directory E:\usr\sap\saprouter
5. From Command Prompt

Change directory to trans as it is holding the downloaded files
E:\usr\sap\trans sapcar -xvf saprouter_12_100004305.sar
118
6. copy the two uncared files in to the saprouter directory.
7. From market place click on Download Area SAP Cryptographic Software

.sar file.
It depends on OS
We can download either CAR or SAR file
Paste the file in usr\sap\saprouter

sapcar -xvf 90000114.car
-----------
Note: Download Manager Configuration
SUSERID and PWD
-----------
8. Create a service called SAPRouter service.
From Command Prompt Saprouter

ntscmgr install SAPRouter -b E:\usr\sap\saprouter\saprouter.exe - p "JOSADM"
It will create a service.
JOS is the SID
9. Define a file SAPROUTTAB

Create a file SAPROUTTAB in the saprouter dir with out any extension
119
10. SNC (Secured Network Connection Needs to be added)
For this
Goto www.service.sap.com/SAPROUTER-SNCADD
Apply
Copy [ Shows the Distinguished Name] Hit Continue
11. Define the Environment Variable.

My Comp Properties Advanced
Variable : SECUDIR
Path: E:\usr\sap\saprouter
Variable :SNC_LIB
Path: E:\sur\sap\saprouter\nt-X86_64\sapcrypto.dll
Sapcrypt.dll to encrypt and decrypt the messages.
12. Generating certificate from Customers End (SOLMAN System)

Use the command
Sapgenpse.exe will be in nt-X86_64 so goto
Saprouter CD nt-X86_64
Saprouter\nt-X86_64
sapgenpse get_pse -v -r certreq -p local.pse "Paste the distinguished name"
Prompts for PIN : any password
Twice
Sapgenpse - SAP Generic Personal Security Encryption
13. Work file certreq in \nt-X86_64

Open with notepad
And copy from BEGIN to END
Paste in the STEP 10 in the text box and hit Continue
Click on request certificate
It generates a text with BEGIN to END.
Now copy from BEGIN to END from SAP that site/ Screen
Paste it in a notepad file(without extension) with file name srcert in the folder nt-X86_64
14. Importing the Certificate

Nt-X86_64 sapgenpse import_own_cert -c srcert -p local.pse
15. being in nt-X86_64 sapgenpse seclogin -p local.pse -o JOSADM

Will create a file cred_v2
16. SAPROUTTAB open with notepad

copy the whole content (from already configured system)
120
provide SAP IP
Our IP.
17. TO check the Distinguished name

Sapgenpse get_my_name -v -n issuer
18. Router as Service

Services.msc saprouter
From Logon Tab
Select This Account : JOSADM
Apply
--------------------------------------------
To Uninstall
Ntscmgr install saprouter -b E:\.........
SAPSR3 - 14
SAPSR2 - 9
SAPSR1 - 6
------------------------------------------
19. Execute SM59

SAPOSS Change
IP Address of SAPRouter at Customer Side
And also change at SAP Side Router String
---------------------------------------
Goto Market Place
Download service connection
Maintain Data System Data
SOLMAN
Production System
Goto DB Server
Hostname SOLMAN
IP Address : 124.12.124.19
OS : NT/ INtel
Version : Win2003
DB Release : 9.2.0.8.0
Router String: H/220.227.194.202/s/3299

Create New Connection RFC Connection
Logon Security
E1
001
121
SCO4013677
AISUSER tcode
-------------------------------------
SAP ROUTER
Theory
1. Maintain our systems in the Market Place

2. SAP able to connect and we need to provide authentication
3. SAP Router provides the authorization and we need to provide the authentication.
The password will be visible [ ].
SAP router side will restrict the user.
Market place connect to SAP
R/3 Support
Open connection
Take out the access from SCC4, SE38, SA38...
SAP Router is an executable which is used to restrict the access to the customer systems
over the network. It works like a firewall/ proxy to permit and deny the access to the SAP
systems.
It needs to be configure before implementation Part of SAP.

--------------
RMMAIN tcode only in SOLMAN
Implementation Road Map Technical Infrastructure Planning
Order for Remote Connection to SAP
Project Preparation Phase.
-------------
SAP Router
1. Create message to SAP along with your SAP Router [Hostname], IP Address and
Customer Number (SAP Router need not to be installed on Solution Manager /DEV/
QAS/ PRD. It can be installed on any desktop, but it is advised to install on SOLMAN
system to ensure that it is monitored periodically.
Cust Number : When we buy SAP we will be provided with the customer number.
.SAR - SAP Archive

.CAR - Compressed Archive
Kernel comes with .SAR only

[Global Host] - DB - Central Instance - Dialogue Instance
Usr\sap
122
2. SAP responds with Distinguished name.
3. Create SAP Router directory and copy the executables from exe\uc\NTi386 or
download from the market place. (www.service.sap.com/swdc) copy only SAPCAR.exe,
SAPROUTER.exe and NIPPING.exe
4. Download the Cryptography files from Market place related to OS and bit version
(Download *.SAR files)
5. Uncar the files into SAPRouter directory

6. sapgenpse......... executable used to generate the personal security environment.
SAPROUTETAB is a file (without any extension) used to have ACL (Access Control
List) S - Secure; P - Permit; D - Deny; K -SNC (Secure network connection)
7. Generate the certificate using distinguished "DN" name with executable SAPGENPSE.
8. Copy and Paste certificate from Begin to End the market place url
/Saprouter-SNCADD
9. Request a certificate from the market place copy into srcert.
10. Import the certificate into router system using SAPGENPSE
11. Start the router using command saprouter -r -k "DN"
12. Goto SMP ---- Report Error --- Connect to SAP

Select the system - Maintain System Data -- Download service connector --
Maintain Router details ------- Start service connector -- Open connection by selecting the
service---- Specify no of days and hours. Similarly maintain all the other systems in the
landscape. Inform SAP to connect to our systems.
13. On each backend system we need to maintain the RFC details in OSS1 Transaction. It
will update SAPOSS RFC Connection.
SAPOSS, SAP-OSS, SAPSNOTE are created on communicating with the Market Place.
---------------------------------------------
ST02 continuation.
Used to monitor the buffer swaps on the Application Server/ Instance

LRU - Least Recently used.
Buffer swaps occurs when there are no sufficient directories or space. When more swaps
occur they are displayed on ST02 in swaps column.
Analysis:
123
Identify the buffer areas whose swaps/ Database access are more.
BUFFER SWAPS indicate the following
1. No Sufficient space or directories

2. The content is frequently modified
3. Mass transportation of objects
4. The configured buffers are small
5. During the restart and when support packages are applied and when upgrade is
performed.
Do no take any decisions based on the readings on a specific day. Analysis has to be
carried out if there are atleast 10,000 requests.
BUFFER HIT RATIO.
SAP recommends this value to be around 98%

{For every 100 request '2' request goes to database and the remaining should be from the
buffers}
Key areas that effect the performance are program buffers, table buffers and Table and
Field definitions. Change the program buffer using ABAP/ buffer_size to a maximum of
600 MB on 32 bit Machines.
Remaining parameters based on SAP recommendation from RZ11.
TABLE Buffering
SAP stores the content in tables (Every data except start and stop logs is stored in
DATABASE, no prog/ no data is available in the file system)
There are four types of Buffering
1. FULL Buffering
2. Generic Buffering
3. Single Record Buffering
4. No Buffering
This is maintained for each table SE13 refer USR02 Table.
1. Full Buffering: The tables which are frequently used and rarely modified are eligible
for buffering. (Also which are small in size)
Eg: T000 have all the clients and required to create a client copy. (This is fully buffered)
2. Generic Buffering: Tables which are relatively large, frequently used, rarely modified
using a set of keys (Fields)
124
Eg: USR02; T001 Company info
3. Single Record Buffering: The tables which are large in size, frequently used and
rarely modified are buffered using a primary key.
4. No Buffering: The tables which are large frequently used, and frequently modified are
not eligible for buffering.. VBAK (SALES), EKKO (PURCHASE)
BUFFER SYNCHRONIZATION
When more than one application server is configured then buffers between
different instances may not be synchronized. In order to synchronize buffers set the
parameter
Rdisp/ buffermode = Send on; exec auto.

Rdisp/ buffertime = 60 Sec.
Mechanism
1. User1 request to APP1 for update Sales order to Rs. 500 @ 10:00:01
2. User2 request to APP2 for update the same sales order to Rs.550 @ 10:00:20
3. User3 request APP1 for display @ 10:00:40
WP will ask DDLOG table to check for recent update within 60 Sec. (DDLOG is a buffer
synchronization table).
If there is any change then it will fetch from DB and swap out the buffer. IF there are no
updates fetches the same from APP1 Buffer. If the content is requested after 60 Seconds,
by that time it will be synchronized between APP1 and APP2.
DDLOG is a synchronization between instances and maintain TIMESTAMP
Note: DB13, DB02, DB buffer.
Refer - All the programs are stored in TADIR,

TSTC, T001, EO70, SE01
125
All the programs is in Uncompiled mode in TADIR table.
SGEN - Compiles the programs
ST04 DB PERFORMANCE MONITOR
- SQL server performance analysis. It is used to display the database

buffer hit ratio. It is recommended that it should not be less than 94% i.e. for every
hundred reads only 6 should goes to the database.
- Database hit ratio comes down below 94% then consider the following.
1. Frequent updates on the database

2. DB Buffer size is not sufficient to hold the content fetched from the database.
It is calculated by using formulae
[ Logical reads - Physical Reads]/ Logical Reads * 100
Logical Reads is the sum of [Physical reads and Buffer Reads] (Buffer Gets/ Reads)
FROM ST04
Physical Reads: The reads from the database.

If the buffer hit ratio comes down it effects on the DB response time.
Ensure that DB Buffers are configured as per the available memory. Some times
complete memory will be dedicated to DB Buffers.
ST06 OSMONITOR
126
It Fetches the data using service SAPOSCOL and it displays CPU Utilization, Memory
Utilization and disk response time.
The CPU idle time should not be less than 30% [For Portal up to 80% to 85%]
If it is below 30% we can consider the following.
1. The ABAP programs are expensive with multiple conditions and endless loops.
2. The CPU is not sufficient to handle the load because the hardware is not procured as
per sizing.
Probably the hardware is procured as per sizing but the number of users grown
dynamically (300-600). In this scenario we advice to deploy additional instances.
3. If the programs are expensive then refer to development team.
It also displays the memory installed on the machine, Memory available(Free)

along with the SWAP space. Ensure that physical memory free is available to handle the
user requests. If not memory bottleneck.
It is also used to start and stop SAPOSCOL (during Upgrades)
Note: OSCOL brings the operating system information into ST06. If OSCOL is not
started ST06 will be blank.
We can check TOP CPU utilization for the current in the last 24 Hrs.
LAN CHECK BY PING is used to ping to all the systems in the Network/ Landscape.
If a user complaints that he could not connect to the server (Ping to the desktop)
127
Click on Presentation Server
128
ST07 Used to identify whether the system is optimally designed or not.
Say for Eg: from the below screen.
Users are 9944 and the WP are 27 so each WP serves 5-10 Users so 27*10 = 270
Here users are including Active and Inactive Users.
Ask the customer to provide the list of Active users.

Each work process serves around 5-10 Users. Calculate the number of Process Vs Users
to determine no of Users/ Process.
Based on the number of servers we can also define logon load balancing. It is also used to
identify the memory utilized.
This is also used to identify Response time and Buffers Utilization.
AL11 : List the SAP Directories on Application Server.
ST11: It is used to display the work directory. It displays the log files related to work
process.
129
ST01 and ST05
Used to trace the following
1. RFC Trace
2. Buffer Trace Available in ST01 and ST05
3. Enqueue Trace
4. SQL Trace
5. Authorization Trace Only in ST01

6. Kernel Trace
1. When the RFC/ CPIC time are going beyond threshold value then switch on RFC
Trace.
2. When more buffer swaps occurs in the table buffering ST02. Switch on Buffer Trace.
3. Enqueue Trace: When the enque or enque wait time is increasing by 5 M.Sec on
CI(Central Instance) 100 M.Sec on Dialogue instance (Consider switching enqueue trace)
4. When there are too many expensive SQL Statements which are increasing the database
response time in ST04 then switch on SQL Trace. (Identify those statements in ST04)
Eg. Select * from can be fine tuned by using select single * from with appropriate where
conditions.
ST04 Detailed Oracle Session SQL Statements.
5. Authorization Check: Whenever user encounters missing authorizations and could

not be traced in SU53 can be traced out by switching the trace on User.
6. Kernel Trace: Used to identify the consistency of Kernel. It records all the calls that
are made to kernel when the trace is ON.
Note: Do not switch on the traces when they are not required. It will populate enormous
log files and occupies the complete disk place and system stands still. As a practice
switch on the trace and inform the user to run the transaction. Switch Off the trace.
RC=0 (Return Code)
Note: Tuning is not testing we need enormous analysis and data to justify the conclusion.
130
IMPLEMENTATION OF SAP
Pre-Requisites
1. Motivation of SAP for an ERP Software

2. Landscape Deployment Plan
3. Hardware Sizing
4. Hardware and Software Order
5. Installation of the Software
6. Post Installation Steps
7. User management
8. Router ------ Remote connection to SAP
9. Landscape Configuration
10. Transport Management
11. Testing Strategy
12. Go Live Strategy
13. Parallel Run
14. Go-Live
15. Support - Phase
1. MOTIVATION OF SAP FOR AN ERP
1.1. Customer wanted to deploy an application that suites to his requirements by

replacing the existing software due to the following reasons.
1. The existing Hardware is old and the response times are high.
2. The software is out of maintenance with no updates, or with no company
(Company Bankrupt/ Merger etc.)
3. The customer could not be competitive in the market due to the legacy methods
deployed
B1 - C++
No ABAP, BASIS, NW
4. The existing software is not capable to communicate with other systems

5. The software is not user friendly to take the user inputs.
6. It cannot communicate with print, fax, sms, paging devices.
7. Too many legacy systems, too little integration, manual inputs, monitoring are
the various issues with the current software.
Customer enquires in the market and calls for the Auditors to identify the software,
hardware and the Implementer.
Delloite, Bearing Point, KPBG, PWC (Price Water Coupons) are the auditors to
identify the requirements in the company. They define the pain points of every business
user owner and document them.
131
Example:
- The software should be installed on all the operating systems and databases.
- The GUI should be compatible, user friendly, ergonomically designed, colors, fonts,
languages, password change.
- The software should be unicoded language to support all the languages.
- The software should support (Online, Offline, incremental, partial, table level backup)
- The software/ Hardware should support mirroring, RAID, clustering, Disaster
Recovery, Restore etc.
- The software should support Mobile devices, Email, Fax, SMS, Pager, PDA etc.
Note: ATP Server - Available to Promise ----- Ware House.
Issue --- Description ---- Possible/ Not Possible/ Customizable/ If customizable Amount
of effort.
These requirements list will be floated as RFQ feasibility of software.
SAP is Strong in Manufacturing, Weak in Retail } Tcode-SFW5(Switch Framework)

SA38 - GETSYSDEF
- These list will be submitted to Oracle Apps, NAVISION, Hyperion, Peoplesoft, Seibel
(CRM) implementing partners.
Note: Toughly Coupled/ Hardly
- Preparatory costs has to be borne by vendors
TDMS - Test Data Migration Server

QAS
PRE PROD
SAND
DEV/ CUST/ GOLDEN
UNIT TESTING
INTEGRATION
PAYROLL/ TDMS 8
TRAINING
PRE PROD
PROD
- Customer decides software with the help of feasibility reports and assistance from
auditors.
132
- Customer calls for quotation to implement SAP
This is the first official document released to implement SAP.
- Support partners like IBM, TCS, WIPRO, MAHINDRA submits the proposal. They can
also raise questions in the form of RFI (Request for Information)
------------------
C:\pf\sapinst_instdir\ERP\system\ORA\central\AS
Ensure that there should not be any .bck files while reinstalling the SAP
Refer: sapfans.com; sapconsultant.com; sapbasis.com
Auditor gather info from - Business partner owners - Software Vendors.
RFQ - Request for Quotation (Released by customers)

RFI - Request for information
------------------
It can contain as follows

1. Module specific questions
2. Technical questions related to Hardware, Desktops, Routing, Access, VPN, Backup,
Disaster, Recovery etc.
3. Risk and mitigation
---------------
1. Project Implementation Methodology

2. Process
3. Company Strengths
4. Financial Background and Share Value
5. Past Projects and experience in that area
6. Average man power experience going to be deployed
7. Case studies and customer references
8. Implementation of solution manager (Provides Roadmap, Business Scenarios,
Documentation (Upload, Download) etc.
9. Certifications (CMMI - Capability Maturity Model, SIX SIGMA, Sap Partnership)
10. Challenges in the project, risks and mitigations
11. Assumptions
133
Based on the above proposal customer and audit team shortlist the two or three software
vendors (IBM, TCS, WIPRO etc) - Implementation Partners and call them for Interview
(technical discussions) to exhibit their capabilities.
Based on 4th and 7th vendor will be finalized to implement SAP
Note:
External Security
Routing
Switching
Proxy
Firewall
Internal Security
Authenticating Authorized users is Internal Security.
Project Costing:
1. Number of hours required/ No of Man days/ No of Man Months
2. Cost of the Man hours/ Man Days/ Man Months

Offshore 20-30$ 160-240$
Onsite 60-100$ 1000$ 20000$
3. Project can be a fixed bid let us say 2,00,000 (i.e. @ Million Dollars for completion all
inclusive (Fares, accommodation, staff, Replacement, Holidays, vacations, sick etc).
Payment will be released in Parts ---- Project Start 10%, Blue print - 20% Realization -
20%, Final Preparation - 20%, Go-Live - 30%.
4. Let us say the Project Manager is SAP. We need to provide manpower to SAP to
implement @ customer site. Eg. SAP Project bidder is SAP for 28 Crores in Singareni
Collories ... They out sourced to Seal Infotech for training and implementation.
5. Critical Tasks are based on Man days/ Man Hours

Example : Disaster Recovery
1. Fixed Bid
2. Time and Material (T&M)
3. Resource Based
4. Activity Based (Try to include Wait time)
The scope of work needs to be defined properly before sign-on. If SOW is not defined
properly, it is vendor responsibility.
Risks and mitigations has to be clearly stated in the SOW.
134
Delay in Software, Hardware requirements from customers are to be documented.
II. LANDSCAPE DEPLOYMENT PLAN
1. RFQ and RFI (Customer and Vendor)

2. RFP (Customer and Vendor)
3. SOW and Project Award (Customer and Vendor)
4. Landscape Deployment......... (Basis Consultant)
Landscape Deployment Plan:
It consists of the number of systems that are going to be deployed in the

customer data center. It may serve the customer as an overview of the SAP systems. But
exact number of systems will be known only after the Hardware sizing
1 CPU / 2 Parallel Process

By default 3 Parallel Process.
III. HARDWARE SIZING
It is an exercise carried out by Basis consultant with the help of the customer business
process owners, Project Manager and Hardware vendors (IBM, HP, SUN, DELL). It is
used to determine the CPU's, Storage (Hard disks) and Memory.
SAP Provides quick sizing toll (http://service.sap.com/sizing)
Goto Sizing tool Click on Quick sizer

It will be opened on new window
Provide customer number, Provide Project name and create a Project for sizing.
1. Provide Customer details to SAP
(Name of the contact, Email Id, FAX)
2. Platform and communications
3. OS, DB, Mirroring, RAID, CLUSTERING
Standby server or do you need any suggestions.
135
Note: Legacy database size (get the details from customer what amount of data they are
planning to migrate into SAP, Example Customer Database size is 400GB but they want
to migrate 250GB into SAP (Customer, Vendor, Supplier, Material, Address, FI
Transactions)
High Availability options (Time of Availability)
These are the general details that are required for sizing.
Load On the System:
Users work on the system on various modules

MM - Logistics
SD - Sales
FI - Financial
40% More to the sizing result.

SAP's - SAP Application Benchmark for Performance Standards)
It is calculated in terms of Hardware vendors provide CPU in terms of the CPU's
Eg. IBM P Series generates 800 SAP's/ CPU.
Note:
----------------------------
IBM - DB2 [AIX O/s - DB2 Database]; I Series V5R4 - DB2]
SAP - MAXDB
Oracle
SQL Server - Microsoft
P Series, X Series (I Series V5R4) is the O/s
Clustering (Mechanism : PING PONG)
DD02L - ALL Sap tables will be stored

65,611
SQLSelect bname, mandt from SAPSR3.USR02;
SAPSR3 - Database schema owner

SAPSR3DB - JAVA
------------------------------
Sizing is performed by quick sizer which is proprietary by quick sizer which is

proprietary tool of SAP. Sizing is based on the following.
1. High Availability
2. Type of Users
3. Modules used
136
1. RAID1 - Mirroring (1:1) on disk goes down other should take over.
2. RAID5 - (5 Disks---- Util -4; 1 Spare/ Parity)
3. SAN - Storage Area Network

4. Backup - SAN
5. If disaster occurs ------ Setup DR Server in a different geographical location
6. If the connectivity fails ...... buy more leased lines from different vendors
7. If the existing server collapses -- due to power cable --- multicables -- UPS -- etc --
Generator
Network Cable --- More than one cable

CPU's -- Multiple CPUS
Memory - Hosted on Multiple slots
DISK - RAID and SAN
8. If the complete system collapses due to hardware failure use clustering -- Two Parallel
systems (Used for failover or Load balancing)
Eg. IBM P-Series
Unless unlocked by IBM we cannot make use of the additional Hard Disks
137
Note: For Upgrade - Sizing
Capacity - Sizing
Module Selection: Select the modules that are going to be implemented like
Logistics, Financials, Product life cycle Management (Currently HR is not going to be
implemented but, there is a plan to implement in future, If it before three years consider
HR in sizing if not.
1. User - 480 Dialogue Steps with the system

- 40 HRS * 60 Mins
1Dialogue Step - 40*60/480 = 5 Min = 300 Sec
2. 480 - 4800 Dialogue Steps - 40 Hrs - 30 Sec
3. 480 - 14400 - 40 Hrs - 10 Secs
Eg. Purchase Order / Week - 200 * 10 Dialogue Steps = 2000.
Service Desk
1.Need to activate some services

2. SICF
3. Execute
4. Default Host
- SAP
- Public
- bsp
- SAP
- htmlb RT Click Activate Service
Note: This should be done as Post Installation Steps

SPRO SAP Solution Manager
General Configuration
Activating BC Sets (BC- Business Configuration)

Tcode: scpr20
From End user system

If any one stuck @ point executing a command SM59 Help
Create Mssg.
Component BC-MID-RFC
138
Test
Low
Test -- TKT No: 008000000001
The Strategy is to migrate/ upgrade the hardware for every three years. The sizing
is based on
2. Modules and
3. No of users
Along with legacy database and future growth of users
User Low Medium High

FI 50 250 250
CO 50 250 250
The sizing is also called as T-Shirt sizing which determines your servers as (S, XS, M, L,
XL, XXL) Sizing output determines the memory, storage and CPU in terms of Saps'.
SAPS is ( SAP APPLICATION BENCHMARK FOR PERFORMANCE STANDARDS)
SAPS are calculated based on Sales module. SAP assumes that a sales order/ Purchase
order consumes around 8-12 Dialogue steps. For every 2000 sales documents that are
generated per hour requires 100 SAPS.
CPU cannot be arrived directly because the process speed depends upon the
hardware vendor. (The hardware vendor determines the CPU Size based on SAPS
example an ISeries machine single CPU generates 800 SAPS.
If the sizing output requires 3200 SAPS then we need 4 CPU's.

The Hardware resources are required for the following which needs to be considered
while sizing
1. OS
2. Database
3. Interfaces (Like Fax, Email, SMS, Pager etc.)
4. Printers
5. Third party communication (Batch processing etc)
So we can consider adding 30-50% to the sizing results.
IV. HARDWARE ORDER
1. Customer calls the RFQ from various vendors to supply hardware.

- Based on companies stability, consistency, reliability, past experience, case studies,
price and support (warranty)...
139
- Hardware vendors take 3 weeks to 4 weeks to deliver based on the availability of the
hardware.
HP ships from Singapore, Philippines and Malaysia
IBM ships from US
V. ORDERING SAP SOFTWARE
ISUSER (INDIAN SAP USER FORUM)

ASUSER(AMERICAN SAP USER FORUM)
Communicate with SAP vendor (Channel Partners) and purchase the license.
License is a single user based. i.e. If we buy one license we can access ... ERP, SRM, BI,
PI, EP, Solution Manager, MI etc.)
SCM. SRM CRM are charged Separately.
If we buy MYSAP business suite then all comes under one license.
* There is no lock for licensed users in the system. We can buy 100 Users and used for
10,000 Users.
* Every year we need to run USMM and send the report to SAP.
License Cost varies based on Geographical Location

MySAPFI - Oracle Apps
MySAPSCM - Peoplesoft
MySAPCRM - Sieble
Each license cost 2000 USD

Each Developer Cost 4000 USD
After negotiation in Indian Market the Single user cost comes to 40,000 to 1,00,000
depending upon number of users.
For 40,000 we should have atleast 150-200 Users for 10+1 cost 18 Lakhs.
---------------------------
Note:
Heap Memory - Part of the Physical Memory (RAM Memory)

Physical Memory - RAM
Virtual Memory - Part of the Memory from the Hard disk
Buffer
Bin - Points to the target system
BIN contains default.pfl
SAP_BC_ADMIn
140
S_Transports
CTS_Admin
Disp+exe ( PING, Etc Entry, Any Kernel upgrade has been done (DEV_DISP.log)
---------------------------
BASIS
- It provides runtime environment for SAP Applications.
- 2.0 is based on two tier which is built on Mainframes.

- 3.0 onwards and upto 3.1I it is based on three tier and web services are provided by
using ITS.
- 4.0; 4.5A, 4.5B
- 4.6 A, B, C and D is kernel versions
(Mining, Textile, Chemical, Oil, Utilities, Real Estates, baking, Insurance... etc.)
SAP determined to bring all the components on to a common platform and introduced
SAP Web Application Server (WAS)
The first version of WAS is 620 (A direct jump from 4.6D)
On 620 ....... ERP Version is 4.7E

On 620 ........BW version is 3.1C
Owner of the Database
- SAPSR3........... Upto BASIS 4.6C

4.6D is the Kernel Version.
- SAP<SID ..... from WEBAS 620 to 640

It provides built in ITS to make application server as WEB Application Server.
- SAPSR3 from WEBAS 700

It is a Netweaver (640...... 700...........710).
Next Level of WAS is 640
ERP - ECC 5.0

BW - 3.5
SCM - 4.0
CRM - 4.0
2.0, 3.0, 3.1 are BW Versions

2.0, 3.0, APO are SCM Versions
2.0, 3.0, SRM are SRM Versions
141
XI - 3.0
EP - 6.0
Next level of WAS is 700
ERP - ECC6.0
BW - BI7.0
EP - EP7.0
XI - PI7.0
SRM - 5.0
CRM - 5.0
Install ABAP(CI, DBI), JAVA add on. Install Central System Installation (Select Usage
type during Installation)
R/3 Setup is used to install SAP upto Versions Basis 4.6C

SAPINST introduced in WEB Application Server 620-640. Interactive SAPINST is to
modify the inputs move front and back to review the inputs introduced in WAS700.
BASIS only Non-Unicode
From SAPWEBAS 640 unicode is introduced.
Run directory is used to host executables of kernel upto 640 where as OS version
(NTI386, AMD64, IA64) with UC/ NUC is available in version 700.
OLD: The database table spaces are 27 which ends with D(Data) and I(Index)..[SAPR3]
owner.
From 620
The database contains only 6 tablespaces(Physical Location) in 640 owner is SAP<SID
PSAP<SID
PSAP<SIDUSR
PSAP<SIDREL
SYSTEM
PSAPROLL(PSAPUNDO)
PSAPTEMP
SQL Select tablespace_name from dba_tablespaces.
The database contains only 8 tablespaces in 700. Owner is SAPSR3 for ABAP engine
and SAPSR3DB is for JAVA Engine.
142
SYSTEM - Database Related
PSAPUNDO - For Roll Back
SYSAUX - From Oracle Log for Administration
PSAPTEMP - Temp Storage Memory
PSAPSR3 - Component Specific
PSAPSR3700 - Version Specific
PSAPSR3USR - USER RELATED Info
PSAPSR3DB - JAVA Specific DB
GUI Versions
46C
46D
620
640
700
710
Based on Windows and JAVA
SQL select username from DBA_USERS;
Database Users (DDIC and SAP* are SAP Users resides in USR02 Table)
SQL select count(*) from DBA_USERS where owner = 'SAPSR3';

17476
SQL select count(*) from SAPSR3.DD02L;

65611
SQL select count(*) , owner from DBA_USERS group by owner;
Eg. [CDCLS] Cluster Table.
The difference is because of --
19,xxx 65xxx
Components: BASIS BASIS+ERP
DATABASE
It is a storage. It is used to store the data in the hard disk.
143
We can also store the data in terms of file system like test.txt, test.pdf, test.doc, test.rtf,
test.xls, test.ppt, test.pps
Disadvantage of the file system
1. The data is not in the organized format.

2. There are no indexes to search the data.
3. The data does not follow the LUW concept and so it is not consistent and reliable.
4. The version management will be difficult and time consuming to get the required/
identify the file.
5. The backup management and reorganization is not available.
These are the reasons for the evolution of DB.
Database: Used to store the data in the organized format and it has to follow RDBMS
rules (Relational Database Management System)
- Data is stored in terms of tables (Tables contain rows and columns). Columns are
headers and rows are the data.
- Duplication of data is avoided and uniqueness is obtained by using primary and

secondary keys.
- Data search is faster by using indexes (based on Keys)
Eg: As in windows we can create as many folders and subfolders with the same name and
the search criteria depends on the search string.
C:\shawn\shawn\shawn.......
- Database has its own structure to manage the data using the database specific binaries
and libraries.
Oracle/bin; mssql/bin; db2/bin;
Oracle/lib; mssql/lib; db2/lib;
- Database provides tools for backup management, reorganization, restore and recovery
- Databases follow RDBMS rules to achieve consistency, reliability and transaction

LUW.
LUW - LOGIC UNIT OF WORK.
It consists of one or more transactions that are bundled together which can be committed
as a group or rollback without any data loss.
144
RFQ(Approved) - Sales Order
Purchase Req - FI Dept (Approval) - Purchase Order - Tenders (Contractors)
(Eg: Purchase Order, Sales Order, Invoice, GR(Goods Receipt), GI (Goods Issued) AP
(Account Payables), AR (Account Receivables)
- Data is normalized and denormalised according to the requirements of the customer.
NORMALIZATION
Process of splitting up the larger tables into smaller tables using primary keys and
secondary keys... ERP(ECC6), SRM.
Databases are normalized.
DENORMALIZATION
Process of grouping smaller tables into larger tables for having data comprehensively
available for analysis and reporting BIW.
[SELECT, INSERT, UPDATE, MODIFY, DELETE]
Scenario
User requests for weekly status report.

2. Request is handled by dispatcher
3. Keeps the request in Queue
4. Based on the available processes requests are served based on FIFO.
5. R/3 Work process handles the user request by interpreting the screen elements,
program logic (Insert, Modify, Delete, Update)
6. The response is fetched from buffers if they are accessed earlier
7. If the request is not accessed earlier, the request is converted into Native SQL
statements of the respective database.
8. R/3 Work process communicates with database process to get the response.
9. Database work process checks whether the table exists, if table exists then checks for
the fields, if the field and table exists, then asks for the optimized path to go to the
database table and identify the relevant rows based on keys/ Indexes (Five 5 Seconday
Indexes)
145
10. The data is fetched into Database buffers before the response is sent to R/3 work
process.
11. R/3 Work process keeps a copy in the R/3 Buffer and response is sent to user.
UPDATE COMMAND
1. User request for updating a purchase order/ quotation / Invoice

2. The request is received by the dispatcher
3. Dispatcher keeps the request in queue based on FIFO
4. R/3 Work process handles the request and update the document into temporary tables
(cannot update the permanent tables because all the LUW's in the transaction has to be
completed)
5. In the process of updating it will communicate with enqueue and obtain the lock on the
document so that no other user updates it.
6. The update request goes to the database.
7. Database process handles the request and checks whether table, table definitions and
execution (Cost based optimizer) path are valid.
8. All the update requests goes to the database and lock the record in the database so that
no user update it.
9. Database process keeps a copy of the record in roll back segment PSAPROLL/
PSAPUNDO table space to roll back in case of CRASH/ System Failure.
10. Gets the record to database buffer for modification (No record is modified in the
database directly)
11. As the database buffers need to be accessed by user modifications are not performed
in DB Buffers instead in log buffers.
Eg. Consider a pan shop

Customer - Cigarette Paper - Accounts book
Log buffers are a small area around 1Mb - 4 Mb. As the log buffer is small the content is
moved in to Redo logs periodically.
Redo logs are duplexed (Mirror logs and Orig Logs) and ensure that the data is updated
in the database.
12. The committed data is updated into database
13. The locks are released and rollback gets invalidated.
Note: Committed data can be updated or Redo.
14. User gets the response that the record is updated.
ORACLE
146
Oracle is a database that is used by 2/3rd of SAP Customers. In order to
support SAP Customers it is mandatory to know the database management.
Oracle is provided by Oracle Corporation which owns (PeopleSoft, Seibel,

JDEdwards, and other small software's to compete with SAP.
Oracle is a proven, well spoken among customers, strong, reliable,

consistent, robust database to handle any amount of data in Terra bytes.
Microsoft SQL Server from Microsoft, DB2 from IBM and

SAPDB(MAXDB) from SAP shares the remaining 1/3rd of SAP Customers.
Versions
Oracle has versions of database
SAP License is costlier on Oracle than any other combinations.
SAP R/3 4.6C 8.1.7

R/3 4.7 and ECC5.0 9.2.0.2; 9.2.0.4; 9.2.0.6; 9.2.0.7
ECC6.0 10.2.0.2.0; 10.2.0.2.4
Linux - SAPDB (MAXDB) is the cheapest combination.
147
ORACLE:
DATABASE
A collection of information that has been systematically organized In form of
physical files for easy access and analysis..
A database is a set of files:
1. Control file
2 Redo file.
3. Datafile
4. Parameter file
Every running Oracle database is associated with an Oracle instance. When a

database is started on a database server , Oracle allocates a memory area called the
System Global Area (SGA) and starts one or more Oracle processes. This combination of
the SGA and the Oracle processes is called an Oracle instance. The memory and
processes of an instance manage the associated database's data efficiently and serve the
one or multiple users of the Database.
148
PARAMETER FILE (init<sid.ora)
Oracle uses a parameter file when starting up the database. The pfile is a text file
containing the parameters and their values for configuring the database and instance.
The default location is under $ORACLE_HOMe/dbs directory .
The parameter files tell oracle the following when starting up an instance:-
• The name of the database and location of control files.

• The size of the SGA.
• The location of the dump and trace files.
• The parameters to set limits and that affect capacity.
Some of the important parameters are:

· db_block_size
· db_files
· undo_management
· log_buffer
· max_dump_file_size
· db_block_buffers
· shared_pool_size
log_checkpoint_interval
INIT<SID.SAP:
The SAP utilities BRBACKUP, BRARCHIVE, and BRRESTORE must be configured

before they can be used. To do this you must set the appropriate parameters in
initialization profile init<DBSID.sap. Before using one of the SAP utilities, find out
exactly which parameters you have to configure. Changes to parameter values do not take
effect until you call the corresponding utility.
InitSID.sap is located in /usr/sap/<SAPSID/SYS/exe/run/initSID.sap
Important parameters in init<Sid.sap
• archive_copy_dir: This parameter identifies the directory used by BRARCHIVE

to back up the offline redo log files to a local disk
• backup_mode: This parameter is used by BRBACKUP and BRRESTORE to

determine the scope of the backup/restore activity.
• backup_type: Identifies the default type of the database backup. This parameter
is only used by BRBACKUP
tape_size: Storage size in gigabytes (G), megabytes (M) or kilobytes (K) for the tapes
that will be used for backups and for archiving redo log files.
149
remote_host: this parameter is to specify the name of the remote host, if you want to
make a backup to a remote disk
volume_archive: This parameter is used by BRARCHIVE to identify the

volume/directory to be used for the archive of the offline redo log files
volume_backup: This parameter is used by BRBACKUP to identify the

volume/directory to be used for the backup of the database or non-database files
backup_dev_type: Determines the backup medium that you want to use .It may be a
disk, tape etc
Database Buffer Cache:
Is a fairly large memory object that stores the actual data blocks that are retrieved
from datafiles by system queries and other data manipulation language commands
The buffers in the cache are organized in two lists:

– The write list and,
– The least recently used (LRU) list.
The write list holds dirty buffers – these are buffers that hold that data that has
been modified, but the blocks have not been written back to disk.
The LRU list holds free buffers, pinned buffers, and dirty buffers that have not
yet been moved to the write list. Free buffers do not contain any useful data and are
available for use. Pinned buffers are currently being accessed
Redo Log buffer Cache:

The Redo Log Buffer memory object stores images of all changes made to database
blocks. As you know, database blocks typically store several table rows of organizational
data. This means that if a single column value From one row in a block is changed,
the image is stored. Changes include insert, update, delete, create, alter, or drop.
Data dictionary Cache:

The Data Dictionary Cache is a memory structure that caches data dictionary
information that has been recently used. This includes user account information, datafile
names, table descriptions, user privileges, and other information.
The database server manages the size of the Data Dictionary Cache internally and
the size depends on the size of the Shared Pool in which the Data Dictionary Cache
resides. If the size is too small, then the data dictionary tables that reside on disk must be
queried often for information and this will slow down performance.
150
DBWn:
Writes to datafiles when one of these events occurs that is illustrated in the figure below.
LGWR:
The Log Writer (LGWR) writes contents from the Redo Log Buffer to the Redo
Log File that is in use. These are sequential writes since the Redo Log Files record
database modifications based on the actual time that the modification takes place.
LGWR actually writes before the DBWn writes and only confirms that a COMMIT
operation has succeeded when the Redo Log Buffer contents are successfully written to
disk. LGWR can also call the DBWn to write contents of the Database Buffer Cache to
disk. The LGWR writes according to the events illustrated in the figure shown below:
151
SMON:
The System Monitor (SMON) is responsible for instance recovery by applying

entries in the online redo log files to the datafiles. It also performs other activities as
outlined in the figure shown below
• If an Oracle Instance fails, all information in memory not written to disk is lost.
SMON is responsible for recovering the instance when the database is started up
again. It does the following:
• Rolls forward to recover data that was recorded in a Redo Log File, but that had
not yet been recorded to a datafile by DBWn. SMON reads the Redo Log Files
and applies the changes to the data blocks. This recovers all transactions that
were committed because these were written to the Redo Log Files prior to system
failure.
• Opens the database to allow system users to logon.
• Rolls back uncommitted transactions.
• SMON also does limited space management. It combines (coalesces) adjacent
areas of free space in the database's datafiles for tablespaces that are dictionary
managed.
• It also deallocates temporary segments to create free space in the datafiles.
PMON
152
The Process Monitor (PMON) is a cleanup type of process that cleans up after
failed processes such as the dropping of a user connection due to a network failure or the
abend of a user application program. It does the task shown in the figure below:
CKPT:
The Checkpoint (CPT) process writes information to the database control files
that identifies the point in time with regard to the Redo Log Files where instance
recovery is to begin should it be necessary. This is done at a minimum, once every three
seconds.
153
checkpoint records as a starting point for recovery. DBWn will have completed
writing all buffers from the Database Buffer Cache to disk prior to the checkpoint, thus
those record will not require recovery. This does the following:
• Ensures modified data blocks in memory are regularly written to disk – CKPT can
call the DBWn process in order to ensure this and does so when writing a
checkpoint record.
• Reduces Instance Recovery time by minimizing the amount of work needed for
recovery since only Redo Log File entries processed since the last checkpoint
require recovery.
• Causes all committed data to be written to datafiles during database shutdown.
• If a Redo Log File fills up and a switch is made to a new Redo Log File (this is
covered in more detail in a later module), the CKPT process also writes
checkpoint information into the headers of the datafiles.
• Checkpoint information written to control files includes the system change
number (the SCN is a number stored in the control file and in the headers of the
database files that are used to ensure that all files in the system are synchronized),
location of which Redo Log File is to be used for recovery, and other information.
• CKPT does not write data blocks or redo blocks to disk – it calls DBWn and
LGWR as necessary
Logical Structure:
It is helpful to understand how an Oracle database is organized in terms of a
logical structure that is used to organize physical objects.
154
Tablespace:
A tablespace is a logical storage facility (a logical container) for storing objects
such as tables, indexes, sequences, clusters, and other database objects.
Each tablespace has at least one physical datafile that actually stores the
tablespace at the operating system level. A large tablespace may have more than one
datafile allocated for storing objects assigned to that tablespace, belongs to only one
database.
Tablespaces can be brought online and taken offline for purposes of backup and
management, except for the SYSTEM tablespace that must always be online.
Tablespaces can be in either read-only or read-write status.
Datafile:
Tablespaces are stored in datafiles which are physical disk objects.
A datafile can only store objects for a single tablespace, but a tablespace may
have more than one datafile – this happens when a disk drive device fills up and a
tablespace needs to be expanded, then it is expanded to a new disk drive.
The DBA can change the size of a datafile to make it smaller or later. The file
can also grow in size dynamically as the tablespace grows.
155
Segment:
When logical storage objects are created within a tablespace, a segment is
allocated to the object. Obviously a tablespace typically has many segments. A segment
cannot span tablespaces but can span datafiles that belong to a single tablespace.
Extent:
Each object has one segment which is a physical collection of extents. Extents are
simply collections of contiguous disk storage blocks. A logical storage object such as a
table or index always consists of at least one extent – ideally the initial extent allocated to
an object will be large enough to store all data that is initially loaded.
As a table or index grows, additional extents are added to the segment.
A DBA can add extents to segments in order to tune performance of the system.
An extent cannot span a datafile.
Block:
The Oracle Server manages data at the smallest unit in what is termed a block or data
block. Data are actually stored in blocks.
156
Oracle Database Backup
Three ways of doing database backup:
– Full Offline(Cold) Backup
– Full Online(Hot) Backup - archiving must be on
– Export Utility Backup
Cold backup:
cold backup is taken when database is shutdown normal. The following filles
should be backed up.
– All Datafiles
– All Control files
– All Online Redo logs
– Init.ora
Hot backup:
Hot backup is taken when database is up and running in Archive log mode. Hot
backup Is taken on tablespace by tablespace mechanism .We put the tablespace in Begin
backup mode and after finishing the backup you must set it to end backup mode.
Export and import:
Is an oracle utility used to store database data in export format (.dmp) files for
later retrieval. These files can be later used to write back into Oracle database via import.
• Exports basic function is to extract the object definition and table data from oracle
database and store them in binary format. Three levels of export are:
• Table level
• Schema level
• Database level
Syntax: $ exp <username/password parameters
Exports are of three types:
• Incremental Export
• Cumulative Export
• Complete Export
Types of Backups
• online : Database backup in online mode, in other words, with the database
running.
• online_cons : Database backup in online mode. As well as the database files, the
offline redo log files generated during the backup are copied to the same volume.
You then have a logically consistent dataset available. This backup of the offline
redo log files with BRBACKUP runs completely independently of other
BRARCHIVE backups.
• Offline: Database backup in offline mode, in other words, the database is shut
down during backup. When you select this parameter, BRBACKUP checks that
no SAP system users are connected to the database. If an SAP System is active,
the database is not shut down and BRBACKUP terminates the process with an
error message.
157
• offline_force: Database backup in offline mode, in other words, the database is
shut down during backup. BRBACKUP always shuts down the database, even if
the SAP System is active.
• offline_standby: Data backup of a standby database in offline mode; in other

words, the standby database is shut down during the backup. This backup mode is
only relevant for the disaster recovery configuration.
• online_split: The mirror disks are split and backed up while the database is
running. The tablespaces to be backed up are only placed in BACKUP status
during the split. This backup mode is only relevant for the ‘split mirror’
configuration
• offline_split : The database is only shut down for the mirror disks split. The
backup of the mirror disks can take place whilst the database is running. The R/3
System is available during the entire split mirror backup. No transactions can be
carried out during the short period of time that the database is shut down. This
backup mode is only relevant for the ‘split mirror’ configuration.
• offline_stop: Database backup in offline mode without a consequent startup of

the database. After its backup the database can be transferred directly into the
mount standby status. This type of backup is only relevant in the following case:
The productive database is saved and then takes over the role of a standby
database. The backup itself becomes a productive system
TAPE MANAGEMENT
Before a backup can be performed, you must initialize the tapes to be used,Set the backup
profile parameters ,Label the tapes
The profile init<SID.sap is used to set the following parameters:
tape_use_count defines how often a tape can be reused.
expir_period defines the length of the backup cycle. To allow the tape to be reused after
28 days,
set this parameter to 28.
backup_dev_type defines the type of backup device used. To perform backups to a local
tape
device, enter tape. Other options include pipe (remote), tape_auto (auto loader), util_file
(backint
interface), and disk.
volume_backup defines the tape pool for the database backups
volume_archive defines the tape pool for the offline redo log file backups
When using hardware or software compression, data on tape requires less storage space.
The
compression factor indicates the degree of compression possible for the backup data.
Use SAPDBA to determine which compression ratio to use when backing up your data.
158
This factor depends on the fill level of the database files to be backed up. Because of the
changing
fill level , you should redetermine the compression rate frequently (at least once per
backup cycle).
159
Administration using BRTOOLS
Starting and Stopping Instance
STEP 1. Start BRTOOLS from command prompt to get the below screen
STEP 2. Enter Option 1 to get the below screen where you can perform lots activities on
instance
STEP 3. Enter 1 to Start database

Enter 2 to Shutdown database
160
Switching Archivelog Modes
Follow STEP 1 and STEP 2 as above.
STEP 3: Choose 3 and continue
STEP 4
STEP 5 Enter 3 to switch to Archive log mode
161
Enter 4 to switch to Non Archive log mode
Tablespace % fill level
Follow STEP 1
STEP 2 Enter 2 for Space management
STEP 3 Enter 7 to get below options
STEP 4 Enter 1 to check the tablespace fill level
162
The below screen displays the list of tablespaces and the % used space
Adding Datafiles
Follow STEP 1 in Starting and Stopping Instance

Follow STEP 2 in Tablespace % fill level
STEP 3 Enter 1 to get the below screen
163
STEP 4 Enter 3 to give tablespace name
The following screens allow to change file size and path
164
STEP 5 Enter N to start adding data file.
165
Health check procedure
The Main goals of system monitoring

 To keep the system running
 To analyze and correct errors
To make the system run perfectly, monitoring should be done periodically.

Monitoring is done using some Transaction Codes.
TRANSACTION CODES
Check for active Application Servers:
SM51 is the T-Code used to view active application instances/servers . SM51 shows
only active servers. So make sure all the instances are up and running. Below is
the Screen shot of SM51
To check whether all the instances are active/inactive in the SAP system
RZ03 T-Code is used . Below is the screen shot
166
Check for Work Processes status of all Application servers
Run SM51. It displays all active instances/servers. Double click on each of the
instance then it displays all the work process and their current status (SM50). If the
work processes is in PRIV mode we have to copy and paste it in (SM50).
Check for System logs :
SM21 is the T-Code which display system logs. Run SM21 , choose log for all remote
application servers and also specify date & time if required.
167
Then click on Reread system log
When click reread system log it displays the system logs. System Log stores all
messages including problems warnings & information .In this system log we mainly
look for errors related to Database listed as ORA-???? Error and update terminate
errors. Then copy and paste it in SM21.
Check for ABAP/4 Dumps:
ST22 is the T-Code which displays the ABAP dumps. Run ST22, in ST22 their will
be 2 options i.e., TODAY and YESTERDAY. Click on Today option
168
It list out all the ABAP dumps generated for the day. Copy and paste it in ST22 row.
If there are more than 20 dumps ,Shoot a mail to the client.
Check for Lock Entries:
SM12 is the T-Code which displays the lock entries. In SM12 any lock entry which
is quite old i.e., active more than 26 hours , has to copied and pasted in SM12 and
also shoot a mail to the client.
Check for Background Job status:
SM37 is the T-Code used for monitoring background job status. Give the server
time and execute. If there are any cancelled jobs, we will copy and paste it in SM37
Cancelled jobs and also take the job log of that particular cancelled job and paste it
169
in SM37 Job Logs. If one particular job is cancelled more than 20 times ,a mail
should be shoot to the client.
To check the job log select the job which is cancelled and click on job log
Below is the job log screen shot
Check for Database growth :
DB02 is the T-Code which displays the Current sizes of all the Tablespace. SAPDBA
is the tool used at OS Level to View size of the Table space. Below is the screen shot
CLICK on Refresh and then click on DB checks & updates histories
170
Then you will get the below window after the above step .Now click Yes
After refresh, click on current sizes
171
Then it displays the current sizes of all the Tablespace as shown below
If the Table space has reached near capacity (i.e., above 90%).Mark it in red, but
don’t send mail. If the Table space has reached (i.e., above 97%).Shoot a mail to the
client
DB02 is also of below page,if it is MS SQL and so copy and paste the box values as
shown below
172
Check for Log on Load Balancing:
SMLG is the T-Code for Logon Load Balancing. We check for load distribution,
Average Response time and Quality Ratio.
173
Now press F5 for Load distribution or click. It displays the below screen, copy and
paste only the selected path.
174
Check Sap System Performance or Average Response time for DIA process:
ST03 is the T-Code used to check system performance. In this we can check the
Dialog Response time for each Application instance.
Click on Detail analysis menu
Then click on compare all servers
175
Then click on other task type and select Dialog and press the tick
176
Then Copy the below part only means Dialog steps and Average response time and
paste it.
Check for Logged on users:
AL08 is the T-Code which displays the users logged on each application instances.
Select only Active Instance and No. of Users and paste it.
177
Check for Update Terminated:
SM13 is the T-Code which displays the update records. We mainly look for
Terminated Updates. Look at the detailed information of each failed update record.
Select cancelled and execute it
After executing the above step, if there are any cancelled update records copy and
paste it and if there are more than 10 update errors shoot a mail to the client.
178
Check for Backup Logs
Go to DB12 .Take the information of successful Backups. Below selected part has to
be copied and pasted in DB12 .If the SQL is the server below screen will be
appeared.
If Oracle is the server then below screen will be appeared. Go to DB12, Click on
Archive directory status as shown below
179
After Clicking Archive directory status, you will get the below window. Copy and
Paste the selected part.
180
Check for Traces
To check the traces, go to ST05. Copy and paste the selected part as shown below
Check for Long Running Jobs:

To check for long running jobs, SM66 Transaction code is used. Go To SM66
If there is any job which is running for than 3000 ms, Copy and paste it in SM66.
Also if there is any job running more than 50,000ms in Dialog and job running more
than 1, 00,000 ms in Background must be escalated to the client through mail.
Below is the screen shot.
Check for Batch Input Errors:

To check for Batch input Errors, SM35 Transaction Code is used. Run SM35.
Then click on INCORRECT as shown below
181
After clicking Incorrect Option, if found Batch Input Errors of that particular date
Copy and paste it in SM35.If the errors are more than 20 , mark it RED
Check for Security Audit Logs:

To check Security Audit Logs, Use SM20 Transaction Code. Run SM20
And select as shown below
182
Click on REREAD AUDIT LOG
Copy and Paste the User Locked and Users created information, As shown below
183
Check for Scot Errors:-
Run SCOT transaction code for Scot Errors. Copy and paste the selected as shown
below. If the Scot errors are more than 10 escalate to the client through mail
Check for OS –Logs :

To check for OS logs , ST06 Transaction Code is used.
RUN ST06, copy and paste the selected part as shown below
184
Then click on DETAILED ANALYSIS MENU
After the above step , click on OS LOGS
185
In OS Logs, if there are logs related to DISK, SRV, EVENT LOGS, copy and paste
it in ST11 .
Check for Sap Buffers:

To check SAP Buffers, ST02 Transaction code is used.
Go to SM51, Double click on Central instance and run STO2. Copy and
Paste all the values which in RED Colour. The same procedure is performed
186
For all the Application servers. Below is the screen shot
Check for Spool Errors:

To check for Spool errors, SP01 Transaction code is used.
Run SP01 .Below is the screen shot
187
After executing, below screen will be displayed. Press Ctrl+Pagedown or
Click on the option which shown below
Once you click on last page option, below screen will be displayed .In this the
Spool Requests with errors should be selected .As selected below,
After clicking on the above option, below screen will be displayed. Copy and paste
the spool errors in SP01 .If there are more than 50 spool errors, then they have to be
deleted.
Check for Database Locks:

To check for Database locks, DB01 Transaction code is used. Run DB01,
If there are any DB Locks or Lock waits, it displays the list in the page .Copy and
paste It in DB01.
188
Common Basis Transaction Codes
Administration
AL11 : Display SAP Directories

BD54 : Maintain Logical Systems
OSS1 : Logon to Online Service System
SALE : IMG Application Link Enabling
SARA : Archive Management
SCC3 : Copy Analysis Log
SCC4 : Client Administration
SCC5 : Client Delete
SCC7 : Client Import Post-Processing
SCC8 : Client Export
SCC9 : Remote client copy
SCCL : Local Client Copy
SCU0 : Customizing Cross-System Viewer
SICK : Installation 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
SM35 : Batch Input Monitoring
SM50 : Work Process Overview
SM51 : List of SAP Servers
SM56 : Number Range Buffer
SM58 : Asynchronous RFC Error Log
SM59 : RFC Destinations (Display/Maintain)
SM66 : System Wide Work Process Overview
SAINT : SAP Add-on Installation Tool
SPAM : SAP Patch Manager (SPAM)
SPAU : Display modified DE objects
SPDD : Display modified DDIC objects
ST11 : Display Developer Traces
ST22 : ABAP/4 Runtime Error Analysis
SU56 : Aalyze User Buffer
Alert Monitoring
AL01 : SAP Alert Monitor

AL02 : Database alert monitor
AL04 : Monitor call distribution
AL05 : Monitor current workload
189
AL16 : Local Alert Monitor for Operat.Syst.
AL18 : Local File System Monitor
RZ20 : CCMS Monitoring
Configuration
FILE : Cross-Client File Names/Paths

RZ04 : Maintain Operation Modes and Instances
RZ10 : Maintenance of Profile Parameters
RZ11 : Profile parameter maintenance
SE93 : Maintain Transaction Codes
SM63 : Display/Maintain Operating Mode Sets
SPRO : Customizing: Initial Screen
SWU3 : Consistency check: Customizing
Database Administration
DB01 : Analyze exclusive lockwaits

DB02 : Analyze tables and indexes
DB12 : DB Backup Monitor
DB13 : DBA Planning Calendar
DB15 : Data Archiving: Database Tables
Jobs
SM36 : Define Background Job

SM37 : Background Job Overview
SM39 : Job Analysis
SM49 : Execute External OS commands
SM62 : Maintain Events
SM64 : Release of an Event
SM65 : Background Processing Analysis Tool
SM69 : aintain External OS Commands
Monitoring
AL08 : Current Active Users

OS01 : LAN check with ping
RZ01 : Job Scheduling Monitor
RZ03 : Presentation, Control SAP Instances
ST01 : System Trace
ST02 : Setups/Tune Buffers
ST04 : Select DB activities
ST05 : Performance trace
ST06 : Operating System Monitor
ST10 : Table call statistics
ST03 : Performance, SAP Statistics, Workload
ST07 : Application monitor
190
STAT : Local transaction statistics
STUN : Performance Monitoring (not available in R/3 4.6x)
Spool
SP01 : Output Controller

SP11 : TemSe directory
SP12 : TemSe Administration
SPAD : Spool Administration
Transports
SCC1 : Client Copy - Special Selections

SE01 : Transport Organizer
SE06 : Set Up Workbench Organizer
SE07 : CTS Status Display
SE09 : Workbench Organizer
SE10 : Customizing Organizer
SE11 : ABAP/4 Dictionary Maintenance
SE16 : Data Browser
SE80 : Repository Browser
SM30 : Call View Maintenance
SM31 : Table Maintenance
STMS : Transport Management System
User Administration
PFCG : Profile Generator (Activity Group Maintenance)

PFUD : User Master Data Reconciliation
SU01 : User Maintenance
SU01d User Display
SU02 : Maintain Authorization Profiles
SU03 : Maintain Authorizations
SU05 : Maintain Internet users
SU10 : User Mass Maintenance
SMLG : Maintain Logon Group
SUPC : Profiles for activity groups
SUIM : Infosystem Authorizations
Other Transactions
AL22 : Dependent objects display

BAOV : Add-On Version Information
SA38 : ABAP reporting
SE38 : ABAP Editor
HIER : Internal Application Component Hierarchy Maintenance
ICON : Display Icons
WEDI : IDoc and EDI Basis
WE02 : IDoc display
191
WE07 : IDoc statistics
WE20 : Partner profiles
WE21 : Port definition
WE46 : IDoc administration
WE47 : Status Maintenance
$TAB : Refreshes the table buffers
$SYNC : Refreshes all buffers, except the program buffer
192
XI / PI - Transactions
XI Transactions
SXMB_IFR Start Integration Builder
SXMB_MONI Integration Engine - Monitoring
SXI_MONITOR XI: Message Monitoring
SLDCHECK Test SLD Connection
SLDAPICUST SLD API Customizing
Integration Engine -
SXMB_ADM
Administration
SXI_CACHE XI Directory Cache
SXMB_MONI_BPE Process Engine - Monitoring
SWF_XI_CUSTOMIZING Automatic BPM Customizing
XI URLs
(<host is the host name of the XI server and <sys# is its system number)
http://<host:5<sys#00/rep/ Exchange Infrastructure Tools

http://<host:5<sys#00/sld/ System Landscape Directory
http://<host:5<sys#00/rwb/ Runtime Workbench
http://<host:5<sys#00/MessagingSystem/ Message Display Tool
http://<host:5<sys#00/CPACache/ CPA Cache: Monitoring
http://<host:5<sys#00/CPACache/refresh?mode=delta Delta CPA cache refresh
http://<host:5<sys#00/CPACache/refresh?mode=full Full CPA cache refresh
http://<host:5<sys#00/nwa/ SAP NetWeaver Administrator
Communication Channel
http://<host:5<sys#00/mdt/channelmonitorservlet
Monitoring
193
SAP BASIS STANDARD REPORTS
BASIS
RSCOLL00 Performance Collector
RSBPCOLL Collect Values for statistics
RSSNAPDL Delete ABAP Dumps
RSTRFCER Delete EXEC LUWs
Delete old jobs
RSBPSTDE Delete old job statistics
RSBTCPRIDEL Reorganization of Print Parameters for Background Jobs
RSPO1041 Delete old Spool Files
Delete XMI-LOG Files
RSPO1043 Spool Data-Consistentcy check in Background (SP12)
Delete Central User Administration
RSBDCREO Delete Old Batch input Files
SAPconnect: Start Send Process Fax/Email
RSTBPDEL Delete Entries in DBTABLOG
RSARFCER Deletes entries in arfcstate and arfcdata for RFCs (ARFC)
RSTRFCES Deletes tRFC and qRFC entries (arfcrstate, trfcqout)
RSTS0024 Deletes joblogheaders 4m TST01 that are older thanjobs in TBTCO
SBAL_DELETE deletes application logs (balhdr)
RBDCPCLR Deletes Obsolete change pointers
RSARFCEX Retries entries in sm58 that may have failed due to temp conn errors
RSARFCDL Cleans up log file for sm58 transfers
RSN3_STAT_COLLECTOR- Non R/3 Stat collector
RSAL_BATCH_TOOL_DISPATCHING - Job for monitoring
RSN3_AGGR_REORG Program for Starting the Reorganization Function
DATABASE
View v$tables
RSORADJV Select DBA tables
RSANAORA Analyze table stats
TMS ( Transport Management System)

RDDNEWPP Schedule DDIC Jobs
RSTMSTIQ Adjust Queue
TMS_BCI_START_SERVICE - Automatic import
194
AS Java Stack most common LOG Files
This blog describes the most commonly looked log and trace files paths and their
purpose. I felt it will be handy for Basis Engineers in administering and troubleshooting
Java Stack based systems especially for beginners.
This Blog was created to provide comprehensive overview of Java log, trace files paths
and their purpose. Howerver this blog cannot cover all potential items as part of AS Java
troubleshooting related information. At glance, this blog covers instance, server node,
startup framework, bootstrap and etc,. logs, trace files.
This is being my first blog appreciate if any suggestion to improve.
Instance log files
Contents... Information about the J2EE instance startup, including parameters such as the
startup profile used, the system ID (SID), the instance name, and the startup command
used.
Use to analyze...Problems with the startup of the entrie J2EE instance. For example, the
central and dialog J2EE instances are running on different physical servers and the
startup profile is stored on the central J2EE instance. If a J2EE dialog instance cannot
access the startup profile on the central J2EE instance due to access restrictions, it would
report the permission problem in this log.
Location The log files of may be located under the following folders depending on the
type of the instance:
•/usr/sap/<SID/JC<XX/work for Java Central instance
•/usr/sap/<SID/J<XX/work for Java Central or Dialog instance
•/usr/sap/<SID/DVEBMGS<XX/work - for ABAP/DoubleStack Central instance
•/usr/sap/<SID/D<XX/work - for ABAP/DoubleStack Dialog instance
Log files The following log files can be distinguished:
•Files starting with std_: Log files from the standard output of the processes. In this file
you may find the output produced by System.out
•Files starting with jvm_ :The file may contain JVM error messages.
•Files starting with dev_ : The file may contain information about the exit code of the
processes.
•stderr2 : Redirect out/err before start of framework
•dev_jstart: Developer trace of the JStart controller
195
Processes and log files
SAPStart service
Content... JStart and all its child processes have different log, trace files and all these
files are located in work directory of jave instance.
Use to analyze...Contains information about startup process. You can check these files in
case of errors and undesired behavior during the startup process.
Location: The logs can be found in these locations:

Log files
sapstart.env: Environmental data
sapstart.log: Log messages from the startup process
sapstart.old: Backup log file from the previous startup
sapstartsrv.log: General logs
Startup framework
Location: The logs can be found in these locations:

•/usr/sap/<SID/JC<XX/work for Java Central instance (deprecated)
Log files
dej_jstart: Log messages containing JStart flow information
dev_jstart.0, dev_jstart.1: Backup log files from the previous startups
dev_*: Log files containing information about the startup of different processes
Example: dev_server0 is log file containing startup flow information about the first server
node.
dev_.0, dev_.1: Old startup flow log files for different processes
Bootstrap
Content...Information about files that are synchronized at startup., including the J2EE
component JAR files containing the J2EE libraries, services, and applications, and the
J2EE component property files. In addition to it, java startup and control framework
crates separate log files for each J2EE dispatcher and J2EE server process.
Use to analyze... Problems with bootstrap functionality that results in conditions such as
unsynchronized J2EE configuration modifications or outdated java libraries.
196
Location: The logs can be found in the locations:
•/usr/sap/<SID/JC<XX/work for Java Central instance (deprecated)
Log files
dev_bootstrap: Contains Startup Framework flow entries
dev_bootstrap.0, dev_bootstrap.1: Old files containing Startup Framework flow entries
from previous starts
log_bootstrap.log*: Rotating log files of the bootstrap process
std_bootstrap.out: The files contain the redirected output of Java's System.out
std_bootstrap.ou0, std_bootstrap.ou1: Backup logs from previous executions of the
bootstrap
jvm_bootstrap.out: The file contains the redirected output of the JVM
jvm_bootstrap.ou0, jvm_bootstrap.ou1: Backup logs from previous executions of the
bootstrap
Server
Contents...Information about a particular J2EE server process startup and shutdown. This
file contains a list of loaded J2EE of loaded J2EE managers (LogManager, PoolManager,
etc.), services and applications. If problem occurs, this log contains a description and
reason, the GC statistics, and a J2EE server process thread dump.
Use to analyze...Problems with the statup of a particular J2EE manager or service.
Location: The logs of the Startup Framework and the System.out output can be found in
the locations:
The logs of the Startup Framework and the System.out output can be found in these
locations:
The logs of the server node are located here:
/usr/sap/<SID/JC<XX/j2ee/cluster/server<X/log - for Java Central instance

/usr/sap/<SID/J<XX/j2ee/cluster/server<X/log for Java Central and Dialog instances
/usr/sap/<SID/DVEBMGS<XX/j2ee/cluster/server<X/log – for DoubleStack
Centralinstance
/usr/sap/<SID/D<XX/j2ee/cluster/server<X/log - for DoubleStack Dialog instance
197
Log files
defaultTrace_.trc*: Traces from the server processes, intended for developer's (and
debug) use.
server_.log*: Located in log-server folder. Targeted to system administrators. The file
contains entries for serious problems
dev_server.out*: Startup Framework flow logs from the server node startup
dev_server.0, dev_server*.1*: Old startup flow log files for different processes
std_server.out*: System.out output of the server processes
std_server.out0, std_server*.ou1*: Backup logs from previous executions of the server
node
jvm_server.out*: The file contains the redirected output of the JVM
jvm_server.ou0, jvm_server*.ou1*: Backup logs from previous executions of the
processes
Important periodic jobs

Certain jobs must run periodically in a SAP System production - for example, deleting
obsolete jobs or spool objects. If these periodic jobs do not run, system performance may
gradually deteriorate. Unfortunately, there is currently no easy-to-use support for such
jobs in Basis Customizing. Therefore, the jobs must be scheduled manually. For more
information, see SAP Note 16083.
The general procedure is to create a variant of each of the reports mentioned in this list
and create a job (e.g. with the name listed here) that contains this report as a job step.
Report Frequenc Recomm. Jobname, add. Short Description

y Notes
RSBTCDEL daily SAP_REORG_JOBS, Report RSBTCDEL
RSBTCDEL2 w/ SAP Note deletes entries from
525933 tables BTC* that contain
background job
administration data.
RSPO1043 daily SAP_REORG_TSP, SAP Note Report RSPO1043
98065 deletes inconsistent
objects in spool tables
TSP* that contain spool
job admin data
RSBDCREO daily SAP_REORG_BATCHINPUT Report RSBDCREO
deletes entries from
BDC* and APQ* tables
that contain Batch Input
administration data.
198
y Notes
RSBPSTDE monthly SAP_REORG_JOBSTATISTI Report RSBPSTDE
C deletes entries from
tables BTCJSTAT, and
deletes by this statistics
for background job
runtimes.
RSCOLL00 hourly SAP_COLLECTOR_FOR_ Report RSCOLL00
PERFMONITOR, SAP Note collects various
12103 statistical data for
performance monitoring
RSSNAPDL daily SAP_REORG_SNAP Report RSSNAPDL
gradually deletes old
short dumps that are not
marked for retention
from the SNAP table.
RSBPCOLL daily SAP_COLLECTOR_FOR_ Report RSBPCOLL
JOBSTATISTIC collects runtime
statistics of background
jobs which are used e.g.
for an SAP Going Live
check.
RSBTCPRIDEL monthly SAP_REORG_PRN, SAP Note Report RSBTCPRIDEL
307970 reorganizes print
parameters for
background jobs that
before 4.6A had been
deleted by RSBTCDEL
RSAL_BATCH_TOOL hourly SAP_REORG_TOOL_DISP Report RSAL_BATCH_
_ DISPATCHING TOOL_DISPATCHING
is necessary to start
method dispatching for
SAP system monitoring
in the background
RSXMILOGREORG weekly SAP_REORG_XMI, SAP Note Report
182963 RSXMILOGREORG
reorganizes the table
TXMILOGRAW which
contains log info on the
XMI interface.
199
y Notes
RSTS0024 weekly SAP_REORG_JOB2, SAP Report RSTS0024
Note 666290 deletes job logs that no
longer belong to any job
and orphaned jobs after
run of RSBTCDEL.
FAQ’s
Search answers for the below.....
What is your system landscape?
What are you roles and responsibilities in your company?
What are versions of SAP & R/3, Oracle you are using?
Patch numbers of SAP kernel & Oracle you are using
If a user wants to execute a background job immediately but there is

no Background work process available. How u will do?
What is common House keeping background jobs that run in your system?
What are common transport errors u faced while transporting?
How you will do client copy? If SAP * user is not available at all in
your system then how u will do client copy?
How u will apply OCS patches?
What is the database backup strategy in your company?
What is upgrade process? And how u will do that?
How u will give new authorizations?
How to adjust user master records? If user master record doesn’t

adjust what will you do?
How to check Kernel, tp versions?
Briefly explain a recent problem you faced, which u felt proud by

solving that? And ho u solved?
How you will rate your self in SAP, Oracle from a scale 1 – 10?
200
What are your daily activities in your company?
What are common background jobs that will run in your system?
If a background job runs more than the time it should be completed

normally then what actions will u take?
How to schedule background jobs at OS level?
How to add authorizations, how you will maintain profiles?
What are common transport errors and their codes?
Transport request types and its syntax
Where will u find transport error logs?
How to do transport at OS level?
How to transport objects from Production to Development?
How to define instances and operation modes?
What are Homogenous system copy and Heterogeneous system copy and how
you will do that?
What is oracle Architecture?
At OS level in which directory oracle alerts are stored?
If a lock entry is holding more than 24 hours then what will you do?
If another user wants to share that lock but the user using that lock
haven’t released lock he went for holiday what will u do? This user
wants lock ASAP then what will u do?
What will you do if u got Update failure?
What will you observe in System log (SM21)?
201
How to increase tables space, resizing, backups and when will you do?
Various client copy methods and how you will do them?
How you will get help from OSS notes?
What is the need of having Development system?
Difference between Application server and Central Instance?
How you will check whether database is active or not from OS level?
What is Transport domain and Domain controller?
What is Consolidation route and delivery routes?
How to lock a client? How to delete a client?
How to login in to SAP from command level?
How to define Logon groups? And what is Logon load balancing?
How you will rate your self in SAP, Oracle from a scale 1 – 10?
How you will do client copy?
If SAP* is not available then how u will do?
After client copy is table space and database sizes will be increased or not?
How to do client copy fast?
What are various profiles available for client copy?
How to do transport’s between Production and Development?
How to apply OCS Patches?
202
How to do client copy?
How to do transports from OS level?
Where the transport data files will be placed?
How to make security authorization reports?
In which table failed user login attempts will be there?
How to see the t able entry values?
How you will give new authorizations?
Have you participated in Kernel upgrading and OCS Patches?
Have you done any up gradations?
How to configure TMS?
What is transport domain?
What is Consolidation route and delivery routes? How you will identify them?
Transport error codes and their description?
The transaction should not be displayed in User Easy access menu but
he must execute that transaction how to do that?
203
SM51 ACTIVE SERVERS OVERVIEW
i) It displays list of Active application servers.
ii) It displays the process configuration.
iii) Double click on the servers to login to respective AS.
iv) It takes to SM50 screen.
v) Click on release notes to find o/s, DB and Kernel Version.
SM50 WORK PROCESS OVERVIEW
i) It displays all the WP of an Instance.
ii) Displays various work process in the application server along
with process it.
iii) Status of the WP (running,waiting,stopped,hold)
iv) Error reason for status[PRIV,reason,NUM,UPDATE]
v) Which Client,User,Report and action on the user worked on
work process.
vi) Here we can will the WP.
SM66 GLOBAL WP OVERVIEW
i) It displays active work processes in the R/3 system.
ii) Active processes of all Application servers.
iii) Identify work process which is consuming more heap memory
in sm66 and inform the user before terminating workprocess.
Every action will be done through CRF(change request form)
or notification to the user will be using the tcode.
iv) Here we cannot kill the process.
SM04 LOGON USERS OF PARTICULAR SERVER

i) In order to find users logged on instance.
ii) Display terminal from which user connected and display the
memory consumed.
iii) We can find total number users logged on the instance.
iv) Kill the user session.
AL08 GLOBAL LOGGED ON ACTIVE USERS
i) Displays list of users Globally.
ii) Displays no. of sessions programs, reports, running.
iii) Displays terminal from which user cancelled.
iv) Cannot kill a process.
v) Displays statistics of Application Servers and users.
SM21 SYSTEM LOG :

i) Here all systems messages are recorded.
ii) Here can see local & remote systems logs also.
iii) Runtime problems are recorded.
iv) Table space errors are recorded.
v) Operating System Problems.
vi) Programmatical Problems.
204
SM12 SYSTEM LACKS:
i) The locking process done by Enqueee.
ii) Screen lock required by the users will be displayed among
the user, we need to identify the locks which have been locked
since long time below are the steps to evaluate the locks.
iii) Check the lock table which is used in long time and identify
the user who has locked the table.
iv) Check the user is active are not.
v) If the user is not active are not found the go to SM04 or Al08
then release the lock.
vi) If the user is found try to call the user and send notification to
the user about the lock.
vii) Once approves release the lock.
ST22 ABAP DUMPS:
i) The runtime errors of the system will be logged in dump
analysis.
ii) Whenever there is a programmatical eror (or) reports exceeds
maximum for time execution, table space overflow, loop
errors, max extents reached will be logged into the screen.
iii) It gives detailed analysis of the error when it was occurred,
why, how, where and what could be done.
iv) When there is a bug in program we need to identify the error,
search sap notes with error.
v) In SM12 screen lock required by the users will be displayed
among the user, we need to identify the locks which have
been locked since long time below are the steps to evaluate
the locks.
vi) More number of locks in SM12 makes the system updates
inactive because of lock argument, will never allow the update
process to update into the database. Therefore it is essential to
monitor the locks.
SM13 CHECK FOR THE TERMINATED JOBS

i) To check for the update records.
ii) There are too many locks obtained by the users, the users are
not getting the locks to update their requests.
iii) Reaching the max. size of table, which can be identified by
analyzing the system lock and DB locks, once it is table size
is fixed or auditing then we need to restart the update process
manually.
iv) If it is frequently caused programming error this can be
identified in SM13 and inform the respective developer and
the user.
Types of Updates : V1 for critical updates,
V2 Non-critical updates.
205
Status of Update process is init,auto,run and error.
SM14 UPDATE ADMINISTRATION:
i) Whenever update assumes a problem or an error is occurred
or going to occur or database is inconsistent update server
becomes inactive.
ii) It is locked in syslog and also in sm21
iii) We need to identify the inconsistency and troubleshoot the
areas which are affected.
SM35 BATCH INPUT MONITOR

SM37 MONITOR BACKGROUND JOBS
i) The status of the background jobs i.e., scheduled, released ,
ready, active, finished, cancelled, double click on the job go
the job analysis.
ii) The following are the few reasons for job.
a) Authorizations are not assign to the user to run the
particular job.
b) File which is to be uploaded is not found.
c) If you are running BDC program from file to DB the file
structure is difference then job terminated.
d) Table space overflow.
e) Max extends reached.
iii) The job which is cannot be changed.
SM59 RFC CONNECTION
ii) It is used to communicate b/n one client to another client, one
system to another system or used to connect external
interfaces(legacy systems or parallel system.
iii) It is created in SM59, Go to SM59, Type of connection
R2,R3 , Description of the RFC, Technical Settings, Specify
like client, UID,PWD, Save the connection, Test the
connectivity and test the authorization.
iv) Types of RFC’s i) Synchronous ii) Asynchronous
iii)Transaction iv) Queed RFC
iv) Problems in RFC 1) Network problem. 2) Change in pwd
3) Change authorization in SAP as well as file systems.
4) Interface problem.
SCOT MONITOR SYSTEM CONNECTIVITY.
i) It is used to connect to exchange server SMTP, internet, fax,
pager and sms.
ii) Using iii rd party we will do the above.
iii) We monitor SCOT to find the configure services are active or
not.
iv) We can monitor request waiting to be processed in SC07.
206
SMLG MONITOR LOGON LOAD BALANCING.
This is used to optimize the resources of application server by creating
Logon groups and ensure that users are logon to their groups.
Advantages of logon load balancing are :

ii) Load balancing application servers.
iii) Effective utilization of buffers by logon groups and assigning
user GUI’s configured to that group.
iv) Effective utilization of memory and cpu.
v) Fail over [ when application server fail we can redirect that
group another application server ].
Configuring LLB:
i) Goto SMLG, define Groups , based on the functionality.
ii) Assign Instance to the logon group.
iii) Then SAVE, goto the GUI, logon groups, click on logon tab,
where we need to input 1)SAP <SID>. 2) Message server
host.
iv) Display the groups.
v) Select the group.
vi) Save and logon, make an entry in host file and SAP
MSTCP/3600 in service file.
DB01 DATABASE LOCKS

 ) to identify exclusive lockwait situations and to display
information about the:
 Lock holder
 Number of lock waiters
 Primary key locked
 If exclusive lockwait situations occur because a user holds the

lock too long, analyze the application and determine whether:
 More commits can be safely built into the application
 The lock period can be shortened by acquiring the lock
later
 If exclusive lockwait situations occur because many users want to
access the same record in high-volume processing, you can
schedule the jobs to be performed at different times.
DB02 DATABASE STATISTICS, MISSING INDEXES displays an overview

of the storage behavior of the database and the status of the database
objects.
 To perform a detailed analysis of storage related issues, use the

Tables and Indexes Monitor (transaction DB02).
 The Tables and Indexes Monitor has three levels of resolution:
207
Database level, Tablespace level, and the Tables and Indexes
level. In any one of the generated views, double-click the line of
an object to display the elements of the object. From the lowest
level, that is from the Tables and Indexes level, you can access a
history view for this object. Navigating to higher levels of
resolution works for most of the available views.
DB04 DATABASE MONITOR
DB12 DATABASE BACKUP LOGS
DB13 DATABASE CALENDER

DB24  DATABASE BASE OPERATION MONITOR provides you with
a central point from which you can check the status and logs of all
database operations, including backup monitoring, updates of the
optimizer statistics, and dba checks.
ST01 SPOOL TRACE

ST02 BUFFER TUNE TRACE
ST03 WORKLOAD ANALYSIS
 The load analysis of the system will monitor
here. The amt of time consumed by individual components like roll
time, wait time, CPU time, DB time. Etc., will be displayed for each
user, transaction, programs and for each processes. Good response
time of a dialog step will be in between 1 sec to 1.5 sec. (1 sec = 1000
m.s)
 Roll-in time and rollout time should be more
then 10% of the response time.
 Load, CPU, DB times should be more then 40%
of (RT – WT).
 If CPU time is more , look into ABAP programs
 The
ST04  DATABASE MONITOR displays an overview of the load and
configuration of the database management system and the
database.
ST05 SYSTEM PERFORMANCE

 It is used to trace the Run-Time problems.
ST06 OS MONITORING
 Operating performance.
 The CPU idle time always above 30%.
ST07 APPLICATION SYSTEM MONITOR:

 It is used to find the no. of users created in the
system.
208
 No. of Instances
 No. of users in R/3 system.
 It gives details about modules used and no. of
users using the modules.
 The main objective is to calculate the load on the
module.
 It helps “logon load balancing”.
The Database Alert Monitor (can be started from transaction RZ20) is a tool you can use
to monitor all the preset alerts for different areas of the database
Trans-
Title Menu Path
action
DB01 Analyze Exclusive Lockwaits Tools  Administration  Monitor 
Performance  Database  Exclusive lock
waits
DB02 Analyze Tables and Indexes Tools  CCMS  Configuration  Logon
groups
DB03 Parameter Changes in Database Tools  Administration  Monitor 
Performance  Database  Parameter
Changes
DB12 DB Backup Monitor Tools  CCMS  DB Administration 
Backup logs
DB13 DBA Planning Calendar Tools  CCMS  DB Administration  DBA
Planning Calendar
DB16 DB System Check: Monitor Tools  CCMS  DB Administration  DB
System Check  Display alerts
DB17 DB System Check: Tools  CCMS  DB Administration  DB
Configuration System Check  Configuration
DB21 DB Cost-Based Optimizer: Tools  CCMS  DB Administration  Cost-
Configuration based optimizer  Configuration.
DB24 Database Operations Monitor Tools  CCMS  DB Administration 
Operations monitor
RZ20 CCMS Monitoring Tools  CCMS  Control/Monitoring  Alert
monitor
SE12 ABAP/4 Dictionary Display Use transaction SE11
SE11 ABAP/4 Dictionary Display Tools  ABAP Workbench  Development 
ABAP Dictionary
209
Trans-
Title Menu Path
action
SM21 Online System Log Analysis Tools  Administration  Monitor  System
log. Or: Test  System log (from the ABAP/4
Development Workbench initial screen)
SM31 Maintain Table Views System  Services  Table maintenance 
Extended table maintenance
SM66 Systemwide Work Process Tools  CCMS  Control/Monitoring  All
Overview work processes
ST04 Select DB Activities Tools  Administration  Monitor 
Performance  Database  Activity
ST06 Operating System Monitor From the Performance Monitoring screen:
Operating system  Local  Activity
ST22 ABAP Dump Analysis Tools  ABAP Workbench  Test
Workbench  Dump Analysis
210
If you are going for interview, please remember the below questions and answers:
Question1. Something tell about your self.?
Ans: Start from your name, your qualification , your expertise in your sap ( if possible
activiites(kernal upgrade, support packs, spool administration, security , oracle dba etc.,)
and Netweaver(ep,pi,bi) and solution manager.
Question2: In your currect project what is the team size and what your activities?
Ans: Our Team size 4 or 5, your are team member, you are having r3(dev,qas,prd,snd)
four system or five systems landscape, activities you are in support, supporting for spool
administration, security, transports,health check(should remember 20 t-codes).
Question3: What is your RAM and Hard Disk of your R/3 systems?
Ans: For entire landscape(DEV, QAS,PRD etc.,) you will be having same RAM and
Hard Disk . RAM must above 20GB and Hard Disk 800GB on production 20GB or
30GB lesser in DEV and QAS. WHATEVER YOU SAY WITH 100%
CONFIDENCE....CONFIDENCE ONLY LEADS TO SUCCESS.
Question4: What are the solutions you give in your regulary Health Check?
Ans: You can explan entire your health check procedure and you can say that you will do
daily production health and check weakly all the systems check.
Example : if more background jobs fail then you coordinate the user by intimating about
the situation, if any tablespace problems you add the data files, if any more r/3 locks with
date you delete them by coordinating User and you will be having all the resolution in the
doc(health check) pl proceed as per the same.
Question5:Explain about your project?
Ans: You can say whether your project is 24/7(5 is team size), 24/5(4 is the team size).
Exaplain in detail about your project regarding activities, if you say that you r in
implementation say that you are installing the same, in supporting all the 14 activities in
sap basis you explain, upgrade means find difference between RESOURCE MINIMIZE
AND DOWNTIME MINIMIZE and you can say that you are very very good System
Copies(ABAP , Java, ABAP+JAVA), if you are not having this exposure you will not get
job. You can say that system copies you regularly do like 3 months once from
production to qas or qas to dev or dev to sandbox.
211
Some more important Questions:
1. How to de-activate the mass transports

2. How to build up clusters
4. How to roll back a note
5. What to do when the truck gets stuck while importing
6. With JSPM can we upgrade the kernel?
7. User complaining about the performance issue with one transaction code
8. How many application servers do you have?
9. What do you do when a background job is running for long time?
10. How many profiles does u have in your have as default?
11. Which backup you perform
12. How to apply support packs
13. How to you manage support pack
14. How to trace an activity in SAP system
15. If there is problem with the index and want to create a new index how do
You create an index
16. What activities do you perform in java stack?
17. How do you apply patches in java?
18. Where do you check the logs of java stacks if there is any problem?
19. How do you resize the data files step by step procedure?
20. Where do you check the alert logs files in oracle DBA?
21. Can we reset the password for a user from a database level?
22. How to de-active the mass transports
23. What is the difference between remote client copy and client export/import
24. One server process can hold how many users
25. How can we add one more server process?
26. Difference between client copy and export/ import
27. Did u perform any database recovery?
28. Which backup type you follow offline/online
29. Where do we create the logon groups in SAP?
30) What is DB REFRESH?
31) How to increase through table space administration
32) How to add network printers
33) What do you monitor in spool administration?
34) Memory parameters like (heap memory) where we should go (config /visual admin
tool)
35) Can we deploy or undeploy with JSPM
36) What task perform in in visual admin and how to open config tool
37)applying patches where should we check if it takes more time for what processing
going on ?
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239

SAP Full Notes Latest

Uploaded by

Copyright:

Available Formats

SAP Full Notes Latest

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP Full Notes Latest

Uploaded by

Copyright:

Available Formats

BUSINESS APPLICATION SOFTWARE FOR INTEGRATED SOLUTIONS

ERP: Enterprise Resource Planning.

What are the functionalities in a company?

A company is having different modules like

Integrationof all the modules done by ERP – SAP.

Basics to startup with BASIS Administartion

Software is often divided into two categories:

Computer Hardware devices

Motherboard – It is the main component inside of a computer designed using electronic

The three basic types of networks include:

Local Area Network:

Wide Area Network:

 A corporate network enables communication among various offices of the same

 An "internetwork", sometimes called a Wide Area Network (because of the wide

The 7 Layers of the OSI Model

Application (Layer 7) -This layer supports application and end-user processes.

A protocol is a set of rules that governs the communications between computers on a

Subnet Mask (netmask)

Netid and hostid conventions:

IP network ranges by class:

What is Database and uses:

1) Storing data in an organized way

Difference between i) On site and ii) Off site

What is Data Centre?

1) Windws 2) Unix 3) Linux 4) Solaris 5) AIX

1) Oracle 2) SQL server 3) DB2 4) Sybase 5) Informaix

High Availabiligty: for HDs

RAID: (Redundant Array of Independent Disks)

Storing the same data in different place on multiple hard disks.

SAN is also having mirroring. So there is no chance to lose of data.

5) Clustering (In case of Overload):-

5) Stand by servers (In case of Disaster Recovery)

In case of any disaster/calamatees…there may be chance of nor working of server. If

a) Log shipping :- It is time consuming.

b) Replication:- It will directly done at database level.

a) OFF line Backups: -

1) Rich set of modules.

To analyse the business requirements of an organization level depending

There are 2 types of Hardware sizing.

1) User based: In this again of 2 types i) Named users i) concurrent users.

Low Normal 0-480 dialog steps.

User communicating with system through application server & database.

* Who are logged into the system is called as Named users.

 SAPS are calculated based on the usage of processors.

SSCR: SAP Software Change Registration.

I) Our own font settings

Types of SAP GUI:

1. SAP GUI for Windows.

SAP GUI for JAVA: It is used only where java is supporting.

GUI initialization: GUI is initialized by the following INI files.

4. sapdoccd.ini: This files is initialized when the library is accessed. It

Note: All the work process runs with executable disp+work.exe

Ex: Roll memory, extended memory, heap memory

There are two types of buffer areas

1. User related buffer (user specific)

User buffers are nothing but user context.

Dialog : Dialog work processes fulfill all

5. Proper hardware is received according to H/W Sizing.

[Landscape : Arrangement of systems.]

There are 2 installation tools: