SAP Library - Find your answers

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.

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.

SAP Transaction code to pre-compile all system program

If I have to run SGEN and have to recycle the server as well for clearing out memory, does it make sense to run SGEN first and recycle afterwards, because SGEN will sort of litter the memory or is it inconsequential what runs first.

SGEN is ued to "compile" ABAP programs. Results are put in database.

So, if you restart SAP, compiled results will still be in the database, so, no need to run SGEN again.

Make use of the transaction 'SGEN' to re-generate all the SAP programs after you change version of your SAP kernel, upgrade SAP system or apply support packages.

Do take care of the table spaces and use SAPDBA to observe them.

Do it during a weekend which is the best or a period of time with very very low users activity.

It will takes about 5 to 8 hours depending on the type of hardware configuration you are using.

If I have to run SGEN and have to recycle the server as well for clearing out memory, does it make sense to run SGEN first and recycle afterwards, because SGEN will sort of litter the memory or is it inconsequential what runs first.

SGEN is ued to "compile" ABAP programs. Results are put in database.

So, if you restart SAP, compiled results will still be in the database, so, no need to run SGEN again.

Make use of the transaction 'SGEN' to re-generate all the SAP programs after you change version of your SAP kernel, upgrade SAP system or apply support packages.

Do take care of the table spaces and use SAPDBA to observe them.

Do it during a weekend which is the best or a period of time with very very low users activity.

It will takes about 5 to 8 hours depending on the type of hardware configuration you are using.