HI , As an SAP BASIS member , Why do we need to monitor lock entries(SM12) an

HI ,
As an SAP BASIS member , Why do we need to monitor lock
entries(SM12) and Update Errors(SM13) , wht is the trouble
shooting for those ?

Question Posted / rajesh

3 Answers
16820 Views
IBM, Infosys, I also Faced
E-Mail Answers

Answers were Sorted based on User's Feedback

HI , As an SAP BASIS member , Why do we need to monitor lock entries(SM12) and Update Errors(SM13..

Answer / srikanth

We need to monitor atleast once in a day whether we have
many exclusive locks. There are different types of locks
which can be put on tables. If it is an exclusive lock then
that particular user who put the lock on the table only
willl be able to access it. If at the sametime someother
user or someother background job which tries to access the
sam table to hold out and those transactions will be struck
until the table is released. Well if thee are many locks on
many tables the transactions in SAP will be awaiting and
they are not processed further and it may effect the
business seriously. If there are many locks see who locked
it. Then go for Tcode "al08" and see whether the user is
active. If he is not then try to comminicate with him and
delete the lock. If he is not and lock is continued from a
long time and affecting the business then delete the lock
after the confirmation from the user.

Is This Answer Correct ?

30 Yes

2 No

HI , As an SAP BASIS member , Why do we need to monitor lock entries(SM12) and Update Errors(SM13..

Answer / syed mahboob feroz ahmed

Hi,
We need to monitor lock entries and update errors as when
anyone is making changes on particular ST Code only one
single instance is possible at a time and when someone from
another system logged in and trying to make use of the same
T code for same user for making changes then that
particular User cannot make use of that T code and will
receive message that it is locked this is the work of SM12
and when coming to SM13 here one can see updates going on
and while making changes through SM12 and the same T code
being used with another User so we can cancel that
particular session which is locked with,
"Cancel without Core" which will not input any logs related
to changes being update in Update workprocess (SM13).

Is This Answer Correct ?

4 Yes

7 No

HI , As an SAP BASIS member , Why do we need to monitor lock entries(SM12) and Update Errors(SM13..

Answer / syed mahboob feroz ahmed

Hi,
Usually lock entries occur because of enqueue process and
to monitor these lock entries one should make use of SM12
and to update these lock entry errors one should make use
of SM13 T code and this code presents the object name where
the lock has been entered and one can cancel the lock entry
without core if it is cancelled with core then one can make
out who has cancelled the lock entries on that particular
object assigned entries with whole log information .So to
overcome this lock entry one should cancel it without Core
to overcome logs.

Is This Answer Correct ?

0 Yes

4 No

Post New Answer