SAP R3 Sysadminstartor

System Administration Made Easy
Microsoft®SQL Server TM
R/3 System Release 4.6A/B
ST
SAP Labs, Inc.
Palo Alto, California
Copyright
© 2000 by SAP AG. All rights reserved.

Neither this documentation nor any part of it may be copied or reproduced in any form or by any means or translated
into another language, without the prior consent of SAP AG.
SAP AG makes no warranties or representations with respect to the content hereof and specifically disclaims any
implied warranties of merchantability or fitness for any particular purpose. SAP AG assumes no responsibility for any
errors that may appear in this document. The information contained in this document is subject to change without
notice. SAP AG reserves the right to make any such changes without obligation to notify any person of such revision or
changes. SAP AG makes no commitment to keep the information contained herein up to date.
Trademarks
SAP, the SAP logo, R/2, R/3, ABAP, and other SAP-related products mentioned herein are registered or
unregistered trademarks of SAP AG. All other products mentioned in this document are registered or unregistered
trademarks of their respective companies.
Simplification Group
SAP Labs, Inc. 3475
Deer Creek Road Palo
Alto, CA 94304
www.saplabs.com/simple
simplify-r3@sap.com
Printed in the United States of America.

ISBN 1-893570-43-6
o This book uses EcoFLEX lay-flat binding. With this lay-flat feature—developed by and exclusively available
at Johnson Printing Service (JPS)—you can open this book and keep it open without it snapping shut on you.
You need not worry about breaking the spine. EcoFLEX makes books like this one easier to use.
Contents at a Glance
Introduction xxi
R/3 System Administration Basics 1-1
Chapter 1:
Disaster Recovery......................................................................................2-1
Chapter 2:
Backup and Recovery................................................................................3-1
Chapter 3:
Scheduled Daily Tasks...............................................................................4-1
Chapter 4:
Scheduled Weekly Tasks...........................................................................5-1
Chapter 5:
Scheduled Monthly Tasks..........................................................................6-1
Chapter 6:
Scheduled Quarterly Tasks........................................................................7-1
Chapter 7:
Scheduled Annual Tasks............................................................................8-1
Chapter 8:
Multi-Role Tasks.........................................................................................9-1
Chapter 9:
R/3 System Administration......................................................................10-1
Chapter 10:
Security Administration...........................................................................11-1
Chapter 11:
User Administration.................................................................................12-1
Chapter 12:
Database Administration - Microsoft SQL Server..................................13-1
Chapter 13:
Output Management.................................................................................14-1
Chapter 14:
Network/OS/Server Administration.........................................................15-1
Chapter 15:
Operations.................................................................................................16-1
Chapter 16:
Change Management................................................................................17-1
Chapter 17:
Troubleshooting.......................................................................................18-1
Chapter 18:
Performance..............................................................................................19-1
Chapter 19:
SAPNet—Web Frontend...........................................................................20-1
Chapter 20:
SAPNet-R/3 Frontend...............................................................................21-1
Chapter 21:
Remote Services.......................................................................................22-1
Chapter 22:
Special Maintenance.................................................................................23-1
Chapter 23:
Useful Transactions..................................................................................A-1
Appendix A:
Useful Resources and Products B-1
Appendix B:
Useful SAP Notes......................................................................................C-1
Appendix C:
Upgrade Discussion..................................................................................D-1
Appendix D:
..............................................................................................................................1-1
Index
System Administration Made Easy iii

Contents at a Glance
4.6A/B iv Release
Detailed Table of Contents
Acknowledgements..............................................................................................................................xix
Introduction xxi
What Is This Guidebook About?............................................................................xxii
Who Should Read This Book?...............................................................................xxii
Prerequisites.............................................................................................................xxiii
System..................................................................................................................xxiv
Organization...........................................................................................................xxv
Content..................................................................................................................xxv
Conventions..............................................................................................................xxvi
Special Icons.........................................................................................................xxvii
Chapter 1: R/3 System Administration Basics ............................................................................1-1
Overview..................................................................................................................1-2
Roles of an R/3 System Administrator..................................................................1-2
Within R/3..................................................................................................................1-2
External to R/3..........................................................................................................1-3
Traits of an R/3 System Administrator..................................................................1-4
R/3 System Guidelines............................................................................................1-4
Protect the System....................................................................................................1-5
Do Not Be Afraid to Ask for Help...............................................................................1-5
Network with Other Customers and Consultants......................................................1-6
Keep It Short and Simple (KISS)...............................................................................1-7
Keep Proper Documentation.....................................................................................1-7
Use Checklists..........................................................................................................1-8
Use the Appropriate Tool for the Job.........................................................................1-9
Perform Preventive Maintenance..............................................................................1-9
Do Not Change What You Do Not Have To............................................................1-10
Do Not Make System Changes During Critical Periods..........................................1-11
Do Not Allow Direct Database Access....................................................................1-12
Keep all Non-SAP Activity Off the R/3 Servers.......................................................1-12
Minimize Single Points of Failure............................................................................1-13
Corollaries to Murphy’s Law................................................................................1-13
Special Definitions................................................................................................1-14
Application server...............................................................................................1-14
System................................................................................................................1-14
Chapter 2: Disaster Recovery.......................................................................................................2-1

System Administration Made Easy v
Overview .................................................................................................................. 2–2

What Is a Disaster? .................................................................................................. 2–2
Why Plan for a Disaster? ........................................................................................ 2–3
Planning for a Disaster ........................................................................................... 2–4
Creating a Plan ......................................................................................................... 2–4
What Are the Business Requirements for Disaster Recovery? ................................. 2–4
Who will provide the requirements? ............................................................................ 2–4
What are the requirements? ....................................................................................... 2–4
When Should a Disaster Recovery Procedure Begin? ............................................. 2–5
Expected Downtime or Recovery Time ..................................................................... 2–5
Expected Downtime .............................................................................................. 2–5
Recovery Time ..................................................................................................... 2–6
Recovery Group and Staffing Roles ......................................................................... 2–6
Types of Disaster Recovery ...................................................................................... 2–7
Onsite ................................................................................................................... 2–7
Offsite ................................................................................................................... 2–7
Disaster Scenarios .................................................................................................... 2–8
Three Common Disaster Scenarios .......................................................................... 2–8
A Corrupt Database ............................................................................................. 2–8
A Hardware Failure .............................................................................................. 2–8
A Complete Loss or Destruction of the Server Facility ......................................... 2–9
Recovery Script ...................................................................................................... 2–10
Creating a Recovery Script .....................................................................................
Recovery Process ...................................................................................................
Major Steps
............................................................................................................................
Crash Kit .................................................................................................................
Business Continuation During Recovery
Offsite Disaster
Integration Recovery
with your Company’sSites General Disaster Planning ..................................
When the R/3 System Returns ...............................................................................
Test your Disaster Recovery Procedure .............................................................
Other Considerations ...........................................................................................
Other Upstream or Downstream Applications .........................................................
Backup Sites ...........................................................................................................
Minimizing the Chances for a Disaster ...............................................................
Minimize Human Error ............................................................................................
Minimize Single Points of Failure ............................................................................
Cascade Failures ....................................................................................................
2–10 2–10 2–10 2–11 2–14 2–15
2–15 2–15
2–15
2–16
2–16 2–17
2–17
2–17 2–18 2–18
Chapter 3: Backup and Recovery.................................3-1
Overview..................................................................................................................3-2
Restore.....................................................................................................................3-2
Strategy.....................................................................................................................3-2
Testing Recovery..................................................................................................3-3
Backup.....................................................................................................................3-3
Transaction Logs..................................................................................................3-5
Operating System Level Files................................................................................3-6
Backup Types...........................................................................................................3-6
What Is Backed Up...............................................................................................3-7
How the Backup Is Taken......................................................................................3-8
vi Release 4.6A/B
Backup Strategy Design............................................................................................3-9

Supplementary Backups......................................................................................3-10
General Procedures................................................................................................3-10
Backup................................................................................................................3-10
Transaction Log Backup.....................................................................................3-10
Verifying Backups...............................................................................................3-10
Monitoring/Controlling.........................................................................................3-11
Design Recommendations......................................................................................3-12
Backup Procedures and Policies.........................................................................3-13

Tape Management.................................................................................................3-13
Tracking..............................................................................................................3-15
Handling..............................................................................................................3-16
Retention Requirements.........................................................................................3-17
Recommendations..............................................................................................3-18
Storage....................................................................................................................3-18
Performance..........................................................................................................3-20
Backup....................................................................................................................3-20
Backup Options.......................................................................................................3-21
Back Up to Faster Devices.................................................................................3-21
Parallel Backup...................................................................................................3-22
Backing Up to Disks, Then to Tape....................................................................3-22
Restore Options......................................................................................................3-23
Useful SAP Notes..................................................................................................3-24
Chapter 4: Scheduled Daily Tasks................................................................................................4-1
Overview..................................................................................................................4-2
Critical Tasks...........................................................................................................4-3
The R/3 System........................................................................................................4-4
Database..................................................................................................................4-6
Operating System....................................................................................................4-6
Other.........................................................................................................................4-7
Notes........................................................................................................................4-7
The R/3 System........................................................................................................4-8
Critical Tasks...........................................................................................................4-9
Verify that the Backups Ran Successfully.................................................................4-9
OS Monitor (Transaction OS06)..............................................................................4-11

Select Background Jobs/Graphical Job Monitor (Transaction SM37/RZ01)............4-11
CCMS Alert Monitor (Transaction RZ20)................................................................4-11
Lock Entry List (Transaction SM12)........................................................................4-12
System Administration Made Easy vii

vii
Update Records (Transaction SM13)......................................................................4-12

System Log (Transaction SM21).............................................................................4-13
Batch Input (Transaction SM35)..............................................................................4-13
Work Processes (Transactions SM50 and SM51)...................................................4-14
Spool (Transaction SP01).......................................................................................4-14
Tune Summary (Transaction ST02)........................................................................4-14
Workload Analysis of <SID> (Transaction ST03)....................................................4-14
Database Performance Analysis (Transaction ST04).............................................4-15
ABAP Dump Analysis (Transaction ST22)..............................................................4-15
Chapter 5: Scheduled Weekly Tasks............................................................................................5-1

The R/3 System........................................................................................................5-2
Database..................................................................................................................5-3
Other.........................................................................................................................5-3
Notes........................................................................................................................5-4
Database Performance (Transaction DB02).............................................................5-4
CCMS Alert Monitor (Transaction RZ20)...................................................................5-4
Spool (Transaction SP01).........................................................................................5-4
TemSe (Transaction SP12).......................................................................................5-5
Transaction STMS (TMS System).............................................................................5-5
Chapter 6: Scheduled Monthly Tasks...........................................................................................6-1
The R/3 System........................................................................................................6-2
Database..................................................................................................................6-2
Other.........................................................................................................................6-4
Notes........................................................................................................................6-5
Database Performance (Transaction DB02).............................................................6-5
Chapter 7: Scheduled Quarterly Tasks.........................................................................................7-1
The R/3 System........................................................................................................7-2
Database..................................................................................................................7-3
Other.........................................................................................................................7-4
Notes........................................................................................................................7-4
Edit System Profile Parameters (Transaction RZ10)................................................7-4
Select Background Jobs (Transaction SM37)...........................................................7-5
User Maintenance (Transaction SU01).....................................................................7-5
Chapter 8: Scheduled Annual Tasks............................................................................................8-1

The R/3 System........................................................................................................8-2
Database..................................................................................................................8-3
Other.........................................................................................................................8-4
Notes........................................................................................................................8-4
Transaction SA38/SE38............................................................................................8-4
Transaction SE03/SCC4............................................................................................8-4
viii Release 4.6A/B

Chapter 9: Multi-Role Tasks..........................................................................................................9-1

Starting the R/3 System..........................................................................................9-2
Start R/3—NT............................................................................................................9-3
Stopping the R/3 System........................................................................................9-5
Tasks to Be Completed Before Stopping the System...............................................9-6
Check that No Active Users Are on the System (AL08/SM04)..............................9-9

Check for Batch Jobs Running or Scheduled (SM37).........................................9-11
Check for Active Processes on All Systems (SM51)..........................................9-15
Check for External Interfaces..............................................................................9-15
Stopping R/3...........................................................................................................9-16
STOP R/3—NT...................................................................................................9-16
Chapter 10: R/3 System Administration.......................................................................................10-1
Overview................................................................................................................10-2
Major System Monitoring Tools...........................................................................10-2
CCMS Central Alert Monitor (Transaction RZ20)....................................................10-2
Accessing the CCMS Alert Monitor (RZ20).........................................................10-4
Current View and Alert View...............................................................................10-5
Switching Between the Current and Alert Views.................................................10-6
Configuring the Batch Job to Collect Historical Data (RZ21)............................10-10

View the Alerts..................................................................................................10-12
Acknowledge the Alert......................................................................................10-14

Provide System Configuration Information (Transaction RZ20)........................10-15
Maintaining The Alert Thresholds for RZ20........................................................10-17
Hiding SAP Standard Monitor Sets...................................................................10-19
Add a Monitor to the Monitor Set......................................................................10-24

System Administration Assistant (Transaction SSAA)..........................................10-28
Specific Transaction Monitoring Overview.......................................................10-32
Failed Updates (Transaction SM13).....................................................................10-32
Managing Update Terminates...........................................................................10-35
System Log (Transaction SM21)...........................................................................10-38

Locks (Transaction SM12)....................................................................................10-41
Active Users (Transactions SM04 and AL08)........................................................10-43
Single-Instance System (Transaction SM04)....................................................10-44
Multi-Instance System (Transaction AL08).......................................................10-45
Work Processes (Transactions SM50 and SM51).................................................10-46
For a System with Application Servers..............................................................10-46
For a System Without Application Servers.......................................................10-47
ABAP Dump Analysis (Transaction ST22)............................................................10-48
Simple Selection...............................................................................................10-49
Free Selection...................................................................................................10-49
System Message (SM02).....................................................................................10-51
Creating a Message..............................................................................................10-52
Editing a Message.................................................................................................10-54
ABAP Editor (SE38)..............................................................................................10-55
For Information About a Program or Report.....................................................10-56
System Administration Made Easy ix

Chapter 11: Security Administration............................................................................................11-1

Overview................................................................................................................11-2
Keeping Unauthorized People out of the System...............................................11-2

Keeping People out of Places Where They Should Not Be................................11-2
Safeguarding the Data from Damage or Loss.....................................................11-3
Complying with Legal, Regulatory, and Other Requirements.............................11-3
Audits.....................................................................................................................11-4
Financial Audit........................................................................................................11-4
Audit Considerations...............................................................................................11-5
Security Layers.....................................................................................................11-6
Access Security.......................................................................................................11-7
Application Security............................................................................................11-9
Operational Security................................................................................................11-9
Data Security........................................................................................................11-10
Application or R/3 Security....................................................................................11-11
Prevent Multiple User Logins.............................................................................11-11

Preventing Changes in the Production System.....................................................11-11
Setting the Production System to “Not Modifiable” (Transactions SE03, SCC4)11-13
Client-Independent Changes (Transaction SE03)............................................11-14
Client-Independent and Client-Dependent Changes (SCC4)............................11-15
Verifying that Dangerous Transactions Are Locked..............................................11-17
To List Locked Transactions.............................................................................11-24
Operational Security...........................................................................................11-25
Segregation of Duties............................................................................................11-25
Restricting Access to SAP* or DDIC.....................................................................11-26
Change Management............................................................................................11-27
Password Issues and Tasks.................................................................................11-28

Setting Password Standards Using Transaction RZ10.....................................11-29
Eliminating Some Easy Passwords...................................................................11-29
Maintaining a Table of Prohibited Passwords...................................................11-30
Recording System Passwords...........................................................................11-31
NT.....................................................................................................................11-35
Databases.........................................................................................................11-36
DB2...................................................................................................................11-36
Informix.............................................................................................................11-36
Oracle/UNIX......................................................................................................11-36
Audit Tools..........................................................................................................11-37
Audit Information System (Transaction SECR).....................................................11-37
Complete Audit.................................................................................................11-38
Running the Audit Log......................................................................................11-46

Setting Security Audit Log Parameters (SM19).....................................................11-47
Release 4.6A/B
User Security Audit Jobs.......................................................................................11-54

Audit Tasks..........................................................................................................11-57
Review that all Named Users are Valid.................................................................11-57
Reviewing Profiles for Accuracy and Permission Creep.......................................11-58
Chapter 12: User Administration..................................................................................................12-1

Overview................................................................................................................12-2
User Groups............................................................................................................12-2
Profile Generator.....................................................................................................12-2
Recommended Policies and Procedures............................................................12-3
User Administration.................................................................................................12-3
System Administration.............................................................................................12-5
New User Setup.....................................................................................................12-7
Prerequisites...........................................................................................................12-7
General Process or Procedure...........................................................................12-7
The User’s Desktop............................................................................................12-7
Recommended Prerequisite for the GUI Installation...........................................12-7

Installing the Frontend Software-SAP GUI..............................................................12-8
Installing SAP GUI from a File Server.................................................................12-8
Installing SAP GUI from the Presentation CD....................................................12-14
To Add Additional Systems in the SAP Logon..................................................12-15

Setting Up a New User (SU01).............................................................................12-16
Copying an Existing User (SU01)......................................................................12-16
Creating a New User (SU01).............................................................................12-21
Maintaining a User (SU01)..................................................................................12-24
Resetting a Password (SU01).............................................................................12-26
Locking or Unlocking a User (SU01).................................................................12-27
User Groups.........................................................................................................12-29
How to Create a User Group (SU01)....................................................................12-30
Deleting a User’s Session (Transaction SM04)................................................12-32
How to Terminate a User Session........................................................................12-33
Active Users (Transactions SM04 and AL08)........................................................12-34
Single-Instance System (Transaction SM04)....................................................12-35
Multi-Instance System (Transaction AL08).......................................................12-36
Chapter 13: Database Administration - Microsoft SQL Server..................................................13-1
Overview................................................................................................................13-2
Starting and Stopping the Database....................................................................13-2
Starting the Database..............................................................................................13-2
Stopping the Database............................................................................................13-3
Overview.................................................................................................................13-4
Database Activity (ST04).........................................................................................13-4
Database Allocation (DB02)....................................................................................13-7
Scheduling Database Tasks (DB13).....................................................................13-9
System Administration Made Easy xi

Determining the Tape (Label) Necessary for a Backup.........................................13-13

Deleting an Entry from the Planning Calendar (DB13)..........................................13-14
Checking the Database Backup (DB12).............................................................13-15
Database Backups with Microsoft Tools...........................................................13-19

Online Backup - Using SQLServer 7.0 Enterprise Manager..................................13-19
Offline Backup - Using NTBackup.........................................................................13-24
Database Error Logs...........................................................................................13-28
R/3 - ST04.............................................................................................................13-28
Microsoft SQL Server 7.0 - Enterprise Manager...................................................13-28
Verify Database Consistency.............................................................................13-29
Run Update Statistics.........................................................................................13-29
System passwords..............................................................................................13-30
Chapter 14: Output Management..................................................................................................14-1

Contents.................................................................................................................14-1
How to Set Up the Printer in the R/3 System......................................................14-2

Check the Spool for Printing Problems (Transaction SP01).............................14-9
Check that Old Spools are Deleted (SP01)........................................................14-12
Printing the Output (SP01).................................................................................14-15
Printing the Screen.............................................................................................14-18
Check Spool Consistency (SPAD).....................................................................14-21
Check TemSe Consistency (SP12).....................................................................14-23
Chapter 15: Network/OS/Server Administration.........................................................................15-1

Overview................................................................................................................15-2
Operating System Alert (AL16)...............................................................................15-2

System Logs (OS06)...............................................................................................15-3
NT Event Logs....................................................................................................15-5
Checking File System Space Usage (RZ20)...........................................................15-6
Changing the Alert Threshold (RZ20).....................................................................15-9
Cleaning Out Old Transport Files..........................................................................15-11
Other Tasks.........................................................................................................15-12
Clean the Tape Drive............................................................................................15-12
Uninterruptible Power Supply................................................................................15-13
Check the Uninterruptible Power Supply..........................................................15-13
Check your UPS Shutdown Process..................................................................15-13
Check Maintenance Contracts..............................................................................15-14
Review Hardware or a System Monitor Paging System........................................15-15
Chapter 16: Operations.................................................................................................................16-1
Overview................................................................................................................16-2
Check that All Application Servers Are Up (Transaction SM51).......................16-2
Performance.......................................................................................................16-4
xii Release 4.6A/B

Housekeeping Jobs............................................................................................16-4
Others.................................................................................................................16-5
Performance Factors for Background Jobs.............................................................16-5
Creating and Scheduling a Batch Job (SM36)........................................................16-8
Background Jobs (SM37)...................................................................................16-15
Checking the Job Log.......................................................................................16-17
Graphical Job Monitor (Transaction RZ01)...........................................................16-19

Batch Input Jobs, New or Incorrect (SM35)...........................................................16-20
Operation Modes.................................................................................................16-21
To Define the Operation Mode (RZ04)..................................................................16-23
Assign an Instance Definition to an Operation Mode (RZ04).................................16-25
The First Time You Generate an Instance Operation Mode.............................16-25
Adding a New Operation Mode.........................................................................16-26
Defining Distribution of Work Processes (RZ04)...................................................16-29
Assigning Operation Modes (SM63)......................................................................16-32
Backups...............................................................................................................16-36
Periodic Archivals.................................................................................................16-36
Backup the Database............................................................................................16-36
Performing a Full Server Backup..........................................................................16-36
Checking the Backups (DB12 & DB13).................................................................16-38
Operating System Level Backups.....................................................................16-40
NT.....................................................................................................................16-40
Checking Consumable Supplies........................................................................16-42
Chapter 17: Change Management................................................................................................17-1

Table Maintenance (Transaction SM31)..............................................................17-2
Creating an Entry in the Table (SM31)....................................................................17-2
Deleting an Entry from a Table (SM31)...................................................................17-6
Change Control.....................................................................................................17-9
Managing SAP Notes............................................................................................17-9
Change Control (Managing Transports)............................................................17-12
Transporting Objects..........................................................................................17-15
Transports into the Production System.................................................................17-15
Transporting Objects.............................................................................................17-15
TMS Method......................................................................................................17-16
Operating System Method................................................................................17-16
Standard Transport Process.................................................................................17-17
Importing the Entire Import Buffer.....................................................................17-18
Special Transports from SAP................................................................................17-18
Releasing a Request (Transport)..........................................................................17-19
TMS Method of Transporting.................................................................................17-24
The Main TMS Screen......................................................................................17-24
Adding a Special Transport into the Import Buffer............................................17-25
Using TMS to Import a Transport Request.......................................................17-27
Check the Transport Log..................................................................................17-32
OS Method of Transporting...................................................................................17-34
Adding a Special Transport Into the Import Buffer............................................17-34
Checking the Transport Log (Transaction SE10)..............................................17-35
System Administration Made Easy xiiix

Chapter 18: Troubleshooting........................................................................................................18-1

Overview................................................................................................................18-2
Basic Troubleshooting Techniques.....................................................................18-2
Gather Data........................................................................................................18-2
Evaluate the Alternatives....................................................................................18-3

Make only One Change at a Time.......................................................................18-3
Document the Changes......................................................................................18-3
Get the Complete Error Message............................................................................18-4
Get the SAP Patch Level.........................................................................................18-5
Determining What Support Packages Have Been Applied......................................18-6
Chapter 19: Performance..............................................................................................................19-1

Overview................................................................................................................19-2
Critical Assumption.................................................................................................19-2
General Procedure................................................................................................19-3
R/3...........................................................................................................................19-4
Workload Analysis of the System (Transaction ST03)............................................19-4
Buffers (ST02).........................................................................................................19-8
Memory Defragmentation......................................................................................19-10
Database..............................................................................................................19-11
Operating System................................................................................................19-11
Operating System Monitor (OS07)........................................................................19-11
Hardware..............................................................................................................19-15
CPU and Disk........................................................................................................19-15
Memory.................................................................................................................19-15
Chapter 20: SAP Net—Web Frontend..........................................................................................20-1
Overview................................................................................................................20-2
Logging on to SAPNet..........................................................................................20-3
Solving a Problem with SAPNet...........................................................................20-5
Entering Customer Messages.................................................................................20-9

How...................................................................................................................20-11
Viewing Customer Messages................................................................................20-13
Viewing Customer Messages...........................................................................20-14
Registering a Developer or Object....................................................................20-15
Registering a Developer........................................................................................20-15
Developer Requests Developer Key.................................................................20-16
The System Administrator Gets the Access Key...............................................20-16
Registering a Developer...................................................................................20-17
Deleting a Developer.............................................................................................20-19
Registering an Object............................................................................................20-19
Developer Requests Object Key.......................................................................20-20
The System Administrator Gets the Access Key:..............................................20-20
xiv Release 4.6A/B

Chapter 21: Delete an Object...................................................................................................20-23

Online Correction Support.................................................................................20-24
Getting the Latest SPAM version..........................................................................20-25
Downloading Support Packages...........................................................................20-27
Specific Support Package-Related Notes.........................................................20-28
Downloading Suppor Packages........................................................................20-30
SAPNet-R/3 Frontend...........................................................................................21-1
Overview................................................................................................................21-2
Useful SAP Notes..................................................................................................21-3
Connecting to SAPNet-R/3...................................................................................21-3
Researching a Problem with SAPNet-R/3............................................................21-6
Finding Notes in the SAPNet-R/3............................................................................21-6
Entering Customer Messages (Problems) into SAPNet-R/3.................................21-10
Getting Status on Your Message..........................................................................21-15
Review the Action Log......................................................................................21-16
Display Long Text.............................................................................................21-17
Registering a Developer or Object....................................................................21-22

Registering a Developer........................................................................................21-22
Developer Requests Developer Key.................................................................21-23
Chapter 22: Registering an Object...........................................................................................21-26

Developer Requests Object Key.......................................................................21-26
Opening a Service Connection..........................................................................21-30

Order of Access to Systems.............................................................................21-30
Remote Services...................................................................................................22-1
Overview................................................................................................................22-2
Retrieving Files from SAP, SAPSERV4...............................................................22-2
Connecting to SAPSERV4 Using a GUI (NT)..........................................................22-3
An Example of an FTP Client..................................................................................22-4
Connecting to SAPSERV4 Using the Command Prompt........................................22-6
Navigating in SAPSERV4...................................................................................22-6
Connecting at the Command Prompt......................................................................22-6
Chapter 23: Downloading Files...................................................................................................22-9
Partial Organization of SAPSERV4.......................................................................22-10
Unpacking a File...............................................................................................22-13
Special SAPNet Notes..........................................................................................22-14
EarlyWatch Session............................................................................................22-14
Special Maintenance.............................................................................................23-1
Overview................................................................................................................23-2
Changing Parameters (Transaction RZ10)...........................................................................23-2
System Profile Support Packages...............................................................................................23-11
System Administration Made XV

Easy
Strategy.................................................................................................................23-12
High-Level Process of Applying Support Packages..............................................23-12
Determining What Support Packages Have Been Applied...................................23-13
Getting Information on the Support Package from SAPNet-R/3............................23-15
Requesting SPAM or a Support Package from SAPNet-R/3.................................23-22

Downloading a Support Package (Hot Package) - SAPNet-R/3.......................23-24
Uploading the Support Package from a CD or SAPNet-Web................................23-25
Support Package Collection CD.......................................................................23-26
SAPNet-Web....................................................................................................23-26
Updating SPAM....................................................................................................23-29
Applying the Support Package..............................................................................23-31
Object Conflicts.....................................................................................................23-37
Useful SAPNet - R/3 Frontend Notes....................................................................23-39

Kernel Upgrade...................................................................................................23-40
Client Copy..........................................................................................................23-42
Special Notes....................................................................................................23-42
Useful SAP Notes.............................................................................................23-43
Creating a Client...................................................................................................23-44
Copying a Client....................................................................................................23-47
Copying on the Same System/SID...................................................................23-47
Copying to a Different System/SID....................................................................23-50
Post-Client Copy Tasks........................................................................................23-52
Deleting a Client....................................................................................................23-52
Reviewing the Client Copy Log.........................................................................23-54

Production Refresh Strategies...........................................................................23-56
Database Copy of Production System..................................................................23-57
Benefits.............................................................................................................23-57
Disadvantages..................................................................................................23-57
Client Copy of the Production System with Data...................................................23-57
Advantages.......................................................................................................23-57
Disadvantages..................................................................................................23-57
Client Copy of the Production System - Without Data...........................................23-58
Advantages.......................................................................................................23-58
Disadvantages..................................................................................................23-58
Appendix A: Useful Transactions...................................................................................................A-1

Useful Transactions................................................................................................A-2
Transaction Code Switches.......................................................................................A-2
Transaction Code Table............................................................................................A-2
Appendix B: Useful Resources and Products...............................................................................B-1

Other System Administration Resources.............................................................B-2
SAP Resources.........................................................................................................B-2
Books....................................................................................................................B-3
CDs.......................................................................................................................B-4
Training Classes.................................................................................................B-4
xvi Release 4.6A/B

Other.....................................................................................................................B-5
White papers.........................................................................................................B-5
SAPNet, Selected Items of Interest......................................................................B-5
Third-Party Resources..............................................................................................B-7
Books:...................................................................................................................B-7
R/3........................................................................................................................B-7
UNIX.....................................................................................................................B-8
NT.........................................................................................................................B-8
OS/400..................................................................................................................B-9
Microsoft SQL Server...........................................................................................B-9
Informix.................................................................................................................B-9
DB2.....................................................................................................................B-10
Oracle.................................................................................................................B-10
Other Topics.......................................................................................................B-10
Magazines:..........................................................................................................B—11
Helpful Third-Party Information............................................................................B—11
Web Sites................................................................................................................B-11
SAP.....................................................................................................................B—11
SAP Affiliated......................................................................................................B-12
Third Party..........................................................................................................B-12
Internet News Groups.............................................................................................B-12
Other Resources.....................................................................................................B-13
Operating System...............................................................................................B-13
Database.............................................................................................................B-13
Other Helpful Products: Contributed by Users...................................................B-13
UNIX.......................................................................................................................B-14
Backup................................................................................................................B-14
Monitor................................................................................................................B-14
Scheduler............................................................................................................B-14
Spool Management.............................................................................................B-14
Other...................................................................................................................B-14
NT...........................................................................................................................B-14
Backup................................................................................................................B-14
Monitor................................................................................................................B-14
Remote Control...................................................................................................B-15
Scheduler............................................................................................................B-15
Spool Management.............................................................................................B-15
Other...................................................................................................................B-15
Common, Both UNIX and NT..................................................................................B-15
Network...................................................................................................................B-16
Appendix C: Useful SAP Notes.......................................................................................................C-1
Overview..................................................................................................................C-2
R/3 Notes..................................................................................................................C-2
Operating System Notes.........................................................................................C-6
Common to Multiple Operating Systems...................................................................C-6
NT.............................................................................................................................C-6
UNIX.........................................................................................................................C-8
AS-400......................................................................................................................C-8
Database Notes.......................................................................................................C-9
MS SQL server.........................................................................................................C-9
DB2 / UDB..............................................................................................................C-11
Informix...................................................................................................................C-12
Oracle.....................................................................................................................C-13

Appendix D: Upgrade Discussion...................................................................................................D-1

Upgrade Discussion................................................................................................D-2
Reasons Not to Upgrade...........................................................................................D-2
When to Upgrade......................................................................................................D-2
Upgrade Issues........................................................................................................D-3
Other Considerations..............................................................................................D-3
Software Issues.........................................................................................................D-3
Hardware..................................................................................................................D-3
Performance..............................................................................................................D-4
Index ..............................................................................................................................1-1
xviii Release 4.6A/B

Acknowledgements
The combined experience in SAP and general systems administration of those who contributed to this book is
measured in decades. I hope that I am able to share with you some of their wisdom.
I also wish to express appreciation to the following individuals who provided time, material, expertise, and resources
which helped make the Release 4.6A/B guidebook possible:
Customers and partners: Bill Robichaud, Bridgestone/Firestone; Chad Horwedel, XXX; Doris Steckel, Agilent/HP;
Gary Canez, Motorola; Hanumantha Kasoji, Celanese Acetate; John Blair, Steelcase; Joyce Courtney, Infineon; Laura
Shieh, John Muir Mt Diablo Health System; Kerry Ek, Finteck; Lynne Lollis, e.coetry/Chaptec; Otis Barr, Ceridian;
Paul Wiebe, TransAlta; Richard Doctor, Acuson; Sam Yamakoshi, Timothy Rogers; Tony Schollum, Ernst & Young;
Thomas Beam, NCUA; HP; Udesh Naicker, HP.
SAP AG: Andreas Graesser, Dr. Arnold Niedermaier, Dr. Carsten Thiel, Fabian Troendle, Georg Chlond, Dr. Gert
Rusch, Herbert Stegmueller, Joerg Schmidt, Dr. Meinolf Block, Michael Demuth, Michael Schuster, Dr. Nicholai
Jordt, Otto Boehrer, Rudolf Marquet, Stephen Corbett, Dr. Stefan Fuchs, Thomas Arend, Thomas Besthorn, Dr. Uwe
Hommel, Uwe Inhoff, and Dr. Wulf Kruempelman.
SAP America: “Casper” Wai-Fu Kan, Daniel Kocsis, Daniel-Benjamin Fig Zaidspiner, Jackie Wang, Lance
Pawlikowski, Maria Gregg, Sue McFarland.
SAP Labs: Dr. Arnold Klingert, Jaideep Adhvaryu, “Jody” Honghua Yang, John Wu, Kitty Yue, Nihad Al-Ftayeh,
Peter Aeschlimann, Philippe Timothee, Dr. Thomas Brodkorb.
SAP UK: Peter Le Duc.
Contributing authors: Patricia Huang, SAP America; Jerry Forsey, SAP America.
QA testers: Brad Barnes, e.coetry; Claudia Helenius; Jeff Orr, Utilx; Lynne Lollis, e.coetry; Marc Punzalan, Heat and
Control; Patrick McShane, Bramasol.
Documentation and production: Rekha Krishnamurthy, John Kanclier, Kurt Wolf.
Gary Nakayama, CPA SAP

Labs, Inc., 2000
System Administration Made Easy xix

xx xx Release 4.6 A/B
Introduction
Contents
What Is This Guidebook About?..........................................................................xxii

Who Should Read This Book?..............................................................................xxii
How to Use This Guidebook................................................................................xxv
What’s New............................................................................................................xxv
Special Icons.......................................................................................................xxvii
System x
Administr x
ation
Made
Easy
Introduction
What Is This Guidebook About?
What Is This Guidebook About?
Philosophy
Release 4.6 of the System Administration Made Easy Guidebook continues in the direction of the 4.0
version. The primary focus is the importance of the on-going nature of system administration. This
book is written for an installed system, where all installation tasks have been completed. Installation
and related tasks, which are usually performed once, have not been included in this guidebook.
Organization
We have tried to group items and tasks in job role categories, which allows this guidebook to be a
better reference book.
Content
Real world practical advice from consultants and customers has been integrated into this book.
Because of this perspective, some of the statements in this book are blunt and direct. Some of the
examples we have used may seem improbable, but “facts can be, and are, stranger than fiction.”
Because system administration is such a large area, it is difficult to reduce the volume to what can be
called “Made Easy.” Although material in this book has been carefully chosen, it is by no means
comprehensive. Certain chapters can be expanded into several books [two examples are the chapters
on disaster recovery (chapter 2) and security (chapter 11)].
What Is Not Provided
Although there are chapters on problem solving and basic performance tuning, these chapters are only
introductions to the subjects. This guidebook is not meant to be a trouble shooting or performance
tuning manual. Installation tasks are not presented. We assume that your SAP consultant has
completed these tasks.
Who Should Read This Book?

The target audience for this guidebook is:
► The customer person or team where:
► The R/3 administrator is from a small to mid-size company with a small (one to three
people) technical team.
► Each team member in the team has multiple job responsibilities.
► The system administrator has a basic knowledge of the operating system and database.
► The junior consultant
Release 4.6 A/B

x xii
Introduction
Senior consultants, experienced system administrators, and DBAs may find portions of this guidebook
very elementary, but hopefully useful.
Prerequisites
\<6tltf0# To help you use this guidebook, and to prevent this guidebook from becoming as thick as an unabridged
dictionary, we defined a baseline for user knowledge and system configuration. The two sections below
(User and System) define this baseline. Review these sections to determine how you and your system
match. This book is also written with certain assumptions about your knowledge level and the
expectation that particular system requirements have been met.
User
We assume that you have a baseline knowledge of R/3, the operating system, and the database. If you
lack knowledge in any of the following points, we recommend that you consult the many books and
training classes that specifically address your operating system and database.
You should know how to complete the following tasks at the:
► R/3 using menus and transaction codes
System There are screens that do not have menu paths and the only way to access them is by using the
transaction codes. In the “real world,” navigating by transaction codes is faster and more
level:
efficient than menus.
► Be
► Operating system level:
able
► Be familiar with the file and directory structure
to
► Be able to use the command line to navigate and execute programs
log
► Set up a printer
on
► Perform a backup using standard operating system tools or third-party tools
to ► Perform basic operating system security
R/3 ► Copy and move files
► Kn ► Properly start and stop the operating system and server
ow
► Database level
ho
w ► Properly start and stop the database
to ► Perform a backup of the database
nav
igat R/3 runs on more than five different versions of UNIX. In many cases, significant differences exist
e in between these versions. These differences contributed to our decision to not go into detail at the
R/3 operating system level.

xxiii
Introduction
System
For an ongoing productive environment, we assume that the:
► R/3 System is completely and properly installed
► Infrastructure is set up and functional
The following checklist will help you determine if your system is set up to the baseline assumptions
of this book. If you can log on to your R/3 System, most of these tasks have already been completed.
Hardware
Is the backup equipment installed and tested?
Infrastructure
► Is the Uninterruptible Power Supply (UPS) installed?
► Is a server or system monitor available?
Software
► Are the following utility software installed (as appropriate)?
► Backup program
► Hardware monitors
► System monitors
► UPS control
► R/3 System
■ Is R/3 installed according to SAP’s recommendation?
■ Is the TPPARAM file configured?
(In Release 4.6, TMS creates a file to be used as the TPPARAM file.)
► Is the TMS/CTS configured?
► Is the SAProuter configured?
► Is the OSS1 transaction configured?
► Is the ABAP workbench configured?
► Has initial security been configured (default passwords changed)?
► Are the NT sapmnt share or UNIX NFS sapmnt exports properly configured?
► Is the online documentation installed?
► Can users log on to R/3 from their desktops?
Desktop
For optimal results, we recommend that the minimum screen resolution be set as follows:
► For the users, 800 x 600
► For the system administrator, 1024 x 768 and a minimum color depth of 256 colors
The Release 4.6 GUI displays better with 64K colors.
xxiv Release 4.6 A/B

Introduction
How to Use This Guidebook
How to Use This Guidebook

This guidebook is organized in the following fashion:
► The first two chapters provide a high-level view of disaster recovery and backup and recovery.
► Chapters 4-8 are helpful checklists that help the system administrator complete various tasks,
including daily, weekly, and yearly.
These chapters also provide helpful transaction codes and where in the book these codes are
found.
► Chapter 9 discusses how to stop or start the R/3 System.
► Chapters 10-13 involve the following topics:
► R/3 administration
► Security administration
► User administration
► Database administration (SQL Server)
The rest of the book covers subjects such as operations, troubleshooting, remote services, change
management, and SAPNet R/3-Frontend (formerly known as OSS). The four appendices cover useful
transactions, other resources, SAPNet R/3-Frontend notes, and a discussion on upgrades.
Organization
All the task procedures are classified in one section and by job roles, where related tasks are placed
together. Regardless of the job schedule, all jobs related to a job role are grouped in one place.
What's New
This guidebook evolved from the previous versions of this guidebook and incorporates customer
and consultant comments. Send us your comments, so we can make future versions better meet
your needs.
Content
The new features of the Release 4.6 guidebook are:
► System Administration Assistant (transaction SSAA), chapter 10
► New chapters on:
► Security (chapter 11)
► Microsoft SQL Server / Windows NT (chapter 13)
► Basic problem solving (chapter 17 )
► Basic performance tuning (chapter 22)

xxvxxv
Introduction
What’s New
The procedures to perform regularly-scheduled tasks have been moved to the Roles section. The
unscheduled tasks section from the 4.0B guidebook has become a role-oriented section. This change
accommodates customers who perform scheduled tasks at times other than the times presented in this
guidebook. Therefore, all the task procedures are classified in one section and by job roles, where
related tasks are placed together. Regardless of the job schedule, all jobs related to a job role are
grouped in one place.
Conventions
In the table below, you will find some of the text conventions used throughout this guide.
Column Title Column Title
Sans-serif italic Screen names or on-screen objects (buttons, fields, screen

text, etc.)
Monospace User input (text the user types verbatim)
Name1 —> Name2 Menu selection Name1 is the menu name, and Name2 is the
item on the menu
Sample R/3 Release 4.6 Screen
Menu Bar Standard Toolbar
Screen Title SAP Easy Access

otnermenu Create menu
¨ ApplicationToolbar ____________________________|_ F/ I I *"* I -^ I I B I
Assign users Documentation
^B
Favorites
User menu SAP standard menu
_i Office
© SBWP-Workplace
[> □ Telephone Integration
SAP standard menu
l> CJ Appointment Calendar
[> CJ Room Reservations 0 SWUI-Start Workflow
[> d Business Documents [> CJ Logistics [> CJ
Accounting
§ Workplace Menu t[> CJ Human Resources > CJ Information Systems > Q
Tools
¨ Status Bar Application toolbar: [> JALFTAYEH 13 pawdf042

IMS
xxvi Release 4.6 A/B

Introduction
Special Icons
The screenshots shown in this guide are based on full user authorization (SAP_ALL). Depending on
your authorizations, some of the buttons on your application toolbar may not be available.
§ Workplace menu:
Depending on your authorizations, your workplace menu may look different from screenshots in
this guide which are based on SAP_ALL. The User menu and SAP standard menu buttons provide
different views of the workplace menu.
To learn how to build user menus, see Authorizations Made Easy guidebook Release 4.6A/B.
Note: In this guidebook, we show the technical names of each transaction. To match our settings,
choose Extras —> Settings and select Show technical names.
Special Icons
Throughout this guide special icons indicate important messages. Below are brief explanations of
each icon:
U W ''< to
Exercise caution when performing this task or step. An explanation of why you should be careful is
included.
\»<M o#
This information helps you understand the topic in greater detail. It is not necessary to know this information to
perform the task.
0 These messages provide helpful hints and shortcuts to make your work faster and easier.

xxvii
Introduction
Special Icons
xviii Release 4.6 A/B

xxviii
Chapter 1: R/3 System Administration
Basics
Contents
Overview................................................................................................................1-2
Roles of an R/3 System Administrator................................................................1-2
Traits of an R/3 System Administrator................................................................1-4
R/3 System Guidelines.........................................................................................1-4
Corollaries to Murphy’s Law..............................................................................1-13
Special Definitions..............................................................................................1-14
System 1
Administra -
tion Made
Easy
Chapter 1: R/3 System Administration Basics
Overview
Overview
This chapter is about the roles that a system administrator plays. These roles cross all functional
areas, and the number and intensity of the tasks depends on the size of the company. In a small
company, one person can be the entire system administration department. In a larger company,
however, this person is probably part of a team. The purpose of this “definition” is to help clarify
the roles of a system administrator. This chapter is a list of commonly used system
administration terms and their definitions.
At the end of this chapter is a list of 14 R/3 System guidelines, which a system administrator must be
aware of while working with the system.
Sample guidelines include:
► Keep it short and simple (KISS)
► Use checklists
► Do not allow direct database access
Roles of an R/3 System Administrator
Depending on the size of the company and available resources, R/3 administrator(s) may range from
one person to several specialized people in several departments.
Factors that affect an R/3 system administrator’s tasks, staffing, and roles:
► Company size
► Available resources (the size of the Basis group)
► Availability of infrastructure support for:
► Desktop support
► Database
► Network
► Facilities
The R/3 system administrator may wear many hats both in or directly related to, R/3 and indirectly or
external to R/3.
Within R/3
► User administrator
Set up and maintain user accounts Security administrator
► ► Create and maintain SAP security profiles
► Monitor and manage security access and violations
1-2 Release 4.6A/B

Roles of an R/3 System Administrator
► System administrator
► Maintain the system’s health
► Monitor system performance and logs Transport
► administrator
► Transport changes between systems
► Manage change requests Batch scheduler
►
Create and manage the scheduling of batch jobs Backup 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 SAPNet R/3 note fixes to programs Data Dictionary
(DDIC) manager
►
Change the Data Dictionary (when applicable) Data Base
Administrator (DBA)
External to R/3
► DBA for the specific database on which the system is running
► Manage database specific tasks
► Maintain the database’s health and integrity Operating system administrator
► ► Manage the operating system access and user IDs
► Manage operating system specific tasks Network administrator
► Manage network access and user IDs
► ► Manage network support and maintenance Server administrator
Manage the servers Desktop support
Supports the user’s desktop PC
►
Printers
Facilities
►
Manages facilities-related support issues, such as:
► Power/utilities
► Air conditioning (cooling)

1-3
Traits of an R/3 System Administrator
■ Physical server access
Traits of an R/3 System Administrator
An R/3 system administrator should:

► Have a proper attitude
■ Protect and safeguard the system.
The system administrator is the guardian of the system.
■ Know when to call for help
The ability to know when you need to get help is a strength.
The weakness is not knowing when to get help and getting into trouble.
■ Be willing to work the hours required to support the system
Certain tasks must be done after hours or on weekends to avoid disrupting normal business
operations.
► Be technically competent
► When necessary, the company must invest in training for the Basis staff.
► You must also take responsibility for your own training and education, whether your
company pays for it or not.
► Be a team-player
The system administrator will have to work with various functional groups, users, the IS staff,
and others to successfully complete the necessary tasks.
R/3 System Guidelines
When working on an R/3 System:

► Protect the system
► Do not be afraid to ask for help
► Network with other customers and consultants
► Keep it short and simple (KISS)
► Keep proper documentation
► Use checklists
► Use the appropriate tool for the job
► Perform preventive maintenance
► Do not change what you do not have to
► Do not make changes to the system during critical periods
► Do not allow direct database access
► Keep all non-SAP activity off the SAP servers
► Minimize single points of failure
1-4 Release 4.6A/B

Protect the System
What
Everything you do as a system administrator should be focused on protecting and
maintaining the system’s integrity.
Why
► If the system’s integrity is compromised, incorrect decisions could be made based on invalid data.
► If the system cannot be recovered after a disaster, your company could be out of business.
How
► The system administrator must have a positive, professional attitude.
If the system administrator has less than this attitude, critical tasks may not be properly
completed (for example, backups may not be taken as scheduled and backup logs may not be
checked, which reduces the chances for a successful recovery).
► System administrators should maintain a “my job is on the line” attitude.
This attitude helps to ensure that administrators focus on maintaining the integrity of the system.
The company may not survive if the system crashes and cannot be recovered.
► The system must be protected from internal and external sources.
One problem today is employees “poking around” in the network.
Do Not Be Afraid to Ask for Help
Why
► R/3 is so large and complex that one person cannot be expected to know everything.
If you are unsure which task to complete or how to complete it, you could make a mistake
and cause a larger problem.
► Mistakes within the system can be expensive.
Certain things cannot be “undone,” and once set, are set forever.
► The only way to learn is to ask.
There are no dumb questions—only dumb reasons for not asking them.
How
► SAPNet R/3 notes
► Various web sites and news groups
► Consultants
Also see the section in this chapter that covers networking with other customers and consultants.

1-5
Network with Other Customers and Consultants
What
Get to know the R/3 Basis and system administrators in other companies.
Why
► Other customers may be able to provide solutions to your problems.
► Customers who help each other reduce their consulting expenses.
► The more people you know, the better your chances of finding someone to help you solve a
problem.
When, Where, and How

When you have the opportunity, meet:
► Other SAP customers and consultants, especially those in your specialty area
► Others using your operating system or database
Where to network:
► Training classes
► SAP events
► Technical Education Conference (TechEd)
► SAPPHIRE
► Participate in user groups:
► Americas SAP Users Group (ASUG)
► Regional SAP users groups
► Database user groups, such as those for Microsoft SQL Server, Informix, DB2, or Oracle
► Operating system user groups, such as those for UNIX (the various versions), NT, or IBM
(AIX, AS400, or OS390)
► Participate in professional organizations
Participation means getting involved in the organization. The more you participate, the more
people you meet and get to know.
<$>U ► Whenever you attend an event, carry a stack of business cards.

% Set the goal of collecting “at least” ten business cards, of people in your area of specialty
► Do not forget to ask the “old-timers.”
Decades ago, the mainframe community may have solved many of the issues and
problems you now face.
Release
4.6A/B 1–6
Keep It Short and Simple (KISS)
Why
► Complex tasks are more likely to fail as situations change.
A process with 27 steps has 27 chances to fail, because complex tasks are difficult to create,
debug, and maintain.
► It is difficult to train people for complex tasks.
► Explaining a complex task on the telephone increases the chance that what is said will not be
properly understood and an error will be made. If the error is severe, you may have a disaster on
your hands.
How
► Keep tasks as simple as possible.
► Test
Keep Proper Documentation
What
Document processes, procedures, hardware changes, configuration changes, checks performed,
problems, errors, etc. If in doubt about what to document, write it all down.
Why
► As time passes, you will forget the details of a process or problem.
At some point, you may not remember anything about the process or problem. In an extreme
situation, which happens with short-term memory, you can quickly forget the information in
minutes.
► If you violate the KISS principle, complete documentation becomes even more important.
► If the process is complex, complete documentation reduces the chance of errors.
► If you are sick or unavailable, complete documentation can help someone else do the job.
► If changes need to be undone, you will know exactly what needs to be done to complete this task.
► Documentation helps train new people.
Employee turnover must be planned for. Proper documentation makes the training and transition of
new employees easier and faster.

1-7
When
Documentation must be changed when:

► Documented items change.
Inaccurate documentation could be dangerous because it describes a process that should not be
followed.
► Changes are made to the system.
► Problems, such as hardware failures, error log entries, and security violations, occur.
“Hot” projects or emergencies tend to take precedence over writing documentation. Do not postpone
writing documentation, or the task may never get done. Record everything that is done to the system
—as it is being done.
How
► Record everything done to the system, as it is being done, so details are not forgotten.
► Document items clearly and sufficiently so that, without assistance, a qualified person can read
what you have written and perform the task.
► Re-read older documentation to see where improvements can be made. Obvious items get
“fuzzy” over time and are no longer obvious.
► Use graphics, flowcharts, and screenshots to clarify documentation.
Where
► Keep a log (notebook) on each server and record everything that you do on the servers.
► Keep a log for everything done remotely to any of the servers.
► Keep a log for other related items.
Use Checklists
What
A checklist lists the steps required to complete a task. Each step requires an
acknowledgement of completion (a check) or an entry (date, time, size, etc.).
Why
► Checklists enforce a standardized process and reduce the chance that you will overlook
critical steps.
For example, if you were to use a checklist every time you drive a car, then you would
remember to turn off your headlights when you park your car, or you would not drive off with
your parking brake still set.
► Checklists force you to document events, such as run times, which may later become
important.
1-8 Release 4.6A/B

When
Checklists are especially useful for tasks that are:

► Complex or critical
If a step is missed or done incorrectly, the result could be serious (for example, inability to restore
the database).
► Done for the first time
► Done infrequently
It is difficult to remember how to do a complicated task that you do only once a year.
How
See examples in Scheduled Tasks.
Use the Appropriate Tool for the Job

Sometimes a low-tech solution is best. Depending on the situation, a paper-and-pencil solution may
work better and be more cost effective than a computerized solution. Paper and pencil still works
during a power failure.
Perform Preventive Maintenance
What
Preventive maintenance is the proactive monitoring and maintenance of the system.
Why
► It is less disruptive and stressful if you can plan a convenient time to do a task, rather than have it
develop into an “emergency” situation.
► Fix a potential problem before it negatively impacts the system and company
operations.
An extreme situation is that the entire system is down until a particular task is completed (for
example, if the log file space goes down to zero (0), the database will stop, and then R/3 also
stops. Until sufficient file space is cleared, R/3 will not run and certain business operations, such
as shipping, may stop).
When
► Checking for problems should be a part of your regular routine.
► Scheduling tasks to fix a problem should be based on your situation, and when least disruptive to
your users.
How
► Monitor the various logs and event monitors
► Obtain additional disk storage before you run out of room
► Regularly clean the tape drive(s)
► Check the database for consistency and integrity

1-9
Do Not Change What You Do Not Have To

What
► If the system works, leave it alone.
► Do not change something just to upgrade to the latest version.
Why
► Risk
When something changes, there is a chance that something else may break.
► Cost
Upgrading is expensive in terms of time, resources, and consulting, etc.
When
► A business need exists.
► Legal requirements call for an update.
This really is not an option. If you do not keep up you will not be complying with legal
requirements. The associated penalties can be expensive.
► If the hardware or software release is no longer supported by the vendor.
► The new release offers a specific functionality that offers added business value to your company.
► Fixing a major problem requires an upgrade.
A fix is unavailable in a patch or an “advance release.”
How
► If the change fails or causes problems, make certain you can recover to a before-the-change
condition.
► All changes must be regression tested to make sure that nothing else has been affected by the
change. In other words, everything still works as it is supposed to.
Regression testing of R/3 involves the functional team and users.
► Stage the change and test it in the following order:
1. Test system (a “Sandbox” system)
2. Development system
3. Quality Assurance system
4. Production system
Even if your company does not have all the above-mentioned systems, the key is to maintain the
general order. For example, if your company does not have a test system, test the change in the
following order:
5. Development
6. Quality Assurance
7. Production
1-10 Release 4.6A/B

By the time you reach the production system, you should be comfortable that nothing will break.
Do Not Make System Changes During Critical Periods
What
A critical period is when system disruptions could cause severe operational problems.
Why
If a problem occurs during a critical period, the business maybe severely impacted. Note the
following sequence of events:
8. A system administrator changes a printer in Shipping at the end of the month.
9. R/3 cannot send output to the new printer.
10. The users cannot print shipping documents.
11. The company cannot ship their products.
12. Revenue for the month is reduced.
When
A critical period is any time where the users and the company may be “severely” impacted by a system
problem. These periods differ depending on the particular industry or company. What is a critical
period for one company may not be critical for another company.
The following are “real” examples of critical periods:
► At end of the month, when Sales and Shipping are booking and shipping as much as
they can, to maximize revenue for the month
► At the beginning of the month, when Finance is closing the prior month
► During the last month of the year, when Sales and Shipping are booking and shipping as much as
they can, to maximize the revenue for the year
► During the beginning of the year, when Finance is closing the books for the prior year and getting
ready for the financial audit
How
► Always coordinate potentially disruptive system events with the users. Different user groups
in the company, such as Finance and Order Entry, may have different quiet periods that need
to be coordinated.
► Plan all potentially disruptive systems-related activities during quiet periods when a problem will
have minimal user impact.

1-11
Do Not Allow Direct Database Access
What
Direct database access means allowing a user to run a query or update directly to the database
without going through R/3.
Why
► By not going through R/3, there is the risk of corrupting the database.
► Directly updating the database could put the database out of sync with the R/3 buffers.
How
► When R/3 writes to the database, it could be writing to many different tables.
If a user writes directly to the tables, missing a single table may corrupt the database by putting
the tables out of sync with each other.
► With direct database access, a user could accidentally execute an update or delete, rather
than a read.
Keep all Non-SAP Activity Off the R/3 Servers
What
► Do not allow users to directly access (telnet, remote access, etc.) the R/3 server(s).
► Do not use the R/3 server as a general file server.
► Do not run programs that are not directly related to R/3 on an R/3 server.
Why
► Security
Not allowing users to have access to the R/3 server reduces the chance of files from being
accidentally deleted or changed.
No access also means that user cannot look at confidential or sensitive information.
► Performance
Using the production R/3 sever as a file server creates resource contention, where performance is
a primary concern. Programs running on the R/3 servers will contend for the same resources that
R/3 is using, which affects the performance of R/3.
How
Use other servers to perform functions unrelated to R/3.
1-12 Release 4.6A/B

Corollaries to Murphy’s Law
Minimize Single Points of Failure
What
A single-point failure is when the failure of a single component, task, or activity causes the system to
fail or creates a critical event.
Why
Each place where a single-point failure could occur increases the chances of a system failure or other
critical event.
For example, if:
► You only have one tape drive and it fails, you cannot back up your database.
► You rely on utility line power, and do not have a UPS, the server will crash during a power failure
and possibly corrupt the database.
► You are the only one who can complete a task, and you are on vacation, the task will not be
completed until you return (or you will be “on call” while on vacation).
To guard against a single-point failure, consider the following options:
► Systems configured with a built-in backup
► Redundant equipment, such as dual power supplies
► On-hand spares
► Sufficient personnel
► On-call consultants
► Cross-training
► Outsourcing
Corollaries to Murphy's Law
Murphy’s Law states: “Whatever can go wrong will go wrong.”

The following are some corollaries to Murphy’s Law:
► Without telling you, someone will change something in the infrastructure and crash the
system.
► When the power fails, you find out that the battery in your UPS is dead.
► If you have only one tape drive, it will fail.
► The one thing that you did not test is “where” the problem is.
► Someone will need a network jumper cable, and will remove it from your server.
► When disaster strikes, you will be out of town or unavailable .
► Disaster will strike at the worst time.
► Problems always happen at 2:00 AM.
► Problems come in clusters.

1-13
Special Definitions
► The latest full backup tape will be bad.

► The one time you did not check the backup log will be the time when the backup fails.
► You will need a tape from the backup that failed.
► The computer room will be destroyed—along with all your backup tapes.
► What you did not write down, and forgot, is what you need to know.
► User transparent, is not.
► The Peter Principle will strike.
► A shortcut is the longest distance between two points.
► When you need to send an alpha page, a link in the e-mail system will fail.
► When a disaster strikes, and you need to be found, you will be out of the pager or cell phone
coverage area.
► When a disaster strikes, and you need to be contacted, the battery in your pager or cell phone will
be dead.
Special Definitions
There are terms used in this guidebook that have very specific meanings. To prevent confusion,
they are defined below:
Database server
This is where R/3 and the database resides.
The system clock of the database server is the master clock for the R/3 system.
Application server
This is where R/3 application runs.
On a two-tiered system, this would be combined on the database server. Application servers can
be dedicated to online users, batch processing or a mix.
Instance
An installation of R/3 on a server.
The two types of instances are central, and dialog. More than one instance could exist on a physical
server.
System
The complete R/3 installation for a System ID (SID), for example PRD.
A system logically consists of the R/3 central instance and dialog instances for the SID. This
physically consists of the database server and application servers for that SID.
1-14 Release 4.6A/B

Special Definitions
Three-tiered R/3 Configuration
Layers Physical Devices R/3 Instance What Runs on Each Layer
SAP GUI R/3

Presentation Desktop PC—many N/A
Application Application Server Dialog —N/A —
many
Database Database server only Central Database: SQL Server,
one DB2, Informix, ADABAS,
Oracle
A two-tiered configuration combines the application and database layers on a single server.

1-15
Special Definitions
Release
4.6A/B 1–16
Chapter 2: Disaster Recovery
Contents
Overview................................................................................................................2-2
Why Plan for a Disaster?......................................................................................2-3
Planning for a Disaster..........................................................................................2-4
Test your Disaster Recovery Procedure...........................................................2-15
Other Considerations.........................................................................................2-16
Minimizing the Chances for a Disaster.............................................................2-17
System A
d
2-1
Overview
Overview
The purpose of this chapter is to help you understand what we feel is the most critical job of a system
administrator—disaster recovery.
We included this chapter at the beginning of our guidebook for two reasons:
► To emphasize the importance of the subject
Disaster recovery needs to be planned as soon as possible, because it takes time to
develop, test, and refine.
► To emphasize the importance of being prepared for a potential disaster
Murphy’s Law says:
“Disaster will strike when you are not prepared for it.” The faster you begin planning, the more
prepared you will be when a disaster does happen.
This chapter is not a disaster recovery “how to.” It is only designed to get you thinking and
working on disaster recovery.
What Is a Disaster?
The goal of disaster recovery is to restore the system so that the company can continue doing
business. A disaster is anything that results in the corruption or loss of the R/3 System.
Examples include:
► Database corruption. For example when test data is accidentally loaded into the
production system. This happens more often than people realize.
► A serious hardware failure.
► A complete loss of the R/3 System and infrastructure. For example, the
destruction of the building due to natural disaster.
The ultimate responsibility of a system administrator is to successfully restore R/3 after a disaster.
The ultimate consequence of not restoring the system is that your company goes out of business.
The administrator’s goal is to prevent the system from ever reaching the situation where the ultimate
responsibility is called upon.
Disaster recovery planning is a major project. Depending on your situation and the size and
complexity of your company, disaster recovery planning could take more than a year to
„ Release 4.6 A/B

2-2
Why Plan for a Disaster?
prepare, test, and refine. The plan could fill many volumes. This chapter helps you start thinking
about and planning for disaster recovery.
Why Plan for a Disaster?

► A system administrator should expect and plan for the worst, and then hope for the best.
► During a disaster recovery, nothing should be done for the first time.
Unpleasant surprises could be fatal to the recovery process.
Here are some of the reasons to develop a disaster recovery plan:
► Will business operations stop if R/3 fails?
► How much lost revenue and cost will be incurred for each hour that the system is down?
► Which critical business functions cannot be completed?
► How will customers be supported?
► How long can the system be down before the company goes out of business?
► Who is coordinating and managing the disaster recovery?
► What will the users do while R/3 is down?
► How long will the system be down?
► How long will it take before the R/3 System is available for use?
If you plan properly, you will be under less stress, because you know that the system can be recovered
and how long this recovery will take.
If the recovery downtime is unacceptable, management should invest in:
► Equipment, facilities, and personnel
► High availability (HA) options
HA options can be expensive. There are different degrees of HA, so customers need to determine
which option is right for them.
HA is an advanced topic beyond the scope of this guidebook. If you are interested in this topic,
contact an HA vendor.

2-3
Planning for a Disaster
This chapter is not a disaster recovery “how to.” It is only designed to get you thinking and working on disaster
recovery.
Creating a Plan
Creating a disaster recovery plan is a major project because:
► It can take over a year and considerable time to develop, test, and document.
► The documentation may be extensive (literally thousands of pages long).
If you do not know how to plan for a disaster recovery, get the assistance of an expert. A bad plan
(that will fail) is worse than no plan, because it provides a false sense of security.
What Are the Business Requirements for Disaster Recovery?

W ho will provide the requirements?
► Senior management needs to provide global (or strategic) requirements and guidelines.
► The business units’ needs drive the specific detailed requirements.
These units should understand that as the requirement for the recovery time decreases, the cost
for disaster recovery increases. The units should budget for it, or if the funds come from an
administrative or IT budget, the units should support it.
W hat are the requirements?
Each requirement should answer the following questions:
► Who is the requestor?
► What is the requirement?
► Are other departments or customers affected by this requirement?
► Why is the requirement necessary?
► When R/3 is offline, what does (or does not) happen?
► What is the cost (or lost revenue) of an hour or a day of R/3 downtime?
The justification should be a concrete objective value (such as $20,000 an hour). Define
the cost (per hour, per day, etc.) of having the R/3 System down.
2-4 Release 4.6 A/B
Chapter 2: Disaster
Recovery
Example
► What: No more than one hour of transaction data may be lost.
► Why: The cost is 1,000 transactions per hour of lost transactions that are entered in R/3 and
cannot be recreated from memory.
This inability to recreate lost transactions may result in lost sales and upset customers.
If the lost orders are those that the customer quickly needs, this
situation can be critical.
Example 2
► What: The system cannot be offline for more than three hours.
► Why: The cost (an average of $25,000 per hour) is the inability to book sales.
Example 3
► What: In the event of disaster, such as the loss of the building containing the R/3 data
center, the company can only tolerate a two-day downtime.
► Why: At that point, permanent customer loss begins.
► Other: There must be an alternate method of continuing business.
When Should a Disaster Recovery Procedure Begin?

Ask yourself the following questions:
► What criteria constitute a disaster?
► Have these criteria been met?
► Who needs to be consulted?
The person must be aware of the effect of the disaster on the company’s business and the critical
nature of the recovery.
Expected Downtime or Recovery Time

Expected Downtime
Expected downtime is only part of the business cost of disaster recovery. For defined scenarios, this
cost is the expected minimum time before R/3 can be productive again. Downtime may mean that no
orders can be processed and no products shipped. Management must approve this cost, so it is
important that they understand that downtime are potential business costs.
To help business continue, it is important to find out if there are alternate processes that can be used
while the R/3 System is being recovered.

2–5
The following costs are involved with downtimes:

► The length of time that R/3 is down.
The longer the system is down, the longer the catch-up period when it is brought back up. The
transactions from the alternate processes that were in place during the disaster have to be applied
to the system to make it current. This situation is more critical in a high-volume environment.
► A downed system is more expensive during the business day when business activity would stop
than at the end of the business day when everyone has gone home.
► When customers cannot be serviced or supported, they may be lost to a competitor.
The duration of acceptable downtime depends on the company and the nature of its business.
Recovery Time
Unless you test your recovery procedure, the recovery time is only an estimate, or worse, a guess.
Different disaster scenarios have different recovery times, which are based on what needs to be
done to become operational again.
The time to recover must be matched to the business requirements. If this time is greater than the
business requirements, the mismatch needs to be communicated to the appropriate managers or
executives.
Resolving this mismatch involves:
► Investing in equipment, processes, and facilities to reduce the recovery time.
► Changing the business requirements to accept the longer recovery time and accepting the
consequences.
An extreme (but possible) example: A company cannot afford the cost and lost revenue for the month
it would take one person to recover the system. During that time, the competition would take away
customers, payment would be due to vendors, and bills would not be collected. In this situation,
senior management needs to allocate resources to reduce the recovery time to an acceptable level.
Recovery Group and Staffing Roles

There are four key roles in a recovery group. The number of employees performing these roles will
vary depending on your company size. In a smaller company, for example, the recovery manager and
the communication liaison could be the same person. Titles and tasks will probably differ based on
your company’s needs.
We defined the following key roles:
► Recovery manager
Manages the entire technical recovery. All recovery activities and issues should be
coordinated through this person.
► Communication liaison
Handles user phone calls and keeps top management updated with the recovery status. One
person handling all phone calls allows the group doing the technical recovery to proceed without
interruptions.
_ Release 4.6 A/B

2-6

SAP R3 Sysadminstartor

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP R3 Sysadminstartor

Uploaded by

Copyright:

Available Formats

System Administration Made Easy

R/3 System Release 4.6A/B

© 2000 by SAP AG. All rights reserved.

Printed in the United States of America.

System Administration Made Easy iii

Chapter 2: Disaster Recovery.......................................................................................................2-1

Overview .................................................................................................................. 2–2

Backup Strategy Design............................................................................................3-9

Backup Procedures and Policies.........................................................................3-13

Verify that the Backups Ran Successfully.................................................................4-9

OS Monitor (Transaction OS06)..............................................................................4-11

Lock Entry List (Transaction SM12)........................................................................4-12

System Administration Made Easy vii

Update Records (Transaction SM13)......................................................................4-12

Chapter 5: Scheduled Weekly Tasks............................................................................................5-1

Chapter 8: Scheduled Annual Tasks............................................................................................8-1

viii Release 4.6A/B

Chapter 9: Multi-Role Tasks..........................................................................................................9-1

Check that No Active Users Are on the System (AL08/SM04)..............................9-9

Configuring the Batch Job to Collect Historical Data (RZ21)............................10-10

Acknowledge the Alert......................................................................................10-14

Add a Monitor to the Monitor Set......................................................................10-24

System Log (Transaction SM21)...........................................................................10-38

System Administration Made Easy ix

Chapter 11: Security Administration............................................................................................11-1

Keeping Unauthorized People out of the System...............................................11-2

Prevent Multiple User Logins.............................................................................11-11

Password Issues and Tasks.................................................................................11-28

Running the Audit Log......................................................................................11-46

User Security Audit Jobs.......................................................................................11-54

Chapter 12: User Administration..................................................................................................12-1

Recommended Prerequisite for the GUI Installation...........................................12-7

Installing SAP GUI from the Presentation CD....................................................12-14

To Add Additional Systems in the SAP Logon..................................................12-15

System Administration Made Easy xi

Determining the Tape (Label) Necessary for a Backup.........................................13-13

Database Backups with Microsoft Tools...........................................................13-19

Chapter 14: Output Management..................................................................................................14-1

How to Set Up the Printer in the R/3 System......................................................14-2

Chapter 15: Network/OS/Server Administration.........................................................................15-1

Operating System Alert (AL16)...............................................................................15-2

xii Release 4.6A/B

Graphical Job Monitor (Transaction RZ01)...........................................................16-19

Operating System Level Backups.....................................................................16-40

Chapter 17: Change Management................................................................................................17-1

Checking the Transport Log (Transaction SE10)..............................................17-35

System Administration Made Easy xiiix

Chapter 18: Troubleshooting........................................................................................................18-1

Evaluate the Alternatives....................................................................................18-3

Chapter 19: Performance..............................................................................................................19-1

Solving a Problem with SAPNet...........................................................................20-5

Entering Customer Messages.................................................................................20-9

xiv Release 4.6A/B

Chapter 21: Delete an Object...................................................................................................20-23

Registering a Developer or Object....................................................................21-22

Chapter 22: Registering an Object...........................................................................................21-26

Opening a Service Connection..........................................................................21-30

System Administration Made XV

Requesting SPAM or a Support Package from SAPNet-R/3.................................23-22

Useful SAPNet - R/3 Frontend Notes....................................................................23-39

Reviewing the Client Copy Log.........................................................................23-54

Appendix A: Useful Transactions...................................................................................................A-1

Appendix B: Useful Resources and Products...............................................................................B-1

xvi Release 4.6A/B