cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Locking Issue

former_member182034
Active Contributor
0 Likes
2,831

Dear Support,
some User are facing locking issue against Material, Document, Order, Reservation.

example:

SD: When SD user is trying to access the documents then he is facing that document is blocked by same user.
MM: Material does not exist and blocked by same MM user.
PP: Order Locked by same user, Reservation does not exist:
PM: Order is saved successfully but same  Order does not exist.

When I delete the old entries from SM12 than issue resolved.
but I am getting this issue again and again. How can i solve this issue please help me.


Regards,

View Entire Topic
Former Member
0 Likes

Hi Abdul,

As told my Michael, deleting locks from SM12 should be the last resort. Because if there are running processes it might cause inconsistency. Safe option is to log off the user from SM04 from the application server.

To fix this issue you have to get in touch with application team. If standard SAP program, check for any SAP note. If custom program, check with your ABAP team.

Thanks,

Samik

former_member182034
Active Contributor
0 Likes

hi Michael and Samik,

today, some users complained me that they are getting locking issue. I checked the locked entries in SM12 which were running from last 5 hours, so i asked by users about the locked entries then they said me that right now we are not working. I checked sessions & work process in SM51/SM50 and there were not showing any process and session against concern users.

while there are showing some failed update in SM13 please check the screenshots.

what should I have to do with this update?

Regards,

Former Member
0 Likes

Hello Abdul,

Are the Update Error's timestamp and users same with SM12 lock entry ?

Can you correlate each lock entry with failed updates ?

If yes you need to engage Functional and ABAP team to investigate these update failures. As a Basis admin you are not supposed to restart the Failed updates on your own, however if your functional team gives Go Ahead you can do that. But in this case, I see 'No Retry' which means you will probably not able to reprocess. Double click on the V1 (No Retry) row and see if the pop up gives any error message.

You can also find the source code and check if its standard or custom.

Thanks,

Samik