SUSR_USER_CHANGE_PASSWORD_RFC CHANGE_NOT_ALLOWED

[Former Member]

Hi,

I'm just trying out this FM in SE37. I input the username, current password (which i know is correct because I just logged onto the system with it), and new password that i want.......I don't populate anything else myself....

I keep getting the CHANGE_NOT_ALLOWED exception...

Does anyone know what's going on here?

Regards

Mr.T

[Former Member]

Hi,

I'm just trying out this FM in SE37. I input the username, current password (which i know is correct because I just logged onto the system with it), and new password that i want.......I don't populate anything else myself....

I keep getting the CHANGE_NOT_ALLOWED exception...

Does anyone know what's going on here?

Regards

Mr.T

[Former Member]

Hi Tahir,

You might do not have authorization to create change username password, Ask you Basis people to give you the authorization for this activity and then re execute your program.

Thanks and regards

Anup

[Former Member]

Hi,

Its not working even when I use SAPADM user.

[Former Member]

hai tahir,

why r u changing the password or ur own user id

it is rfc call, so an external system call and change it

u ahev logged in and trying to change so it might be problem

and it is not advisable to change the password of user id

it is basis activity and can be doen thorugh transaction su01

regards

afzal

[Former Member]

Use transaction SU3 instead.

The function module you are using only provides generic information about the password having been changed or not, and does not provide detailed reason codes. For this you would need to trace or debug it.

Probably, the password you are providing does not comply with the login/password* parameter rules and exceptions in table USR40. Possibly, the reason is that it is not sufficiently different to your previous password and / or that you already changed it once today, so you will need to wait until tomorrow.

Cheers,

Julius

[Former Member]

Thanks for all the responses....

The reason in this case was that the password field is case sensitive! And when you use SE37 Test Tool, it converts small case to big case and so it was not accepting my current password.

[Former Member]

hai tariq good solution,

u can check case sensitive in se37 so that u can pass lower case,

if it si solved then close the thread

afzal

[Former Member]

Yes, then your system is configured to be downwardly incompatible and only the new password mechanism has been used or is being evaluated.

Older components will not work, or not as they are expected to.

Cheers,

Julius