Locking of all transactions

[former_member602109]

I have recently developed an email functionality for Shipment as one of the output. This has been working fine in Development server. After moving it to Quality Server, we found, all transactions were getting locked including VT02n,. We are not sure, if the new output processing is causing the error. But it is very strange that very independant transactions like MM02, ME22n, etc getting locked.

Recently the quality server got refreshed. Not sure, if anything to do with db conneciton here.

Will be great to hear suggestion on this, thanks in advance.

[former_member602109]

Its the record getting locked, if you come again.

1. After the locking issue begins, If I go to MM02, change a material, save and come to same material again, it shows lock

[VirtusaBasis]

Your issue is due to update is not working properly so SAP is not releasing locks in SM12, check for SM13 and SM14

If this is caused y refresh ask your SAP BASIS team if Profile parameters like message server

[former_member602109]

Thanks guys for the response.

A quick explanation about the Transaction locks :

1. After the locking issue begins, If I go to MM02, change a material, save and come to same material again, it shows lock
2. This occurs for various business objects like, VA02, ME22n,VT02n etc
3. Most important, this lock event is very random, and occurred 3 times during last 10 days, after the BFT refresh. But there is no particular pattern.
4. It got reported during testing our new email output., keeping VT02n locked! That might be just timing. But, its a serious concern.

[Matt_Fraser]

Saurabh,

Do you mean the transaction code is locked, i.e. no one can start the transaction code? This is what Raymond and S Sriram are referring to with SM01.

Or do you mean that records in the underlying tables are locked for editing by another user/process?

Can you provide the exact error message you are getting?

Cheers,
Matt

[Sriram2009]

Hi Saurabh.

In back end DB check the transaction code SM01 status in the table name TSTC - filed name - CINFO value - 'A0' locked & '80' Unlock transaction.

Regards

Sriram

[raymond_giuseppi]

Locking transaction is managed by transaction SM01, does someone forger to release those after a copy/refresh?

Regards,
Raymond