SAP R/3 Administration Tasks (From ERP网事随风)

SAP R/3 Administration Tasks，日常的管理工作以及常用命令的解释

 

 

 

JOB TYPE TASK TRANSACTION DESCRIPTION PROCEDURE CHECK OFF/ INITIAL
Critical Tasks Check that the R/3 System is up. Log on to the R/3 System
Check that daily backups executed without errors. DB12, DB13, DB14– Backup Logs: Overview Check database backupDatabase backup run time
Check operating system level backupOperating system backup run time

R/3 Check the CCMS alert monitor RZ20 – CCMS Monitor Look for alerts.
Check System Log SM21- System Log Set date and time to before the last log review.
Check for:ErrorsWarningsSecurity messagesAbendsDatabase problemsAny other different event
Output Devices in the SAP Spool System SPAD
Checking Spool Output Requests for Errors SP01 – Spool: Request Screen Look for spool jobs that have been “in process” for over an hour.
Check that all application servers are up. SM51 – SAP Servers Check that all servers are up.
Check work processes (started from SM51). SM50 – Process Overview All work processes with a “running” or a “waiting” status
Review and resolve dumps. ST22 - ABAP Dump Analysis Look for an excessive number of dumps.Look for dumps of an unusual nature.
Look for any failed updates (update terminates). SM13 – Update Records Set date to one year agoEnter * in the user IDSet to “all” updates
Check for lines with “Err.”
Check for “old” locks SM12 – Lock Entry List Enter an asterisk (*) for user ID.
Check for entries for prior days.
Check job log SM35 – Batch input: Initial Screen Check for:Jobs to be processedJobs in error
Review for cancelled and critical jobs SM37 – Select Background jobs Enter * in User IDVerify that all critical jobs were successful.
Review any cancelled jobs.
Check users on system SM04 – UsersAL08 – Users Review for an unknown or different user ID and terminal. This task should be done several times a day.

Oracle Backup and checking the database and offline redo log file. DB12, DB13, DB14– Backup Logs: Overview Check database backupDatabase backup run time
Monitoring Database Growth DB02  Choose Space-critical objects under Tables and indexes to search for tablespaces that are too full
Checking the Alert File ST04 – DB Performance Analysis: Oracle  Choose Detail Analysis Menu.  Choose Database Error  Log.To display all messages, choose All messages. If you want to display error messages only, choose Only alerts.
Monitoring the Archive Log Directory DB12  In the SAP start menu of the database host of your R/3 System, choose Tools  CCMS  Control/Monitoring  Performance menu  Operating system  Local  Alerts  File system.  Find out how full drive E is. This is where the saparch directory is located for a Ready-to-Run System
Evaluating Results of the DB System Check DB16B  call Transaction DB16. A table appears that lists any problems that are found. The column Result shows whether the problem is an error (E) or a warning (W). To display details (source of error, description of error and notes on corrections) on one or more messages, select the appropriate entries in the list and choose Goto  Detail (or double-click the entry). Choose Show SAPDBA log to go to the check log. This log contains extensive information on all checks and the problems they detected.
Checking and Creating CBO Statistics DB13  call the Transaction DB13.  Position the cursor on the entry for a day and choose Create to create a new entry.  Choose Schedule session. A selection field appears.  Choose Check optimizer statistics to check the status of the statistics.  Specify which tables you want to check: a. PSAP%: All SAP tables are checked b. DBSTATC-TAB: All tables entered in the table DBSTATC are checked. This option is used for Ready-to-Run. c. TSP-LST: On the next screen, choose all tablespaces for which you want to check the tables Choose a method for the estimation (E, EI, C, CI).

AIX Monitoring File Systems ST06
Cheking the Operating System Log
Checking Swap Space ST06

Other Check the uninterruptible power source (UPS). UPS program log Review for:EventsUPS self testErrors

NOTES PROBLEM ACTION RESOLUTION

WEEKLY TASKS
System:__________
Date: ____/____/____
Admin: _____________________
JOB TYPE TASK TRANSACTION DESCRIPTION PROCEDURE CHECK OFF/ INITIAL
R/3 TEMSE Check SP12

Oracle Searching for Missing Indexes DB02  call Transaction DB02.  Choose Missing indexes under Tables and indexes. The upper part of the display shows the indexes declared in the ABAP Dictionary, but that do not exist in the database. The lower part of the display shows the indexes that exist in the database, but that are not declared in the ABAP Dictionary.  Optional: To create the indexes which declared in the ABAP Dictionary and are missing in the database, position the cursor on the relevant index and choose Create in DB.
Database Verification - Checking Physical Structure  Log on to the database host as user <PRD>adm or <DEV>adm.  Enter sapdba .  In the first SAPDBA screen, choose k – DB Check/Verification  In the next screen, choose b – DB Verification using DB Verify  In the next screen, choose s – Start Verification . When the operation has been completed, leave the system with q - Return .  Check the created log for errors in directory G:Oracle<SID>sapcheck<date>.dbv (for example: G:OracleR3Psapcheck9901202200.dbv ). If there are any errors, contact the SAP Hotline (SAPNet - R/3 Frontend). You can display the logs from SAPDBA by choosing the option l – Show/Cleanup on the initial screen and a – Show log files / profiles on the next screen

AIX File System Backup

NOTES PROBLEM ACTION RESOLUTION

MONTHLY TASKS
System:__________
Date: ____/____/____
Admin: _____________________
JOB TYPE TASK TRANSACTION DESCRIPTION PROCEDURE CHECK OFF/ INITIAL
R/3 Changing Administrator Passwords SU01

Oracle Analyzing the Entire Database
Changing the Database Administrator Password  svrmgrl connect internal  alter user SYS identified by <newpassword>  alter user SYSTEM identified by <newpassword>  alter user sapr3 identified by <newpassword>  exit

NOTES PROBLEM ACTION RESOLUTION

UNSCHEDULED/OCCASIONAL TASKS
System:__________
Date: ____/____/____
Admin: _____________________
JOB TYPE TASK TRANSACTION DESCRIPTION PROCEDURE CHECK OFF/ INITIAL
R/3 Checking the Transport Management System (TMS) STMS  Configuring the transport routes using a graphical editor  Displaying the import queues for all SAP Systems in the transport domain  Importing all the requests in an import queue  Importing all the requests in a project  Importing individual requests  TMS Quality Assurance  Transport Workflow  Special features when using multiple transport directories
Deleting Old User Master Records SU01
Changing Administrator Passwords SU01
Checking User Activities SM04
Scheduling Jobs SM36  Call Transaction SM36 or choose CCMS  Jobs  Definition   Assign a job name. Decide on a name for the job you are defining and enter it in the Job Name field.  Set the job’s priority, or "Job Class": High priority: Class A  Medium priority: Class B  Low priority: Class C In the Target server field, indicate whether to use system load balancing. For the system to use system load balancing to automatically select the most efficient application server to use at the moment, leave this field empty.  To use a particular application server to run the job, enter a specific target server. If spool requests generated by this job are to be sent to someone as email, specify the email address. Choose the Spool list recipient button.  Define when the job is to start by choosing Start Condition and completing the appropriate selections. If the job is to repeat, or be periodic, check the box at the bottom of this screen.  Define the job’s steps by choosing Step, then specify the ABAP program, external command, or external program to be used for each step.  Save the fully defined job to submit it to the background processing system.

Oracle Extending the Database (Adding Data Files)  Enter the command sapdba . This starts the program SAPDBA.  Choose c - Tablespace administration .  Use option a to enter the name of the tablespace that you want to expand (see the error message for the name of the tablespace).  Choose the suboption f - Alter tablespace <ts> Add Datafile check the recommended values, particularly the file size. Change the file size if necessary.  Use option s to create the new data file. Back up the data file after it has been added. SAPDBA prompts you to start the backup menu after you create the data file: Do you want to backup the tablespace <y/n> (y) ==>  Switch to the backup menu. The name of the new data file is already entered.  Add the name of a tape by entering j– backup volume(s) and then start the backup. For this special backup, you need the next tape from the series of your backup tapes. Remember that in this case, the sequence of the tapes has been moved back by one place for the normal backup. In these cases, you can hold back a number of backup tapes from your normal backup strategy. You also have to initialize these tapes just like your other tapes (for example with SAPDBA).


NOTES PROBLEM ACTION RESOLUTION

ADDITIONAL ADMINISTRATION TASKS
System:__________
Date: ____/____/____
Admin: _____________________
JOB TYPE TASK TRANSACTION DESCRIPTION PROCEDURE CHECK OFF/ INITIAL
SAP System Administration Printing: Installing Additional Printers SPAD
Sending System Messages SM02 You can use short messages to send important information to the users of an R/3 System. You can either display the messages to all users on all application servers, or only to the users who are logged on to a particular application server.
Profile Generator: Maintaining Activity Groups PFCG
Users: Copying a User SU01
Users: Locking and Unlocking Users
Users: Changing a Password
Users: Finding a Missing Authorization SU53 By entering Transaction SU53 in the command field, you can analyze an access-denied error in your system that just occurred.You can use Transaction SU53 from any of your sessions, not just the one in which the error occurred. You cannot analyze an authorization error in another user’s logon session from your own session.
Users: Checking Active Users SM04 You can display all the users active in the system who are logged on to the application server by choosing System monitoring  User overview, or Transaction sm04 .
Maintaining System Profiles RZ10
Operation Modes: Creating a New Operation Mode RZ04
Operation Modes: Adjusting the Timetable SM63  Choose CCMS  Configuration  Operation mode timetable. Alternatively, call Transaction SM63.  Choose Normal operation (24 hr), and Display. The system displays the timetable for the 24 hour cycle. To assign other times to the operation mode, choose Normal operation (24 hr) and Change.  Double-click on the start time and end time that you require.  Choose Assign to assign these times to the operation mode.  Enter the name of the operation mode to be active for the time period that you defined. You can only select productive operation modes. Save the changes.  Finally, save the table.
Operation Modes: Manually Switching Modes
Operation Modes: Scheduling Exception Operation SM63 1. call Transaction SM63.2. Choose Exception operation, and Display.  The system displays the timetable for the 24 hour cycle.3. Go back and then choose Exception operation, and Change. 4. You can now change the date on which the operation mode is to be activated. Choose Day+1, Day-1, Specify a day accordingly. 5. Choose Assign to set the time at which the operation mode is to be activated.  You do not need to define a full 24 hour cycle for exception operation. You must only define the period in which you want the operation mode to be active.6. Save the changes.
Jobs: Scheduling Jobs SM36 1. Call Transaction SM36 2. Assign a job name. Decide on a name for the job you are defining and enter it in the Job Name field. 3. Set the job’s priority, or "Job Class": High priority: Class A  Medium priority: Class B  Low priority: Class C4. In the Target server field, indicate whether to use system load balancing. For the system to use system load balancing to automatically select the most efficient application server to use at the moment, leave this field empty.  To use a particular application server to run the job, enter a specific target server.5. If spool requests generated by this job are to be sent to someone as email, specify the email address. Choose the Spool list recipient button. 6. Define when the job is to start by choosing Start Condition and completing the appropriate selections. If the job is to repeat, or be periodic, check the box at the bottom of this screen. 7. Define the job’s steps by choosing Step, then specify the ABAP program, external command, or external program to be used for each step. 8. Save the fully defined job to submit it to the background processing system.  Note: Release the job so that it can run. No job, even those scheduled for immediate processing, can run without first being released.
Jobs: Checking Job Status and Displaying Logs SM37 1. call Transaction SM37. 2. You can also choose Extended Job Selection, where you can more precisely define the specific criteria that determine which jobs to select. You can display jobs in all clients.3. Once you have set the criteria for you job selection, choose Execute.
TMS: Determining Old Data in Transport Directories
TMS: Clearing Old Data from the Transport Directories
Importing Support Packages SPAM


Monitoring Performance SAP: Checking Performance - Buffers ST02
ORACLE: Checking Database Performance ST04 1. call Transaction ST04. 2. Check the information displayed using the following fields. Data Buffer:  Quality:  Physical reads and writes  Busy waits  Shared Pool Log buffer Calls Commits Rollbacks Recursive calls Parses Reads / User calls Time statistics  Table Scans Short tables Long table  Continued Row  Sorts Disk
SAP: Checking Performance - System Workload ST03
SAP: Checking Operating System Activity ST06
SAP: Memory Management - Checking Pages In/Pages Out ST06
SAP: Memory Management - Checking Ext. Memory/Roll/Paging ST02

Database Administration ORACLE: Naming Conventions for Backup Tapes When you define the data backup in Transaction DB13 of the CCMS, the tape name is defined in the screen Volumes for Database Backup: <SID>B<DATE>
ORACLE: Searching for Missing Indexes DB02 1. call Transaction DB02. 2. Choose Missing indexes under Tables and indexes. The upper part of the display shows the indexes declared in the ABAP Dictionary, but that do not exist in the database. The lower part of the display shows the indexes that exist in the database, but that are not declared in the ABAP Dictionary.3. Optional: To create the indexes which declared in the ABAP Dictionary and are missing in the database, position the cursor on the relevant index and choose Create in DB.
ORACLE: Monitoring the Growth of Extents DB02 1. Call Transaction DB02. 2. Choose Space-critical objects under Tables and indexes to search for tablespaces that are too full.3. Choose Checks  Extents of tables and indexes.4. Compare the values under Extents and Max. extents. If you find tables for which the Extents value has almost reached the Max. extents value, you need to raise Max. extents. You must avoid tables with a large number of extents (>250) because it can seriously affect database performance.
ORACLE: Recovering the Database For more detailed information on recovering an Oracle database, see the SAP Library under SAPDBA DATABASSE RECOVERY.




NOTES PROBLEM ACTION RESOLUTION

SERVICE AND SUPPORT
System:__________
Date: ____/____/____
Admin: _____________________
JOB TYPE TASK TRANSACTION DESCRIPTION PROCEDURE CHECK OFF/ INITIAL
Logging On to SAPNet - R/3 Frontend OSS1 1. Log on to the R/3 System. 2. Call Transaction OSS1. 3. Click Log on to the SAPNet - R/3 Frontend. The SAP R/3 screen appears. 4. Keep the default client (001). 5. Enter your SAPNet user ID in the field User ID.6. Choose a logon language and confirm with ENTER. You are now logged on to the system. If you log on in English or German, the screen System News appears. If you log on in Japanese, the Inbox appears.
Searching the Notes Database 1. Log on to SAPNet - R/3 Frontend. The menu System News appears. 2. Choose Continue. Your Inbox appears. 3. Choose Gen. functions. A window appears that contains the group Notes. 4. In this group, choose the option Find. 5. Enter search criteria. You can use wildcards (*). For example, if you enter 'remote', all Notes appear that contain the term 'remote' (such as remote access, remote services, and so on).
Entering a Customer Message 1. Call the Inbox of the SAPNet - R/3 Frontend. 2. In the first row of options choose SAPNet. 3. Choose Messages  Create. The dialog box Select Customer System/Platform appears. The system displays installations for which you can create customer messages. 4. Double-click the installation number for the relevant installation. (You can find out the installation number of an SAP Systems by choosing System  Status.) 5. Enter all the necessary information. 6. Save your entries.
Tracking Message Status 1. Choose SAPNet  Messages  Sent to SAP. 2. Double-click the short text of the message you are interested in. 3. Choose Action Log. The information about the message appears. 4. Read about how the message is being processed.5. Choose Close to go back to the original screen.
Receiving Responses from SAP 1. Choose SAPNet. 2. Choose Messages (in the group SAPNet). 3. Choose Inquiry from SAP. The screen Inquiry from SAP: Original messages appears. 4. Double-click the short text message that you want to answer or add to. 5. Choose Long text to display the answer from SAP. You can read it or print it out. 6. Return to the previous screen. 7. Choose Display  change. 8. Choose Supplementary info. 9. Enter the information that will help SAP process your message. 10. Return to the previous screen. 11. Choose Send to SAP
Confirming an Closing Messages 1. Go to the SAPNet - R/3 Frontend Inbox . 2. Choose SAPNet.3. Choose Messages in the group SAPNet. 4. Choose Solution provided. The screen Solution provided: Original messages appears. 5. Choose Long text, to display any additional information provided by SAP. 6. Check if a Note is attached. 7. Choose Confirm, to close the problem message permanently.
Finding Support Packages 1. Choose SAPNet. 2. Choose Service (in the group SAPNet). 3. Choose Service (in the group Service). 4. Choose SAP Support Packages (in the group SAP Patch Service). A list of available R/3 Releases appears. 5. Double-click the icon "+" in front of the R/3 Release that corresponds to your installation. A list of available Support Packages appears. If you have an add-on release, choose Add-on view to display the Support Packages developed especially for add-on releases. 6. Search the list for the Support Package that you need.
Requesting Support Packages 1. Log on to the SAPNet - R/3 Frontend and choose Inbox. 2. Choose SAPNet. 3. Choose Service (in the group SAPNet). 4. Choose Service (in the group Service). 5. Choose SAP Support Packages (in the group SAP Patch Service). A list of available SAP Releases appears. 6. Double-click the "+" in front of the SAP Release that corresponds to your installation. You now see a list of available Support Packages. 7. Check the Support Package you want and choose Request patch. A new screen appears that lists all installations for which you are responsible.8. Select the installation you want. 9. In the column SID (System ID) enter the system name (for example, C11) where you want to use a specific Support Package. 10. Choose Continue to request the Support Package. The list of available Support Packages appears again and you receive a confirmation that the Support Package was requested.
Downloading and Importing Supoort Packages 1. Enter Transaction SPAM or choose Tools  ABAP Workbench  Utilities  Maintenance  Patches. 2. Choose Patch  Download. The dialog box Electronic Parcel Service: Confirm Transmission appears with a list of Support Packages you have requested. 3. Choose one or several Support Packages. 4. Choose Continue. As soon as the Support Package has been downloaded, the SAP Patch Manager (SPAM) screen appears. 5. If you want to use the Support Package immediately, choose Yes.
Online Service System: Import. Prelim. Trans. from Ext.Syst. 1. Log onto system <DEV>. 2. Enter Transaction STMS . The initial screen of the Transport Management System appears.3. Choose Overview  Imports. The system reads the import queues. 4. Double-click <DEV> in the Queue column or select <DEV> and then choose Import queue  Display. 5. Select the transport request of the preliminary transport and choose Request Import.
SAP's Remote Services 1. Early watch2. Remote Consulting
Opening a Connection for Remote Service For more detailed information on setting up a Remote Service connection, see the guide The SAPNet - R/3 Frontend User Guide. You can download this guide from the following address: http://sapnet.sap.com/oss-guide .
Testing a Remote Service Connection 1. Enter Transaction SEPS . The Electronic Parcel Service initial, screen appears. 2. Choose EPS  Connection test. A list appears showing if the connection worked. The system tries to receive data from the server. If the test fails, note the error message.3. Leave the screen. 4. Then select Send parcels to server and repeat the connection test. 5. Repeat the test.
Scheduling an EarlyWatch Session In SAP’s EarlyWatch service, an experienced SAP technician inspects your R/3 System, operating system, and database system remotely. The idea is to give you advance notice of any emerging problems (such as shrinking free space) and to ensure that your system is configured for optimum performance. You must arrange for an EarlyWatch session, and, as with all SAP remote services, you must first establish a connection to SAP before an EarlyWatch technician can log on to your system.
Scheduling a Remote Consulting Session Choose the component XX-RC (RC stands for Remote Consulting) and then add the area you are interested in, for example XX-RC-BC.For more information, see Note 65864.
Registering Developers and SAP Objects Using SSCR For more information, see the R/3 Modification Guide under:Registering a Development userRegistering an ObjectDisplaying an Overview

NOTES PROBLEM ACTION RESOLUTION