How To Fix 00790 - Password was not used for a long period and therefore deactivated

SAP Error Message - Details

• Message type: E = Error

• Message class: 00 -

• Message number: 790

• Message text: Password was not used for a long period and therefore deactivated

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message 00790 - Password was not used for a long period and therefore deactivated ?

  The SAP error message "00790 Password was not used for a long period and therefore deactivated" indicates that the user account has been locked due to inactivity. This is a security measure to prevent unauthorized access to accounts that have not been used for a certain period of time.
  Cause:
  
  Inactivity: The user has not logged into the SAP system for a specified duration, leading to the automatic deactivation of the password.
  Password Policy: The system may have a password policy configured that deactivates passwords after a certain period of inactivity to enhance security.
  
  Solution:
  To resolve this issue, the user or an administrator can take the following steps:
  
  
  Reset Password:
  
  An administrator can reset the password for the user account using transaction code SU01 (User Maintenance).
  After resetting the password, the user should be able to log in again.
  
  
  
  Reactivate User:
  
  If the user account is locked, the administrator can unlock it in the same SU01 transaction.
  Check the "Lock" status and unlock the account if necessary.
  
  
  
  Review Password Policy:
  
  Review the password policy settings in the system to understand the inactivity duration that leads to deactivation.
  This can be done in transaction RZ10 or by checking the profile parameters related to user management.
  
  
  
  User Education:
  
  Inform users about the importance of regularly logging into the system to avoid account deactivation.
  Encourage users to change their passwords periodically as per the organization's security policy.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SU01: User Maintenance
  SU10: Mass User Maintenance (for bulk changes)
  RZ10: Profile Parameter Maintenance
  
  
  
  SAP Notes: Check for any relevant SAP Notes that may provide additional information or updates regarding password management and user account policies.
  
  
  Security Best Practices: Regularly review and update security policies to ensure they align with organizational needs and compliance requirements.
  
  
  By following these steps, the user should be able to regain access to their SAP account and prevent future occurrences of this error.