topic Issue while locing an user using BAPI_USER_LOCK in Application Development and Automation Discussions

Issue while locing an user using BAPI_USER_LOCK

lrayapat73 — Tue, 16 Mar 2021 08:18:18 GMT

Hi All,

I am using BAPI_USER_LOCK to lock users, while executing this BAPI for a particular user, if the user account is kept open in SAP GUI client, BAPI is unable to lock the user. Giving following message,

Maintenance of user user1 locked by user adminuser1

I am using SAP .Net Connector(NCo 3.0) SDK to make the calls. Is there any flag we need to set inorder to avoid above behavour.

Thanks in advance.

Re: Issue while locing an user using BAPI_USER_LOCK

MateuszAdamus — Tue, 16 Mar 2021 08:24:25 GMT

Hello lrayapat73

It's a standard and correct behavior. Other user is editing the data and has locked the record. That's what this functionality is for.

Kind regards,
Mateusz

Re: Issue while locing an user using BAPI_USER_LOCK

jmodaal — Tue, 16 Mar 2021 08:28:04 GMT

Hello,

that is the normal behaviour for concurrent accesses on the same data. The "adminuser1" currently maintains this user, therefore your attempt fails due to the lock entry created by the transaction of "adminuser1". The lock entry should be visible in SM12. There is no flag which allows you to bypass this.

Re: Issue while locing an user using BAPI_USER_LOCK

matt — Tue, 16 Mar 2021 08:59:50 GMT

I have a program that needs to modify user accounts via BAPI. Where someone is editing an account that my program needs to change, it triggers a workflow to the person locking and their manager that they need to get out as my program is more important than what they're doing.

It also sends a popup message to the admin person's gui session.