IdM User automatically locking ABAP account after setting new password

Hi Experts

We are currently facing a problem, where it seems that the idmuser used when provisioning to ABAP is setting a value 128 (locked due to wrong logon) almost simultaneously as setting the new password on the user. I have found the information under SU01 and changes on the user account.

I cannot find anywhere in IdM that the value 128 is set to the "islocked" attribute. When provisioning new passwords, we do'nt even try to set the "islocked" attribute. We do unlocking/locking in separate tasks - and NEVER us the value 128.

Does anyone have a good explanation as to why/how this can happen?

Kind regards

Heidi Kronvold