Basis - System Message SM02

Configure System Messages

For example, when a user blocks himself out and receives a message :

"User blocked. Contact system administrator"

You can open a repair and change the message in Message class 00.  

This can be done in transaction SE91 - Message Maintenance.

Messages allow you to communicate with the users from your programs.  

They are mainly used when the user has made an invalid entry on a screen.  

To send messages from a program, you must link it to a message class.  

Each message class has an ID, and usually contains a whole set of message. Each message has a single line of text, and may contain placeholders for variables (e.g. & & & - three variables).  

All messages are stored in table T100.  

Once you have created a message, you can use it in the MESSAGE statement in a program.

Changing the default password for sap* user

You are trying to change the password for sap* user, however when you go into su01 and enter sap* as the user name, the following message is displayed, user sap* does not exist.

You can delete the SAP* user using ABAP code :-
Delete from usr02 where bname = 'SAP*' and mandt = '***';

Where '***' means your client no.

Then login to your client using password SAP* and password PASS

However, if you delete it, then it will automatically created once again with password PASS

The userid, SAP*, is delivered with SAP and is available in clients 000 and 001 after the initial installation. In these 2 clients, the default password is 07061992 (which is, by the way, the initial date when R/3 came into being...). It is given the SAP_ALL user profile and is assigned to the Super user group. When I say it is "delivered" with SAP, I mean that the userid resides in the SAP database; there are actually rows in the user tables used to define userids.

If you delete the userid, SAP*, from the database, SAP has this userid defined in its kernel (the SAP executable code that sits at the operating system level, i.e., disp+work).  When this situation exists, the password defined in the SAP code for SAP* is PASS.  This is necessary when you are performing client copies for example, as the user information is copied at the end of the process. You can sign into the client you are creating while a client copy is processing using SAP* with password PASS (but you should have a good reason to do this - don't change anything while it's running).

Anyway, if the SAP* userid is missing, you can sign in to the client you want and simply define it using transaction SU01 and, as I stated above, assign it to the SUPER user group and give it the SAP_ALL profile.  You define its initial password at this point. If you've forgotten its password and don't have a userid with sufficient authorization to create/change/delete userid,  
then you can use the SQL statements to delete it from the database and then you can use SAP* with PASS to sign back into the client you want to define it in and recreate it.

There is also a profile parameter which can override the use of SAP* with PASS to close this security hole in SAP (login/no_automatic_user_sapstar).  When this parameter is defined either in your DEFAULT.PFL profile or the instance-specific profile and is set to a value of '1', then the automatic use of SAP* is deactivated. The only way to reactivate the kernel-defined SAP* userid at this point would be to stop SAP, change this parameter to a value of 0 (zero), and then  
restart SAP.

The default password for SAP* is 06071992. (DDIC has 19920706)

Changing the Title of SAP Transaction

Sometimes, internal user or customer might request you to change the Title of the SAP Transaction code to a more meaningful one and SAP allows this to be done painlessly.

The steps to change the Title of any SAP transaction code are as follows:

First, goto tcode SE63

On the top left Menu of the screen - Click Translation - Short texts - Transactions

For example, assuming you want to change the title of the tcode FB01 from Post Document to Post Document for G/L.  On the first screen, fill in the following information:

Transaction code - FB01

Source Language - English
Target Languate - English

To change the Title, click the Edit button

On the second line, type in the Title (For e.g. Post Document for G/L) you want for the transaction code

Click the Save button

Now, called up the transaction code /nFB01 again and you should be able to view the new Title.

Creating a SAP mail distribution lists

Transaction code SO23

X Shared distribution lists

Name : ZXXXX

Title : XXXXX Mail Distribution

Don't enter anything in the Folder field.

Folder : Click the down arrow

Next screen :

Folder Name : ZXXXX

Folder Title : Mailing address

Folder Area : Shared

Click Create Folder

Next screen :  

Indexing : Tick

Specify the 'Retention period of a document in this folder (days)'.

Choose the 'Folder access authorization'.

Finish, click the Enter button.

Click the tabstrips 'Distri. list content' to type in your mailing list.

Save your entries.

Finally, test it by sending a mail via the distribution list ZXXXX.

Fwd: Delete multiple spool request

The program are RSPO0041 or RSPO1041.

This is handy whenever you encounter a user who managed to create a lot of spool requests which are choking your system.

Deleting them with SP01 will be too slow and you will get time out if it exceed the online time limit specify by your basis people.

Find your SAP transport request number even if you forgot

If you happend to be one of those who forgot the transport request number of your abap program.

You can easily find it via the Versions Management.

Steps :-

Transaction SE38

Filled in your ABAP program name.

Then click Utilities -> Versions -> Version Management

SAP system will display this sample list :-  

Versions: Report source ZPROGRAM

Version Cat Fla SAP Rel. Arch Request              Date       Time     Author

Version(s) in the development database:

X activ          X  46X                                      01.08.9999 15:21:56 SAP

Version(s) in the version database:

X 00002             46X        ABCD123456      01.08.9999 15:52:43 SAP
X 00001  S    X  46X                                     00.00.0000 00:00:00

Hide the User Menu

Is there a way of masking or hiding the User Menus as we are using SAP Standard Menu instead of User Based Menus?  

To put it simple, when the user logs on to the system he should have only the SAP Standard Menu.  

You have two ways to control this :

1.  Default hide for all the SAP users.

Goto SM30 and edit the table SSM_CUST and set ALL_USER_MENUS_OFF = YES and transport the same in production server.  

or  

2.  Hide based on individual SAP users.

you can also try SM30 and maintain table USERS_SSM for individual users.

How can I create multiple User Id at Random

We usually created Id though SU01, it only one by one.
Can I create multiple user id having same profile at once.
 

Yes you can, use tcode SCAT. First, make sure your client setting (SCC4) is enabled with ' X eCATT and CATT allowed'. Just in case your Production disabled this.

- Then, you need to create a simulation (test case) of creating new user id by calling tcode  
 SU01 later.  
- Test case must start with Z, example ZCREATE_NEW_USER. Create this case, put title and  
  choose component as BC (basis components).  
- Save and choose Local if you dont want to transport it or choose a dev. class (example ZDEV)  
  if you want to transport it later.
- Go back and click Change button. Then key -in Object as example SU01, and choose Record  
  button on top. When it prompts to enter Transaction code, key in SU01 (if for roles,  
  key-in PFCG) and begin recording. As usual in SU01 create 1 user id, dept field, password,
  roles, group and so on.  
- Make sure you press Enter on each field because we want to capture the value/object and  
  SCAT is a bit stupid if you become familiar later....but still useful...indeed.  
- You will see a clock on the bottom which means the recording process is on going.  
  Once done, click Back button and press End button to end the recording.

Note -  I noticed you said the profiles are all the same. Then this is much easier...no need to enter the roles/profiles, just duplicate this ID and change the name, dept and password only.

Okay..first stage has finished. Then double click the Object to begin inserting parameters. Then you will see an object for each fields that you run from SU01. Choose the right field example user id (BNAME) and choose button 'Insert Import Parameter (F6)' and you may click Next Screen to 'watch' what have been recorded and proceed to choose several other objects like password field (PASSWORD1, PASSWORD2), roles field (AGR_NAME), group field etc. If you happen to choose the wrong object, then you can reset back (Edit -> Reset Parameterization). You may see so many junk fields captured and this is because SCAT records every steps/dialogs.  

Once done, choose Back and save this case. Then you need to click 'Goto -> Variant -> Export' and save it. After that use Ms Excel to open it and begin inserting all other user ids. Save and close. Remember to close this file because SCAT will use it.

Then last one, get back to SCAT and click button execute, processing mode chose Background, choose external file 'the one you created with Excel' and execute. At this moment don't use tcode SU01 bcoz you may interrupt the simulation. Wait for the logs.  If you see reds then error was  
happening.  

Hoping this will help you. I have done (Sap 4.6C) this to create thousands of user ids and also thousands of roles/profiles (pfcg). I heard with Sap 4.7, the SCAT has so many extra features.....

Correct me if i'm wrong elsewhere.....just shared my experience.

How can I print A3 format in SAP

My printer is HP LaserJet 5100

Note I can print ms word document in A3 format but I can't print A3 format in SAP

My output device setting are:

DeviceAttributes:
Device Type = THSAPWIN: MS-Windows-Printer via SAPLPD
Device Class = Standard printer
Access Method:
Host Spool Access Method = S: Print Using SAP Protocol

When I print SM50 output and select format X_65_255, it can print successfully but its format is A4.

What may I do wrong? Please help me how to set up for A3 printing in SAP.

Ps. Do I need to assign A3 format to be default format in that printer?

Is this task for BASIS or ABAP?

Bankly

In printer settings - SPAD - tray info - you can give the Page format for that tray .  
did you try setting that ? Try setting  DINA3.

Liju

Go to START --> SETTINGS ---> Printers

Right click on HP LaserJet 5100 ... Properties..
General Tab --> Printing Preferences --> Advanced --> Paper Size -->
Change it to 14x11 or A3

and

hplaserjet 5100 --> Properties --> Advanced Tab
Printing Defaults --> Advanced --> Paper Size -> change it to 14x11
or A3

hplaserjet 5100 --> Properties --> Device Settings tab -> Autoselect -
-> A3 or 14x11...

PrakashP

Our ABAPer already changed some attributes(ex. font name & size) in print control of SPAD followed by SAP Notes 21738.

Like this ->
# THSAPWIN Z_65_255

# SAPWIN indicatior makes it possible to send via berkeley protocol
\e%SAPWIN%
# change WinCharSet to 222 (Thai)
\eW222;
# set orientation(LANDSCAPE)
#\ePL
# set font name
\eFAngsana New;
# set font size(5.5ponits)->8p->5.5
\eS220
# set vertical spacing(8.7LPI)
#\el3.0;
# set horizontal spacing(24.0CPI)->20->18 (255/11) ->23
#\ec5.0;
# set top/left margin(1.0cm=568.5)
#\eMT567;
#\eML567;

However, it take moderately time to change font size and test report printing for A3 format.

Thank you for your recommend.

Bankly

I follow by your instruction. It's work well.

Note It doesn't need to setup these config at all.

Tab "Output Attributes"
Paper tray = "Paper tray 3"

Tab "Tray Info"
Tray 3 = "DINA3"

Key points of this solution, If the SAP spool server and the Microsoft Windows spool system are not on the same host, you must create a remote PC connection to the printer and force paper size to be A3 (Prakash's instruction)

By the way, I also adjust HP Laserjet 5100 from "EXEC" to "A3" in Tray 3 physically too. After that I can print ABAP List in A3 Format successfully.

Thank you again for the solution.

Bankly

Information on how the OPS$ Users Work

Content Author: Sachin D. J.

Does anyone have information or a good understanding of how the OPS$ users work and operate under an Oracle SAP environment.

I would greatly appreciate some assistance as I have problems with my Brconnect and Brbackup within DB13 due to the OPS$ users.

I need info on how to permanently delete the OPS$ users and then recreate it, due to the fact that I have incorrect OPS$ users in some of the tables affected by the OPS$ users.

Below is the document I have prepared on recreating the OPS$ machanism. It helped me solve all my problem on DB13 and also on Schema owner connecting to database.

Hope this could help you.

Also refer to the following sapnotes:  
1. 400241 : Problem withe ops$ or sapr3 connect to oracle
2. 134592  : Importing the SAPDBA role (sapdba_role.sql)
3. 361641  : Creating OPS$ users on UNIX
4. 50088   : Creating OPS$ users on Windows NT/Oracle
5. 437648  : DB13: External program terminated with exit code 1/2

----------

select owner from dba_tables where table_name='SAPUSER';

## If owner is not the sid you require, then drop the table SAPUSER

Drop table "<owner>".SAPUSER;
#or#
Drop table "domain\OPS$SIDadm".SAPUSER;

## IF THE ANSWER IS 0 ROWS SELECTED THEN CREATE THE TABLE SAPUSER

# Check whether OPS$<SID>adm user exist, if no then create it

create user OPS$SIDadm default tablespace psapuser1d temporary tablespace psaptemp identified  

externally;

# if exist then drop it;

DROP USER OPS$SIDADM;
 

# Grant connect & resource roll to OPS$<SID>ADM;

grant connect, resource to OPS$SIDADM;

# Creat table SAPUSER

create table "OPS$SIDADM".SAPUSER ( USERID VARCHAR2(256), PASSWD VARCHAR2 (256));

# update "OPS$<SID>ADM.SAPUSER with the follwoing command

insert into "OPS$SIDADM".SAPUSER  values ('SAPR3', 'sap'); #sap = <password>

# Under NT it is required that user sapservice<sid> can also access the SAPUSER table. In order  

to avoid problems with the data consistency, it does not make sense to create an additional  

SAPUSER table having the same contents. You should rather define a synonym. Check if a suitable  

synonym exists by using the following call:

SELECT OWNER, TABLE_OWNER, TABLE_NAME FROM DBA_SYNONYMS WHERE SYNONYM_NAME = 'SAPUSER';

# IF NOT THEN CREAT IT  

create public synonym sapuser for OPS$SIDADM.SAPSUER;

# if synonym already exists drop the existing synonym by the following command

drop public synonym sapuser;

#If another name <name> is returned as first value:

DROP SYNONYM "<name>".SAPUSER;

# AND CREAT it again with above command

# To allow access to the synonym (or the associated table), a grant
           needs to be executed. The authorization for this has only the
           ops$ user who is the owner of the actual table - that is
           ops$<sid>adm. Therefore, you need to log on with the
           corresponding operating system user (<sid>adm) and execute the
           following commands:

            CONNECT /
           GRANT SELECT, UPDATE ON SAPUSER TO "OPS$SAPSERVICE<sid>";

# Now you can recreate the synonym (not PUBLIC, if possible):

 CREATE SYNONYM "OPS$SAPSERVICESID".SAPUSER FOR "OPS$SIDADM".SAPUSER;

 CREATE SYNONYM OPS$SAPSERVICESID.SAPUSER for OPS$SIDADM.SAPUSER;
 

# COMMIT AFTER COMPLETION of the activity & restart the DB

How to Check Missing Authorisation for User

How to check the missing authorisation for the user not having the option "/nsu53 ?"

You can use the following procedures to determine which authorizations a user requires to carry out a transaction:

You can use Trace function, ST01, you can trace the user activity and from the log you can see the authorization missing.

Start an authorization trace using the ST01 transaction and carry out the transaction with a user who has full authorizations. On the basis of the trace, you can see which authorizations were checked.

This procedure generally works well. However, sometimes the result is very surprising because certain programs can and do ignore some authorization checks by using preliminary checks and buffered results. In such cases, these methods are not very effective. You can recognize these cases because certain fields of the corresponding programs are specified with * or DUMMY at some point of the authorization check.

Analyzing authorization problems in an unknown program

The most frequently used method to analyze authorization problems in an unknown program involves you setting the Debugger breakpoints to the AUTHORITY-CHECK and MESSAGE commands. Then execute the program and analyze its behavior.

Determining all the authorizations a user has for an authorization object

When troubleshooting, it is often helpful to find out all the authorizations a specified user has for a specific authorization object. A simple method of reading these authorizations as raw data from the user master record is to execute the GET_AUTH_VALUES function module in the SUSR function group. Use the SE37 transaction or SE80 in test mode to do so. The result table is not formatted for output, but is very compact and easy to understand for authorization experts.

Analyzing an authorization problem that occurs for only one user

It is often the case that a certain authorization problem occurs for only one specific user. This kind of authorization problem generally affects users with no Debugging authorization. If you want to assign a user Debugging authorization without changing the HR authorizations, you can add the S_A.DEVELOP authorization profile (if available) to the user's authorization profiles. In production systems, note that changes such as these to authorizations enable users (with relevant knowledge of the development environment) to access any system data easily (especially in other clients

Incorrect SAP login logs

With report RSUSR006, you can check those users that have been locked.

For those that are not locked, the report will list down the number of wrong login that the users have done.

How To Do the TMS Configuration?

We have two systems with version ECC 5.0

The SID is XY1 - Development & Quality
                XY6 - Production

Now we need to configure TMS between these two systems by assigning XY1 as domain controller. I beleive we also need to establish an RFC Connection for this. Also explain how to update the local files of this systems?

How can I make thro it?

First decide which system you would like to define DOMIAN controller. Configure the Domain Controller Steps to configure
------------------
1. Login to the system with sap* in client 000
2. Goto SE06.
3. Click Post installation activities
4. Goto STMS
5. It will ask for Domain controller name.
6. Enter DOMAIN_<SID> as domain controller name and enter the description.  
7. Click Save button

Steps to add the other system with Domain controller
----------------------------------------------------
1. Login to system with sap* in client 000
2. Goto SE06
3. Click Post installation activities
4. Goto STMS
5. It will ask for Domain controller name.
6. Enter System ID of the Domain controller
7. Enter DOMAIN_<SID> as domain controller name and enter the description.  
8. Click Save button  
9. Login to Domain controller system  
10. Approve the added system.

List of Inactive Users Logs

To list out all the users who are inactive for the last 6 months, which means they have not logged into the SAP server.  

If you have lots of affiliates to your main company, this will result in lots of users. Out of them, there might be lots of inactive users who have left the company.  

You may wish to delete those inactive users.  

Use SA38 to run RSUSR200.  

This report is part of the AIS (Audit Information System) and will report users who have not logged on for a specified period of time.

Mass Lock All Printers with SPAD

If you have lots of printers (50 or more) and need to lock them for maintenance, you can used this mass locked printers tips to locked or unlocked all the SAP printers at one go.

To mass Lock all the printer in SAP:

Go to transaction code SPAD

On top of the screen menu click Utilities -> For output devices -> Export devices

On the screen Import and Export of Device Descriptions:

Export/Import file name: c:\temp\printer.txt

Frontend computer: Tick

Export: Tick

Export Export: Tick

Output device: Choose the Selection options Pattern and type a *  
                      (* for all or a* for all printers starting with a)

Click the Execute button

Open the text file do a replace all of PADISABLED = "" to PADISABLED = "X"

Then import the same file.  

or

Another way is to go through each output device in SPAD and click on 'Lock Printer in SAP System' which is in the DeviceAttributes tab  

Meaning behind those unconditional tp command mode

Content Author: PrakashP

Can anyone tell me what's the meaning behind all those unconditional mode U1 or U126 or U148 or anything?
tp import transportrequest <sid> clientxxx U1
tp import transportrequest <sid> clientxxx U126
tp import transportrequest <sid> clientxxx U148

The u stands for unconditional force ( how hard you want to force the request into the system - do you want to overwrite without warnings, or softly try to load the objects).  

0: Called a overtaker; change request can be imported from buffer without deleting it and then uncoditional mode 1 is used to allow another import in the correct location.  

1: If U1 is used with the export then it ignores the correct status of the command file; and if it is used with import then it lets the user import the same change request again.  

2: When used with tp export, it dictates the program to not to expand the selection with TRDIR brackets. If used in tp import phase, it overwrites the originals.  

3: When used with tp import, it overwrites the system-dependant objects.  

5: During the import to the consolidation system it permits the source systems other than the integration system.  

6: When used in import phase, it helps to overwrite objects in unconfirmed repairs.  

8: During import phase it ignores the limitations caused by the table classification.  

9: During import it ignores that the system is locked for this kind of transport.  

u128 is combination of 128 OF THE above points.

Monitor and Administrate 4 SAP Systems

If there are 4 systems installed SAP, how should I connect all of them in one network so that I can administrate the 4 systems with one among them as main server.

This should help you:

After installing an R/3 System, you can use transaction RZ20 to monitor the system. To monitor all systems of your system landscape centrally from one system, first customize the alert monitor by choosing Tools > CCMS > Configuration > Alert monitor or calling transaction RZ21.

Then, to specify the remote systems by System ID and RFC destination (which must have been created beforehand), choose Technical infrastructure > Create remote monitoring entry.  

Next, to change your monitor definitions (you can only change your own monitors),  choose Tools > CCMS > Control/Monitoring > Alert monitor or call transaction RZ20.

Activate the maintenance function by choosing Extras > Activate maintenance function.
Then, double click on the monitor and choose Monitoring change.  
Parameter R3system defines which systems can be monitored by an alert monitor. Change parameter R3system from <CURRENT> (only the current R/3 System can be monitored) to <ALL> (all R/3 Systems defined in RZ21 can be monitored).  Save the changes.

It will help you monitor & use spome other activities centrally.

No System name and transaction code in SM04

If you have more than one application server, use AL08 instead of SM04.

or

It is because they are at the logon screen which has established a connection.

You will notice that the transaction code shown when there is no user name is SESSION_MANAGER.

This shows you which workstations out there have the login screen up but have not yet entered a user name and password.

The transaction column shows the Last executed transaction code.  

Sometimes your users will have multiple sessions open. If they do, to the system, it is the same as multiple logins as it relates to the resources used etc.  

So the user name will show up more than once in AL08.

Under the application server they are logged into, each instance of that user name on that application server represents a session open.  

For instance if you run AL08, you will have your name show up at least twice on the application server you are logged into.  

One will show AL08 and the other will not have a transaction next to it.  

Then you will notice your user name showing up on all other application servers with no transaction. This is because you are using AL08.  

Parallel printing to all the SAP device printers

If you have a situation where reports need to be send to multiple printers, you can configure a pool device type. A pool device type contain a list of SAP printers which the reports will be directed to.

Do this in transaction code SPAD for spool administration.

For example, in SPAD, type ZXXX next to the field 'Output devices',

Click the button Output devices.

In change mode, click the Create button.

Specify the Device type of your printer.

Click the tabstrips 'HostSpoolAccMethod'.

In the field "Host spool access method" set to "P: Device Pool".  

Click the tabstrips 'DevicePool'

Click the options "Send to all devices in pool".

Type in the list of the SAP printers device you want the report to go to in this pool under the section 'Pool Device List'.  

Now, when the users send a print to the new device for e.g. ZXXX, it will print to all the spool device you have specify.

The above step is done using SAP 4.6c

Remove the import all request (big truck) button from STMS

To change the automatically generated profile parameters for the transport control program:

Log onto the SAP System functioning as the transport domain controller (the QA or PROD system).  

Call Transaction STMS.  

Choose Overview -> Systems.  

The system overview appears.  

Double click on the SAP System you want to change.  

In the SAP System, click Configuration -> Change.  

The screen Change TMS Configuration: System <System name> appears.  

Choose the tab Transport tool.  

First, all the global parameters are displayed and then all the local parameters.

The global parameters are identical for all SAP Systems in the domain.

To change a global parameter to a local parameter, you must delete the global parameter and enter the new local parameter.

The operating system is only displayed if values exist for this field.

Finally to remove the import all request (big truck) button from STMS

·        click the Insert Line (button)

·        Tick Global

·        Fill in Parameter = NO_IMPORT_ALL,   Value = 1.

Save your entries.

Reporting a Problem to SAP

When I tried to report a problem to SAP using  
http://service.sap.com/message  url it provided 4 steps to follow:

1) Choose system
2) Prepare Solution Search
3) Find Solution
4) Enter Message

I could do the step 1 but dont know what to do at steps 2, 3 and 4.

SAP changed the customer message screens so you now have to navigate through a search of the SAP Notes before being able to create a message.

We usually search the Notes extensively before we create a message, so we just enter a blank search and then go on to create the message.

Follow the steps, It may solve your problem:

1. Copy following url into web browser : http://service.sap.com/message

    It will ask you for your OSS ID and password .
   A Screen which contain a push Button Select System displayed .  

2. Push the Button Select System .
   It will open a sub screen in which there will be a hierarchical structue which looks like

   - <Your SAP Customer Number >
        -<SAP Installation number for a specific product1 >
            <radio Button><System SID1 for which you have registered a license>
            <radio Button><System SID2 for which you have registered a license>

        +<SAP Installation number for a specific product2 >
        +<SAP Installation number for a specific product3 >

Here  + indicate that you have a sub tree .
        Specific product  like SAP R/3 T for Services , SCM , CRM , ERP   etc

3. Select the system for which you need to log a message
   It will take you to message screen  screen.

4. Select you domain for problem for example Basis problem with Database where dataBASE IS  oracle then Message type will be BC-DB-ORA
* .
5 Select priority of Message

6 . Write Message and send it to SAP

SAP Administrator Daily Activities

SAP DAILY ACTIVITIES

1] Check that all the application servers are up:
sm51           SAP Servers
sm04/al08    Logon Users

2] Check that daily backup are executed without errors
db12 Backup logs: overview

3] SAP standard background jobs are running successfully. Review for cancelled and critical jobs.
sm37 Background jobs--- Check for successful completion  of jobs. Enter * in user-id field and verify that all critical successful jobs and review any cancelled jobs.

4] Operating system Monitoring
st06

5] Extents monitoring
db02 Database monitoring--Check for max-extents reached

6] Check work-processes(started from sm51)
sm50 Process overview-- All work processes with a running  or waiting status.

7] Check system log
sm21 System log-- Set date and time to before the last log  review. Check for errors ,warning, security, message-bends,   database events.

8] Review workload statistics
st03 Workload analysis of <sid>
sto2 tune summary instance

9] Look for any failed updates
sm13 update records

10] check for old locks
sm12 lock entry list

11] Check for spool problems
sp01 spool request screen-- check for spool that are in  request for over an hour.

12] Review and resolve dumps
st22 ABAP Dump analysis

13] Checking .trc file in SAP trace directory for block corruption on daily basis.
C:\ORacle\sid\saptrace

14] Archive backup
brarchive -f force -cds -c
Insert the archive backup tape

15] Review NT system logs for problem
-> NT system log- look 4 errors or failures
-> NT security log- failed logon 2 sap servers
-> NT Application log -look 4 errors or failures

SAP Load Balancing

The benefit of segregating user groups by line-of-business (using logon groups) is related to the point that groups of users (like SD users or HR users, for example) tend to use the same sets of data.  They (generally) work with the same groups of tables and hit the same indexes using the same programs (transactions).

So, if you can group all of the users hitting the same tables, onto (or one set of) App server(s), then you can tune the App server buffers to a much greater extent.  If the FI users (generally) never hit against the HR tables then the App servers in the FI group don't (generally) have to buffer any HR data.  That leaves you free to make memory and buffer adjustments to a more drastic extent, because you don't have to worry (as much) about screwing the HR users (as an example), when you're adjusting the FI server group.

So, (in opinion only) you should start with a buffer hit ratio analysis / DB table & index access analysis (by user group) to see where you would get the best benefit from this kind of setup.  If you don't have this kind of info, then creating logon groups by line-of-business may have no benefit (or worst case, may make performance degrade for the group with the highest load %).  You need some historical information to base your decision on, for how to best split the users up.  

You may find that 50% of the load is from the SD users and so you may need one group for them (with 3 App servers in it) and one other group for everyone else (with the other 3).

The logon group(s) will have to be referenced by SAP GUI, so SAP GUI (or saplogon.ini + maybe the services file, only) will have to change to accomodate any new groups you create in SMLG.  Also consider that there's variables for time-of-day (load varies by time-of-day) and op-mode switches (resources vary by op-mode).

SAP System Performance Issues

My server becomes slow when more users login.
What could be the reason?  Is it because of less hardware resource?

Server configuration is 104GB HDD, 2GB Ram.
OS:Win 2003 server.
Database:Oracle.

I manage SAP R/3 4.6C systems on Risc 6000 machines, under Oracle 9.2.

The overall performance problem for me is to know if SAP response time is acceptable ; if not, do this :
- at AIX level : utilities are topas, to catch what's wrong : Disk I/O ? CPU bottleneck ? Too much swap ?
- at Oracle level : tkprof but don't know much about this.
- at SAP level : you can manage SAP memory, Oracle and OS too.

If SAP response time is acceptable, then try this :

Try to have a look at OS response time : ST06 : look at CPU, Memory, Swap, Disk and Lan response time.

Try to have a look at buffer quality : ST02, if many fields are red, investigate each fields dependant parameters.

Try to have a look at DB response time : ST04N, databuffer quality (SGA zone), how much physical reads / logical reads Ratio, wait times, number of user calls, Shared Pool cache hit ratio should be >96%, Sort usage, Redo logging.

I use this kind of procedure to manage my systems.

It depends how much you allocated for SGA (database buffers, shared pool buffer, redo log buffers), how much you allocated for SAP buffers esp. Program buffers and whether the server have any other external processes/programs running.

How many Dialog Work Processes you allocated…I think your problem most likely is you don't have enough of these Dialog processes. Also maybe users running inefficient reports/programs which are holding the Dialog processes, goto SM50 & check all DIA (Dialog) with status "waiting"…if ALL are "running" then you have wait time (problems !) for other users wanting to process transactions .

To troubleshoot performance, you need these tcode tools:-

ST04 – Database  ß in here, check especially for Expensive SQLs (Detail Analysis à SQL Request)

ST02 – SAP buffers

ST06 – OS stats

ST05 – SQL trace

SE30 – Abap runtime analysis

A few step which you can exercise to sort/identify performance issues.

* ST03, ST02, ST04 are the tcode for workload, tuning and DB Performance Monitoring codes.

* ST06 FOR Operation System Monitoring.

** SM51 OR SM50 is process overview which tells you the workprocess sequence. ( Ideally 10-15 process with  OLTP and batch process scheduled at peak and off peak times respectively) say 8-17 hrs and 17-8 hrs for Batch Process)

Operation Mode can be configured in RZ04 tcode.

** Check for top CPU in ST06 tcode.  CPU should not exceed more than 60% for long time for any process.

** Based of No. of instances ( Application Servers ) should have adequately sized.

** Most resources intensive process have to be scheduled in Batch Process ( in Background in Non Peak Hours )

** Look for unnecessary Jobs Active During Prime  Time
** Look for Parameters Set To Your Business Process.
   ( RZ10, RZ11 ) Check Snote:0124361

** Refer Early Watch Alert Periodically for Overall System Performance.. ( Tcode SDCC )

Search for SAP Transaction codes

You can access all the transaction codes by using the transaction code 'SDMO'.

This is the transaction code for the Dynamic Menu.

Based on your search string, you can get all related transaction codes for all the SAP application modules.

See from which network IP address and host name a user has logged on

To see the network IP address from which a user has logged on,  

perform the following steps:  

Call transaction OS01,  

click "Presentation Server" button, "Change View" button.  
 

If you are using Citrix, you will not be able to view the user individual IP address as it will be the same Citrix IP address.
 

To check the speed and quality of the user's network connection,  

select the desired presentation server and click "10 X Ping" button.  

Sending faxes from SAP

Some guidelines how to you can setup faxing from SAP :-

You will need an additional software to be installed.  

The best way to do this is to get a standard desktop PC with a modem attached. Buy a copy of Winfax 10 (its only about $100 to buy.)  

When you have Winfax setup and working locally, install SAPLPD (put it in the startup group so its loads on startup).  

WinFax will create a shared fax on the PC (For e.g. IFAX).

When this is done create a printer/Fax in transaction SPAD.  
Device type = SAPWIN Rel.4.x/SAPlpd  
Device class = Fax  
Host Spool access method = S;print using SAP protocol  
Dest. host = PC IP address  
Host printer = Shared fax name on PC(i.e IFAX)  

Make sure you have all the lasted SAPLPD + dll's  

After that is done create the locations in transaction SCOM, they are self explainitory from there.  

SPAU and SPDD

When you apply a package, a large number  of objects are changed.
If you have applied any OSS notes to objects in your system, the hot package may overwrite these objects.  
SPDD is used to identify dictionary objects  

and

SPAU (repository objects), will identify any objects where the hot package is overwriting changes you have made through OSS notes.  
You must check all objects identified in SPAU and decide whether you need to reapply the OSS note or reset the code to the original SAP Code.  
If, for instance, you are applying hot package 34, SPAU identifies an object where you have applied an OSS note.  You must check the OSSs note and see if SAP have fixed that note in a hot package.  
If the OSS note has been fixed in hot package 34, then you should reset the object to its original source code.  This means that there is no repair flag set against this object again and it is now SAP standard code.  
If, however, the object is not fixed until hot package 38, or there is no fix available you have to reapply the OSS note, otherwise users will encounter the problems they had before the note was applied.
You must transport all reapplied notes and Reset to SAP Standard objects after you apply your hot package to your QAS and PRD systems.

Tcodes used for Daily System Monitoring

After running daily system monitoring transaction, what should we check for:

In st22 look for the core dumps if any and report to the respective consultants and try to know why it happened.

In sm21 try to check for errors.

In sp01 try to see if any spool jobs have failed.

In st02 look if any swaps are happening, swaps are not good for performance.

In st04 look for Database alert logs and Performance.

In st03 look for ratio hits.

In sm59 look for connectivety tesing if there are other systems also connected to your SAP R/3 system

In db13 look if the jobs have run successfully.

In sm37 look for any cancelled scheduled job and take action appropriately.

In sm12 look for any pending locks from the previous days.

In sm13 look for any hanged updates, or updates pending for long or updates in PRIV mode.

Useful SAP System Administration Transactions

AL01          SAP Alert Monitor
AL02          Database alert monitor
AL03          Operating system alert monitor
AL04          Monitor call distribution
AL05          Monitor current workload
AL06          Performance: Upload/Download
AL07          EarlyWatch Report
AL08          Users Logged On
AL09          Data for database expertise
AL10          Download to Early Watch
AL11          Display SAP Directories
AL12          Display table buffer (Exp. session)
AL13          Display Shared Memory (Expert mode)
AL15          Customize SAPOSCOL destination
AL16          Local Alert Monitor for Operat.Syst.
AL17          Remote Alert Monitor for Operat. Syst.
AL18          Local File System Monitor
AL19          Remote File System Monitor
AL20          EarlyWatch Data Collector List
AL21          ABAP Program analysis
AL22          Dependent objects display
CREF          Cross-reference
BD64        
BSVW          Linkage Status Update-Workflow Event
CMOD          Enhancements
DB01          Analyze exclusive lock waits
DB02          Analyze tables and indexes
DB03          Parameter changes in database
DB11          Early Watch Profile Maintenance
DB12          Overview of Backup Logs
DB13          Database administration calendar
DB14          Show SAPDBA Action Logs
DB15          Data Archiving: Database Tables
DB16          DB System Check: Monitor
DB17          DB System Check: Configuration
DMIG          Start Transaction for Data Migration
DB2           Select Database Activities
DB20          DB Cost-Based Optimizer: Tab. Stats
DB21          DB Cost-Based Optimizer: Config.
DB24          Database Operations Monitor
DB26          DB Profile:Monitor and Configuration
DB2J          Manage JCL jobs for OS/390
DBCO          Database Connection Maintenance
FILE          Cross-Client File Names/Paths
NACE          WFMC: Initial Customizing Screen
OAA1          SAP ArchiveLink: Maint.user st.syst
OAA3          SAP ArchiveLink protocols
OAA4          SAP ArchiveLink applic.maintenance
OAAD          ArchiveLink Administration Documents
OAC2          SAP ArchiveLink: Globaldoc. types
OAC5          SAP ArchiveLink: Bar code entry
OACA          SAP ArchiveLink workflow parameters
OAD0          SAP ArchiveLink: Objectlinks
OAD2          SAP ArchiveLink document classes
OAD3          SAP ArchiveLink: Link tables
OAD4          SAP ArchiveLink: Bar code types
OAD5          SAP ArchiveLink: Customizing Wizard
OADR          SAP ArchiveLink: Print list search
OAM1          SAP ArchiveLink: Monitoring
OAOR          SAP ArchiveLink: Storeddocuments
OARE          SAP ArchiveLink:St.syst.return codes
OS01          LAN check with ping
OS03          O/S Parameter changes
OS04          Local System Configuration
OS05          Remote System Cconfiguration
OS06          Local Operating System Activity
OS07          Remote Operating SystemActivity
OSS1          Logon to Online ServiceSystem
OY18          Table history
OY08          Development Class Overview
PFCG          Activity Group
PFUD          Authorization Profile comparison
RLOG          Data migration logging
RZ01          Job Scheduling Monitor
RZ02          Network Graphics for SAP Instances
RZ03          Presentation Control SAP Instances
RZ04          Maintain SAP Instances
RZ06          Alerts Thresholds Maintenance
RZ08          SAP Alert Monitor
RZ10          Maintenance of profile parameters
RZ11          Profile parameter maintenance
RZ12          Maintain RFC Server Group Assignment
RZ20          CCMS Monitoring
RZ21          Customize CCMS Alert Monitor
SA38          ABAP/4 Reporting
SAD0          Address Management call
SADC          Address: Maint. communication types
SALE          Display ALE Customizing
SAINT         Plug-in Installation
SARI          Archive Information System
SAR3          Customizing Archiving
SAR4          Define Archiving Class
SAR5          Assign Archiving Class
SAR6          Archiving Time Generator
SARA          Archive management
SARL          Call of ArchiveLink Monitor
SARP          Reporting (Tree Structure): Execute
SART          Display Reporting Tree
SB01          Business Navigator - Component View
SB02          Business Navigator - Process flow vw
SBAS          Assignments to Process Model Elemts
SC38          Start Report Immediately
SCAT          Computer Aided Test Tool
SCC0          Client Copy
SCC1          Client Copy - Special Selections
SCC2          Client transport
SCC3          Client Copy Log
SCC4          Client administration
SCC5          Client Delete
SCC6          Client Import
SCC7          Client Import – Post Processing
SCC8          Client Export
SCC9          Remote Client Copy
SCCL          Local Client Copy
SCDO          Display Change DocumentObjects
SCMP          View / Table Comparison
SCOM          SAPcomm: Configuration
SCON          SAPconnect - Administration
SCPF          Generate enterprise IMG
SCPR1          Customizing Profiles : Maintenance Tool
SCPR2         Comparing Customizing profiles
SCUA          Central User Administration : Distribution Model Assigment
SCUG          Central User Administration Structure Display
SCUL        
SCUM          Central User Administration Field Selection
SCU0          Table Analyses And Comparison
SCU1          Table Comparison - Export to Tape
SCU2          Table Comparison Against Tape
SCU3          Table History
SD11          Data Modeler
SDBE          Explain an SQL Statement
SECR          Audit Information System
SE01          Transport and Correction System
SE02          Environment Analyzer
SE03          Transport Utilities
SE06          Set up Workbench Organizer
SE07          Transport System Status Display
SE09          Workbench Organizer (Initial Screen)
SE10          Customizing Organizer
SE11          Data Dictionary Maintenance
SE12          Data Dictionary Display
SE13          Maintain Technical Settings (Tables)
SE14          Convert Data Dictionary tables on Database Level
SE15          Repository Info System
SE16          Display Table Content
SE17          Generate Table Display
SE30          ABAP Objects Runtime Analysis
SE32          ABAP Text Element Maintenance
SE33          Context Builder
SE35          ABAP/4 Dialog Modules
SE36          Logical databases
SE37          ABAP Function Modules
SE38          ABAP Editor
SE39          Splitscreen Editor: Program Compare
SE40          MP: Standards Maint. and Translation
SE41          Menu Painter
SE43          Maintain Area Menu
SE51          Screen Painter
SE52          Parameterized screenpainter call
SE54          Generate table view
SE55          Internal table view maintenance call
SE56          internal call: display table view
SE57          internal delete table view call
SE61          R/3 Documentation
SE62          Industry Utilities
SE63          Translation: Initial Screen
SE71          SAPscript form
SE72          SAPscript Styles
SE73          SAPscript font maintenance (revised)
SE74          SAPscript format conversion
SE75          SAPscript Settings
SE76          SAPscript: Form Translation
SE77          SAPscript Translation Styles
SE78          SAPscript: Graphics administration
SE80          Object Navigator
SE81          Application Hierarchy
SE82          Application Hierarchy
SE84          R/3 Repository Information System
SE85          ABAP/4 Repository Information System
SE86          ABAP Repository Information System
SE88          Development Coordination Info System
SE89          Maintain Trees in Information System
SE91          Maintain Messages
SE92          New SysLog Msg Maintenance as of 46A
SE93          Maintain Transaction Codes
SE94          Customer enhancement simulation
SE95          Modification Browser
SEPS          SAP Electronic Parcel Service
SERP          Reporting: Change Tree Structure
SEU           Repository Browser
SF01          Client-Specific File Names
SFAW          Field Selection Maintenance
SIAC1          Web Object Administration
SHDB          Record Batch Input
SICK          Installation Check
SIN1          SAPBPT: Inbox
SINA          SAPBPT: Maintain Standard Config.
SLG0          Application Log: ObjectMaintenance
SLIN          ABAP: Extended Program Check
SM01          Lock Transactions
SM02          System Messages
SM04          User Overview
SM12          Display and Delete Locks
SM13          Display Update Records
SM14          Update Program Administration
SM21          System log
SM23          System Log Analysis
SM28          Installation Check
SM29          Model Transfer for Tables
SM30          Call Up View Maintenance
SM31          Table maintenance
SM31_OLD           Old Table Maintenance
SM32          Maintain Table Parameter ID TAB
SM33          Display Table ParameterID TAB
SM34          Viewcluster maintenancecall
SM35          Batch Input Monitoring
SM36          Batch request
SM37          Background job overview
SM38          Queue Maintenance Transaction
SM39          Job analysis
SM49          Execute Logical Commands
SM50          Work Process Overview
SM51          List of SAP Servers
SM54          TXCOM maintenance
SM55          THOST maintenance
SM56          Number Range Buffer
SM58          Asynchronous RFC Error Log
SM59          RFC Destinations (Display/Maintain)
SM60          Borrow/Return Objects
SM61        
SM62        
SM63          Display/Maintain Operating Mode Sets
SM64          Release of an event
SM65          Background Processing Analysis Tool
SM66          System-wide Work Process Overview
SM67          Job scheduling
SM68          Job administration
SM69          Display/Maintain Logical Commands
SMEN          Dynamic menu
SMGW          Gateway Monitor
SMLG          Maintain Logon Group
SMLI          Language import utility
SMLT          Language transport utility
SMOD          SAP Enhancement Management
SMT1          Trusted Systems (Display <-> Maint.)
SMT2          Trusting systems (Display <->Maint.)
SMW0          SAP Web Repository
SMX           Display Own Jobs
SNRO          Number Range Objects
SO02          SAPoffice: Outbox
SO03          SAPoffice: Private Folders
SO04          SAPoffice: Shared Folders
SO05          SAPoffice: Private Trash
SO06          SAPoffice: Substitutionon/off
SO07          SAPoffice: Resubmission
SO10          SAPscript: Standard Texts
SO12          SAPoffice: User Master
SO13          SAPoffice: Substitute
SO15          SAPoffice: DistributionLists
SO16          SAPoffice: Profile
SO17          SAPoffice: Delete Shared Trash
SO18          SAPoffice: Shared Trash
SO19          SAPoffice: Default Documents
SO21          Maintain PC Work Directory
SO22          SAPoffice: Delete PC Temp. Files
SO23          SAPoffice: DistributionLists
SO24          SAPoffice: Maintenance of default PC
SO28          Maintain SOGR
SO30          SAPoffice: Reorg.
SO31          Reorganization (daily)
SO36          Create Automatic Forwarding
SO38          SAPoffice: Synchr. of Folder Auths.
SO40          SAPoffice: Cust. LayoutSet MAIL
SO41          SAPoffice: Cust. LayoutSet TELEFAX
SO42          SAPoffice: Cust.Layout Set TELEFAX_K
SO43          SAPoffice: Cust.Layout Set TELEFAX_M
SO44          SAPoffice: Cust. LayoutSet TELEX
SO70          Hypertext: Display/Maint. Structure
SO71          Test plan management
SO72          Maintain Hypertext Module
SO73          Import graphic into SAPfind
SO80          SAPfind: Free Text Retrieval Dialog
SO81          SAPfind: Free Text Indexing (Test)
SO82          SAPfind: Free Text Retrieval Batch
SO95          Pregenerated Search Queries - Selec.
SO99          Put Information System
SOA0          ArchiveLink Workflow document types
SOBJ          Attribute Maintenance Objects
SOLE          OLE Applications
SOLI          Load OLE type info
SOPE          Exclude Document Classes
SOTD          SAPoffice: Maintain Object Types
SOY1          SAPoffice: Mass Maint. Users
SOY2          SAPoffice: Statistics data collect.
SOY3          SAPoffice: Statistics Evaluation
SOY4          SAPoffice: Access overview
SOY5          SAPoffice: Inbox overview
SOY6          SAPoffice: Document overview
SOY7          SAPoffice: Folder overview
SOY8          SAPoffice: Mass Archiving
SOY9          SAPoffice: Inbox Reorg.
SOYA          SAPoffice: Change folder owner
SP00          Spool and Relate Area
SP01          Spool Control
SP02          Display output Requests
SP03          Spool: Load Formats
SP11          TemSe Contents
SP12          TemSe Administration
SPAD          Spool Management
SPAM          SAP Patch Manager (SPAM)
SPAU          Display Modified DE Objects
SPCC          Spool Consistency check
SPDD          Display Modified DDIC objects
SPHA          Telephony administration
SPIC          Spool : Installation Check
SPRM          Current Customizing
SPRO          Customizing
SQ01          SAP Query: Maintain queries
SQ02          SAP Query: Maintain funct. areas
SQ03          SAP Query: Maintain user groups
SQ07          SAP Query: Language comparison
SQVI          QuickViewer
SSAA          System Administration Assistant
SSCA          Appointment Diary: Administration
SRZL          CCMS
SSM1          Session Manager generation call
SSM5          Create Activity Group
ST01          System Trace
ST02          Setups/Tune Buffers
ST03          Performance SAP Statistics Workload
ST04          Select activity of the databases
ST05          SQL Trace
ST06          Operating System Monitor
ST07          Application monitor
ST08          Network Monitor
ST09          Network Alert Monitor
ST10          Table Call Statistics
ST11          Display Developer Traces
ST12          Application Monitor
ST14          Application Analysis
ST22          ABAP Runtime Error Analysis
ST22          ABAP/4 Runtime Error Analysis
ST62          Create industry short texts
STAT          Local transaction statistics
STMS          Transport Management System
STUN          Performance Monitoring
STW1          Test Workbench: Test catalog
STW2          Test workbench: Test plan
STW3          Test workbench: Test package
STW4          Test Workbench: Edit test package
STW5          C maintenance table TTPLA
STZAC         Maintain time zone act.in client
STZAD         Disp.time zone activat.in client
SUMM          Global User Manager
SU01          Maintain User
SU01D         Display users
SU02          Maintain Authorization Profiles
SU03          Maintain Authorizations
SU05          Maintain Internet Users
SU10          Mass changes to User Master
SU11          Maintain Authorizations
SU12          Mass Changes to User Master Records
SU2           Maintain User Parameter
SU20          Maintain Authorization Fields
SU21          Maintain Authorization Objects
SU22          Auth. object usage in transactions
SU24          Disables Authorization Checks
SU25          Imports SAP Check Indicators defaults
SU26          Adjust Authorization checks
SU30          Total checks in the area of auth.
SU52          Maintain own user parameters
SU53          Display check values
SU54          List for Session Manager
SU56          Analyze User Buffer
SUPC          Profiles for activity groups
SUPF          Integrated User Maintenance
SUPO          Maintain Organization Levels
SUIM          Repository Info System
SWDC          Workflow Definition
SXDA          Data Transfer Workbench
TU02          Display Active Parameters
USMM          Customer measurement