民丰纸业5troubleshooting.pptVIP

Troubleshooting Learning Objectives Identify the Transaction Code Logon Errors Users Locked out of R/3 ABAP Short Dump SU3 - Maintaining User Defaults and Options Changing Printers Create Variants Create Variants (2) Save Variants Access Variants Access Variants (2) Exercises Summary Troubleshooting TroubleShooting At the conclusion of this unit, you will be able to: Identify the transaction code for a particular screen. Understand common sources of logon errors. Lock/Unlock User’s out of R/3 Understand how to look up ABAP dumps. Understand how user defaults are maintained. Understand the Print function in R/3. Understand how to create, save and access variants 1. Wrong client 2. Wrong Password 3. User Account expired or does not exist 4. System is down 5. User is locked out Logon Errors could be caused by any of the following: After 6 Attempts to log in, the user is locked out. Unlock Parameters Defaults Printer Spool Control Date Format Decimal Format Address Logon Language User data 2. Remove “Local printer” 1. Use Matchcode 3. Select printer SAVE Variants can be used to save parameters in commonly used transactions for future use. Enter required information on screen Click the Goto option. Click Variants. Click Save as variant Enter in variant name and description and click the Save icon. Go to the input screen you require. Click the Goto option. Click Variants. Click Get You will see a list of variants. Double click the one you want. You can use System ? Status to find the transaction code for a particular screen. Common sources of logon errors include wrong client, wrong password, user account expired or does not exist, system is down, user is locked out. If a user attempts to log in unsuccessfully 6 times, the system will lock them out. Unlocking users is done through the transaction SU01. You can look up ABAP dumps when GUI crashes occur to determine what happened. User defaults are maintained by users or administrators. The Print