1

ADVANTAGES OF SAP:

1) platform/database independent:

O/S: DB:

Windows---------Microsoft Oracle------Oracle Corporation.

Hp-UNIX---------HP MS-SQL------Microsoft
Linux------suselinux, o.e.linux, r.h.l. DB2uDB------IBM
Sun-------Subsystems Informix
As/400, OS/400/mainframes---IBM

2) Enterprise Resource Planning

It is an ERP product. Complying all requirements of ERP standards.

3) Richest of products:

ECC5.0/6.0---------ERP product
CRM5.0-------------Customer Relationship Management
SRM5.0-------------Supplying Relationship Management
SCM5.0-------------Supply Chain Management

BI7.0-------------- --Business Intelligence

PI7.0---------------- Process Integration
EP7.0----------------Enterprise Portal.

4) Richest of modules:

FI ---------- Financial
SD ----------Sales and Distribution now order processing
CO-----------Controlling
MM-----------Material Management
RE-----------Real Estate
CS-----------customer service
HR-----------Human resource
PP-----------production process
PM----------project management

Banking, Insurance etc., at present we have 30 modules is there.

5) Industry specific solutions & add-ons

[Pharmacy, mining, textile, fabrications, utilities, oil and gas, dairy...]
6) Support all the languages i.e., 90,000 characters, it is Unicode languages
7) Single GUI to access all the components and products.
8) It is built in net weaver.

1
 2

9) It can be customizing by using OOP---> 'ABAP' & 'JAVA'.

10) It supports mobile Infrastructure.(SMS,PDA, LAPTOP..)

11) It supports 24*7*365 global support for production systems.

12) Continues improvement through bug fixes, enhancements, support packages,

paths& upgrades.

13) Communication with external systems i.e., SAPS & NON-SAP systems for data
transform.

14) It is a decision making system for analyzing the data (past current) to forecast

Feature planning resources.

15) Discussions, forums, online/offline messaging rooms, sharing documents.

16) Field level security. Authorization is defined at a granular level.

17) Integration between modules.

18) Software is consistence, reliable for the past 30 years and has a proven track
record.

BASIS Roles and Responsibilities:

Implementation & Upgrades:

1) Installation & Configuration of Solution Manager

(Solution Manager is a tool which is mandatory (compulsory) for Implementation

and
Upgrades)

It provides the following functionalities:

1) Generating license key (Solution Manager Key) which is mandatory for

installation.

2) Early watch alert.

3) Used as project management tool (to track the status of the project).
4) Used as a helpdesk system.

2
 3

5) Maintenance optimizer to download support packages.

6) Change (or) transport management system

7) Used to generate key.

a) Hardware sizing using sap proprietary tool.

(It is used to determine hardware resources like storage, CPU & high avilability,
memory).

b) Communicate with hardware vendors (seller)/suppliers for hardware.

Communicate with SAP for software.

c) Define a hardware compatibility report comprising with existing infrastructure.

d) Procuring (agent) hardware and software (customer).

e) Getting requirements on the customer or end-users. [The functionality the (PM &
Team) are expecting (PM & Team)]

f) Installation of software & post-installation activities.

g) Transport Management System.

h) Applying support packages support stacks, patches & notes

i) Perform kernel upgrade.

J) Installation library.

k) Transporting objects from one system to another system.

l) Preparing the system for GO-Live checks.

m) Create users and train the users (end-users).

n) Installation of GUI the end-user desktops.

o) Define security to protect sensitive data.

p) Allow the system for customizing & development

q) GO-LIVE & support.

3
 4

UPGRATED: o/s, D/B, H/W, R/3

1) Define upgrade strategies.

2) Run prepare, ICNU, R3UP
3) SPDD, SPAU (update repository)
4) Upgrade front-ends.

SECURITY:

1) Define security Implementation strategy.

2) define a role matrix as per SOX (sarbanes Oxley) (who does what).

3) Define roles, composite roles, and derived roles.

4) Handling missing Authorizations.

5) Transporting roles.

6) Roc companion and defining security object.

7) User creation, mass user creation & role Assignment.

Performance Tuning:

1. Identify the critical users, programs, transactions that are becoming bottle
neck on the system.
2. Identify memory, CPU, buffer & DB utilization.
3. Tracing the critical activities.
4. Identifying expensive SQL statements explain the path and tune them.
5. Define adequate primary & secondary indexes.

Support Phase:

It is used to support the SAP productive environment.

Some of the activities in the Support Phase are:
1. Monitoring the systems. [ Health Check]
2. Monitoring the Background process.
3. Monitoring Updates.
4. Interfaces.
5. Batch jobs.
6. Gateway
7. Spool (Print)
8. Create Printers.

4
 5

9. Logon load balancing.

10. Operation modes.
11. RFC connections.
12. Resolving end-user problems (Level 11) [Cannot login, cannot
print/upgrade]
13. Communication with SAP to resolve runtime issues ( ).
14. Applying Notes & Patches.
15. Opening connection to SAP for Remote login
16. Reset Password, Lock and Unlock Users.
17. Monitoring Archiving jobs.
18. Installing GUI’s to the Users.
19. Creating Users and Assigning Roles.
20. Working with SAP Router( All-Access control list).
21. Working with Helpdesk systems.
22. Performance Tuning ( ).
Database:

1. Capacity Planning [ size of the disk].M

Monitoring & Comparing the daily, weekly and monthly growth.
2. Monitoring Backup (Data & Log).
3. Scheduling the DB house keeping jobs.
4. Extend Tablespace by adding (or) resizing data files.
5. Handling DB related errors that start with Ora1631, 1632, 1653, 1654, 255,
272.
6. Monitoring Performance of database (Response time, CPU Memory & Buffer
utilization).
7. Establishing DR site.
8. Tuning expensive SQL statements.
9. System copies & DB refresh.

Net Weaver:

It is a new technology, platform which is used to accesalarate the business.

Net weaver does not contain any business. It is only catalist.

-----------------------------------------------------------------
| | EP 7.0 |
| P | people integration |
| | collaboration, knowledge mgt |
| | |
| -----------------------------------------------
| | master data management 5.5 |
| I | implementation integration |
| | BIW/BW/BI7.0,Knowledge mgt7.0 |
| |` |
| ----------------------------------------------

5
 6

| | XI3.0 / PI 7.0 |
| | process integration |
| P |integration broker/business focus |
| | mgt |
| -----------------------------------------------
| | |
| A | Application platform |
| | ABBP7.0 / JAVA7.0 |
| | |
|-----------------------------------------------------------------

Advantages of net weaver:

1) Communicate with any system (non-SAP & SAP system) if necessary user
adaptors.

2) It communicates with systems & process the messenger.

3) It gets the data from communication system and analyses it to define target.

4) The data can be displayed in the browser without any GUI from part of the world
(Internet is available

5) Irrespective of O/S, D/B, language & Application.

Network concepts:

_______
| |
| |
| |
| |
-----------
| |
| |
-----------
| |
-----------

Mirroring:
Mirroring is a process of writing into two hard disk simontanuasly.
One of the hard disk fail the other hard disk will be used. Mirroring is a feature
provide by hardware

6
 7

vendors and most of the severs provided by IBM,HP,DELL,SUN as default mirroring

for o/s. mirroring can not be used for database because it is expensive to by at the
rate of 1:2.
Ex: 1TB database require, 1TB database for measuring.
RAID: (Redundant Array of Independent Disk)

1) RAID is a method of protecting your data by combining or copying the space on

hard
disks to improve disk fault tolerance and/or data throughput.

2) These are many levels of RAID implementation, each of which works in a

different way and has different applications and benefits.

3) RAID isn't always redundant (another for fault tolerant) RAID level '0' (dis
striping
without parity) is not fault tolerant because it contains no redundant data to help
You re-create lost data, as you'll see in a minute.

4) A group of drivers can band together and, acting in concert, provide speed,
capacity
and fault tolerance.
This solution is called Redundant Array of Independent Disk (RAID).

5) Hardware RAID is still both more flexible and reliable than its software cousin.

6) These are vendors RAID levels like RAID1, RAID5 etc. RAID1 Referred as
mirroring.

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

| | | | | | | | | |
| | | | | | | | | |
----- ----- ----- ----- -----
| | | | | | | | | |
----- ----- ----- ----- -----

Here, if RAID5 is down immediately that data will store in remaining 4 RAID levels.

RAID1: _____ _____

| | | |
| | | |
| | | |
------- ------

7
 8

SAN: (Storage Area Network)

It is difficult to maintain various RAID'S for different applications.

Ex: mail server, web server, and time in/time out, HR systems

BACKUP:

Hard disks are backed up (Database) to a tape and the tapes are stored in
remote
location other than data.
MEMORY:
It is a temporary work area where the computations are performed no
calculation
will be performed on the hard disk the data which is going to be Updated is fetched
into
memory and calculations are carried out upon commit they are stored into disk.
The memory can be crased and leaked will not be used. Instead various memory
stick we
deferent slats are used.

CPU: (Central Processing Unit)

CPU provides processor to process the user request. right now we have 32
CPU's.
in order to secure CPU's and provide more processors as Dual CPU, Multi CPU,
CPU's
in again hardware vendors.

NIC: (Network Interface Card)

It is used to provide connectivity to other system in the network.

COMPUTER:
It is a device which consist of hard disk memory i.e., RAM, CPU, NIC, board
Audio/video graphic etc

SERVER:

It is high and computer which uses SCSI disks, with mirroring, RAID, and
multiple CPU’s to serve the client request.

CLUSTERING:

It is the process of providing two servers which has referred as Node A and Node B.
If node A fails node B gives life to the application.

8
 9

There are 2 types of clustering:

1) Node A
2) Node B
Node A and Node B as active & active
In this scenario both the nodes are active & active and server as load balance.
Node A & Node B has active & passive their servers as a failover.
Note: most of the above features are hardware vendor specific.

NIC: (Network Interface Card)

NIC will be assigned with IP addresses.

There are 2 types of IP addresses:

1) Static IP
2) Dynamic IP

1) Static IP: These IP's are assigned to the servers and mostly they are not changed.

2) Dynamic IP: these IP's are assigned to user desktops and may change for every 2
weeks.

PRIVATE IP'S AND PUBLIC IP'S:

Private IP: The IP address is which are used locally in the companies are referred
as Private IP. This IP addresses are used to communicate with in the LAN.
The recommended Private IP's starts with 172 and 10.
However 192 is also used but it is left for R&D.
127 is referred as loop back.

Public IP: This IP address is used to communicate with external world. Each
company has their own Public IP's to communicate externally.

NATTING: (Network Address Translation)

The request from Private IP goes to a proxy and uses Private IP to

communicate
with external systems.

TCP/IP: (Transmission Control Protocol)

It is set of rules which govern the transmission.

9
 10

NETWORK CABLE:

It is often referred as LAN cable which is used to communicate between the systems.

1) Straight cable
2) Cross cable.
It is known as CAT5 cable.

HUB:
It is a device which provides ports to communicate with various systems. But
the
data transmission is distributed.

SWITCH:
It is used to communicate between the systems. it is an intelligent HUB.
Which
is used to transfer the data uniformly.

ROUTER:
It is a device which is used to control the incoming and outgoing request of
the
company. it is a gateway which will be communicated by other systems in the world.

LAN: (local area network)

It is a group of systems which are in the same Ip range. It is also referred as
Intranet (with in the company).

WAN: (wide area network)

It is used to communicate between local area networks using routers.
Routers communicate through ISP (Internet Service Provider)

VPN: (virtual private network)

This is used to communicate remotely to the customer network using
security devices.
When VPN is establish a separate tunnel is opened between your desktop and
customer system.

LOG-IN TO THE NETWORK:

Companies provides user ID, password, domain name to log in to the

network. We need to change the password immediately.

SERVER:
A server accepts client requests and they are highly scalable and reliable.
It has its static IP.

10
 11

a) DOMAIN Server:

It is the server where your company domains is maintain it may consist of

the
following services.

1) DNS server: (domain name server)

It is used to name your domain so that all the systems in the LAN will
be
under one domain.

2) DHCP server: (dynamic host configuration protocol)

It provides ip addresses to the user desktops.

3) ADS server: (active directory server)

It is used to create users, administrate users and privileges.
b) MAIL server: (Microsoft exchange IBM lotus)

It is used to provide you an e-mail to communicate with users internally

and externally and most of the synarios the user id's are populated from ADS.

c) Web server:

It is used to provide the web services to access the company details over the
internet and intranet.

d) PRINT server:

It is the server which is used to control the entire printer in the company.

e) FILE server:
It is used to provide storage to all the users to store the information that
need to be protected or can be shared.

HOST NAME:

Hostname is the name of the machine and it is from the area of predefined namic

conversations. Hostname should 8 characters in length and describe the purpose of

it.

Each hostname should have a valid static IP address.

11
 12

32-bit servers:
It is architecture of the machine where each process can use 3GB of memory to
process the user request.

Note: Supply Chain Management (SCM) system and Netweaver2004 s sR2, live
cache 7 are not recommended to install on 32-bit machines.

64-bit server:

There is no restriction on memory allocation

Ex: SAP live cache database is installed on memory.

CLIENT:

Client is an application which will send the user request in the

understandable
format of the servers.
Ex: Microsoft Exchange Server requires Msoutlook, oracle, seible, sap requires their
own client application on the end user desktop.
---> The user desktop is loaded with client software i.e.
a front-end language + database connectivity.
---> Front-end languages, c, c++, java, vb and database clients are oracle client, ms-
sql,
sapdba client etc.

SERVER:
It is a backend to serve the user request. it accept the request in the native
form.

FILE SYSTEM:

The data is stored on the file system in terms of directories and files. When
there
are less no. of files it is very easy to access but when the file sizes grows or the
number grows it is very hurt to fetch and retrieve. The data is not stored in an
organized way; there is a possibility of duplication of records.

DATABASE:

The data is also stored on the file system but in an organized way to avoid
duplicates (primary key, foreign key) and fetch the data using indexes.

Note: other RDBMS rules are also applicable.

12
 13

OPERATING SYSTEM:

It is used to operate the computer peripherals and it provide an interface to

communicate with them.

There are many operating systems available

Windows, hp-UNIX, suse, Sunsolaries.

Disadvantages of CLIENT/SERVER ARCHITECHTURE:

1) Clients are highly loaded with front-end software and database client software.

2) For each request clients are directly hitting the database there by database is
congested and traffic is increased.

3) User request interpretation is performed at client level.

4) There is no queue mechanism to handle the user request.

5) There is common area where frequently accessed data is stored.

6) Database resources are (CPU, Memory) completely used utilize to serve the user
request.

Due to the above disadvantages there was a need deploy an addition layer
between client and server which will serve as shock observer to both client and
server.
APPLICATION SERVER: it is used for the following purpose.

1) It reduce load on the database

2) The user requests are queued installed of hitting the database directly.

3) The user requests are provided with dedicated resources on the all the
application server

4) Most frequently used data is buffered.

5) Database clients are installed on the application server their by reducing load on
the
clients.
----> SAP adapts 3tire architecture and it has its own usage for each layer.

13
 14

R/3 Architecture:

It comprise of 3 layers

1) Presentation layer
2) Application layer
3) Database layer
Note: These layers are also referred as server because each layer functions as a
server.
1) Presentation server:
This is the layer where end-users use to communicate with SAP systems.
There are various types of presentation servers and SAP refers then as SAPGUI.

There are 3 types of GUI's

1) SAPGUI for HTML (Internet Explorer)

2) SAPGUI for JAVA (installed on java supported)

3) SAPGUI for WINDOWS (windows operating machines)

ADVANTAGES OF SAP GUI:

1) It is ergonomically designed by changing colors, fonts etc.

2) It supports all the languages are installed (provided that the languages are
installed)

3) It is downward compatible to handle.

4) There will be only on GUI to handle all the SAP

applications(ERP,SRM,SCM,CRM,BI,PI etc)

5) Use function key F1 for Field Help.

6) Use function key F4 for to display the list of possible values.

7) You can define your own favorites which are available across the systems.

8) Frequently used inputs are stored as parameters so that there was no need to
enter the
inputs again and again.

GUI can be customizing according to customer requirement.

9) We can specify low speed connectivity to connect to the system using low
bandwidth.

14
 15

It will support GUI elements.

10) SAP provides SAP GUI Logon pad to restrict the editing by end users.

11) SAP GUI is used to use logon groups and servers to identify the least loaded
server in
the landscape.
12) Logon groups are used to identify the least loaded instance on that group.
Logon groups are used to identify least loaded server only in that queue.
We can download the output to a file, word, and spreadsheet.
Roles specific.
Use SAP Logon pad to the users.

GUI ADVANTAGES:

1) It is operating system and database independent.

2) You can define our startup transactions.

3) User menus can be role specific or we can use SAP Easy Access menu.

4) GUI can be customized according to customer requirement.

5) We can specify low speed connectivity to connect to the systems using low
bandwidth,
It will suppress GUI elements.

6) SAP provides SAPGUI logon pad to restrict the adding by end-users.

7) SAPGUI is used to use logon groups and servers to identify the least loaded server
in
the landscape.

8) Logon group are used to identify the least loaded instance on that group
Ex: US group has 5 servers, UK group has 5 servers, and AP has 5 servers.

9) Logon groups are used to identify least loaded server only in that group.

10) We can download the output to a file, word, excel sheet.

PRESENTATION SERVER:
Note: SAPlogon7.10 is the latest version.

GUI Server Elements:

15
 16

1) Command field:

It is used to user creation. Used to keying the transaction code to navigate to

the represent functionality to the one step.

2) Transaction:

It transaction is a abbreviated code assign to programs. These are used to

access the programs.

3) Logoff (icon) (shift + F3)

--> Back F3

-->cancel F12

-->checkboxes (allows multiple selections)

-->Radio buttons

-->windows generate the new session. we can create up to maximum of

6 sessions.

-->Basis is common foundation for the all SAP components

-->component is software it designed for separate module. Whatever

component you want you need to pay separately.

-->Basis is nothing but Application Server.

-->Sap web AS (basis+web)

-->mySap business suit is built on net weaver.

-->The purpose of mysap business is to increase the more business as

well as more functionalities.

--> ASAP-- accelerated SAP

Which will control your implementation
You can install any no. of GUI's there is no cost.

Command window options:

/O + command -> it open the new window.

/nex -----> exist window of the current user.

16
 17

/new -- change the existing screen

/n ----- go to home page.

/O - ask you the question.

----> Programs are stored in table in TADIR.

----> Transactions are stored in table TSTC

----> Tables are stored in DD02L

----> Clients are stored in table T000

----> Users are stored in table USR02

GUI INSTALLATION:

1) Single user
2) Mass user
a) 10 users
b) 100 users
c) 1000 users

There are various versions of SAPGUI:

1) 4.6C ----- 4.6D

2) 6.20 ----- 6.40
3) 7.00 ----- 7.10 --- Latest version
Types of SAPGUI

1) SAPGUI for windows

2) SAPGUI for JAVA
3) SAPGUI for HTML

1) SAPGUI for Windows: It is used to install on windows operating system.

90% of the users use SAPGUI for windows.

2) SAPGUI for JAVA: This is installed on the machines where java is installed. Mostly
this is used for non-windows. However it can be installed on windows also.
Ex: LINUX, UNIX, AIX, etc.
3) SAPGUI for HTML: It is used to access sap system using internet explorer.

17
 18

INSTALLATION:

----> Insert the DVD labeled with Presentation Server with version.
----> go to label.asc file, you will see SAP Presentation Server 6.40 or 7.00

SINGLE USER INSTALLATION:

Click on sapguisetup.exe and follow the instructions to install GUI

There are various options provided by GUI to support different components of sap.
Select the components what actually you want.

Mass user installation:

If you need to install GUI for more that one user copy the sapgui DVD into a common
folder (shared folder) and provide the path to the admins to install it on the end-
user desktops. Alternatively we can also write a batch file (.Bat extension) along
with Installation.

Documentation to Install SAPGUI7.10

1) Please click on the unclosed batch file

2) Click next.
3) Expand the sapgui for windows 7.10 to list the components.
4) Select the component to the install (whatever you want)
5) Click on Next to install GUI
6) GUI is installed successfully.

Unattended Installation:

Prepare a batch file to specify the inputs automatically and handover it to

system admin team a file as a logon script.
SMS Server:

It is a management server which is used to manage all the systems in the

company. It pushes the software (MS-word, WinZip, acrobat, sapgui, virus updates,
windows update) to all end-users.

SAPGUI installation server:

In order to maintain end-user desktops to manage SAPGUI and initialization

files SAPGUI used. it is provided by SAP and it is only applicable for windows . it is
used for uninstalled GUI, upgrade GUI and patch set Implementation.

18
 19

SAPGUI Initialization:

When SAPGUI initialized, it initializes the following files.

SAPGUI Initialization files:

1) saplogon.ini
2) sapmsg.ini
3) saprouter.ini
4) sapdoccd.ini

1) sap logon.ini:

It is used to provide logon entries to login to various systems. It is

initialized when user clicks on SAPGUI.

Note: saplogon.ini is used to copy massively to avoid creating GUI entries manually.

Note: while uninstalling ensure that logon.ini is backed up to a common or shared

folder.

2) sap msg.ini:

It is used to communicate with message sever to route the request to the

least loaded sever (when logon load balancing is configure).

3) sap route.ini:
It is used to communicate with SAP Servers across the routers.
4) sap doccd.ini:

It is initialized when SAP Documentation (sap library) is installed. It is used

to provide application context help of the screens.

PROBLEMS WITH SAPGUI:

Note: code page specify the types of languages installed on the systems. Default
code page 1100 supports English and German. This is also referred as non-
Unicode.
Unicode support around 90000 characters supporting all the languages. But we
need to install the respective language using transaction SMLT.
 SAP is SCP (Single Code Page) 1100.

1) Characters are not displayed properly.

2) GUI DDL are corrupted (dynamic link layer)
3) GUI is outdated (so you need to upgrade)
4) Logon.ini files are missing

19
 20

5) Cannot connect to my application server?

 Client does not exist (000,800) or client exist but it is block
 User id does not exist or user exists but it is locked.
 Password mismatch or caps lock
 Logon to the system using language i.e., not installed
 Host is not reachable i.e., application server might not be started.
 It is started but we are connecting to different instance number ( 2
digits number)
 The router entries are not valid
 Message server is not reachable to identify the least loaded server and
the request is timed out.
 Reasons could be :
SAPmsg.ini doesn’t exist
Message server port is blocked or not reachable.
6) How to disable editing SAPGUI by end-users?
R) Instead of providing SAPGUI, provide SAP logon pad.
7) Problems with special character sets?
R) e.g.: I am trying to login to a language (chainies) which is installed on the
system, but the characters are not displayed probably.
a) Go to visual settings and select the language which is logged on
b) Check whether GUI requires an update or upgrade.
8) Login to sapgui it is throwing an error program not found or
Dynpro_not_found?
R) When we apply patches the main screen is modify and GUI could not reach
the main page. This is due to problem in the patch application.

Note: In order to communicate with gui we need to use only users of type dialog
(it should not be system, communication, reference user)

9) Menus are not displayed properly, fields or buttons are missing or menus
behave erroratical?
R) Go to visual design and set the system to logon language

10) How to download GUI?

R) www.service.sap.com/swdc (software download center)
Note: network problems from GUI to application server prevents login
Ex: due to low bandwidth, select low speed connection to suppress GUI’s
Note: The application servers could not trace the problems in the TCP layer
therefore we need to check in SAPGUI level.

Note: SAPGUI disappears with out living any message probably this could be due
to virus are checking the setting of GUI.

Note: GUI icon on the desktop is missing, copy the GUI icon from the installation
directory and paste to the icon on the desktop.

20
 21

Note: GUI does not specify any error message increase the trace level in GUI and
check the flow of user request.
Note: Some of the icons are deactivated probably the user does not have
authorization
Note: Do not turn off sapgui crash in the registry

11) Problems with 7.10?

R) It is release recently and SAP is added rising the bugs reported by customer from
time to time. Each GUI version has its own version and patch levels.

12) Document the frequently occurred errors in to a knowledge based so that end-
users looking to KB (knowledge base) before the report an error.

13) Using sapgui icon not use the following

1) BEX (Business Explorer)
2) Sap scripts
3) Some parts of CRM.
R) While installing GUI you need to select various components to get the above
functionalities.
Ex: select BI; select GUI for development, CRM to get the above functionalities.
Note: ticked means problem on request.

APPLICATION SERVER:
1) Login scenario
2) Task scenario

LOGIN SCENARIO:

USER REQUEST WORKFLOW :

1) User request using SAPGUI to communicate with SAP application server

2) Dispatch on the application server receives the user request and keep them
in queue (dispatcher wait queue)
3) Based on the available free work process dispatcher allocates work process
to handle the user requests on FIFO (first in first out)
4) Work process as task handler to process the user request
5) Task handler consist of 3 interpreters:
a) Screen Interpreter:
It is used to interpret the screen in the user request
b) ABAP Interpreter:
It is used to interpret ABAP code in the user request
c) SQL Interpreter:
It is used to interpret SQL code and SQL statements
6) If the request is accessed earlier and the context is available in buffer. It is
fetched from or the request is saved from buffers.

21
 22

7) If the content is accessed for the first time , it is converted OPEN sql to
NATIVE SQL of the database using DB client (DBSL library)
8) The request goes to database and handover the task to database processes.
9) Database process handles the request and sends the response back to the
work process.
10) R/3 work process checks, if the response is eligible for buffering & store a
copy in R/3 buffer.
11)The response is re-interpreted to sent it back to the user
12)Buffer sending the response it is stored in user context
13)User context is only accessed by the user (himself) and it is available till the
user session. If user log off the user context is no more.

USER CONTEXT: It is a memory area it contains user related information such as

user authentication, authorization, parameters, earlier access screen.
User context remain s until user session. If the session is terminated or user
logged off user context will no more available.

TASK SCENARIO:

1) User request to display last week sales report.

2) User request goes to dispatcher and sits in queue
3) Dispatcher allocates work process based on FIFO and available work process.
4) Work process roll-in user context into task handler
5) Work process interprets the user request
6) Checks whether the user request response is available in R/3 buffer.
7) If available sends the response back to the user ( roll-out user context)
8) If the context is not available convert the request to native sql request and
communicate with database to process user request
9) Database sends the response back; eligible content is stored in R/3 buffers.
10)The response is send to the user before it roll-out to user context.

Roll-out:
The process of rolling out (save in the user related information) user
specific info into memory (user context) its termed as roll-out.

Roll-in:
The process of copying the user related information into work process
task handler (TSKH) is referred as roll-in.

OPEN SQL statement:

SAP uses OPEN SQL in ABAP programs. This is ensuring that the
programs are independent of database.

NATIVE SQL:

22
 23

This is the language used by database

Ex: oracle user’s pl/sql, Microsoft uses T-sql

The usage of open sql has the following advantages:

1) R/3 becomes database independent.

2) Optimal utilization of R/3 buffers avoids complete database times
3) Using native sql increases performance for the first records where as open
sql had bad response time initially but later considerably improved by using
R/3 buffers.
4) Open sql user R/3 locking mechanism to handle SAP transaction.

COMPONETS OF APPLICATION SERVER:

1) Dispatcher
2) Work process (TSKH)
3) Buffer area
4) DB client
5) User context
6) Dedicated memory of CPU for work process

INSTANCE:

1) own /shared CPU ------ sizing

2) own/shared memory ----- based on usage
3) own buffer -----------based on usage
4) dispatcher ---each instance has only one
5) work process and task handler -----depend upon configuration but not
exceed
6) DB client to interface with database ---75-150 MB of memory for 1 work
process

TYPES OF WORK PROCESSES:

Each instance can have one or more processes depending upon configuration

1) Dialog process
2) Background process
3) Update process
4) Spool process
5) Gateway process
6) Message process
7) Enqueue process

23
 24

1)Dialog process:

It is used to communicate with end-users. It is only the process which

handles end-users request. Each dialog process handles around 5-10 users and each
work process requires around 75-150 MB memory
75*90=6.75GB
150*90=13.50GB
The dialog work process is restricted by its runtime 600 seconds. If the process
complete could not his task with in 600 seconds, the user request will be timed out.
There should be atleast 2 dialog process for each instance.

2)Background process:
It is non-interactive process which is used to handle the jobs during off-peak
hour.
It does not require any user input and can run beyond 600 seconds. The 600 sec
limit is only for dialog work process. Dialog process defines Background jobs and
provides run time inputs has variants. There should be at least 2 background work
processes in the system. Background process runs various jobs during off-peak
hours for optimum utilization of system.
Ex: During day time load on the system will be more (dialog process)
During night time we create the load using background process.

3) Update process:
It is used to update the database from the temporary tables. There are 2
types of updates (normally 3 types V1, V2, V3).

V1--- handle high priorities jobs

V2---handle low priorities jobs
There should be atleast one V1 update for each instance.

4) Spool process:
It is used to print the documents. Dialog process defines the spool requests
that are to be printed. Spool process converts them into output specific format and
prints them in the background. As many spool processes can be configure
depending upon available resources.

5) Gateway process:
It is used to communicate between systems. There will be only Gateway for
each Instance. If Gateway is blocked, one could not communicate with the Instance.

Note: the above processes are instance specific.

24
 25

6) Message process:
Even though it is included as a processing the architecture. But its purpose is
not specific to an instance. There must be only one message server in the R/3
system. It is used for the following
a) It is ménages all the dispatches
b) It is used to identify the least loaded instance in the landscape.

7) Enqueue process:
It is used to lock and unlock SAP objects. The consistency in the system is
maintained by using this process. In most of the environments there will be only one
process but it can be increased based on the requirements. Ex: critical update
system.
Enqueue process is also referred as enqueue server and in ideal situations enqueue
and message will be installed on the same instance.
D V E B G S [M] ----INSTANCE: all are them installed in one instance
D V [E] B [M] G S:------- Central Instance.
Note: Instance is nothing but application server
CENTRAL INSTANCE:
The instance on which message server and enqueue server are installed is
known as Central Instance. If the load on the Central Instance increases, we will
deploy dialog instances.

DIALOG INSTANCE:
It is used to provide dialog processes to the user. This will be installed in
addition to Central Instance to handle the load. Depending upon the situation a
dialog instance can be called as a spool instance, background instance update
instance, Enqueue instance.

DATABASE INSTANCE:
It is the third layer in the architecture and it is used to store the data of the
customers. It has the following components,
1) database server
2) own process management
3) dedicated CPU and memory
4) Database buffers.
Database uses native SQL language and data is dependent on the database.

INSTANCE NUMBER:
Instance number is a two digit numbers that is 00 to 97. 98 and 99 are
reserved for routing purpose. Instance number will be used as a suffices to access
dispatchers, Gateway and Message Server.

Ex: if instance number is 55 (in between 00-97)

Dispatcher is --------3255

25
 26

Gateway is ----------3355
Message is ----------3655

Note: if an application server is capable of installing more than instance we can

install up to 98 instances to differentiate between instances, instance number is
used. However if there are installed on different physical machines some instance
number can be used.

Installation Prerequisites:
Before we start installation we need to ensure that installation
prerequisites are met. If these are not met the installation may be aborted,
abnormally.

1) Define the host name of the instance as per naming conventions of the
company.
Ex: ERP_US_DEV, BW_US_PRD, CRM_UK_QAS
2) Get the static IP address from the system admin team.
3) Download the installation guide from the website
www.service.sap.com/instguides .
4) Download known problems smp/notes using search criteria installation
problems in 4.7 of SAP.
5) Java runtime environment (JRE) -- SAP installation tools or program using
java. So, in order to execute these programs we need java runtime
environment.
6) Install java and setup the environment variables.

ENVIRONMENT VARIABLES:
These are used to set the run time environment of the installed components
Ex: java con be installed in any drive or any slice.
C: \program files\java\j2rel 4.2_10
/usr/java/j2rel .4.2_10
/opt/java/j2rel.4.2_10
How the installation tools do knows that java is installed on that drive.

We need to set 2 environment variables

1) HOME ENVIRONMENT: it is specify the directory where it is installed
2) EXCUTABLES PATH: specify the executable path.

SETTING ENVIRONMENT VARIABLES ON WINDOWS:

 Go to my computers and right click go to properties

26
 27

 Click on environment variables

 Define JAVA_HOME and specify the path where java is installed
 Setup the path in system variable to bin executable.
There are 2 types of environment variables.
1) user variable
2) system variables
User variable: these are used to setup environment for specific users.

System variables:. There are used to setup the environment for all the users who
logs into the system. These are also referred as global variables. Because they are
available globally to all the users.

On UNIX environments set the path using command set. Or set these environment
variables in bash profile. If you use set command it will be set only for the session
and for that user only.

 Install operating system and apply the patches

 Dump the software into a temp folder so that installation continues with out any
user inputs (non-interactive) more.
 The folder names should not consist of spaces, special characters.
 Ensure that hardware is procured as per hardware sizing reports.
 Ensure that software is procured and the right software is available verify each
DVD by getting the DVD number and verifying it on market place.
www.server.sap.com/swdc (software download)
 Ensure that nun of the ports are blocked.
 Use command net stat ( net stat –p) or ask the system administrator not to block
21212, 21213 these are used for SAP installation GUI and ensure that you are
not blocked ex: oracle port 1521 to 1529
 Ensure that the installation user ID is authorized to create users, groups, assign
roles and run the services.
 Ensure that internet connection is available to avoid run time issues and
communicate with counter parts.
 Prepare a check list from the documentation and follow the checklist during
installation.
 Ensure that you have valid s-sap user ID with authorization to create messages
to sap.
Note: until 4.7 enterprise edition we can install (or) out need to install central
instance separately. But from ECC5.0 sap provide a means to install both instances
together that is central system installation.

REQUIRED SOFTWARE:

 JAVA runtime environment

 Oracle database server and client
 Installation master to install sap

27
 28

 Kernel DVD for executables

 Exports DVD’s for database.

CENTRAL SYSTEM:
If Central Instance and Database Instance are install together on one
system it is referred as Central System.
If the install separately on deferent boxes it is referred as distributed
system installation. In larger companies distributed installation is chosen. While
installing central instance and Database Instance, most of the companies configure
high availability.

HIGH AVAILABILITY:
It is to ensure that the system is up and running. Even though one of the Instance is
down.

1) MSCS: (Microsoft clustering monitor programs)

It is provided by Microsoft to configure high availability on windows
environment.

2) HACMP: (High Availability Clustering Monitor Program)

It is provided by IBM, HP, SUN for non-windows environment i.e., UNIX
platforms.

Distributed System:

If Central Instance fails Database Instance gives live as well as Database Instance fail
Central Instance give live.

 Dump the software into a temp folder

 Go to installation master
 Click on SAPINST.exe on windows type ./sap inst on UNIX environments
 Up to 4.7 versions the installation tool is installed on programs or in home
directory of the user.
 But from ECC5.0 on windows installation can be directory initialized by using
SAPINST.exe.

INSTALLATION UP TO 4.7:

1. select the sap R/3 enterprise 4.71 for oracle default for direct installation
2. MSCS for node A and MSCS for node B are chosen to install high availability.

28
 29

3. Export ABAP system database/sap system database. It is used to setup a new

system based on the existing system. Example makes a copy of production to
development or test system.
4. specify the system ID
it should be a three character ID and it should be not be chosen from the list of
reserved key words like SAP, ALL, BIW ,CRM,SRM etc..
5. refer to installation guide for reserved key works
6. The SID should not start with numbers or special characters. Ex; 47A, 47#
It can contain number like S47, D47, D50, D60 But ensure that SID specified a
significance in the landscape .ex: first letter
signifies --- location, product, role in the landscape. Ex: US, UK, AP Regions.
BIW,CRM,SRM,EP,XI products BIW----B, CRM---C, SRM-----S, ECC--------E
development-----D, testing---------T, quality--------Q, sandbox---------S,
Production--------P.
7. select Central Instance click on Next
8. specify instance number
it is a number between 00—97 which is used to prefix the standard ports
9. Specify DB SID and HOST.
As central instance need to communicate with DB---- provide details about
DB.
DB SID may or may not be same as central instance (CI) SID.
10. Specify the installation to be local/domain/in a different domain.
a) Local -------- means it is a installed locally with local admin rights. Create
users,
Services, groups and run services.
b) Domain-------- it is installed in the domain.
We should get admin rights to create users, services, groups and run
services. If
Don’t get rights install locally and join the domain later.
c) Other domain--------mostly not choosed
11. Specify the amount of memory that is going to be used during Central instance
installation. By default it takes around 60% of physical memory.
12. Specify the host where transport directory is going to reside. This should be a
high available drive (probably SAN)
13. Specify database schema ID ---- SAPSID.

.DATABASE SHEMA:
It is used to identify database. It is in the naming convention SAP <SID>.
Specify the database home.
Note: it is possible to have multiple homes.

DATABASE CHARACTER SET:

It is used to set the type of characters supported by characters. By default it
is WE8DEC. it represent database code page. It is also specifies that it supports only
the languages which are supported by the characters.

29
 30

Ex: English and German are supported by default. If you need to have chainees , we
need to install a different character set.

 specify the password for SAP system administrator

 Specify the password fro SAP system service administrator. It is used to run
the services.
 Specify the CD (or) DVD path for kernel
 Specify the ports for the following services.
1. message server port-------- always 3600+instance number
2. gateway port----------------- 3300+instance number
3. dispatcher port----------------3200+instance number
4. dispatcher security port------- 4700+instance number
5. gateway security port -------- 4800+instance number
Then click on next to start the installation

DATABASE INSTANCE: select

It is used to install SAP application database

 specify SID (which is specified in central instance)

Standard installation (select)

System copy/migration
1) standard installation: it is an normal installation installed through exports
DVD’s
2) System copy/migration: it is installed to export dump.

 Select the option of install SAP system into a new database or install
(additional) SAP system an existing database.
 System copy/migration, it is available sense oracle 9i, it is gives to install
multiple components on one database.

MCOD: this feature is used to install multiple components on a single database.

It has following advantages.
1) Instead of having multiple servers. One server will be used to install the
entire database.
2) Single administration
3) Backup and maintenance is very easy
Disadvantage:
1) If the database server is down all the application will be down.

 specify database SID

 specify instance number
 specify local installation
 Allocate 40% of the RAM for database instance.
 Specify the host with transport directory
 Specify the database schema ID

30
 31

Character set, database home and path for the following directories
Sapark, sapbackup, saprebackup, sapcheck, saptrace, oraarch
There should not be any space between them.
 specify the same password for service administrator and system
administrator
 specify the kernel path
 specify the listen port (if multiple databases are installed)
 configure database with log files and data files
 Specify the path for origlog A mirrorlog B , origlog B mirrorlog A in two
different drives on one physical drive.
 Specify the export DVD’s path
 Specifies the location for database directories
 Specify DB code page as 1100
 (select) load the packages according to the size of their data files
 Specify the password for schema user (SAP SID) sys and system database
users.

INSTALLATION LOGS:
Go to installation HOME directory to check for the following
 SAPinst.log

Central Instance installation process:

 check for JRE

 check for ports
 check for ip address to HOST NAME (host entry)
 Check for user/groups and user-group assignment. If exists it will checks, if
not it will create.
 Extract the kernel executables (/usr/sap dir)
 Create services and run the services
 Define ports for the various services (dis-3200; meg server-3600; gateway-
3300)

Database Instance Installation process:

 check for JRE

 check IP address to HOSTNAME (host entry)
 check for user/groups and user-group assignment
 extract the kernel executable (/usr/sapdir)
 create database structure
While creating database it will get the information from DDLORA.TPL
TPL we used to create DB. It is embedded by and file
A command file drives the installation which is available in sapinst
directory with extension.cmd.
PHYSICAL INSTALLATION CHECK:

31
 32

 checks for the users SIDADM and sap.service.SID (used to run the services)
and execute
 Check for the group SAP_SID_globaladmin, SAP_SID_localadmin, and
SAP_localadmin.
 The 3 groups related groups
 Database related gropes
1) ora_DBA
2) ora_SID_DBA
3) ora_SID_OPER
 check services
1) saposcol
2) sap operating system currepted which is used to currept the os
resources that are required to start the instance , it is run by
sapservice_sid
 SAPOSCOL has its own interface to start and stop saposcol
 SAPSID_instancenumber: it is required for the instance if this services is
down
 SAPSID_00: if service is instant specific

Database related service:

1) Listener service: it accepts the calls from the users. If listener is down we can
not connect to the database. even through database is up and down

2) oracle service SID: it is used to communicate between the central instance

and database instance

Directories: start—run--\\willsys27
Use directory is created to work locally, shared mounts also created to access
this directory from other system.
1) saploc
2) sapmnt
These 2 directories are created to share the context across the landscape.
Database directories:
1) log files (redo log files)
Redo log files
Mirrlog A
Mirrlog B
Origlog A
Origlog B
Oraarch

Directories for backup, reorganization and traces.

Sapreorg
Sapcheck

32
 33

Saptrace
Sapbackup
Saparch

Database files
Sapdata1
Sapdata2
Sapdata3
Sapdata4

 What happens when the installation is restarted after a termination or restarted

during a power off?
It will start from the point where it is stopped

 How it is possible?
It reads from KEYDB.XML. it is used to document the steps of installation

Note: do not edit KEYDB.XML, if you do so we are installation is completely aborted.

If the prerequisites are not satisfied then the installation will be thrown into
error. Such as JAVA( in correct version ) , environment variables, corrupted
software (like missing DLL’s) host name, IP address , ports are blocked , database
out of space , no space in the disk , memory insufficient , power failure/abnormal
termination.

STARTING & STOPPING of SAP system:

Startup: the system can be started as startup service, but it is recommended to start
manually.

Shutdown: it is required to shutdown the instance in the following circumstances.

1) Scheduled downtime (like building maintenance, power maintenance etc…)
2) offline backup
3) Patch application on of DB and parameter changes in R/3.
4) Following the downtimes of dependency systems.

STARTUP PROCESS on windows:

Use MMC ----> select <SID> ------ Right click start on UNIX ----go to home directory of
<SID> ADM use script start sap.
When the central instance is started ----
It reads the
Startup parameters from start_DVEBMGS00_<hostname>
Global parameters from default.pfl and
Instance specific parameters from <SID>_DVEBMGS00_<hostname>
These profiles resides in usr\sap\sid\sys\profiles
When dialog instance is started ------

33
 34

It reads the
Startup parameters from start_DOl_<hostname>
Global parameters from default.pfl and
Instance specific parameters from <SID>_DO1_<hostname>

 What happens when the instance is started---- it reads from startup profile and
starts the following:

1) Startup database using command strdbs.cmd and writes a log file into
stderr(standard error) 0,1 (work directory)

2) Starts message server using executable msg_server.exe and writes a log file
into stderr 0,1,2 (work directory) and dev_ms

3) Starts dispatcher and work process executable disp_work.exe and writes a

log file into stderr 0,1,2 (work directory) and dev_dis,
dev_w0,w1,w2,w3,w4---------
4) Starts internet communication manager (ICM) using icman.exe and writes
log into work directory. The complete progress is written into sapstart.log
work directory resides in E:\ usr\sap\DEV\DVMBGSE00\work
executables resides in E:\usr\sap\DEV\sys\exe\run it is similar an UNIX
but .exe extension are not found.
Q) While starting the instance it failed with the following reasons or what are the
problems of the instance is not stored.

A) 1) Database might not be running:

Look into sap trace directory. D:\oracle\sap\trace\background\

alert_sid.log
the database started but could not establish connection to database.

(a) R3 Trans –d, it generates a terms. Log file in the directory where it is executed.
It gives you complete connectivity mechanism to database look for [0000] for
successful connectivity [0004],[0008],[0012] these errors specify there is a problem
in connecting to database . Get the error message like ora-1017, 12542, 12560 and
search for resolution in the market place.

(b) Error message says that tune is login problem check if you have changed
SAP<SID> password.

(c) Check listener control is started using command [Lsnrct1] and if started pointing
to the right port we can also start and stop listener service.
(d) Use command TNSPING <hostname> to resolve the host name.

Other possible reasons:

Database might be corrupted / not started / might be in no mount/mount modes.

34
 35

2) Message server could not be started

Analyze dev_ms log file in detail. We need to see CUSTOMER KEY and
message server port in the log file in the listen state.

(a) the port can be blocked to access

(b) change in the IP address (00) host name
(c) msg_server.exe is outdated (very rare, it is to exhibit the
executable replacement with new msg_server.exe)

3) Dispatcher could not be started: Analyze dev_disp log file in detail

(a) memory is not sufficient to start the instance
(b) dll’s are corrupted by virus
(c) change in hostname or IP address
(d) port 3200 [00 is instance num] is not accessed
(e) dispatcher is outdated [very rear, it is to exhibit the executable replacement
with new disp+work.exe]
(f) Configured with excessive parameter which could not allocate based on
available resources.
4) Work process not started.
(a) change in password of SAP<SID>
(b) no enough resources to start the process
(c) dll’s are corrupted.
5) Other errors: check the following services:

(a) saposcol to collect services

(b) SAP<SID>_00 to start instance
(c) Oracle service <SID> to check database connectivity.
(d) Oracle listener to communicate with database.

 Change in the password of service user SAP service <SID>, service SAP<SID>_00
is deleted.
 Use sapstartsrv.exe to create the service and an entry in MMC.
 if you could not trace the error we the parameter rdisp/trace=0,1,2,3,4,5 in
startup profile/default profile and start the instance to generate the log file .
 Ensure that log is switched to off, it not your system will be out of space.
 It writes log files into start 0, 1,2,3,4 & other developer traces.

POST INSTALLATION ACTIVITIES:

1) check SICK/SM28

2) Execute SE03/ SE06

3) Configure STMS

35
 36

4) Apply license SLICENSE

5) Create a super user and lock sap*, ddic in SU01

6) Configure sap library SR13

7) Install language if any SMLT

8) Configure profile generator SU25

9) Define a checklist for monitoring system health.

10) Configure work process memory & buffer parameters SU25

11)Document all the above activities.

SUPPORT PHASE:
It is use to support the existing projects companies like H.P, nestle, coke, G.E.
deployee 24*7*365 support to handle the run time issues which enables smooth
functioning of the system. They are various support levels.

LEVEL 1:
Support includes monitoring the health of the system. The Consultant
records the status of the system. [DB growth, job termination, performance, press
hold values etc. mostly it is a pro-active monitory. Create users change password
assign roles etc.

LEVEL 2:
Support Consultant resolve the issues which are routed escalated from level
one.
Escalation means it is the process of handling the issues. This could not be resolved
by lower level consultant with in time.
Ex: issues like DB growth. File system growth, programmatically errors,
performance bottleneck, verifying the check list routed from level one, getting
approval from BPO (Business Process own ) to assign/create/modify roles.

LEVEL 3: Performance Analysists

These are used to resolve the performance bottle necks & issues escalated
from level tow decision making to apply support packages patches & notes. Works
closely with data center & signals the downtime for critical activities, like hanging
memory, buffers, work process & other parameters.
Based on the data center size, number of servers, business activity the above level
may change
T1, T2, T3, T4
Tire 1,2,3,4
1234 (3 sap)

36
 37

 Production system downtime is costly. So sap immediately looks into the issues
by using remote connection.
 SAP does not priorities test, quality & development systems & customer should
not expect immediate response.
In the support phase consultant work with check lists as part of a daily
activity It may be daily/weekly/biweekly for test/ devpmt , quality systems but
production system it can be hourly on for every 2.4.8.90, 24 hours. Depending upon
the business.
Apart from the above check list, support consultant needs to handle run time / end
user problems.

END USER PROBLEMS:

1) User could not login.
2) user could not print
3) user could not schedule background jobs
4) user could not update
5) user could not access certain functionality
6) GUI related issues.

 There should be a mechanism to handle end user requests and track the status of
the request.
 There are various tools available in the market some of these are
1) Seibel
2) Remedy
3) SAP CRM
4) Synergy
User logs into the system or call, help desk to resolve his problem, based on his
employee ID the details are captured in the
Issue ID / case ID / Ticket / request ID
User key in description of the case along with the following statuses.

St.no severity description response time closure time

1. Low normal case 4 hrs 72hrs

2. Medium priority 2 hrs 48hrs
3. High high priority 1 hr 24hrs
4. Critical high priority 1 hr 4 hrs
5. Disaster 15 min 1 hr

 Where the request is created the status is

“New”, “assigned”, “work in progress”, “temp fix”, “pending”, “completed”
In a normal situation a consultant needs to resolve at least 6-8 tickets 1 day.

Communication in Supporting Phase:

End user communicates with basis team by using following l

37
 38

1) E-mail
2) Fax
3) A ticket from help desk
[Help desk is a system where all the end users will call for their runtime
issues, not only SAP, related to network, HR, financial, stationary. It can be
ticketing tool which categorizes the issues based on nature (type of activity)]
4) Verbal over the telephone :
It needs to be recorded and send an email for conformation.
5) Ticketing tool:
Users login their queries directly in the tool, it automatically router the
request to the respective consultant based on issues, severity and location
[TIDAL].

 Priority issues in an organization:

1) Local: GUI related + user specific
2) Medium: printer issues, update issues, background jog failure
3) High: common prints, a group of user’s problem, patches, support packages to
[instance down] for the bugs, notes...
4) Very high: payroll processing, shipping & delivers, grade processing
5) Disaster – System failure/down.
DIALOGWORK PROCESS:

Dialog process handles user requests. It is the only process which

communicates with users interactively. It is used to initialize other process like
update, spool and background process. Each dialog process can handle 5-10 users,
each work process requires around 75-150 mc of memory.

Dialog process can be increased based on available resources by using the

parameters
rdisp/ wp_no_dia=2
There should be at least 2 dialog work process for each instance dialog
process can be configured up to 90 instance in a reporting system, but optimally we
need to configure other process to handle spool, update and locking mechanism
ensure that the some of non dialog should always be lower than the total no.of
dialog process.

Work process runtime:

As the dialog process needs to serve 5-10 users its runtime needs to
be controlled if not the work process will be held by expensive users and the work
process cannot be used optimally use the parameter.
rdisp/max_wprun_time=600sec
Any task (job) which exceeds this time limit will be timed out.

SAP transaction:

38
 39

It is a group of transactions which consist of multiple LUW (Logical Unit of

Work).

LUW: it is a transaction where the data has to be committed completely or roll back.
It should not be hanging.

Each transaction (LUW) can consist of 1 or more steps.

Each step is handled by a dialog process.

Work process multiplexing:

The process of handling a single transaction by various dialog processes

depending upon the steps in the transaction. i.e., a dialog process is not restricted to
a user node transaction. (Or) a user can be served by multiple dialog workprocess
either to commit or rollback the transaction.

Dialog Process monitoring:

1) On windows these are monitor using MMC ( Microsoft management console)

2) Use command DBMON (an executable in run directory) on UNIX and

windows.

3) Use transaction SM50 and SM66 if the system is up and run.

Problems with Dialog Process:

1) User can not login to the system?

2) The user report is program timed out?
3) Work process running is oned 600 sec with status? Private mode
4) Work process does not have enough memory?
5) Work process is hanging in sleep mode (RFC+CPSC) mode?

1) User could not connect to instance [hour glass]

a) Queue is too long
R) Increase work process or increase instance.

2) The some of the dialog process are status stop or ended.

R) If you are able to login to the instance go to transaction SM50 and select the work
process and restart. Looking to developer traces.

 Sales order -------- customer / vendors.

Send to hp system at regular intervals ordering server/ work stations.
Vendor / customers sends in a predefine format (agree format)

39
 40

PRIV: (Private mode):

When the work process uses heap memory it is said to be in private mode.
When the work process in private mode it is dedicated to the user request and can
not be timed out by max work process run time. In this case, either the work
processes as to complete the task or the entire memory (assign to your work
process) is exasted. If the private mode is restricting the system accesses
(bottleneck) on the system use DPMON to kill the process.

1) The report is timed out and the dump is recorded in transaction ST22?

R) If the report is timed out, give to max work process runtime, there are 2
possibilities to execute the report

1) Schedule the report using the background process

2) Instance the time limit.

Alternatively we can ask developers to tune the programmers.

BACKGROUND WORK PROCESS:

It is used to schedule and run the programs in the background mode without
user interaction during off-peak hours.
Ex: Order processing, payroll run, delivery schedules, backup, patch applications
etc…

Background work process mechanism:

1) User logs into the system and desire to run a report (expensive or time
consuming)
2) As a report will be timed out user schedules to run in the background. Using
transaction SM36.

3) The background job is saved in to the table TBTCT and TBTCS.

4) Background scheduler runs in the fore ground (dialog) for every 60 sec. and read
the table TBTCT, TBTCS to schedule the background jobs. Or with a frequency that is
specified parameter rdisp/btc time and checks.

5) Based on the available background process the report is run in the unattended
mode.

6) In contrast to dialog background process handle the entire SAP transaction.

40
 41

SAP MSSY: Define background process.

 Go to transaction SM36

 Specify the job name

 Define the job name as per the naming conventions.

 Define the job class it can be A, B, Or C.

JOB CLASS:

There are 3 types of job classes. Which are specified to set the priority of a
job.

1) CLASS A:
It has high priority and these are process before the other classes. This class
required a background process of type A. (it is defined in operation modes). If type A
process not available, type A job will be waiting stage. Type a process can handle
only priority jobs such as payroll run, dunning report, account payables and account
receivables.

2) CLASS B:
It is used to schedule medium priority jobs, which runs periodically to collect
the performance data such as work load analysis, CPU utilization, database analysis,
buffers etc... There is no process dedicated to handle class B.

3) CLASS C: It handles low priority jobs. The default class is C.

 Status: It specifies the status of the job by default it will be scheduled.

 Target: It is specify to execute the job on that target system.

 Spool list recipient: It is used to specify the output recipient such as prints, e-
mail Id’s, PDL (public distribution list), and fax.

DEFINE THE STEP:

To specify what programs are report to be executed.

Click on step, the background job can be executed by using any one of the 3 steps.
1) ABAP program.
2) External commands.
3) External programs.

41
 42

1) ABAP programs:

 Click on ABAP program

 Specify the program name we need to define variant
 Specify the variant

Variant is a program selection criteria i.e. used by program at run time.

 Defining variant:

 Go to SA38 or SC38
 Specify the program name.
 Execute.
 Specify the inputs and save the inputs as variants.
 Use menu go to
 Variants
 Saves variants
 Specify the variant name and save the variant
 Go back to SM36
 Specify the program name and variant and save the background job.

 Specify the start condition:

Click on start condition the job can scheduled immediately

(Or) It later decision time
(Or) Specify periodically
(Or) Specify to trigger when job is completed
(Or) When even is completed
(Or) During operation modes.
(Or) Schedule using factory calendar.

 After job:
To specify the depending job which needs to trigger this job, the start up of
this job depends on the success (or) failure of the dependent jobs.
Ex: Invoice should be created once the purchase order create the system

 After operation modes:

This job will be triggered at operation mode search. Operation mode is used
to convert the dialog to background and background to dialog process. The two
toggling is performing during peak hours and off-peak hours.

Configuration operation mode:

 Go to RZ04
 Define off-peak mode

42
 43

 Specify variant
 Create peak-mode
 Click on instance operation mode
 Create instance by specifying startup profile and instance
profile and assign operation modes.

 Assigning timings to modes:

 Go to SM03
 Select normal operations
 Click
 Select assign and
 Select the interval and select mode.

The switching between processes performs without restarting the instance.

 After event:

The job will be triggered after event, events are SAP specific events to trigger some
activities only system. Go to transaction SM62 to maintain the elements.
Ex: TP (transport protocol), triggers RDDIMPDP jobs.

 Specify factory calendar:

To specify the job to run at beginning of the month or end of the month

Save the job: When the job is saving, the status will be released. The job can also be
defined by using external commands, external programs.

2) EXTERNAL COMMANDS

It is used to run the job by using OS commands or R/3 executables.

Ex: Backup, BRachive, BRtools, SAPDBA.

Some of jobs or BRconnect with parameters: -f cleanup these are house keeping jobs
which are scheduled in DB13. External command is define transaction command
CACL executed in SM49, define and modify in SM69.

3) EXTERNAL PROGRAMS:

This is used to trigger a program on the external systems. Specify the name of
the programs parameter and target host.
 Go to SM37
 Specify the user name or job name
 Specify the job status.

43
 44

 Job status:
 Schedule
 Release
 Ready
 Active
 Finished
 Canceled

1) Scheduled: The background job is defined without date & time. Still we are in
the status of schedule until we specify start date & time or trigger of than job,
event or at operation modes or during factory calendar. (Starting of the
month, ending of the month).
2) Released: The job is specified with date & time.

3) Ready: The job is ready to execute and schedule a peck only a job which are
in the ready stage, the job is in the ready stage longer time there is a
bottleneck of background process.
4) Active: The job is running.

5) Finished: The job is finished.

6) Canceled: The job is canceled or terminated.

 Viewing the output:

 Select the job

 Click on spool
 Click on type
 It will display output
Note: Some times job status will be finished, but actual job is not completed analyze
the job log for the errors.

Job monitoring:
 Go to SM37
 Specify user name
 Specify status
 Start date or
 Specify program name or job name
 Execute
 Jobs are displayed the list
 Specify the jobs which are canceled and double click on it.
 Go to job log to analyze the reason for failure

The following reasons because job failure we need to resolve the issue and restart
the job.

44
 45

1) Problems with external file

a) File is not found
b) File could not be opened
c) File consists of incorrect format
d) File permissions
e) File is in larger size then expected

Action: Inform the respective business process owner to communicate with

vendor/supplier/customer to resubmit the file. File may consist of order, invoice,
billing etc...

2) Database problems:

a) Ora-1631, 1632 max extents reached.

Increase extents using SAPDBA/BRtool

b) Ora-1653, 1654 table space out of space

Increase table space by adding or resizing table space

c) Ora-255, Ora-272 active stuck

Schedule BRacrhive or provide more space to OraArch directory.

3) RFC (Remote Function Call) communication between systems failed

a) The target system may not be available.

b) Target system is available but resource bottleneck
c) RFC user is locked or expired.

4) Interface Issues:

 Problem with conversion of data into sap system

 Monitor the interface and ensure that expected format is derived from the
interface.
 Interface can be time recorder, SMS, paging, FAX, SMTP (Simple mail transfer
protocol) these are configured in transaction SCOT.

5) Memory Issues:

If the memory is not sufficient the job can be terminated.

Increase the memory parameters based on available resources.

45
 46

6) Programmatically issues:

 Customized programs defined specifically.

 Customers may cause lot of problems due to inefficient coding, multiple looping
etc…
(OR) due to expensive SQL programming.
 In any of the above cases please look in to job log in SM37, ST22 and SM21.

After resolving the issue... selects the job.

Note: we can kill the job at any status i.e. Schedule, released, ready and active, but it
is not recommended to kill the active job. Especially the job will relate to update.

The job in ready state and could not be executed longer time we will move the job to
another server.

Select the job with ready states move to different server.

 House keeping jobs:

SAP defined certain house keeping jobs which are scheduled periodically to delete
lob files from database.
Ex: Background job logs, background jobs, which are completed or canceled.
Spool jobs completed or canceled.
Update job completed or canceled.

 Scheduling:
 Go to SM36
 Click on standard jobs
 Click on default scheduling

Some of the jobs are:

1) RSAL_BATCH_TOOL_DISPATCHING:
This is used for collecting the information and passing to CCMS. CCMS is used
for monitoring and razing alerts.
2) RSBPCOLL:
It is used to collect the information for job statistics.

3) RSCOLL 00:
It is used to collect the information for transaction ST03.

4) RSSNAPDL:

46
 47

It is used to delete old ABAP dumps from the table SNAP, based on age.

5) RSBDCREO:
It is used to delete batch input files based on date, time and age. Batch input
files are the files which are coming from external system to create sales orders,
purchase orders, invoices etc…

6) RSBTCDEL:
It is used to delete old background jobs based on username, start date, end
date, age, and end status.

7) RSM13002:
It is used to delete old update requests.

8) RSPO0041:
It is used to delete old spool requests.

Use SM65 to analyze the background processing on the system.

Third party tools:

SAP certifies third party tools to schedule background jobs. Companies like
HP, P&G, Kodak usages various job scheduling tools based on various conditions.
SM36 is not so user friendly to define the background jobs based on multiple
conditions. These multiple conditions are scripted using the tools like
1) MAESTRO from HP
2) SAP job schedule from SAP
3) TIDAL.

UPDATE WORK PROCESS:

Update processes are used to update the database these are 2 types of
updates
1) V1 update
2) V2 update

Note: V3 is used but it is reserved for SAP right now

1) V1 update: It is used to handle the updates with high priority or handles time
critical updates.
2) V2 update: These are used to update non critical updates.

Note: SAP standard programs are defined using V1 and V2 updates. If you want to
define our programs especially update we need to handle V1 and V2. However SAP
not recommended defining your own update programs. Because modularization will
be difficult.

47
 48

Update Mechanism:

 User logs into the system using dialog process.

 User creates or modifies a record.

 If the user is modifying a record the process communicate with enqueue process
to issue a lock on the record to update.

 Dialog processes commit the transaction and get the transaction ID and respond
back to the user.

 Dialog process updates asynchronously in to temp table.

 Update process reads the temporary tables and update the database
synchronously.

Pausing background job:

During update, patch application we need to stopping background process.
Use the reports
BTCTRNS1 to pause background jobs,
BTCTRNS2 to un-pause background jobs.

Need for Update process:

SAP is transaction based and each transaction can consist of one or more
steps.
Each step is handled by a dialog process. If there is an updating word in that step it
is recorded in the temporary tables. Up on from it all the steps update process is
initialize. If any one of the step fails the transaction is rolled back and no entries are
update in to database.

Temporary Tables:
These tables are used to store the data temporarily by dialog process update
process read the temp tables and inherits the locks and update the database.

1) VBHDR: It is used to store the header information.

Lock, username, transaction ID and update server.

2) VBDATA: It consists of the data to be update.

3) VBMOD: It consists of the update function modules to update the database.

4) VBERROR: It is used to store the error messages during the update.

48
 49

TYPES OF UPDATE:

1) Local update
2) Synchronous update
3) Asynchronous update

1) Local update: It is used to update the database directly. Even though it is not
recommended. NATIVE SQL statements update the database directly. (It is
not advised and recommended).
2) Synchronous update: Update process update the database synchronously
reading from temp tables.
3) Asynchronous update: Dialog process updates the temp tables
asynchronously (not sure about updating the database.. we may have
transaction ID but it may not be updated in database.)

Update Monitoring:
 Go to SM13
 To monitor the updates based on the following criteria.

1) V1 executed
2) V2 executed
3) V1, V2 executed.

 The update has the following statements:

1) INIT
2) RUN
3) AUTO
4) ERROR
1) INIT: The update is initializing.
2) RUN: The update is updating database.
3) ERROR: The update is thrown into error.
4) AUTO: If update is deactivated give to various problems, the update jobs are
thrown into error. Up on resolving the update issue the status error will
become as auto (i.e. update is automatically update the database without any
reinitialization.)

Handling Error Updates:

The update will be thrown in to error.

 The following:

1) While updating the database, there is no enough space in the database. Ora1653,
Ora6132, Ora255, Ora273.

2) Problems in the programs:

a) An exit is used BR customer enhanced the SAP standard program.

49
 50

b) There is a bugging the program.

c) Apply node or patch or support package.

3) Lock problems:
Update process inherits the locks from dialog. But in some scenarios
deadlocks occurs. During deadlock inform both the users and leave the decision to
the users. ( to approve to release the lock)

4) Update is deactivated:
If the system identifies any inconstancy. It will deactivate all the entire
update mechanism.

Entire Update Mechanism:

 Go to SM14
 And ensure that update is active
 If it is deactivated
 Go to system logs and
 ABAP dumps (ST22) and
 Analyze the reasons.
Update will be only deactivated during inconsistency, if the parameter
rdisp/vb_stop_active.

 Configuring updates: use parameter rdisp/wp_no_vb2 configuring V2 updates.

 Update reorganization:

1) Define the parameter:

rdisp/vbdelete to delete the update requests which are older than specified
age. Irrespective of status.

2) Use report RSM13002 to delete the old update requests which are
executed on the database.

4) rdisp/vbmail This is used to notify the administer if update error

occur.

Parameter set =1 mail is sent

Parameter set=0 no mail is set

Note: The update is thrown into error and the error is resolved but the update is still
with the status error. Select the update request and respect update (click on)

50
 51

Note: It is also possible that update will be thrown in to error and could not update
the database. In this scenario we may need to recreate the transaction again, i.e.
when the system is terminated abnormally the update request may be lost in the
transit. in this scenario the end users are required to recreate transaction again.

ENQUEUE PROCESS::

It is used to lock/unlock SAP objects during an update.

SAP defines Enqueue and dequeue mechanism in the update programs.

Enqueue process ensures the system consistency by locking and unlocking process
during update.

Enqueue process is configured by using the parameter rdisp/wp_no_enq.

By default there will be only one enqueue process defined in the central instance.

ENQUEUE MECHANISM:

 User communicates with dispatcher for an update

 Dispatcher assigns dialog process to update into temporary tables.

 To ensure that the record which is updated by dialog is not updated by any other
process, a lock needs to be obtaining on that record.

 Dialog process communicates with enqueue process and obtains the lock.

 Enqueue process receives the request and checks the enqueue table. If the lock is
available or it is issued to any other process. If the lock is not issued it tries into the
lock table and issued lock. (C.I)

 The request is coming from a dialog instance, dialog process communicates with
message server and message server in term communicates with enqueue process to
get the lock.

 The enqueue time on a central instance should not be more than 5 m.sec where
as in case of dialog instance it should not be more than 100 m.sec because it includes
RFC time and the time to communicate with message server.

51
 52

ENQUEUE Monitoring:
 Go to SM12
 Specify the username, client and
 Execute to display the list of lock objects as part of routine
maintenance. We need to ensure that none of the lock should
be older than 1 day.

Releasing lock: User complaints that he could not update a P.O.

 Go to SM12
 Check if the lock is obtained on the above transaction.
 Identify the user and go to SM04
 Check whether he has logged into system or not.
 If the user is logged in get the contact details (SU01) and contact him
(verbal cal or mail)

 User logs out of the system & the system (GUI) is connected to server
communicate with the user & get is approval to delete the session in SM0. ensure
that black & white (email) is obtain from the user.

ENQUEUE PROBLEMS:

1) The enqueue log table over flow

Fig:

The Enqueue Process stores logs into enqueue table which is configuring the
parameters. If resides on the shared memory of the instance where the enqueue
process is installed. Increase the enqueue table by 8 mb, 12 mb, and 16mb.

2) Enqueue waited response time is increasing enqueue response time should be

between 1 to 5 m.sec of a central instance. If the request is coming from the enqueue
response should not beyond 100m.sec. if the above trace hold values is crossed that
we need to consider increasing enqueue process.

3) DEAD LOCK

Apart of the transaction let us say ‘A’ is locked by user 1. Which is required
by user2? User 2 requires a part of the transaction let us say ‘B’ is locked by user1.
In this situation deadlock occurs. Inform the user to logout so that any of them are
continued transaction.

52
 53

Note: As a basis consultant do not suggest or recommended any of the users to

logout or release the locks without approval.

4) While updating a record dialog process gets the transaction ID from number
range buffer from the table NRIV. It is possible that there will be no numbers are
available in the buffer or NRIV interval is out of range. We need to concern
respective business process owners to get a separate range for that object in NRIV.

GATEWAY PROCESS:

It is used communicate between two instance or two systems using RFC

connections. Gateway uses 3300+ instance number & 4800+instance number secure
gateway. Gateway writes log file into DEV_RD. DEV_RFC gateway is monitor in
SMGW.

There will be only one gateway for each instance. Gateway trace can be
increasing by using SMGW.

Go to option---Trace gateway ----increase the trace.

Gateway Problems:

1) Gateway connection failed.

2) Partner not reached (the specialized system is not available or the gateway
ports specified or the instance number specified or gateway service.

MESSAGE WORK PROCESS:

1) It is used to manage all the dispatches

2) It is used to identify the least loaded dispatcher in an R/3 system (when logon
load balance is configured)

3) It is used to communicate with enqueue process to obtain the locks for a dialog
process when a request is coming from a dialog instance.

 Message server listens on port 3600

 Message server is monitoring through transaction SMMS.

 If message server is down the R/3 system is down, it is the first process to start
R/3 engine (R/3 level)

53
 54

 When the message server could not be reach ensure that port 3600 is not
blocked.

 If the message server is down, it could be due to changing the H/W. changing the
host name or changing the IP address etc…

 Message servers have it own parameters but there will be only message server in
the entire R/3 system.

SPOOL WORK PROCESS:

It will be only one process which is used to generate output request. Such as
printing documents sending out emails, printing checks etc…

Depending up on the available resources only instance we can configure as many

spool process as possible.

Mechanism:

 User log in to the system and creates print requests.

 The print requests are stored in TemSe.

 TemSe is temporary sequential objects that stores spool requests.

 Spool requests can be stored either in the OS or DB which is define by the

parameter rspo\store_location =‘G’ or ‘db’ here G means grounded.

‘G’ is file system which store the spool request in global directory.

‘DB’ – The spool requests are stored in the database. Database tables TSTO1, TSTO3
are used to store TemSe.

Advantage of choosing global:

 The printing will be faster because the OS files are printed specific and
communicates with host spooler to print the document.

Disadvantage:

 If the file size glows searching for the spool request at OS level consumes time.

 Special case to face the backup at OS level is required.

Advantage and disadvantage of Db:

54
 55

 It consumes more time when compare to global directory, but it overcomes by

indexing the entire spool at db level.

 No special case is requiring for backup.

Print generates/ output request:

Dialog /background generate spool request and stored it global directory (OS level)
or TSTO1 & TSTO3 (db level)

Spool Administration:

Go to SPAD to define output devices, Spool server, access methods & destination
host.

Access methods:

 It specifies how the spool process transfers (convents) into host spool system.

 Spool process uses access methods to converts spool request into output
requests.

 Spool process reads TSTO1 to identify the author name, printer name. no. of
copies, and the data to be printed from TSTO3.

 Spool process generates output requests based on access method.

1) LOCAL ACCESS METHOD:

If the spool process and the local host spooler reside on the same physical
machine it is strong as LAM (local access method)

 Access method L: It is used on UNIX systems and output requests are transfer to
local host spooler.

 Access method C: Access method C for the windows operating system. A spool
server transfer the output requests to NT print manager

L&C are called as local access methods

2) REMOTE ACCESS METHODS:

If the spool server and the host system spooler resides in different machine
then its as remote access method.

55
 56

 Access method U: It is used on UNIX machine to output the data to remote system
using protocol Baskely.

 Access method S: ‘S’ is used for windows to transfer the output data to a remote
system. Using SAP protocol ‘S’.

CONTAIN PRINTING:

It is used to print the document from the user desktop using protocol ‘f’.
The disadvantage of front end printing is background process is not possible and the
spool process is dedicated to the user request

Spool process are configured by rdisp\wp_no_spo

SPOOL SERVER:
The instance if at least one spool process is called as one spool server.

Logical spool server:

 These are defined logically for failed over and load balancing.

 Go to SPAD to define real spool server & logical spool servers.

 Logical spool server should be assign to at least one spool server.

 Go to spool ---- spool server--- create server name as ---logical spool1

Specify description, specify the type of server which is used, specify logical server
mapping.

 Select logical server--- click on allow load balancing provide mapping server &
alternate server and save it.

 Click on output devices to define output devices.

In order to define an output device, the device has to be recognized in SAP

system. If the device is available we can make use of it. If device is not available we
need to write SAP and get the device types.

Including device types:

Go to SPAD---go to utilities---device types---import

56
 57

 Click on new create prints ---- specify the output device as per naming
conventions. So that the prints can be easily identify by location and print purpose.

 Specify device type—device type specify the type of printer & manufacture

 Specify spool server ---it can be a real or logical spool server.

 Specify device class---device class specifies if it is a standard prints, fax etc…

 Specify authorization group—to protect the prints.

 Specify model, location and message.

 Click on Tab access method.

 specify the access method either ‘L’, ’C’, ’S’, ’U’, ’I’.

 Specify the printer name, if you use ‘U’.

 Specify the remote host.

Note: Do not access host spools for output status. If you do not select the process
goes for every minute to get the status from host spooler.

 Click on tab Output Attributes—to set the print cover and page setting.

 Click on tray info specify the tray info and save.

SPOOL MONITORING:

Go to SP01 to monitor the spool requests and output requests. Spool requests based
on request RW, client, and author.

The status of spool request:

1) ‘- ‘ : not at sent to spool system.

2) ‘+’ : spool requested being generated.

3) Waiting: Spool system has not yet processed O/P request not yet to host system.

4) In proc: The spool work process is formatting the out request for printing

57
 58

5) Printing: The host spool is printing the O/P request. The status of printing is
displayed for 1 min and queries the status from host.Depending up on host spool. It
will either completed or error.

6) Completed: The system set the status to complete once the request is printed or it
does not receive any status update from the host spooler then it.

7) Problem: The O/P is printed but with in complete character set or with minor
errors.

8) Error: It could not be printed due to network error.

STATUS WITH PROBLEMS:

In the spool request throws into problems it could be due to page settings or
due to character set problem. If the right character set like chines, Japanese is not
available write to SAP. After obtaining the character set from SAP import using
SPAD.

Go to SPAD--- utilities --- for character set --- import.

Error status:

It the status error is displayed it could be due to the following reasons.

1) The spool process could not get the right status.

2) The spool process waited for 600 sec and did not get the response from host
spooler and shows the status completed. But the user complains that the could not
generated the object.

3) The printer is not available.

4) The printer is available but due to technical reasons like out of paper, cartridge,
not available printing to a wring tray etc…

5) Print server which identifies output devices are not available.

6) Output device definition is changed.

 Exploring O/P devices:

O/P devices can be exported & imported from other system.

58
 59

 Spool Reorganization:

The spool requests needs to be clean from TemSe so that spool condition
never occurs.

Go to --- SPAD.---- Admin----delete old spool requests.

Alternatively gives predefined background jobs

 RSPO1041, RSPO0041 are scheduled periodically based on age and status.

Spool consistency checks:

Use report or standard background jobs RSPO1043, RSPO0043

There reports are used to checks the consistency and release spool locks.

 Alternatively use transaction SPAD

Go to admin---- consistency of spool request

 Use transaction SPIC SPO1 installation check – it is used to report a spool

problems if any.

Use transaction SP11, SP12 to work with Tem Se.

Problems:

1) The spool server can store up to 32000 spool requests in the temse. If it exceeds
spool overflow occurs. We can increase the tem se up to 99000 if it is goes beyond
spool conditions occurs and the user cannot generate any spool requests.

R) Move out old and aged spool requests to an archived system or scheduled
standard background jobs (RSPO1041, RSPO0041)

Storage_free_failed
Spool request can not be generated spool process consumes more and
hour glass occurs while printing a document.

Uses complaints that status is completed but the document is not printed.

 How many spool processes:

We can configure as many as spool process depending on the requirement,
but ensure that sum of run dialog is always less than sum of dialog.

59
 60

SAP uses default driver SWIN—saplpd (line print daemon)

 Printing no longer possible?

Check whether user has been access to the printers?

Check whether spool processes are configured?

Check the spool status in SM50

Check the temse size (i.e. SM21 AND ST22 specifies the error)

External Connection:

Go to SCOT
SAP connects to define paging server, SMS server, mail server, fax server etc…

While define the above interfaces ensure that device is working properly.

---Go to SCOT---- create---- define the node (fax1)---define the description---

continue ---- specify node (RFC/ HTTP NODE) If it is fax, email for RFC specify HTTP
node for SMS--- define RFC destination and specifies it---- select the service as
fax/internet/R/3/prints etc…

Select the out put format i.e. smart forms, list, PDF, txt.

 Go to SCOT or SOST to monitor the messages that are triggered from sap system.

Ex: A tax msg is printout but it doesn’t reach the customer. It can be thrown in to an
error, canceled or waiting.

 Go to SOST specify the send date & time and execute to display the status of msgs,

If the msg could not be send, select the msg repeat send in send process menu.

We can also display the transaction history and trace the msg.

MANAGING INSTANCE:

Instance is nothing but which provides memory, buffers, and processes to handle
the uses requests. We need to control the above parameters based on our
requirement & resources.
The Instance is started by reading parameters from startup profile. And default
profile and instance specific parameters from instance profile.

60
 61

Ex: I want to increase dialog, update, and background processes

A profile resides in \\usr\sap\<SID>\sys\profile directory. We can change

manually at OS level using text editor, but you are not advised about any
parameters. So sap recommends not to change parameters from os level unless it is
recommended… to trouble shoot the system startup problems.

Profile parameters management:

As it is not advise to maintain parameters at OS level.. Use transaction RZ10 to

manage parameters through SPAGUI. But the buffers are located as OS level. In
order to maintain at DB level Import them into database.

Go to RZ10—menu utilities--- import profiles--- of active severs now the profiles are
copied to d/b from OS level

There are three ways to manage profile

1) Administration data
2) Basis maintenance
3) Extended maintenance.

1) Administration data: In most of the scenarios this is untouched unless there is

change in file system.

2) Basic maintenance: It is used by administrator who does not have much

knowledge on sap. We can change parameters without any knowledge on the name
of parameters.
Ex: rdisp/wp_no_dia

3) Extended maintenance: It is used by basis consultants who can work based on

parameters.
---go to RZ10
---- select extended maintenance
---- select instance profile for instance specific, changes & default profile for all the
transaction
-----click on new parameter
---login/system—client
--copy—save—active

The new version of profile is generated at OS level and existing profiles are renamed
as .bak

These profiles will be effective only after restarting the instance

Most of the profiles are static and requires instance restart.

61
 62

These are some dynamic parameters which can be changed in rz11 which are
identified by change value.

Go to RZ11
Specify the parameter
Click on change and set the value
These parameters lost the changes once the system is restarted. So you need to
change in rz10 and rz11 to remain the effect after restarting the server.
Requirement for parameter changes:

 For increase the dialog process, in the ratio of work process to users is not met.

 Background jobs are in ready state for longer time.

 Output request could not be generated due to lock of spool process.

 Buffer swaps occurred in ST02.

 Memory bottle neck forces you to increase memory parameters.

 Security parameters like password length, number of characters in password,

special characters, numbers etc…

 To control the user sessions i.e. user can not login multiple times, to end the
session if incorrect password is given.

OPERATION MODES:

Operation modes are used to dynamically switch between dialog to

background and background to dialog.

Prerequisites:

You need to import profiles in to database using RZ10.

Defining operation modes:

 Go to RZ04

 Click on create to create operation modes.

 Choose the sap variant.

 Create new Instance.

62
 63

 Specify host name.

 Specify instance number

 Specify start up profile.

 Specify instance profile.

 Click on save.

While saving the instance it will form to allocate operation modes.

 Go to SM63

We can maintained time intervals of 15, 30, and 60mins

 Select the interval

 Assign operation mode.

 Again select interval

 Assign peak mode until complete day

 Save.

 RZ03 it is used to stop the instance.

 Select the instance.

 Stop the instance from control menu

And switch the operation mode dynamically.

Note: Restrict RZ03 in the production system.

 When the operation modes are switch it is logged as an event in system logs
SM21.

LOGON GROUPS:

There are used to assign the user request to the least loaded dispatcher. So
that users wait time is reduced. Log on groups are defined and assigned to instances.
User’s logon to logon group, the group identifies the least load dispatcher and

63
 64

assigns the request total dispatcher. Message Server place on important roll in log
on groups.

Defining Logon Groups:

 Go to SMLG

 Click on create to create logon group ex: sales group, material groups
 Save.

 Go to user GUI

 Select groups

 Specify system ID

 Message server – willsys18

 Click on generate list to display logon groups.

 Select the group

 Add and logon

In order to do this on various users, copy SAPMIG.ini and an entry in etc\host and
services to point message server.

 SAPMSSID 3600/tec SAP message server port.

 We need to provide this entry to communicate with message server.

Mechanism:

1) User GUI’s are updated with logon.ini, sapmsg.ini, host file and services file.

2) User selects groups and clicks on logon.

3) As you’re trying to communicate with logon group message server is initializing

through sapmsg.ini.

4) Message server goes to SMLG and based on the group identifies the instances and
communicate with all the dispatches and identify the favorite server and route the
request to the dispatcher.

 Go to SMLG

64
 65

 Go to system diagnosis ----from goto menu----message server status area

To identify the favorite server of message server.

 Goto (menu)—load distribution ---- identify the instance and there response
time.

SERVER GROUPS:

Server groups are used the schedule background jobs either in the remote
system or in the existing system. It is similar to logon load balancing, but used for
RFC communication. While differing server groups we can specify max no. of work
processes, max no. of logon, queue length and wait time.

Data transfer:

In order to transfer the data from 1 system to another system, the system
needs to be communicated using a trusted mechanism.

RFC: (Remote Function Call)

RFC provides a trusted mechanism to communicate between two systems.

RFC’s are defining it transaction SM59.

Go to SM59----- to define the RFC connections.

1) R/2 connections:

There are used to communicate with R/2 machine and the connection type is 2.

2) R/3 connections:

These are used to communicate between R/3 systems like B/W, CRM, and ERP
connection type is 3.

3) HTTP connections: to communicate with XI engine.

4) TCP/IP connections:

Used to communicate the SLD (system landscape directory), JAVA engine,

LDAP (lightweight directory access protocol) etc…

Define RFC connection:

 Go to SM59

65
 66

 Click on create
 Specify the RFC destination name SAPERP_TO_LDAP based on naming
conjunction.
 Specify connection type 3
 Specify the description
 Click on technical settings
 Specify the target host, system number
 Specify the gateway host and gateway service
 Click on logon security
 Specify logon client, user, password
 Save and click on test connection

Note: Do not specify a dialog user in RFC connection specify communication users.

TYPES OF RFC TRANSACTIONS:

1) Synchronous RFC connection:

It is used to communicate with the target system and waits for the response
unit. it is available some times the work process may goes into RFC+CPIC mode 0r
sleep mode.

2) Asynchronous RFC connection:

It is used to communicate with target systems and does not wait for any
acknowledgement. It is not so reliable.

3) Transaction RFC connection:

It is a type of ARFC but a transaction ID generated for each transaction. The

request goes to be target system based on transaction ID. It target system is not
available the work process comes back to the source system with out performing
the work based on transaction ID a background job RSARFCSE is scheduled for
every 60sec and ensure the transaction ID is updated on the target system (perform
work based on transaction ID).

4) Queued RFC’s:

It is a type of TRFC but ensures that the transactions are reached the target
system based on queue (FIFO).
1) LSMW: (Legacy System Migration Workbench)

It is used to transfer the legacy systems data to R/3 system. This is used only
once during the implementation. (1 time data transfer). Functional consultants with

66
 67

the help of business process owners identify the data to be transfer. (Identify the
data, mapping the data, parsing the data, truncating and padding)
 Identify data
 Custom data/employee/asser/vendars/suppliers

2) Batch Input Monitoring (SM35) or SCAT:

It is used to upload the data by using sessions. A session created to

record the execution of a transaction and that session is executed periodically
Ex: HR department submits used list to basis team.

SCAT:

 Create the session

 Record the session
 And execute the session.
Create recording for transaction SU01.
Take the input list and feed input in the same format for 200 users.

Batch Data Communication: (BDC)

If the functionality could not met using LSMW or SM35 developers develop
BDC programs using function modules WS_UPLOAD, WS_DOWNLOAD, GUI_UPLOAD,
and GUI_DOWNLOAD. These are used for periodic or one time data transfer.

TRANSACTION RFC (TRFC) : (SM58)

It is used to monitor the data flow based on transaction ID. It is used in

central user administration using the mechanism “ALE” (application link enabling)

ALE: It is used to communicate between to loosely coupled system (easy

understandable format) i.e. sap to sap.

 The systems are identifying by using logical system names which are defining
SALE.

 CUA uses ALE to transfer data between two systems.

 Go to SALE
 Define sending and receiving systems
 And assign them to clients
 Go to BD64

67
 68

 Create model view

 Assign BAPI ( business application programming interface)
 And assign the sender/receiver
 Define the interface

EDI: (Electronic Data Interface)

To transfer the data between SAP and non-SAP systems.

IDOC: Intermediate document will be defined by implementers to define the

document which is understandable by both sender and the receiver.

 Transaction IDOC is used to check the programs and consistency between the
profiles.

IDOC monitoring WE05:

 Go to WE05
 Specify the time or the IDOC number
 And execute.

There are various statuses for the IDOC.

 51 -- Application document for the IDOC.

 53 -- IDOC posted.

 Out bound IDOC status is 1 to 40 while inbound IDOC begins with 50.

 While monitoring IDOC’s customers provide the list of errors and the steps to
resolving the steps to resolving errors.
QRFC monitoring: (inbound queue)

It is used to monitor

Go to SMQR, it is a QRFC monitor to register the queues

Use SMQ1 for outbound queues

Use SMQ2 for inbound queues.

68
 69

1) Create RFC (OB) I 1) create RFC (IB)

2) Receive (IB) D 2) Send quotation (OB)

3) Create PO (OB) O 3) Receive PO (IB)

4) Receive invoice (IB) C 4) Generate invoice (OB)

5) Receive shipping (IB) 5) Generate shipping (OB)

 Inbound is monitor in SMQ2

 Outbound is monitor in SMQ1

 QRFC is monitor in SMQR.

Monitoring:

Monitoring the system for health check (preventive) to identify the runtime
issues like file system or database abnormal system, excessive paging, memory
utilization etc…

Each company has their own check list to monitor the systems, interfaces,
connectors etc…
 Monitor the work process SM50

Go to SM50 or SM66

It list the following

It specifies the serial number of work process, type of work process (dia, bec, upd,
pic, status…)

Process ID which represents a process at OS level.

They are represented as disp+work (NT) or DW in (UNIX)

ps–ef |grep DW *

On windows use task manages to display the list of process ID.

Map corresponding process ID at OS level with respective to R/3 work process.

69
 70

Status: Running, waiting, holding, ended/stopped/terminated

Running: The process is running a job or handling a request or working to update,

print, getting lock or waiting for resource on the target system.

Waiting: The process is waiting to serve the user requests.

Holding: The process is holding by user request (expensive program, time

consuming program, private mode, sleep mode, RFC + pic mode…

Ended/stopped: The process is ended or stopped or terminated due to time out c

connectivity failure to database, or it is killed abruptly.. Or terminated due to
programmatic errors.

Reasons for the status:

Some times the work process is ended status or running or hold. The various
reasons are display for the status.

Enqueue: waiting for the response to enqueue request

Priv:

Sleep: cause of a resource of bottle neck. The process is communicated with either
SAP or non sap. The resources on a target system are not available to process the
uses request for data transfer

NUM: work process is waiting for a transaction id from the numbering stage. If its
wait for longer time their may be queue in numbering table or numbers are not
available in buffer.

Start: It can be either YES or NO. if a work process is terminated or abrupt by a

program. If you wanted to know the reason for termination, the start mode set yes,
the work process is restarted immediately after termination and we do not have
option to identify the reason for termination. When there are abnormal
terminations in column Err.

Error: Err indicates the number of times work process terminated.

SEM: (semaphore) It specify the number of semaphore which blocks at OS level.

There are 55 semaphores which can block the WP. (Semaphore is related to OS)

CPU: It determine the CPU time utilized by the WP

Time: Time consumed by the individual.

70
 71

Report: Specify the name of the report or program reach the WP.
CL: client specifies the client.

User: name of the user

Action: It specify the type of action that is sequential read, direct read, physical
read, insert, commit, Rollin, rollout.

Table: name of the table. When the time is consumed by particular WP, select the
record to display the activity performed by the WP. We can display the select
statement, type db action, memory utilize based on this we conclude the following.

1) The memory i.e. private memory utilization if we user private memory very soon
it is going to be bottle neck.

2) Ensure that SQL statements coming from customers (starts with ‘Y’ and ‘Z’ are
not using select *)

We can also kill the expensive processes by using ‘cancel with core’ or ‘cancel
without core’

Before killing the WP, select the WP go to user info get the telephone num & inform
the user about the killing the session.

Use SM66 to display the global work process overview. I.e. the work process is
belonging to all the instances.

Heap memory is nothing but private memory.

Go to SM66 to display the work process based on the status, these hold values like
response time, schedule time and transaction use, report and based on client , user
etc…

It displays the transaction used and started time.

Scenario-1:

q) All the work processes are in status running

Work processes are not enough

Work process congestion
Queue time increases
Check time in how long they are running.

71
 72

SM04 and AL08:

SM04 is used to display active user list based on instance. We can identify the
terminal, memory used by the user. (Go to terminal)
Based on the requirement we may need to logoff the user from the session.

Do not delete the lock instead delete the session as part of monitoring we will
monitor the no. of results lock on the system (instance)

We log into AL08 to identify the user in all instances. AL08 provides only snap shot
information.

SM51:

It is used to display active servers and the type of process config on the
instance. It is used to check the release note

Click on release note.

It displays the kernel version, support level, kernel patch.
Select the instance ----- go to process
Process SM50, user SM04, SNC status SM21
As part of check list we need to check all the available instances are active.
If any one of the instance is down escalate the issue to data center or if you have the
access resolve using startup problems.

Using SM51 we can log into other instance by double clicking on the instance name.
SM21: SYSTEM LOG

It is used to write all the important logs. Ex: work process startup, WP shut down

It writes operation mode switch, log all oracle related errors (ora-1631,1632…),
program timed out.

As part of the check list we need to identify the issues which are colored in red.

SM22: ABAP DUMPS.

SAP has everything built with programs if any one of the program could not be
executed .it is thrown into error.

ABAP dumps are stored into SNAP table in order to delete dumps based on age
RSSNAPDL.

72
 73

SOME OF THE ERRORS:

1) The program is standout due to expensive reports or long running programs.

2) If the program is timed out due to excessive memory i.e. each process can trace
around 2GB. If it seem beyond terminate it and records in ST22.

3) The program can be terminated due to bug in a prog (excessive conditions,

multiple loops etc...)

4) The programs are terminated due to mismatch of kernel executives (OS, D/B, and
R/3)

The above problems can be resolved b applying patches, support packages, tuning
the programs (developers), creating indexes, running standard background jobs
periodically, the other ABAP dumps could be

1) SPOOL related errors.

2) Update errors
3) DBIF_SQL errors (database interface)
4) Errors starting with ora ora—1631,1632,1633,1634

SM63 RZ04 SM66 SM04/AL08 ST11 AL11 SM35 SM12

SM13/SM21 SM14/SM22 SP01 SP12 WE05 SMQ1
SMQ2 SMQR SM59 SM58
SM51: Check if all the servers are active. If any server is not active report in the
excel sheet.

SM50: Check the status of all process and report if any abnormalities are found i.e.
work process that are running for longer time.

AL08: Active uses of all the instances.

SM04: Active users of that entire particular instance.

SP01: Identify the spool requests that are not converted to output requests, we may
need to report based on the status (problem, error, +, -, waiting)

SM37: Identify the background jobs that are running in the background mode with
status (cancelled and ready)

SM12: Check for long pending locks based on time.

73
 74

SM13: Check for long pending updates based on time and users.

SM14: Check the update mechanism is active or not

SM21: Include the logs that are with errors.

SM58: TRFC checks for transaction ID that is pending….

SM59: Check the connectivity if critical connections like BIW/CRM

DB02: The table space with above 90% is critical check for missing indexes and
report if any.

ST03: Check the response time of if dialog proves…

ST02: Check for buffers and report swaps if any (swaps are displayed in red color)

ST02: Check for usage of heap memory

ST04: Specify the database buffers his ratio ensures that it always greater that 94%.

ST06: Check the CPU idle time. It should be always greater that 30%

ST07: Check the work process / users/instances inform if the distribution is odd.

SM35: Check for the status of batch input programs logs select the job and click on
lob

Disk quotas:

Drive total used free

C:
D:
E:
F:
G:
/root
/user
/oracle
/oraarch
/tmp
OS version ------------- patch version -----------

DB version------------ patch version-------------

74
 75

R/3 version-------------component version--------

Web as release---------

Kernel release & patch level

Basis
ABAP
APPL
HR

WE05-------- Check for pending IDOCS

SMQ1-------- Check for outbound queue.
SMQ2-------- Check for inbound queue
SMQR------- Check for QRFC registration.

SM37: Check the standard background jobs

DB12: Check the status of backup (db and log)

DB24: Check the status of all the operations of database.

CCMS: (Computing Center Monitoring System)

Go to RZ20

It displays CCMS monitor sets. CCMS is used to create out own customizes alert
monitoring system. But mostly we will try to adopt the SAP standards

Go to extras

Active maintenance function on us can create our own monitors. Copy monitors,
modify, display.

Create monitor set, and include monitoring tree elements.

DATA ARCHIVING:

The data which is hold (it is defined during implementation) and not required for
any updates is eligible for archiving. Archiving perform the following circumstances.

1) When the DB size grows dramatically.

2) The admin costs goes high due to tape management
3) The DB is fragmentize
4) The existing tapes in the data center

75
 76

To recommend performing archiving based on age.

Process of archiving:

Identify the objects

Identify the tables that needs to be archived

Get the requirements from business process owners. This is expensive. Involve
functional consultants to identify the objects.

Go to DB15

Identify the respective objects or tables

Check the amount of space that will be available after archiving;

Go to SARA------ click on customizing --------executes errors client filenames/path or

go to transaction file.

To define logical path and physical path

Go to file---- click on new entries--------define logical path

Specify syntax group----- Windows NT
Physical path as D:\usr\sap\dev\sys\global--------- select logical file name
definition.

Go to SF01 to define client specific archiving data

Go to
Select the output
Define write, delete, read, reload, and process.
Specify start date, spool parameters to inform and maintain the variant.

Create variant based on material based on material click on execute

Schedule the archiving, monitoring archiving in SM37 after write check the
readability of the archived files and schedule delete.

Note: Third party tools like archiving IXOS are use to perform archiving. Archiving
cannot increase performance. We need to perform db reorganization soon after
archiving.

76