SAP Basis Guide

Document Sample
SAP Basis Guide Powered By Docstoc
					Feature’s of SAPGui.
The different features on the Initial SAPGui screen,

Maintain Favourites
Activate display of Technical names in menu tree
Activate Quick cut and Paste feature when required
Activate to display the Key id’s in drop down list wherever it is available.
All the following transactions explored using the Menu tree under Tools.
Transaction SU01
This transaction is used to manage the SAP users; it can be used for Creating
a User, Changing a User, Displaying, Deleting, Locking, Unlocking and Set
new password. As in Solaris Chemtech we have implemented the Central
User administration model, all System and clients cannot perform all these
mentioned function using SU01. The SAP System UED and Client 150 are
defined as the controller of all child systems and clients integrated in the
model. Each SAP systems client 000, 001 and 066 are not included in this
model.
The transaction further includes multiple tabs within in which other
information is to be maintained as required and some are mandatorily to be
maintained. The General information contains, Name of user in 2 parts – Last
and First. We also can maintain more information’s like Communication
language, Department, Function, Telephone, Email id, Company address,
Under Default Tab - User type –“Dialog”, Valid from, Valid to, Default
parameters like Logon language, date format, Decimal Format, Time format,
Output device, Time zone of the user, Under Roles – multiple roles will be
assigned along with the child receiving system.




Transaction SM50
To monitor the status of all the work processes in the SAP system, this is
used. This lists all the work process with their type, current status, and
program, user id, action being performed at that point of time. This is always
dynamic and a good screen view is to have work processes free (waiting) so
that any call by a user can be taken up immediately without any delay in
response time.

In case a work process is stuck then we cancel the work process job selecting
– Process>Cancel without core. In case the work process is stopped after an
error in one of the job it was executing, then Restart it choosing – Process>
Restart after error >Yes so that the work process is available for the users.
Transaction SM04
By this transaction we can check how many users are logged into the system
and in which client and how many session each user is generated and in each
session what transaction is being executed. We also have the time when this
session was started. The terminal used by the User, type of connection and
the amount of storage space utilized by the user depending upon the
transaction and selection options.
Transaction SM21
In this transaction the SAP system log is displayed for the values inputted in
the initial screen. The values that can be maintained is the From Date
The list can be restricted for Problems Only, Problems and message and All
messages. The information in this list can further used to analyze the errors
which are indicated with Red sign under Priority. Also we get information of
Tcode that was used by the user when the error got generated.


Transaction ST22
This transaction lists the ABAP dumps generated in the system, we can
restrict for a date, user as required. This each record indicates the reason for
the error, transaction code, variables that caused the error. The types of error
can be of various kinds for which action is to be taken to fix this error from
happening again after analysis. For this we refer also the SAP notes on
http://service.sap.com/notes with the search terms of the name of program,
transaction or other term
Transaction AL08
This is a global version of SM04, in which we can monitor the users logged to
a SAP system from multiple Application servers. The number of users logged
using each application server will be shown and the total kinds of connections
like dialog and RFC .
transaction SU3



MAINTAIN OWN USER PROFILE
Transaction SP01
With this transaction we can monitor the number of spool requests and also
how many spool requests were outputted under the Output requests
In the list we can also set filters to view that were successfully printed, ended
with error, processing or waiting. The print job can be reprinted with the
original parameters or change and print to another printer or page format.

				
DOCUMENT INFO