Password was not used for a long period and therefore deactivated

If you exceed the parameter value for your logon period for the SAP system which you activated the parameter “login/password_max_idle_productive” , then you will get the logon message like below ;

“Password was not used for a long period and therefore deactivated”

and therefore you cannot logon to the relevant system.

English & Turkish message example ;

parolaetkinlik

You can eliminate this situation with following syntax ;

SQL> update sapsr3.usr02 set PWDCHGDATE=’20140115′,PWDLGNDATE=’20140115′,TRDAT=’20140115′, uflag=’0′ where BNAME in ( ‘USER1,’USER2′,’USER3′) and mandt in (’000′,’010′);

SQL> commit;

Important points are ;

- You should change the dates to couple of days ago from the current day

- You should give the USERNAME or USERNAMES to releated area ( ‘USER1,’USER2′,’USER3′) which you want to use

- You should give the CLIENT or CLIENTS to releated area (’000′,’010′) which you want to use

- and don’t forget the COMMIT command :)

 

 

3 Responses to "Password was not used for a long period and therefore deactivated"

  1. ray says:

    Great Info! Every once in a while I find something interesting

  2. Nicolas says:

    How can I do this sytanx in MaxDB?:
    “SQL> update sapsr3.usr02 set PWDCHGDATE=’20140115′,PWDLGNDATE=’20140115′,TRDAT=’20140115′, uflag=’0′ where BNAME in ( ‘USER1’,’USER2′,’USER3′) and mandt in (’000′,’010′);

    SQL> commit;”

    Regards

  3. Ricardo says:

    The “Password was not used for a long period and therefore deactivated” query saved my life literally.
    Thanks so much!

Leave a Reply


five − = 1

Blogroll