ABSTRACT

This document consists basis overview of SAP system

and SAP system installation workflow.

Created by- Neel Chaudhari

SAP overview and installation

Created by- Neel Chaudhari

 SAP overview and installation
Overview of SAP -
 SAP Stands for Systems, Applications, Products
 SAP is the leading Enterprise Information and Management Package
 There are n number of ERP software's in market today, of which SAP is used in medium
to large enterprises.
 Other ERP Applications-
1. SAP
2. Oracle JD Edwards
3. IQMS
4. SysPro

Modules of SAP system -

Created by- Neel Chaudhari

SAP R3 Architecture-

The SAP R/3 System has a three-tier client/server architecture. All data is stored in a database,
and the data is processed in the application layer on the application servers. The SAP GUI
frontend (presentation layer) is the interface to the user. All three layers are connected to each
other with networks.
The Presentation Layer contains the software components that make up the SAPgui (graphical
user interface). This layer is the interface between the R/3 System and its users. The R/3 System
uses the SAPgui to provide an intuitive graphical user interface for entering and displaying data.
The presentation layer sends the user's input to the application server and receives data for
display from it. While a SAPgui component is running, it remains linked to a user's terminal
session in the R/3 System.
The Application Layer consists of one or more application servers and a message server. Each
application server contains a set of services used to run the R/3 System. Theoretically, you only
need one application server to run an R/3 System. In practice, the services are distributed across
more than one application server. The message server is responsible for communication between
the application servers. It passes requests from one application server to another within the
system. It also contains information about application server groups and the current load

Created by- Neel Chaudhari

balancing within them. It uses this information to assign an appropriate server when a user logs
onto the system.
The Database Layer consists of a central database system containing all of the data in the R/3
System.
The database system has two components –
1. Database management system (DBMS)
2. Database.
SAP has manufactured its own database named Hana but is compatible with all major databases
such as Oracle.All R/3 data is stored in the database. For example, the database contains the
control and customizing data that determine how your R/3 System runs. It also contains the
program code for your applications. Applications consist of program code, screen definitions,
menus, function modules, and various other components.

Components of SAP R/3 3-tier Architecture: -

1. Message Server: It handles communication between distributed Dispatchers in ABAP
system.
2. Dispatcher Queue: Various work process types are stored in this queue.
3. Dispatcher: It distributes requests to the work processes.
4. Gateway: It enables communication between SAP system and between SAP system and
external systems.
5. ABAP-Work processes: - It separately executes dialog steps in R/3 applications.

Types of work processes are given as below: -

Created by- Neel Chaudhari

 6. Memory-pipes: It enables communication between ICM and ABAP work processes.
7. Message Server: It handles java dispatchers and server processes. It enables
communication within java runtime environment.
8. Enqueue Server: It handles logical locks that are set by the executed Java application
program in a server process.
9. Central Services: Java cluster requires a special instance of the central services for
managing locks and transmitting messages and data. Java cluster is a set of processes that
work together to build the reliable system. Instance is group of resources such as
memory, work processes and so on.
10. Java Dispatcher: It receives the client requests and forwards to the server process.
11. SDM: Software Deployment Manager is used to install J2EE components.
12. Java Server Processes: It can process a large number of requests simultaneously.
13. Threading: Multiple Processes executes separately in the background; this concept is
called threading.
14. ICM: It enables communication between SAP system and HTTP, HTTPS, SMTP
protocol. It means by entering system URL in the browser you can access SAP from
browser also.

Created by- Neel Chaudhari

How the SAP Logon Process works?

Step 1) Once a user clicks on the SAP system from GUI, the user request is forwarded to
Dispatcher.
Step 2) Request is stored in Request queues first. Dispatcher follows First in First out rule. It will
find free work process and if available will be assigned.
Step 3) As per user request, particular work process is assigned to user. For example, when user
login to the system then Dialog work process is assigned to the user. If user runs a report in
background, then background work process is assigned to the user. When some modifications are
done at database level then update work process is assigned. So as per user's action work process
is assigned.
Step 4) Once user is assigned the dialog work process then user authorizations, user's current
setting are rolled in to work-process in shared memory to access user's data. Once dialog step is
executed then user's data is rolled out from work process. Thus, shared memory will be cleaned,
and other user's data can be saved in shared memory area. Dialog step means the screen
movements. In a transaction, when a user’s jumps from one screen to other the process is called a
dialog step.

Created by- Neel Chaudhari

Step 5) First work process will find the data in the buffer. If it finds data in buffer, then there is
no need to retrieve data from database. Thus, response time is improved, and this process is
called hit. If it does not find the data in buffer, then it will find the data in database and this
process is called miss. Hit ratio should be always higher than miss ratio. It improves the
performance of system.
Step 6) Other requested data is queried from the database and once the process is complete, the
result is sent back to GUI via dispatcher.
Step 7) At the end user's data is removed from shared memory so the memory will be available
to other users. This process is called roll-out.

SAP Installation –
URL for download files: - https://support.sap.com/en/index.html

Product Availability Matrix (PAM) –

The Product Availability Matrix (PAM) bundles technical and release planning information on
SAP Product Versions for quick reference. You will find information on their availability dates,
maintenance end dates and upgrade paths, as well as technical release information (DB
platforms, operating systems etc.)

Created by- Neel Chaudhari

Created by- Neel Chaudhari
Maintenance Planner -

Created by- Neel Chaudhari

Created by- Neel Chaudhari
Created by- Neel Chaudhari
Created by- Neel Chaudhari
Created by- Neel Chaudhari
Created by- Neel Chaudhari
SAP system start order –
1. DB
2. ASCS
3. PAS
Command- <Drive>:\Program Files\SAP\hostctrl\exe\sapcontrol.exe -nr <instance_number> -
function Start

SAP system stop order –

1. PAS
2. ASCS
3. DB
Command- <Drive>:\Program Files\SAP\hostctrl\exe\sapcontrol.exe -nr <instance_number> –
function Stop

Installation Process –
SWPM - SOFTWARE PROVISIONING MANAGER.
A tool that performs software provisioning processes such as installation, uninstallation, system
copy, or system transformation. The Software Provisioning Manager is delivered with the
Software Logistics Toolset.

Created by- Neel Chaudhari

The following are the minimum requirements for SAP R/3 installation −
 Minimum hardware requirements-
1. CPU: Intel PIII 500 MHZ
2. HDD: 30 GB
3. RAM: 256MB
4. Ethernet Card for LAN connectivity

 Minimum software requirements -

1. Windows Server
2. Windows Server Service Pack
3. Internet Explorer
4. Database Software Ex: Microsoft SQL Server
5. SAP R/3 System
6. Report Data CD
7. Export CDs
8. SAP GUI
9. SAP R/3 Kernel CD
10. Dynamic Link Libraries or DLL
11. Active Directory Service Interface or ADSI
12. Microsoft Management Console or MMC

 Required files from Service Market Place -

1. Kernel
2. Database
3. Media Browsers
4. SWPM (Software Provisioning Manager)

STEPS FOR INSTALLING THE SAP SYSTEM -

 Start the installer from the directory to which you unpacked the Software Provisioning
Manager archive

 Double click on sapinst.exe

Created by- Neel Chaudhari

  Select the Version of NetWeaver
 Perform Prerequisite Check
 Select Database
 Expand Installation
 Select the System

Created by- Neel Chaudhari

  Three type of systems-
1. Central system
2. Distributed system
3. High availability

 Define Parameters: -
1. Select Parameter Mode
2. Define SID
3. Assign Domain Name
4. provide Master Password
5. Choose the Windows Domain
6. Upload All Software Packages

Created by- Neel Chaudhari

  Upload all Database Dumps
 Assign Database System Parameter
 Enter Configuration Parameter for Database
 Enter Database User Password

Created by- Neel Chaudhari

  Provide Instance Number
 Assign Message server port and transfer Host
 Enter the password for Web Administration

Created by- Neel Chaudhari

  Review parameters
 execute services
 service completed

Created by- Neel Chaudhari

Directory Paths: -
Log Files while installation – C:/program files/sapinst_dir
Profile files - /usr/sap/SID/sys
Kernel files - /usr/sap/SID/sys/run

Post-installation Steps: -
1. Log on to the SAP System:

2. Perform a system Check (SICK or SM28)

3. Perform a post Installation Activity using Transaction code (SE06)
4. Perform a Database Check (DBACOCKPIT or DB02) :- check for missing tables or
indexes by choosing Diagnostics →Missing Tables and Indexes.
5. Install the SAP License (SLICENSE)
6. Using SCCL tcode Create a custom client by copying master client(000), and make it as
default client using RZ10 by changing login/system client value
7. Configure the RFC(SM59)
8. Configure the Transport Management System (STMS)

Created by- Neel Chaudhari

Kernel Upgrade Steps:
Step 1: Create a new Directory at OS level with enough space. Name of Dir can be
"exe_new<ddmmyy>"

Step 2: Transfer these SAPEXEDB.SAR & SAPEXE.SAR files which you have downloaded to
the new directory at OS level.

Step 3: Change your current directory to path .SAR files are created (cd
/sapmnt/PR2/exe_new20122006). Check the directory path with command 'pwd' to ensure you are
in the same dir (exe_new<ddmmyy>).

Step 4: Now uncompress these. SAR files by sapcar exe. The command used for the same would
be

SAPCAR –xvf sapexe. SAR

SAPCAR –xvf sapexedb.SAR

Step 5: Now create one more directory in that path with the name "exe_old<ddmmyy>". Take the
backup of existing kernel.Copy (only copy not move) the existing kernel from exe directory to
"exe_old<ddmmyy>"

Step 6: Now stop the SAP application. (For kernel upgrade the shutdown of database is not
essential but we need to stop the SAP application)

stopsap r3

Step 7:

Then copy the files from the new kernel directory exe_new<ddmmyy> to the existing kernel
directory exe

cp -rp /sapmnt/<SID>/exe_new<ddmmyy>/* /sapmnt/<SID>/exe/

Created by- Neel Chaudhari

Step 8: This will copy / replace all the files in the existing kernel directory with a new kernel files.

Then check the kernel version from OS level by the command disp+work. It should show that the
patch number has been increased.

Step 9:

Then logon to OS level as root (specific to UNIX). In the kernel directory, there is a script called
saproot.sh. Execute this script

./saproot.sh <SID>

Step 10: This script assigns the correct permissions to all the executable programs in the kernel
such br* file etc...

Step 11:

Then start the SAP system

startsap r3
Step 12: Now you can also check the kernel version level from SM51 or by selecting system à
status.

Created by- Neel Chaudhari