Professional Documents
Culture Documents
Comprehensive Sap Basis Training Day 1
Comprehensive Sap Basis Training Day 1
Course Title
IBM Global Business Services
Introduction to ERP
Module 1
Module 1: Objectives
After completion of this module, you should be
able to:
Define an ERP
Relate SAP to an ERP
Understand the evolution of SAP
Identify the components of SAP.
Understand SAP Netweaver Concept.
Understand the various kinds of Client-Server
Architecture from SAP perspective.
Know SAPs Release and Maintenance Strategy
Module 1: Agenda
Topic 1: ERP: Definition
Topic 2: Relation between SAP and ERP
Topic 3: SAP evolution
Topic 4: Components of SAP
Topic 5: Features of Sap Netweaver
Topic 6: SAP client-server architecture
Topic 7: SAP release and maintenance strategy
Disadvantages:
Systems could not be changed on demand.
Excessive change made the applications difficult to manage.
Required large number of skilled in-house personnel to
maintain the systems.
Very high cost of maintenance.
Make
Buy
Mix n Merge
In-house
developed
applications
3rd Party
developed
applications
Packaged
Corporate
Applications,
such as SAP
& Oracle
Financials
1970s
1980s
1990s
ERP
Overview of SAP
The SAP system is software which is composed of different software and a
server as a whole and has the ability to perform standard business functions
for corporations.
SAP (pronounced ess-aye-pea ) is based in Walldorf, Germany .
It stands for Systems, Applications and Products in Data Processing.
Its an ERP Package.
SAP's foundation is built upon the concepts of specialization and integration.
It is world premier provider of client/server business solutions.
SAP products can be broken down further into modules portions of
functionality.
Evolution of SAP AG
SAP was founded in the year 1972 as Systemanalyse und
Programmentwicklung ("System Analysis and Program Development")
The acronym was later changed to stand for Systeme, Anwendungen und
Produkte in der Datenverarbeitung ("Systems, Applications and Products in
Data Processing").
In 1976 "SAP GmbH" is founded and the following year it moved headquarters
to Walldorf .
SAP AG became the company's official name in 2005 (AG is short for
Aktiengesellschaft).
In August 1988, SAP GmbH transferred into SAP AG (a corporation by
German law).
In 1995, SAP was included in the German stock index DAX and On August 3,
1998, the letters S-A-P appear for the first time on the Big board at the New
York Stock Exchange (NYSW).
Henning Kagermann became the sole CEO of SAP in 2003 till date.
9
Technical solutions
10
ERP packages
SAP ERP 6.0 from SAP
mySAP from SAP
SAP Business One from SAP
PeopleSoft from Oracle
JD Edwards EnterpriseOne & JD Edwards World
from Oracle
11
R/2 system
SAP R/2 is a real-time enterprise resource planning (ERP) software.
R/2 is SAP AG mainframe software that runs on IBM, Siemens, Amdahl, and
compatible equipment.
R/2 can be linked to R/3 systems and share online data.
R/2 system is mainly targeted at enterprises with data intensive and
centralized industries.
R/2 is the predecessor of the client/server R/3 system.
R/2 system offers comprehensive, fully functional business applications to
satisfy the demands of mainframe users.
12
SAPs go-to-market-approach
Source:
Source: SAP
SAP
14
SAP xAPPS
mySAP ERP
mySAP SCM
mySAP CRM
mySAP PLM
mySAP SRM
SAP NetWeaver
16
17
18
19
Source:
Source: SAP
SAP
20
22
Source:
Source: SAP
SAP
23
SAP NetWeaver
SAP NetWeaver is the technical basis of the solutions from
mySAP Business Suite and the Composite Applications the
SAP xAPPS.
It is also the core of the Enterprise Services Architecture,
SAP basic concept for Web Service solution.
It is the functionally successor of the SAP application
platform mySAP Technology and serves the basis for the
Enterprise Services Architecture, in order to meet requests
for flexibility and integration between systems, interfaces,
users and processes.
It connects information, business processes and people
across system and organizational boundaries.
It the central tool for reducing TCO of complex system
infrastructure.
24
Source:
Source: SAP
SAP
Copyright IBM Corporation 2009
NetWeaver: A snapshot
25
26
27
Source:
Source: SAP
SAP
28
Source:
Source: SAP
SAP
29
30
Source:
Source: SAP
SAP
31
Three-tiered architecture
Source:
Source: SAP
SAP
32
Application layer:
The SAP application servers that service requests for data and manage the
interface to the presentation layer.
Database layer:
The actual DBMS that communicates with the application servers to fulfill their
requests for data.
33
34
Source:
Source: SAP
SAP
36
38
Release strategy
The release strategy is based on the following principles:
You can obtain the entire mySAP Business Suite, individual SAP applications
or SAP NetWeaver.
SAP applications and SAP NetWeaver have their individual release cycles.
Usually, SAP delivers a new release of SAP NetWeaver first, and shortly
afterwards, new releases for SAP applications of mySAP Business Suite
follow synchronously.
SAP always gives you access to the current release of an SAP application
and to procedures to upgrade to the current release.
The Ramp-Up
Ramp-Up process is SAPs process of introducing new application releases to
the market.
Ramp-Up program provides a risk-free way for you to implement new SAP
software as soon as it becomes available.
At the beginning of the Ramp-Up process, SAP identifies target industries as
well as customers who then implement and use the new release in closely
monitored and documented projects.
During the Ramp Up, the software is only available for limited circle of
customers, customers apply at SAP to participate in Ramp-Up.
The Ramp-Up servers to take customer wishes into consideration before the
respective SAP software is generally available (unrestricted shipment).
Participants in Ramp-Up are given direct contact to the SAP development and
are provided with wide support in implementing the SAP software.
40
Maintenance strategy
The maintenance strategy for cross-industry applications is based on the
following principles:
SAP offers three successive maintenance phases: mainstream maintenance,
extended maintenance, and customer-specific maintenance.
SAP provides support packages during mainstream maintenance and
extended maintenance. The delivery frequency of support packages is
dependent on the maintenance phase.
SAP also provides legal changes to adapt the SAP application to new or
changed legal requirements during mainstream and extended maintenance.
As part of its release strategy, SAP announces the planned period and scope
of mainstream maintenance for a release as soon as the release is announced
5-1-2 maintenance strategy.
41
Source:
Source: SAP
SAP
42
Source:
Source: SAP
SAP
43
Module takeaways
The SAP system is software which is composed
of different software and a server as a whole and
has the ability to perform standard business
functions for corporations. Its stands for
Systems, Applications and Products in Data
Processing.
SAP has evolved from a R/2 to R/3 type
architecture.
SAP Web Application server opens up a variety
of new opportunities.
SAP follows a release and maintenance strategy.
44
45
Module 1: Summary
Having completed this module, you should now be
able to:
Define an ERP
Relate SAP to an ERP
Recognize the evolution of SAP
Identify the various components of SAP
Put in your own words the underlying features of SAP
Netweaver
Categorize various kinds of client-server architecture
from a SAP perspective
Analyze SAPs release as well as maintenance
strategy
46
Course Title
IBM Global Business Services
Module 2: Objectives
On completion of this module, you should be
able to:
Describe the different phases of SAP
Project Lifecycle
48
Module 2: Agenda
Topic 1: SAP Project Lifecycle
49
Evaluations
Project
Preparation
Business
Realization
Blueprint
Testing
Final
Go live
Preparations
Sustain/
Support
Sustain
Sustain
Evaluation
Realization
Testing
Final
Go live
Sustain
Preparation
50
51
52
Module takeaways
A SAP project lifecycle consists of various
stages starting from evaluation to the projects
subsequent support.
53
54
Module 2: Summary
Having completed this module, you should now be
able to:
Identify the different phases of SAP Project
Lifecycle
55
Course Title
IBM Global Business Services
Module 3: Objectives
On completion of this module, you should be
able to:
Interpret the architecture of SAP Web
Application Server (WAS)
Describe ABAP and JAVA Processes
Identify the different types of SAP WAS
57
SAP NetWeaver
NetWeaver is essentially an umbrella term, encompassing a number of SAP
products and technologies that combine to create a platform for building,
extending, and integrating enterprise applications.
It has built in interoperability which hooks into SAP-, Microsoft-, and Javabased technologies.
Development cost is decreased.
Integration is enabled, speeding up time to deploy as well as shrinking the
time necessary to perform system upgrades and so on.
Total cost of ownership is reduced significantly because maintenance and
support costs are dramatically reduced. Thus, innovation is enabled; IT can
spend more time meeting the needs of the business, and less time
maintaining existing solutions.
58
Source:
Source: SAP
SAP
59
The ABAP
dispatcher
Dialog work
processes (DIA)
Spool work
processes (SPO)
Update work
processes (UPD
and UPD2)
62
Background work
processes (BGD)
The enqueue
work process
(ENQ)
Java processes
The following processes exist in the
Java environment:
The Java dispatcher
The Java server process
The Java message service
The Java enqueue service
The SAP Java Connector (Jco)
63
ABAP services
In addition, the (ABAP) runtime system provides additional services (these are
not work processes) for internal and external communication:
The message server (MS) handles the communication between the distributed
dispatchers within the ABAP stack of an SAP system.
The gateway server (GW) enables communication between SAP systems, or
between SAP systems and external application systems. There is one per
dispatcher.
An instance is an administrative unit that combines SAP system components
providing one or more services.
The instance shows all the processes that are required for error-free operation of
an SAP system, collected on one instance. This instance is distinguished from all
other instances of the SAP system and is also called central instance.
The services that an application server can provide are determined by the type of
work processes it has.
64
Java basics
The Java programming language was first introduced by the company Sun
Microsystems Inc.in 1995.
Java is an object-oriented and platform-independent programming language
that is widely used in many areas.
The powerful concept of Java allows the development of a large number of
different types of application - from the classic application using Applets
implemented in Web pages to client/server applications.
Java was designed to be platform-independent. This means that the same
Java program can be executed on any system for which a Java Runtime
Environment (JRE) is available.
In particular, Java applications can run on different systems that are based on
different hardware.
65
66
Source:
Source: SAP
SAP
67
Java services
All Java components of an SAP system are known as a Java cluster. A Java
cluster consists of:
A (central) Java instance with a dispatcher and at least one server process.
The central services, which contain a message server and an enqueue server.
A database for the central storage of data.
Optionally, additional Java instances.
The central services provide the basis for communication and synchronization for
the java cluster:
The message service administers a list of the dispatchers and the server
processes of the Java cluster.
The enqueue service administers logical locks that are set in a server process by
the executed application program. It is also used for cluster-wide synchronization.
68
Java processes
The dispatcher distributes incoming requests to the server processes.
The server process executes the Java applications.
Every server process is multi-threaded and can thus process a large number
of requests in parallel (in contrast to the ABAP work processes). For each
dispatcher there is at least one server processes and there can be up to 16
server processes.
The Java message service manages a list of Java dispatchers and server
processes. It is responsible for the communication within the Java runtime
environment.
The Java enqueue service manages logical locks that are set by the executed
Java application program in a server process.
The Software Deployment Manager (SDM) is the standard tool used to install
Java software components on the SAP Web AS Java.
69
Source:
Source: SAP
SAP
70
Dispatcher
Instance
Instance
Message Server
Dispatcher
Central Instance
** The terms (SAP) instance and (SAP web) application server are often used as synonyms .
71
JAVA Dispatcher
ABAP Dispatcher
SDM
WP
ABAP
Central
Services
WP
WP
JCo
JAVA
JAVA Server
Processes
ABAP Schema
JAVA Schema
72
Complete Infrastructure in
which is ABAP based
applications can be
developed and used.
1
3
2
3
73
NOTE:
One of the main characteristics of the SAP Web AS is that ABAP
tables, programs and application data are stored in the ABAP schema
of the database while JAVA data is stored in the JAVA schema. Here,
the ABAP runtime environment can access the ABAP schema of the
database, and the JAVA runtime environment can access the JAVA
schema. The SAP Java Connector is used for integrating the ABAP
environment and the JAVA environment (JCo).
SAP Basis FastTrak WAS 700
Module takeaways
The SAP WAS consists of an ABAP engine
and a JAVA engine.
They are constituted by different processes in
SAP WAS Architecture.
The Message Service and Enqueue service
comprise the central services.
74
75
Module 3: Summary
Having completed this module, you should now
be able to:
Interpret the architecture of SAP Web
Application Server (WAS)
Describe ABAP and JAVA Processes
Identify the different types of SAP WAS
76
Module 4: Objectives
On completion of this module, you should be
able to:
Describe the start sequence of an ABAP+JAVA
System
Analyze how to start and stop an SAP
system using SAP
MMC, JAVA MC or
command line argument
Recall the JAVA instance from ABAP
interface
78
Module 4: Agenda
Topic 1: Start sequence of an ABAP+JAVA System
Topic 2: Start and stop an SAP system using SAP
MMC, JAVA MC or command line argument
Topic 3: Restart JAVA instance
79
Source:
Source: SAP
SAP
80
log-on
<sid>adm
2 Start
3
DB
Central instance
81
Other instance
Source:
Source: SAP
SAP
82
SAP<sid>_no.
SAPOsCOL
Database Services
Services
System log
Application
log
Microsoft Windows
83
Source:
Source: SAP
SAP
84
Problem analysis
SAP<sid>instance no.
Database service
DB
Database error log files
SAP
INSTANCE
86
87
<sid>adm
SAP System
Admin
CCMS
SAP MMC
Snap-in
Database Tools
Windows Service
Control Manager
Database Services
SAP Instance
DATABASE
sap<sid>_<inst.no.>
SAPOsCOL
88
89
Database process
DB services
SAP process
OS services
SAP services
90
91
92
JAVA MC
SAP MC is a Java application which is supplied as a Java applet as standard.
You simply use a Web browser to do this.
To use the applet correctly, you require a JRE (Java Runtime Environment) of
version 1.4 or higher. In addition, the corresponding Java plug-in for the
browser must be activated correctly.
To start SAP MC after installing the corresponding SAP NetWeaver AS, enter
the below URL in your browser:
93
Unix
Log on in UNIX as a user with SAP administrator authorization (<sid>adm). To
start the central instance, call the shell script startsap_<host>_<instance no> in
the home directory of the <sid>adm user.
The script startsap first starts the saposcol process which collects statistical data
for the operating system that it provides to the SAP system.
The next step is a check to see if the database is running. If not, the script
startdb is called to start the database.
The final step starts all of the processes for the instance (message server,
dispatcher, work processes, and so on). After the central instance is started, you
can optionally start other instances. The startsap script can be called with the
following options:
DB: starts the database system
R3: starts the instances and associated processes for the instance
ALL: starts the database system and the instance (default setting, can be omitted)
94
Unix (continued)
When you stop the SAP system, you should first stop all dialog instances and
then stop the central instance. You have two options for doing this:
From the SAP system using the CCMS Control Panel. Log on under UNIX as
the SAP administrator (<sid>adm) at operating system level and enter the
command stopsap from your home directory.
The stopsap script can be called with the following options:
DB: stops the database system with the help of the stopdb script
R3: stops the instances of the SAP system
ALL: stops the database system and the instance (default setting, can be omitted)
95
OS/400
Logon on to the AS/400 system with the SAP user profile for administrators.
The authorizations of the group profile <SID>OPRGRP are required for this
user (such as user profile <SID>OFR or <SID>OPR ).
Enter the AS/400 command STARTSAP and request parameters with F4.
Under SAP System ID, enter the name of your system (such as DEV).
Under R/3 Instance, enter the instance number (such as 00). To start all
instances on one or more hosts, choose *ALL.
Under R/3 Instance Host Name, enter the name of the host on which the
instance is to be started. To start all instances on all hosts, choose *ALL. (You
must also have selected *ALL under R/3 Instance.)
96
OS/400 (continued)
Confirm your entries with ENTER. The subsystem R3_nn is then started for
each started instance (<nn> is the instance number). All associated SAP
services are started together with the subsystem (such as dispatcher, work
processes, spool processes).
Enter the AS/400 command WRKACTJOB SBS(R3_<nn>) to check whether
the SAP system(s) were started correctly.
The system displays a screen with the column Status at the right-hand side. If
an SAP system was started correctly, the first line of this column should
contain the value RUN (running), SELW (waiting), or DEQW (waiting for
completion of unlocking). It can take a few minutes for the file system to reach
this status.
97
OS/400 (continued)
Logon on to the AS/400 system with the SAP user profile for administrators
(<SID>OFR or <SID>OPR).
Enter the AS/400 command STOPSAP and request parameters with F4.
Under SAP System ID, enter the name of the SAP system that you want to
stop.
Under R/3 Instance, enter the number of the instance that you want to stop,
such as 90.
To stop all instances on one or more hosts, choose *ALL.
98
OS/400 (continued)
Under R/3 Instance Host Name enter *LOCAL to stop one or more instances
on the local host. To stop all instances on all hosts, choose *ALL. (You must
also have chosen *ALL under R/3 Instance.)
If you enter *YES under Wait for instance to end, the command STOPSAP
waits until the SAP instance is shut down before stopping the SAP system.
(The instance is regarded as shut down if the number of active instance user
jobs in the instance subsystem, other than the SAPOSCOL job, is zero.)
Under Maximum wait time (seconds), you can enter the maximum time that
the command should wait for the instance to be shut down. The default value
is 120 (two minutes). If it takes longer than two minutes for the instance to be
shut down, an exception message is sent. Confirm your entries with ENTER.
99
Module takeaways
The SAP Processes follow a definite start
sequence.
The log files are located in specific folders in an
SAP system.
System can be stopped/started using SAP
MMC in windows.
Command line argument or JAVA management
console exists for other systems. (AS JAVA
usage type)
100
101
Module 4: Summary
Having completed this module, you should now
be able to:
Describe the start sequence of an ABAP+JAVA
System
Analyze how to start and stop an SAP system
using SAP MMC, JAVA MC or
command line argument
Recall the JAVA instance from ABAP interface
102