SAP BASIS Introduction

Introduction to SAP & Netweaver Architecture

CONFIDENTIAL
 Overview of
SAP Products &
Components
 SAP AG – An Overview
• World’s Leading Provider of Business Management Software
• Established in 1972. Headquarters in Walldorf , Germany
• 82000 Customers run SAP in 120 countries
• Addressing business needs of organizations ranging from Fortune
500 Global Organizations to Small & Medium businesses
• Solution offerings for more than 25 diverse industries

Media Courtesy : SAP-TV AG

 SAP Components and Solutions - Overview
• SAP is an acronym for Systems , Applications and Products for Data Processing
• SAP’s ECC 6.0 (Enterprise Core Components) provide the core solutions for
running enterprise business processes in Financials, Logistics and Human
Resources
• SAP’s Netweaver 7.0 Platform provide the computing environment for managing
the core ECC applications using the Web Application Server 7.0 (WAS 7.0). The
server can power business application programming in ABAP as well in JAVA
• SAP’s Netweaver 7.0 Platforms power Business Analytics and Reporting (BI 7.0) ,
Process Integration with other enterprise components (PI 7.0) , Data Management
(MDM 5.5) and People Integration and Collaboration (EP 7.0)
• SAP Cross-Application Business suite components , such as CRM , SRM , SCM
are built on the core business functions provided in ECC 6.0
• SAP provides a wide ranging set of solutions for specific Industries , such as
Utilities , Retail , Oil & Gas , Aerospace , Mining etc , known as SAP Industry
Solutions.
SAP Components & Solutions : Positioning
People
SAP NETWEAVER 7.0 Process
Integration & Integration –
Enterprise Portal 7.0 ERP to ERP ,
Collaboration
Process Integration 7.0 ERP to Non-
ERP Integration
Business Intelligence 7.0
Information
Master Data Management 5.5 Integration -
Composites Composition Environment 7.1 Business
Development – Analytics &
SOA SAP ERP 6.0 Reporting ,
Enablement Master Data
Management
Application
Platform – Core SAP Enterprise Core Components
Business (ECC 6.0)
Functions

Web Application Web Application

Computing Server 7.0 Server 7.0
Engines – Web ABAP JAVA
Application
Servers
SAP Components – One View
SAP Industry Solutions
Retail,Utilities,Oil & Gas,Aerospace
etc

SAP NETWEAVER 7.0

Enterprise Portal 7.0
Process Integration 7.0
Business Intelligence 7.0 Technology
Master Data Management 5.5 Components
Business
Composition Environment 7.1 & xApps
Suite
Composites
Solutions
SAP ERP 6.0
Solution
CRM 2007
SAP Enterprise Core Manager
SRM 2007
Components SAP Kernel
SCM 2007
(ECC 6.0) Composites
SEM 2007
SAPGUI
GTS
SAP ITS
Web Web Plug-Ins
Application Application
Server 7.0 Server 7.0
ABAP JAVA
SAP Offerings based on Company Size

Solution for Small Businesses

• Less than 100 Employees
• Less than 30 Users
• Basic functions pre-configured
e
Si z

SAP
Business Solution for Medium Businesses
ise

One • Between 100 and 500 Employees

rpr

• On demand solution catering to

te

niche process areas

En

SAP Business
By Design Solution for Medium Businesses
• Strong Industry-specific focus
• Stable core business processes
• Preconfigured solutions
SAP Business All-in-One

Large & Very Large Enterprises

• Complete spectrum of business
solutions
SAP Business Suite • Adaptable components to address
business process complexities
• For over 500 employees

Functionality/Industry
Support/Adaptability
 Evolution of SAP Releases

• SAP releases come in two flavours – An application flavour and basis(was) flavour.
• The SAP Application , otherwise called ECC 6.0 was earlier called mySAP ERP 2005 , and this is based on WAS 7.0
• The older release , ECC 5.0 was called mySAP ERP 2004 and was based on WAS 6.40
• The predecessor to ECC 5.0 , was called SAP Enterprise 4.7 , based on WAS 6.20 and 6.30. This was the first time SAP
BASIS kernel came to be referred to as WAS. The JAVA Engine made its first appearance in this release.
• Earlier SAP releases were called R/3. This is starting from R/3 3.1i to 4.6c. The underlying BASIS kernel was versioned
from 3.1i to 4.6D.All such releases were based purely on ABAP engines
SAP BASIS Overview
What is SAP BASIS ?
• The term “BASIS” is a reference to the underlying technical architecture of an SAP
application. The term encompasses the server infrastructure , software and the server
processes that run the SAP application.
Who are BASIS consultants ?
• SAP consultants who design, build and manage the SAP environment are termed as
BASIS consultants. They are the SAP Technical architects in the IT organization.
What is the scope of BASIS consultants in an IT organization ?
• SAP consultants possess the skills required to administer and configure SAP specific
settings in an IT landscape. They are part of a larger organization which may run a
landscape consisting of several SAP and Non-SAP applications.
What are the pre-requisites for starting a career in SAP BASIS ?
• Basic knowledge of operating system administration, network management and
database administration.
SAP BASIS Services in an Organization
Customer

Sales Purchase Finance HR

BUSINESS ORGANIZATION

SAP Functional Analysts – SD , MM , PP , QM

SAP Developers – SAP BASIS

ABAP & JAVA Consultants

SAP IT ORGANIZATION
Introduction to
Netweaver
Introduction to SAP Netweaver

• Basic Concept of SAP Netweaver

• SAP Netweaver Application Server

Basic Concepts
• SAP Netweaver provides the platform for deploying IT processes that support enterprise
business functions. Such IT processes when grouped together form “IT Practices”.
• Each IT practice requires an integration of various IT scenarios as shown below

IT Practices IT Scenarios
 Basic Concepts
• Each IT scenario requires an integration between various components
of the SAP Netweaver stack
• The SAP Netweaver stack consists of 4 broad layers
 People Integration
 Process Integration
 Data Integration
 Application Platform

People Integration Process Integration Data Integration Application Platform

• Achieved by using SAP • Achieved by using SAP • Achieved by using SAP • Platform is based on
Enterprise Portal Process Integration Business Intelligence SAP Web Application
• SAP EP provides tools • PI provides the tools and and SAP MDM Server for ABAP and for
for developing functions for SAP to SAP • A dual stack solution that JAVA
applications for the and Non-SAP provides powerful tools • Platform that provides
presentation layer communications for data extraction, numerous tools for
• Knowledge Management • Provides means for reporting , analytics and administration,
and Collaboration performing Business providing real-time view monitoring and
functions are in-built Performance monitoring of business performance integration
SAP Netweaver Application Server
Architecture View of SAP Netweaver Application Server

SAP Netweaver Application Server Features PRESENTATION

• Multi Level Architecture LAYER
• Runtime environment for both ABAP and JAVA
Programs
• High Scalability

External Systems APPLICATION LAYER

(SAP , Non-SAP)

JAVA ABAP

• Built on a wide range of Operating systems and

Database Platforms DATABASE LAYER
• Choice of Presentation layer tools – SAPGUI ,
WEBGUI
• Development IDES for Java and ABAP
• Standard protocols supported Ex: HTTP , RFC
• Security functions follow industry standards
SAP Architecture
Fundamentals
SAP Architecture Fundamentals

• ABAP & JAVA Runtimes

• Client Server Architecture

• Concept of SAP Instances

• AS ABAP Processes & Architecture

• Request Processing in AS ABAP

ABAP & Java Runtimes

• SAP systems provide the basis for building applications that implement business
processes
• The SAP applications are not dependent on the type of Operating systems and
Databases to a great extent
• Applications can be built in either ABAP or JAVA languages
• ABAP stands for “Advanced Business Application Programming”. Most
applications in SAP are written in ABAP
• To run ABAP programs , the Netweaver application server provides a ABAP
Runtime environment
• To extend SAP applications so that they become highly interoperable with external
and internet web-based applications , the JAVA runtime was introduced in the SAP
Netweaver environment. The JAVA runtime is based on J2EE standards
• IMPORTANT NOTE : The ABAP and JAVA runtimes are also called as ABAP and
JAVA engines
Client Server Architecture
• The client is a device on a network , which transmits requests for data processing. The
client in the SAP architecture can be either the SAPGUI running on Windows , SAPGUI
for JAVA for other OS’ or WEBGUI which can be invoked from any common browser
• The server is the Netweaver application server which processes client requests in the
ABAP or JAVA engine
• Communication happens over a dedicated network infrastructure (LAN) or through
Wireless LAN (WLAN)
• In SAP , there are several types of multi-level architectural scenarios possible :

INTERNET
BROWSER MULTI
TIER

WEBGUI
THREE
APPLICATION TIER
DATABASE
SERVER
SERVER
SAPGUI

TWO
APPS + DB TIER

LOCAL AREA NETWORK

Concept of SAP Instance

• An SAP Instance is the basic building block of an SAP system

• An SAP system can comprise of one or more SAP instances
• It is an administrative unit that combines multiple components to provide one or more
services
• An SAP system comprises of two parts : Application Instance and Database Instance
• When the application instance and database instance reside on the same hardware , it is
then known as a “SINGLE INSTANCE”
• When the application instance and database instance do not share the same hardware
resources , then the instance is known as a “DISTRIBUTED INSTANCE”
• An SAP Instance is uniquely identified with a system ID , known as SID and an instance
number
• Each SAP instance can be distributed over multiple hardware units. These units can be
separate physical machines , logical/physical partitions within the same machine.

The Database Instance ID , also called DBSID is normally the same as the SAP instance ID , or SID.The SID
is always 3 characters long and can contain alphanumerals , but it must start with an alphabet. The
Instance Number is always a 2 digit number , and can be any combination of digits between 0 and 9.
 Concept of SAP Instance
An SAP Application Instance can be broken down to the following types :

Type of Application Server Instance Name Name of Processes

Central Instance Enqueue Server , Gateway Process

ABAP Application Server Central Services Instance Message Server

Dialog Instance ABAP Work Processes
Central Instance Software Deployment
Manager(SDM) , Dispatcher
JAVA Application Server
Central Services Instance Message Server
Dialog Instance JAVA Server Processes

Each SAP system can have only 1 Central Instance , 1 Central Services Instance and only 1 Database instance. It can
have any number of additional dialog instances
Distribution of SAP Instances in a SAP system
Single Instance Distributed Instance Distributed Instance
with multiple dialog
instances
APPLICATION APPLICATION APPLICATION INSTANCE
INSTANCE INSTANCE
CENTRAL CENTRAL CENTRAL
INSTANCE INSTANCE INSTANCE

CENTRAL CENTRAL
CENTRAL SERVICES
SERVICES SERVICES
INSTANCE INSTANCE
INSTANCE

DATABASE DATABASE DIALOG DIALOG

INSTANCE INSTANCE INSTANCE 1 INSTANCE 1

DIALOG DIALOG
INSTANCE 2 INSTANCE 2

DATABASE
INSTANCE

Note : Each Box represents a physical machine or

a partition within the same hardware
Application Server – ABAP
Processes
 AS ABAP Processes
The table shows the different types of Processes in AS ABAP Environment

Process Name Description

Dispatcher Work Process There is 1 dispatcher work process per Application Instance and per each
Dialog Instance.If there is 1 Central Instance and 2 Dialog instances in an
SAP system , there will be 3 dispatchers. The role of the dispatcher is to
distribute incoming requests to the ABAP worker threads.
Dialog Work Process (D) There are a minimum of 2 Dialog work processes required per dispatcher that
need to be configured per instance.This work process executes the
transactions as required and communicates with the database instance
processes
Background Work Process (B) Background work processes execute programs that run without interacting
with the user. At least two background work processes for each SAP system
are required.More than one background work process for each dispatcher can
be configured.
Enqueue Work Process (E) Only 1 enqueue process exists in each SAP system. This process ensures
that updates are serialized with the help of a lock table.
Update Work Process (V) Minimum 1 Update process is required , and more than 1 process per
dispatcher is allowed. This process takes care of processing update requests.
Spool Work Process (S) Minimum 1 spool process is required and more than 1 process per dispatcher
is allowed. This process passes sequential data to output devices such as
printers.
 AS ABAP Processes
The table shows the different types of Processes in AS ABAP Environment (Contd.)

Process Name Description

Message Server (M) Only 1 Message server exists in the SAP system and is installed on the
Central Services Instance. It is responsible for communication between the
different dispatchers of each SAP instance within the same SAP system.
Gateway (G) There is exactly 1 Gateway Per Dispatcher in a SAP system.The gateway is
meant to allow communication between different SAP systems
Internet Communication Manager There is only 1 ICM per SAP system.The ICM receives requests for HTTP
protocol and forwards it to the ABAP dispatches for further processing

SAP uses the acronym DVEBMGSxx , where xx is the instance number to denote an SAP
instance within the SAP system.
Example : If an SAP system comprises of 1 Central instance with number 01 , and 2 Dialog
Instances , with number 02 and 03 , then the SAP system is said to be comprised of
DVEBMGS01 , DVEBMGS02 and DVEBMGS03 instances
AS ABAP Architecture
• Architecture showing the interaction between ABAP processes in a SAP system with a
Central Instance and 1 Dialog Instance

• Note that there is no enqueue process within the dialog instance.

AS ABAP Processes

• The AS ABAP Message Server process is for internal communication. For

example initiating updates , requesting and removing locks , triggering
background requests etc.
• It also keeps track of which instance is available by periodically pinging each
instance
• There is 1 dispatcher per instance. In a system with multiple instances , the
dispatchers communicate with each other through the message server
• All requests received through HTTP are handled by the ICM. Each ICM then
forwards the request to the dispatcher within its own instance.
• The gateway process accepts requests that follow the RFC protocol. Typically
such requests are sent from either other SAP systems or from applications
running outside the SAP system.
Request Processing in AS ABAP
• Users in SAP use the SAP Frontend , called SAPGUI as shown below.The details
of the system to login into has to be specified in the SAP Logon Pad
Processing a user request
Processing a user request
Processing a Dialog Request
• Each SAP program has a number of dialog steps , which are steps that have input
parameters, processing functions and output parameters. Each step is manifested
in the form of screen changes from a user’s point of view.
• Each dialog step can have multiple screens to process. Each step may be
executed by any of the available dialog work processes.This is known as Work
Process Multiplexing.
• A single dialog process therefore may sequentially process dialog steps for any
user and any program during its activity cycle.
Transaction Processing in AS ABAP
• Transactions are processing units, that functionally belong together. They have
four principal characteristics. The initial letters of these characteristics together
form the acronym ACID.
 Atomic
 Consistent
 Isolated
 Durable
• Atomic means that a transaction is either fully successful or does not have any
effects at all. If a transaction-oriented system goes down, you need to ensure that
inconsistent, partial results are not stored.
• Consistent means that the system status changes from one that is accurate and
consistent in business terms to another that is also accurate and consistent in
business terms.
• Isolated means that the changes made within a transaction can only be seen by
other transactions, even those that run simultaneously, after the final confirmation
(Commit).
• The results of a transaction are durable because after the final confirmation they
are stored permanently in the database.
Enqueue & Lock Management
Principles of Asychronous Updates
Print Processing
Background Processing
Internet Communication Manager (ICM)
Notes on SAPGUI
• There are various ways to access an SAP System. The most commonly used are
SAPGUI for Windows , SAPGUI for JAVA and WEBGUI for browsers.
• SAPGUI is a client utility that has to be installed on a user’s machine.
• SAPGUI is available for installation on Windows and on Non-Windows platforms
as well.
• A JAVA based SAPGUI is required for OS such as Linux or any other Unix flavour
• SAPGUI is available as SAPGUI for HTML , popularly called WEBGUI , that is
supported on most common browsers such as IE 6 , Firefox 3
• For Windows desktops , the entries in the SAPGUI logon pad are stored in a file
called saplogon.ini file , which is located in the path C:\Windows
Alternative types of SAPGUI
 Navigation using SAPGUI
ELEMENTS OF SAPGUI

SAP LOGON
SAPGUI PAD
Version

Log On
Button
SAP System
Entries in
SAP Logon
Pad

Create New
System
Entries
 System Entry in SAPGUI
ELEMENTS OF SAPGUI

SAP
Application
Description of
Server Host
the SAP
Name or IP
System.This
address
can have any
convenient
name as per SAP System
the users Number
choice

System ID
 SAP Logon Screen
ELEMENTS OF SAPGUI

Note :
Client
Number is a
logical unit of
an SAP
system
You can Client Number Password
change your field is case-
password sensitive
once a day User ID

Password

2 Character
Language
Field : By
default the
system takes
EN if left
blank. (EN –
English)
 SAP Logon Screen
ELEMENTS OF SAPGUI

Note :
Client
Number is a
logical unit of
an SAP
system
You can Client Number Password
change your field is case-
password sensitive
once a day User ID

Password

2 Character
Language
Field : By
default the
system takes
EN if left
blank. (EN –
English)
 SAP Logon Screen
ELEMENTS OF SAPGUI

Field to enter Transaction Code

• In SAP , all operations are carried out using Transaction Codes.These are codes that can call
reports,programs from the users screen.
• /n denotes a new session.A user can open upto maximum of 6 sessions where he/she can parallely work
• /o followed by a transaction code causes the transaction to open in a new session.
• Each new session means a new window opened on your computer
ABAP Work Processes – SM50

This transaction shows the various

ABAP work processes :
Dialog,Update,Enqueue,Background,
Spool and Update2
The dispatcher process is not shown
here.
 ABAP Work Processes as Unix Processes

• In the previous screen , there were a total of 21 ABAP processes indicated

• On an UNIX OS Level , these processes are realized as individual unix processes denoted by “dw”
• The above screen shows 22 dw processes. This is because there is the additional “Dispatcher”
process
• The ICM process is a process that starts with the name “icman”
• The Gateway process is a process that starts with the name “gwrd”
• The Message server is a process that starts with the name “ms”
Checking for Locks – SM12
• You can check for lock entries in a system using
SM12 transaction

• The above screen shows locks on table VBAK (Sales Order

Table)
• The lock will remain on the table until the user either saves
the sales order data or exits the transaction without saving
Q&A Session