Skip to Content

BAPI_USER_CHANGE rolling back User Lock issue

For user Termination, I have used BAPI_USER_CHANGE for changing End Date and BAPI_USER_LOCK for Changing Lock status in the mentioned order.

But when processed in bulk in CUA system, in the Parent system execution works fine. But in child system the user is end dated but still unlocked.

When checked in SU01 information logs, it shows the Lock is performed first then the End date is changed with a different of 1 second (which should not be the case) and immediately after End date is changed the user is Unlocked without even a second's delay.

What i suspect is, BAPI_USER_LOCK executed and Locked user, then BAPI_USER_CHANGE which had a buffer of USR02, simply updated End Date change but Lock status as before which is leading to immediate user Unlock.

But unable to prove the same since debugging will eliminate the possible system communication delay.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

0 Answers