System Administration Made Easy 7–1

Chapter 7: 8cheduled Quarterly Tasks
Contents
The R/3 System.......................................................................................................7–2
Database ..................................................................................................................7–3
Operating System ...................................................................................................7–3
Other.........................................................................................................................7–4
Notes ........................................................................................................................7–4



Chapter 7: Scheduled Quarterly Tasks
The R/3 System

Release 4.6A/B
7–2
The R/3 8ystem
System: __________
Date: ____/ ____/ ____
Admin: _____________________

Task Transaction Chapter Procedure Check off/Initial
Archive quarterly backup Send quarter-end backup
tapes to long-term offsite
storage.

Security review SU01—User
Maintenance
12 Review user ID for
terminated users that
should be locked or
deleted.


SM31—Table
Maintenance
19 Review list of
“prohibited” passwords
(Table USR40).


RZ10—Edit
System Profile
20 Review system profile
parameters for password
standards.

Review scheduled jobs
SM37—
Background
Jobs
16 Review all scheduled
jobs to determine if they
are still appropriate.


Chapter 7: Scheduled Quarterly Tasks
Database

System Administration Made Easy
7–3
Database

Task Where Chapter Procedure Check
off/Initial
Archive quarterly backup 3 Send quarter-end
backup tape to long-
term offsite storage.

Review all scheduled jobs SM37 16 Review all
scheduled jobs to
determine if they are
still appropriate.

Test database recovery process 2 & 3 Restore database to
a test server.

Test the restored
database.


Operating 8ystem

Task Where Chapter Procedure Check
off/Initial
Archive quarterly backup 3 Send quarter-end
backup tape to long-
term offsite storage.

Archive old transport files. Transport
directories; log,
data, cofiles
15 Archive the old
transport files.

Cleanup SAPDBA logs (Oracle) SAPDBA cleanup Maintain
init<SID>.dba


Chapter 7: Scheduled Quarterly Tasks
Other

Release 4.6A/B
7–4
Other

Task Where Procedure Check off/Initial
Check maintenance contacts Check for expiration
date.

Check for usage
changes.


Notes

Problem Action Resolution



In chapters 4-8, we have included a list of transactions like the ones below. This list contains
basic information about the transactions in the checklist. For additional information on these
transactions, see the chapter referenced in each checklist.
Edit 8ystem Profile Parameters {Transaction RZ10}
What
There are security parameters for the user’s password (for example, the minimum password
length, the time interval that the user must change their password, and so on).
The following is a list of the most important password parameters:
< Minimum password length: login/min_password_lng
A longer password is more difficult to break or guess.
ΠThe standard for many companies is five (5) characters.
< Password expiration time: login/password_expiration_time
This is the length of time before the user must change their password.
ΠThe length of time that auditors recommend is thirty (30) days.
ΠThe maximum that should be used is ninety (90) days.
< Password lockout: login/fails_to_user_lock
This parameter locks out users after attempting to log in with an invalid password for a
defined number of times.
ΠThe standard is to lock a user after three (3) failed attempts.
Chapter 7: Scheduled Quarterly Tasks
Notes

System Administration Made Easy
7–5
Why
Properly assigned parameters will make it more difficult to break into the system.
8elect Background Jobs {Transaction 8M37}
What
Background jobs are batch jobs scheduled to run at specific times during the day.
Why
If you are running critical jobs, you need to know if the job failed because there may be
other processes, activities, or tasks that are dependent on these jobs.
User Maintenance {Transaction 8U01}
What
The lock/ unlock function is part of the logon check, which allows or prevents the user from
logging onto the R/ 3 System. For terminated users, the user’s ID should be locked and the
user assigned to the user group “term.”
Why
< Locking a user
If an employee leaves the company, is assigned to a different group, or is on leave, their
R/ 3 access should be removed. With the lock function, the user’s ID and security profile
remain on the system but the user cannot log on. This function is ideal for temporary
personnel or consultants where, unless the access is required, the user ID remains
locked.
< Unlocking a user
If users incorrectly log on more that the allowed number of times, they are automatically
locked out of the system. (An incorrect logon is usually the result of a forgotten
password.) The administrator must unlock the user ID and more than likely reset the
user’s password.
Chapter 7: Scheduled Quarterly Tasks
Notes

Release 4.6A/B
7–6