User Locking while Production order Confirmation & After MRP Run

[former_member4887]

Dear SAP Experts,

User Locking while Production order Confirmation

We are facing locking issues at the time of our production order Confirmations, While confirming any operation we receive error of "reservation is already being processed" On further trouble shooting we analysed that the reservation is locked by our admin users who don't even perform any transaction related to production / materials .

i have checked for background jobs but there are no background jobs with that users.

This issues resolved once our admin user clear all lock entries. What could be the possible reason of this locking & solution.

User locking After MRP execution

We are also facing locking issues after MRP executions. let say i run MRP on plant/ any material. the system create lock entries by my users & everyone else working in system get locking errors from my users until the admin release all those locked objects.

Every single time we run MRP we need to ask our admin users to delete lock entries after MRP execution so that it don't stop other operations.

Both these locking issuers are now being very critical & even affecting our production line. We also have some production losses because of Locking in order confirmations.

[Caetano]

Hello

Please follow the instructions of the following KBA, and avoid the flag "Include faulty goods movements" when running program CORUPROC every 15 minutes:

2174262 - Performance problems on report CORUPROC

You may run the program with the flag checked once a day, but every 15 minutes is too much.

Regards,

Caetano

[JL23]

Did you already investigate whether you have exits or Badis in use for these 2 transactions?

Transaction ANST does a good job in this regard and can also find OSS notes

And if no manipulations and OSS notes found that address your issue then open a call at SAP Support.

[former_member4887]

Hello Jurgen 🙂

I was in coordination with SAP as well, they recommended me a SAP note # 208477. After reading that Note i checked my Confirmation Configuration settings & found that Auto Gr & back flush is scheduled for background which is running every 15 minutes & it's scheduled by basis user hence i'm getting errors with his user ID.

Please recommend that what should be the settings for " process control for confirmations Tcode = OPKC " & how to resolve this error cox i'm pretty sure now that locking errors are because of that background job.