SUSR_BAPI_USER_UNLOCK not finding user

[Former Member]

Im doing something wrong and I cant figure out where my problem lies. I have two separate programs where I am using JCo 3.0 to create and unlock users based on user logging in incorrectly. The first works fine using SUSR_BAPI_USER_UNLOCK, the second cant find the user. Im thinking it might be something when I create the destination but I was hoping someone could point me in the right direction.

Here is my response from the call I make in the program that doesnt work.

<SUSR_BAPI_USER_UNLOCK><INPUT><LOCK_GLOBAL><BAPIFLAG></BAPIFLAG></LOCK_GLOBAL><LOCK_LOCAL><BAPIFLAG></BAPIFLAG></LOCK_LOCAL><LOCK_WRONG_LOGON><BAPIFLAG>X</BAPIFLAG></LOCK_WRONG_LOGON><USERNAME>locktest</USERNAME></INPUT>

<TABLES><RETURN><item><TYPE>E</TYPE><ID>01</ID><NUMBER>124</NUMBER><MESSAGE>User locktest does not exist</MESSAGE><LOG_NO></LOG_NO><LOG_MSG_NO>000000</LOG_MSG_NO><MESSAGE_V1>locktest</MESSAGE_V1><MESSAGE_V2></MESSAGE_V2><MESSAGE_V3></MESSAGE_V3><MESSAGE_V4></MESSAGE_V4><PARAMETER></PARAMETER><ROW>0</ROW><FIELD></FIELD><SYSTEM></SYSTEM></item></RETURN></TABLES></SUSR_BAPI_USER_UNLOCK>

Any help is appreciated.

Thanks.

[Former Member]

Nevermind, its the difference between upper case and lower case. Normal BAPIs seem to handle lowercase user ids, but SUSRs dont.

[mvoros]

Hi,

is there any reason why you don't use BAPI BAPI_USER_UNLOCK? I can't see any problem but still I would stick with BAPI.

Cheers

[Former Member]

The reason is that I want to be able to unlock this separately from the normal unlock of the global/local lock. If the BAPI gave a little more utility in allowing me to choose what to unlock, then I would use that.