79
SAP R/3 BASIS Training

ERDCI Sap Architecture Final

Embed Size (px)

DESCRIPTION

dqdqd

Citation preview

Page 1: ERDCI Sap Architecture Final

SAP R/3 BASIS Training

Page 2: ERDCI Sap Architecture Final

SAP stands for Systems Applications & Productions in data processing

Sap has two main products in the business software market Mainframe System R/2 & Client server system R/3 . R stands for REAL TIME History of SAP Software 1972 SAP “R/1” • Innovation = Standard Software and Real Time Computing

1983 SAP “R/2” •Innovation = Integration of Applications (Mainframe-based) 1989 SAP “R/3” • Innovation = Relational Database, Client-/Server-Architecture, Platform Independence SAP has no plans for R/4 today .

Page 3: ERDCI Sap Architecture Final

SAP Layers

Three tire client server architecture of the R/3 system separated into three system layers .DATABASE Layer (handles database services)APPLICATION Layer (process business logic & all other services)PRESENTATION Layer (SAP Graphical User Interface SAPGUI)

Presentation Application Database

Central System

Distributed System

2-Tier System

3-Tier System

Page 4: ERDCI Sap Architecture Final

Homogeneous SAP Systems

Where Database server & Application server are running on the same

O.S. Like Win NT & Unix , presentation are running on windows

workstation. Heterogeneous SAP Systems

Database server running on one O.S. (Unix) & Application server

running on different O.S (Win NT) ,& presentation server running on

Windows-based workstations.

Page 5: ERDCI Sap Architecture Final

SAP R/3 Architecture

Presentation Components

Kernel & Basis Services

Database Management System

Database

R/3 Basis System

ABAP Workbench R/3 Application 1 R/3 Application n

R/3 User R/3 User

Page 6: ERDCI Sap Architecture Final

SAP R/3 Communication Protocol

Communication among the three tiers server is accomplished with the use of standard protocol services,such as one provided by TCP/IP or CPIC .

TCP/IP Transmission Control Protocol /Internet ProtocolAt the OS level TCP/IP protocol used , Mainly to communicate with database, application & presentation layer

CPIC Common Programming Interface CommunicationAT the programming level ,R/3 system uses the CPIC protocol for program to program communication and also includes support for Remote Function Calls (RFC).

Page 7: ERDCI Sap Architecture Final

Installation of SAP R/3

INSTALL DATABASE SOFTWARE ON DATABASE SERVER

INSTALL SAP SOFTWARE ON APPLICATION SERVER

UPLOAD DATA TO SAP SYSTEM (Main database creation)

SUPPORT PACKAGE (PATCH) LOADING

1.

2.

3.

4.

POST INSTALLATION Steps 5.

READY FOR USING6.

Page 8: ERDCI Sap Architecture Final

SAP R/3 Supported Platforms(1)

The key of SAP R/3 success was the strategy of making open solutions , in which the applications can run on multiple operating systems , databases ,and communication technologies.

OPERATING SYSTEM LEVEL : AIX COMPAQ TRU64 DG-UX DYNIX/PTX HP-UX NCR UNIX SNI DC/OSX WINDOWS SERVER 32-BIT RELIANT SOLARIS/SPARC LINUX/INTEL OS/400

DATABASE LEVEL : ORACLE SQL SERVER DB2 ADABAS INFORMIX

Page 9: ERDCI Sap Architecture Final

SAP R/3 Supported Platforms(2)

Oracle Informix DB2 SQL SERVER

Adabase D

HP-UX X X X

AIX X X X X

Reliant/UNIX X X X

Digital unix X X X

Solaris X X X

NT 4.0 Intel X X X X X

NT 4.0 Alpha X X X

OS/390 X

OS/400 X

Page 10: ERDCI Sap Architecture Final

SAP R/3 Supported Platforms(3) SAP R/3 3.1H:ORACLE 7.3.2 WIN NT 4.0 INTEL ORACLE 7.3.3 WIN NT 4.0 INTEL ORACLE 7.3.4 WIN NT 4.0 INTELORACLE 8.0.4 WIN NT 4.0 INTEL ORACLE 8.0.5 WIN NT 4.0 INTEL ORACLE 8.0.6 WIN NT 4.0 INTEL

SAP R/3 4.6B: ORACLE 8.0.5 WIN NT 4.0 INTELORACLE 8.0.6 WIN NT 4.0 INTELORACLE 8.1.6 WIN NT 4.0 INTEL ORACLE 8.1.7 WIN NT 4.0 INTELORACLE 8.1.6 WIN 2000 INTEL ORACLE 8.1.7 WIN 2000 INTEL SAP R/3 4.6C: ORACLE 8.0.5 WIN NT 4.0 INTELORACLE 8.0.6 WIN NT 4.0 INTELORACLE 8.1.6 WIN NT 4.0 INTEL ORACLE 8.1.7 WIN NT 4.0 INTEL ORACLE 8.1.6 WIN 2000 INTEL ORACLE 8.1.7 WIN 2000 INTEL

Page 11: ERDCI Sap Architecture Final

SAP support period

Please Upgrade SAP before the mention date

Page 12: ERDCI Sap Architecture Final

SAP R/3 CORE BUSINESS MODULES

•SAP R/3 applications usually categorized in three core functional areas FinancialLogisticsHuman Resource

Page 13: ERDCI Sap Architecture Final

Application Modules

•Financials   Financial Accounting (FI) Controlling (CO)   Asset Management (AM) Enterprise Controlling (EC) Capital Investment Management (IM) Treasury (TR)

•Logistics   Plant Maintenance (PM)   Quality Management (QM)   Production Planning (PP)   Materials Management (MM)   Sales and Distribution (SD) Project System (PS)

•Human Resources (HR) Personal Administration Personal Development

Page 14: ERDCI Sap Architecture Final

INDUSTRY SOLUTIONs (ADD-ON s)Additionally,SAP actively develops special software packages on top of R/3 ,targeted to specialized vertical industries.These packages are known as INDUSTRY SOLUTIONs (IS) .These packages are fully integrated with the rest of R/3 applications.SAP has the following IS packages like•IS-B: Sap Industry solution for Banks•IS-H: Sap Industry solution for Hospitals•IS-IS: Sap Industry solution for Insurance,Money,Foreign Exchange•IS-OIL: Sap Industry solution for Oil companies•IS-P: Sap Industry solution for Publishing sector•IS-PS: Sap Industry solution for Public sector•IS-Retail: Sap Industry solution for Retail•IS-T: Sap Industry solution for Telecommunication Sector

These IS-Packages are a collection of specific business processes,set of transactions,programs,screens,documentation's Which fully integrated with the R/3 applications.

Other solutions like CRM , SCM , BIW , PUBLIC-SECTOR etc. can integrate With the sap system .

Page 15: ERDCI Sap Architecture Final

Basis Software

R/3 BASIS Software is the set of programs & tools which interfaces

with the computer operating system ,database ,Application server &

and the presentation interfaces .

Basis software mainly R/3 common Kernel or R/3 Middle ware

which is the nucleus of a system known as the SAP KERNEL .

The main kernel directory in application server is

\usr\sap\<SID>\sys\exe\run

Page 16: ERDCI Sap Architecture Final

R/3 WORK PROCESS or SERVICES

In SAP naming convention , a service is a process or a group of work process .

Computing system i e running the particular Services known as a

server or Application server .

Page 17: ERDCI Sap Architecture Final

SERVICES in R/3

Page 18: ERDCI Sap Architecture Final

Dispatcher

DIALOG

MESSAGE

GATEWAY

SPOOL

ENQUEUE

BACKGRO

UPDATE

SAPGUI SAPGUI SAPGUI SAPGUI

DATABASE INSTANCE

Standard Work processes

Page 19: ERDCI Sap Architecture Final

The SAP dispatcher is the control program which manages the resources of the R/3 applications.

The main tasks of the dispatcher are as follows: Balanced assignment of the transaction load to the

appropriate work process

Buffer management in the main memory.

Connection with the presentation level.

Organization of the communication process.

Dispatcher processes

Page 20: ERDCI Sap Architecture Final

Dialog Step: A dialog step is a sap r/3 screen,which is represented by a dynamic program(dynpro) .A dynamic program consists of a screen and all the associated processing logic . When users are entered something on the screen & press enter ,they are actually making one dialog step .

The dialog work processes are in charge of interactive task of the R/3 System . A dialog process performs the dialog steps corresponding to the user interactive sessions.

The SAP profile parameter that controls the number of interactive Dialog Work Process per instance is rdisp/wp_no_dia

Dialog work processes(1)

Page 21: ERDCI Sap Architecture Final

Dialog work processes(2)

Page 22: ERDCI Sap Architecture Final

Update work Process

The update process is in charge of executingdatabase changes when requested by dialog orbackground work Processes.

Page 23: ERDCI Sap Architecture Final

Enqueue work Process

The enqueue work process is in charge of lockManagement system. It allows multiple applicationServices to synchronize the access to the databaseand maintain data consistency.

Page 24: ERDCI Sap Architecture Final

Background work Process

The background work processes are in charge ofexecuting ABAP/4 programs submitted forbackground execution.

The SAP profile parameter that controls thenumber of background work processes perinstance is rdisp/wp_no_btc

Page 25: ERDCI Sap Architecture Final

Message work Server

The message server is a service used by thedifferent Application servers to exchange dataand internal messages. The message serverroutes the messages between application servers.

Page 26: ERDCI Sap Architecture Final

Gateway work Server

The gateway server allows the communicationbetween the R/3, R/2 and external applications.

This service is a CPIC handler which implementsthe CPIC protocol for Communication. This iscommonly known as a gateway.

The function of the SAP gateway is to exchangelarger Amounts of data between applicationservers.

Page 27: ERDCI Sap Architecture Final

Spool work Process

The spool work process is in charge of formattingthe data for printing and passing it to the hostspool system.

The SAP profile parameter that controls thenumber of background work processes perinstance is rdisp/wp_no_spo

Page 28: ERDCI Sap Architecture Final

Name of the Services .Min Number of processes

Taken care by the parameters

Dialog Services (D) >=2 rdisp/wp_no_dia

Update Services (V) >=0rdisp/wp_no_vb,rdisp/wp_no_vb2

Enqueue (Lock management) (E) 0 or 1 rdisp/wp_no_enq

Background Process (B) >=1 rdisp/wp_no_btc

Message Server process (M) 0 or 1

Gateway services (G) >=1

Spool services (S) >=1 rdisp/wp_no_spo

Setting of R/3 WORK PROCESS

Page 29: ERDCI Sap Architecture Final

Process Overview

Page 30: ERDCI Sap Architecture Final

Logical flow of a execution of a user request

User enter data using SAPGUI

SAPGUI convert data to sap format & sent to dispatcher

Dispatcher keeps the requests in queues & process one by one

Dispatcher allocates user request to free work process

Real execution takes place inside work processes

End of execution, result goes back to Dispatcher

Dispatcher sends data to user using SAPGUI

1.

2.

3.

4.

5.

6.

7.

Time is taken from step1 to step 7 is known as RESPONSE TIME .

Page 31: ERDCI Sap Architecture Final

Basis Terminology (1)R/3 System

A R/3 System consists of combination of database server and the application servers .

SAP System Identification

The SAP System Identification, often referred to as the SAPSID, or SID, is a unique three-character code that identifies the R/3 System. SAP System Identification codes used are DEV for the development system, QAS for the quality assurance system, and PRD for the production system.

Client

A client is a legal and organizational entity in the R/3 System whose business management data is protected against unlawful access.

In addition, a client:

Has its own set of user data

Is a logical system with separate master records

Has its own set of table data on common table .

System Landscape

The landscape consists of all R/3 Systems (Instances) involved in the implementation project and client architectures that access (or share) a common transport directory.

Page 32: ERDCI Sap Architecture Final

Basis Terminology (2)Customizing

Customizing is the process of configuring the SAP R/3 System such that the R/3 functionality fits the company’s needs.

Database Server

This is where the database resides. Main data stores in this server .

Application Server

This is where R/3 application runs. On a 2 tiered system, this would be combined with the

database server.

Instance

An installation of R/3 on a application server .

GUI:

Graphical User Interface. The SAPgui is the software on users computer or local server that allows to connect to one or more of the SAP environments.

Page 33: ERDCI Sap Architecture Final

Disk Space Requirements

To configure a R/3 Release 4.X System, each database will require approximately 20

GB of disk space.

An application server will require approximately 2 GB of disk space .

A client with pure customizing data will require between 700 to 1500 MB.

If the client also contains application data, such as a production system, the storage

requirements can increase to several GB.

The disk space requirements can also be affected by the:

Relational database management system (RDBMS) selected

Number of clients in the system

Number of master data records

Number of transaction data records

Amount of historical data retained

Page 34: ERDCI Sap Architecture Final

Server Requirement for sap installation (Case study)

Machine TypeDEV Intel 80686 (Mod 8 Step 3)

PRD Intel 80686 (Mod 10 Step 1)

Processor DEV X86 Family 6 Model 8 Stepping 3 Genuine Intel ~789 Mhz

PRD X86 Family 6 Model 10 Stepping 1 Genuine Intel ~700 Mhz

Server Model DEV HP Net Server LC2000

PRD HP Net Server LH6000

Total Physical Memory

DEV 1GB

PRD 4 GB

Total Virtual Memory

DEV 6 GB

PRD 12 GB

Disk Space DEV 60 GB

PRD 130 GB

O.S. Windows 2000 , service pack 2

SAP R/3 Release

46C

Database Oracle 8.1.7.1.0

Page 35: ERDCI Sap Architecture Final

SAP R/3 Directory structure (1)

The physical parent directory of the whole sap application is /usr/sapTransport directory is /usr/sap/transSAP system parent directory <sapsid> , which is /usr/sap/SCMIf more than one sap system will installed on the same machine then additional directory will be created under /usr/sap/….. ..

These sap directories created by sap installation

DVEBMGS00

SCM

Page 36: ERDCI Sap Architecture Final

SAP R/3 Directory structure (2)

Sap mount directory is /sapmnt useful for sharing the common files with all system belonging to the same group .Mainly /sapmnt/scm indicates the directory /usr/sap/scmDirectory /sapmnt/scm/sys/exe/run it contains all sap runtime programs this directory also called sap kernel directory.Most of the program files in this directory are directly used by sap processesDirectory /sapmnt/scm/sys/profile which contains sap profile files like startup-profile ,default-profile & instance-profile. Directory /sapmnt/scm/sys/global which contains global or common data managed by the SAP application & shared by all instances ,all types of logs.

Page 37: ERDCI Sap Architecture Final

R/3 Client

When Sap installed it comes with 3 default clients with default users and default password.

Client User Default Password

000 SAP* 06071992000 DDIC 19920706001 SAP* 06071992001 DDIC 19920706066 EARLYWATCH SUPPORT

Page 38: ERDCI Sap Architecture Final

R/3 Data(1)CLIENT

000

CLIENT

066

CLIENT

001

CLIENT Independent customizing

SAP

Repository Object

An R/3 System is subdivided into clients .

In R/3 most of Customer business data in sub groups divided by clients ,these type of data is client dependent data When the SAP objects are just accessed by only one client, we define them as client dependant data.

Some data in R/3 which is shared by all client like R/3 repository data.This type of data is client independent data.

Page 39: ERDCI Sap Architecture Final

R/3 database can be divided into two logical components:• R/3 repository object • R/3 customer data

R/3 repository : central part of this is ABAP dictionary i.e. programs,screens, reports provided by sap or created or modified by sap user .

Customer data : customer data consists of any kind of data entered into r/3 by the customer in time of sap implementation or day to day business processing . Customizing dataThis data generated when r/3 is configured to meet the particular needs of the customer through customizing.Most customizing data is client-dependent some is independent .Application data Also known as business data ,which generated day by day business processing. Mainly master data , transaction data .User master data Records of R/3 users password & authorization

R/3 Data(2)

Page 40: ERDCI Sap Architecture Final

System strategies(1)

Combination of all the system is called SYSTEM LANDSCAPE .Three types of system landscape are

Single-system Landscape Two-system Landscape Three-system Landscape

•In time of system setup the question we have to face How many R/3 systems will be needed ? What function will be performed by each R/3 system in a system landscape ? How many clients will be needed by each R/3 system ? What role will each client play in the system Landscape ?

Three types of Environment needed for a system strategies Development environment (DEV) For development activities . Quality Assurance environment (QA) For extensive testing the developed or customized object .Mainly for integration testing purpose. Production environment (PRD) For actual company business transaction.

Page 41: ERDCI Sap Architecture Final

System strategies(2)

Single-system Landscape Development client , Testing client , Production Client on a same server . Advantages

•For this type of system , hardware cost & administrative cost is lower .

Disadvantages•Changes to client-independent or repository objects will affect the whole environment .

•The performance of the system affect all clients

•Production data is a accessible from development & testing environment

•Problems during the implementation of other applications , when some production is going on .

•Problems when modifying standard programs

•If the system crashes the all three R/3 systems will be affected .Most of the disadvantages with a one-system landscape are associated with client independent changes, repository changes, & upgrades , that immediately impact the production environment. These disadvantages are a much greater problem once the R/3 System is in a productive state.

Page 42: ERDCI Sap Architecture Final

System strategies(3)

Two-system Landscape For this case development & QA testing done on same system . But production on different system . Advantages•The production system (PRD) containing only the finalized production environment .

After completing the preparation phase (test, verification, and release), the parameters and programs can be transported from the development system (DEV) to the production system (PRD) . (DEV client QA client PRD System).

Minimal amount of hardware investment.

Minimal system administration and change request management required

Disadvantages•Recommended only for projects with a limited amount of ongoing development

•No separate quality assurance system (QAS) for isolated testing

•Client-independent customizing activity must be carefully planned so that, it does not affect other customizing/development activities

Page 43: ERDCI Sap Architecture Final

System strategies(4)Three -system Landscape In this case development ,QA , production take place on different system. The most recommended system in SAP .

Advantages

•New development can start without affecting the production environment.•QA system allows for integration testing of developments before promoted to production.•Production data is secure, security will prevent access to sensitive data & client settings will prevent the unauthorized changing of data .•Production performance is not affected by other clients, there is only one production client .•The general sandbox client (SAND) in the development system (DEV) makes it easier to become familiar with the new application functions and conduct suitability testing•Client-independent customizing testing can occur without conflicts

Disadvantages•Requires increased system administration and change management activities•Increase hardware cost

Page 44: ERDCI Sap Architecture Final

Transport management system

Within the R/3 System Landscape customizing & development changes performed, in a development client ,has to transfer to QAS client & PRD client .

SAP R/3 enables user to record changes to a CHANGE REQUEST ,which is distributed to other client or other R/3 system .

When changes to either customizing or repository objects are made,the changed objects are recorded to a TASK in a Change Request corresponding to a specific user .

After completion the development ,user release the Change Request & transport to QAS & PRD system .

Transport Directory \usr\sap\trans

DEV QAS PRD

Page 45: ERDCI Sap Architecture Final

SAP consultants

SAP consultants divide themselves into 3 categories FUNCTIONAL consultant BASIS consultant ABAP programmers

FUNCTIONAL consultant: Experienced people in some business areas who knows how to customize those modules to meet the customers need.

BASIS consultant: Technical consultants who taken care installation sap administration , database administration.

ABAP programmer: Technical consultant who writes sap programs & reports for any new requirements in sap by using ABAP/4 programming language.

Customizing : Once customer buy one sap-kit,it contains all the modules with all the business processes.the next step is to customize to suit business needs & practices.

ABAP/4 Advanced Business Application Programming (4GL)

ABAP/4 is a SAP programming language used in the development of all standard applications included with R/3 .SAP has designed a full purpose development environment known as ABAP/4 development workbench.

Page 46: ERDCI Sap Architecture Final

START WORKING ON SAP BASIS

Page 47: ERDCI Sap Architecture Final

SAP Screen Features(1)• SAP screen has seven main areas: Screen Header, Menu Bar, Standard Toolbar, Title Bar, either a Navigation Toolbar or Application Toolbar, Screen Body, and Status Bar..

Page 48: ERDCI Sap Architecture Final

Command Field The Command field is used to enter transaction codes

Standard Toolbar ButtonsThe SAP buttons displayed on the Toolbar provide quick access to commonly used SAP functions. If a Toolbar button is gray, it is not available for use on that particular screen.

SAP Screen Features(2)

Page 49: ERDCI Sap Architecture Final

OPENNING A SAP SESSION using saplogon-pad

• Navigation to opening a SAP session 1. Start Programs SAP Fronted SAPLogon 2. Choose any one of the icon ‘SAPlogon’ or ‘SAPlogon-pad’ from the desktop . Choose any server name e.g. ‘SCMA SERVER’ . Then the Sap screen will open & connect to the Application server defined on SAPlogon pad

Continue …..

Page 50: ERDCI Sap Architecture Final

Creating one new entry on SAP-logon

• Creation of new SAPLogon on logon-pad . We create giving the IP address & the system number which is the identification of the instance.`

Continue …..

Enter IP address of the application server & the system number

Page 51: ERDCI Sap Architecture Final

OPENNING A SAP SESSION using sap-session-manager

SAP front-end can be open using SAP Session Manager.

Choose Application server first .Enter Proper USERID,Client ID, Password & Language to open the sap session .

Page 52: ERDCI Sap Architecture Final

FIRST SCREEN ON SAP

Enter Proper Client id ,

User id , Password & Language to open thesap session .

Now start Working

Page 53: ERDCI Sap Architecture Final

Start work on Basis Start Basis Adminstration• Basis Administration• User Administration• Client Administration• Transport Management

SAP menu Tools Administration

Page 54: ERDCI Sap Architecture Final

Navigation Using Transaction Codes SAP provides a unique multi-character identifier for each system task. This shorthand name is called a transaction code which is a navigation alternative to using a menu path to get to a system task Transaction code may contain letters only, or a combination of letters and numbers. Used in conjunction with a prefix such as /n or /o . e.g . SPAM , SU01 . /n ends the current transaction and switches to the new one without saving any data in the current transaction . /o opens a new SAP session and accesses the new transaction without ending the current one (which will remain open in the background session)

Command field with transactionCode.

Page 55: ERDCI Sap Architecture Final

Transaction is an operation that lets a user make changes to a database .

In SAP transaction is a sequence of related steps ,are screens in which data is introduced causing the generation of other events.

The final task of a transaction is to modify the information which ultimately goes into the database. The database is not updated until a transaction has finished.

All the transactions in the R/3 system have an associated transaction code. All available transaction are held in table TSTC .To see the table data we can use the transaction codes SE16 / SE11 .

We can create user defined transaction code by using SE93 .

The Used transaction code by the user can be monitored using the transaction code STAT.

Transaction Code(1)

Page 56: ERDCI Sap Architecture Final

Transaction Code(2)

Transaction code SE93 to maintain TC.

User defined TC start with Y or Z

Page 57: ERDCI Sap Architecture Final

Transaction Code(3)

Transaction code STAT to monitor Transaction code used by any user

Page 58: ERDCI Sap Architecture Final

System Status

Navigation : Menu System Status

Page 59: ERDCI Sap Architecture Final

Client Maintenance Maintain client using the transaction code SCC4

Page 60: ERDCI Sap Architecture Final

User Maintenance

Create or maintain Userusing the transaction code SU01

Page 61: ERDCI Sap Architecture Final

Maintain Authorization Maintain User Authorization using transaction code PFCG

Page 62: ERDCI Sap Architecture Final

Configure & Maintain Transport Management System Maintain Transport management system using transaction code STMS .

Page 63: ERDCI Sap Architecture Final

Maintain Transport request Maintain Transport Request using transaction code SE01 .

Page 64: ERDCI Sap Architecture Final

Maintain RFC connection Maintain RFC connection using the transaction code SM59.

Page 65: ERDCI Sap Architecture Final

Maintain SAP Profile Maintain SAP Profile using the transaction code RZ10.

Page 66: ERDCI Sap Architecture Final

Maintain SAP table data Maintain SAP table using the transaction code SE11.

Page 67: ERDCI Sap Architecture Final

To monitoring Logon user with R/3 Can Monitor any user working or not using TC SM04.

Page 68: ERDCI Sap Architecture Final

To maintain the customizing setting within R/3 Create customizing setting by the transaction code SPRO

Page 69: ERDCI Sap Architecture Final

To upload support package to R/3 Upload the support packages using transaction code SPAM

Page 70: ERDCI Sap Architecture Final

To monitoring system log messages Monitor log of the system using transaction code SM21

Page 71: ERDCI Sap Architecture Final

Database backup scheduling Scheduling and monitoring database backup using TC DB13

Page 72: ERDCI Sap Architecture Final

Sending System Message Send system message to the sap users using TC SM02.

Page 73: ERDCI Sap Architecture Final

SAP SYSTEM STARTUP or SHUTDOWN(1)

Double click on the icon ‘SAP SYSTEM MANAGEMNT CONSOLE’ to START SAPMMC .

SAPMMCWhich used to start & stop sap application server .

Page 74: ERDCI Sap Architecture Final

SAP SYSTEM STARTUP or SHUTDOWN(2)

SAPMMC Right click the application server name (scma here) the start/stop option will come choosethe right one

SAPMMC When the sap system start properly then msg_server.exe & disp+work.exe will green & status will show Running .

Page 75: ERDCI Sap Architecture Final

SAP SYSTEM STARTUP or SHUTDOWN(3)

SAPDBA Sap startup/shutdown also can be done by using SAPDBA tool.

STARTUP/ SHUTDOWN can be done from operating system (dos prompt for WinNT) using the commands

C:\> startsap (Starting sap & db )C:\> stopsap (Stoping sap & db )C:\> startsap r\3 (Starting sap server only ,when db is running )C:\> stopsap r\3 (Stoping sap server only, but db will running )C:\> startsap db (Starting db only ,but sap will not start )C:\> stopsap db (Stoping db ,when sap already stopped )

SAPDBA tool can be invoke from operating system (dos prompt for WinNT) using the command C:\> sapdba

Page 76: ERDCI Sap Architecture Final

Roles of an Basis Admin(1)

Within R/3 : User administrator Set up and maintain user accounts New user setup Reset a password Lock or unlock a user Security administrator Create and maintain SAP security profiles Monitor and manage security access and violationsSystem administrator Create a system message Start or stop the system Maintain the health of the system Monitor system performance and logsTransport administrator Transport changes from one system to another Manage change requests

Page 77: ERDCI Sap Architecture Final

Roles of an Basis Admin(2)

Within R/3 :Batch scheduler Create and manage the scheduling of batch jobsBackup operator Schedule, run, and monitor backup jobs of the SAP database and any required operating system level files Disaster recovery technical manager Create, test, and execute the SAP disaster recovery plan Programmer Apply Online Service System note fixes to programs Data Dictionary (DDIC) manager Change the Data Dictionary (when applicable)

Page 78: ERDCI Sap Architecture Final

Roles of an Basis Admin(3)

Outside R/3 : DBA for the specific database on which the system is running Manage database specific tasks Maintain the database’s health and integrityOperating system administrator Manage the operating system access and user IDs Manage operating system specific tasksDesktop support Supports the user’s desktop PC

Maintenance R/3Changing system profile parametersApplying hot packages or legal change patchesUpgrading the kernelClient copy (create, copy, and delete)Transporting objects from system to system

Page 79: ERDCI Sap Architecture Final

SAP Today

4th largest software vendor in the world

30+ years of business experience

7,500+ customers in 90+ countries

13,000+ R/3 installations 1,400+ R/2 installations ~13,000 employees

Worldwide presence in over 50 countries outside Germany

SAP WORLWIDE HEADQUARTER ADDRESS : SAP AG Germany Neurottstrass 16, D –69190 Walldorf ,Germany Phone : 06227 –34 –0 Web site : www.sap.com www.sap-ag.de