all t codes -with descriptions

8/19/2019 All t Codes -With Descriptions

1/3

Lock Entries Management: SM12 As nature of SAP system behavior, whenever a user performs an update on any table,for that period of time a lock on that particular field of that table will be created toprevent any other user can update that table to obtain data consistency.

During an update process of the user session, if the session get terminated due to anyunforeseen error the lock entry will appear and remains on that field.

The purpose of the lock mechanism is to prevent two transactions from changing the same data on the

database simultaneously . Lock entries are usually set and deleted automatically when user programs access a data

ob ect ! release it again. The lock mechanism is closely related to the Update Mechanism .

1. "ou can use SM12 to check and delete lock entries.

2. #n SM12 , check any lock entry older $ 2 days . #f any outdated entry found, check the corresponding user is

user online %offline in AL08 or SM04 &you can get the transaction code that been use by the user'. (et the user contact

from SU01 and inform about the lock else if the user is offline , release the table from lock by deleting the lock

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

System logs (SM 21)

Transaction code SM21 is used to check and analy)e system logs for any critical log entries.

System Log:

In an SAP system, for every important action system log will get updated. So, in case of any

issues with the system, basis administrators need to check the system log first to identifyany errors or warnings.

Many times, we can resolve system issues by checking the system log and searching forrelevant notes in the market place using keywords found in the system & applying them.

In case of issues like update failure, lock table overflow, spool overflow, operating systemissues, network issues, table space full issues and other database issues system log will getupdated with the error message and the relevant time stamp. y using this timestamp anderror message, basis administrator can identify the cause for the issue and can fi! the issue.

ased on the issue and the time stamp in system log, in many cases, you can find out

relevant A AP runtime dumps in S"## $which provides much more detail about the issue%and the issue can be tackled accordingly.

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

SM 51 /50 TO CHECK SERVER LIST


2/3

Transaction code SM 1 is to display list of acti!e application servers that have registered in the SAP message ser!er .

*urther, you can manage ! display the status , users , wor" process in all application servers belonging to the SAP System.

+#rocesses Display ! control work process. - S /0 1

S 2/0 222 #t shows the status of type of work process and their satatus.

Sm/0

tcode is used to see the workprocess overview in application

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

UP !TE RE"UEST # SM 1$

Update management supports different status for update requests . These status aredisplayed in Update Management (transaction code SM13 in the column Status . Thestatus indicates the phase of the update process that the re!uest has reached" or in #hichthe re!uest has $ecome %stuck&. The $ackground of the status field can $e green (not yet

http://itsiti.com/sm50-process-overviewhttp://itsiti.com/sm50-process-overview


3/3

all t codes -with descriptions

Documents