Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

SAP locks not getting cleared.

Former Member
0 Likes
1,211

Hi,

Recently we had an issue where none of the FI, MM, PM users were able to post a document in SAP. While posting, the document numbers were not actually getting inserted into the database tables and we were getting error message like the document does not exist in database or has been archived when we quickly try to Display it through display transactions.

Basis have found that the issue was because of the SAP locks three in number found in SM12 which were not cleared since some time. Later basis have removed them and fixed the isssue.

But we have been facing this same issue several times now after that.

These exclusive locks always occur on tables QMEL, RKPF and AUFK. I have checked and found that the these three locks are created when we try to Change/Create a PM order from IW31, 32 transactions.

We have almost checked all scenarios from the BASIS side. But not sure why these are getting created frequently.

Did any one faced this kind of issue before? Any help would be greately appreciated.

Thanks,

Venkatesh

4 REPLIES 4
Read only

Former Member
0 Likes
1,005

Hi,

did you check your NRIV (or NRIV_LOKAL if used) for number range issues / overflows? This may occur on V1 or V2 update modules. Also an update task must be reachable working with several servers.

Regards,

Klaus

Read only

0 Likes
1,005

Hi Klaus Babl,

Thanks for your reply.

We have seen the table NRIV and seems that there is no problem there. But could you please shed some light on the below statement that you made:

Also an update task must be reachable working with several servers

Thanks,

Venkatesh.

Read only

0 Likes
1,005

Hi,

in SM51 check process overview for all servers. You need running processes of the following types:

DIA for dialogue requests

BGD for batch processing

UPD for V1 update modules

ENQ for locking

SPO for spool requests

UP2 for V2 update modules

The issue may result from your server configuration (e.g. switching day/night processing)

Regards,

Klaus

Read only

Former Member
0 Likes
1,005

hi,

If something related to SAP standard the would suggest you to check wit SAP.

Rhea.