How To Fix LQ391 - Security creation date set to date of last refresh

SAP Error Message - Details

• Message type: E = Error

• Message class: LQ - Proposal Pool Management

• Message number: 391

• Message text: Security creation date set to date of last refresh

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 LQ391 - Security creation date set to date of last refresh ?

  The SAP error message LQ391 indicates that the security creation date for a particular object (like a user or role) is set to the date of the last refresh. This typically occurs in the context of SAP's security and authorization management, particularly when dealing with roles and profiles in the system.
  Cause:
  The error usually arises due to the following reasons:
  
  Role Refresh Issues: When roles are refreshed, the system may not properly update the security creation date, leading to inconsistencies.
  Authorization Data: There may be issues with the authorization data that is being processed, which can cause the system to default to the last refresh date.
  System Configuration: Incorrect configuration settings in the authorization management or role management can lead to this error.
  
  Solution:
  To resolve the LQ391 error, you can take the following steps:
  
  
  Check Role and Profile Configuration:
  
  Review the configuration of the roles and profiles involved. Ensure that they are set up correctly and that there are no inconsistencies.
  
  
  
  Re-Refresh the Role:
  
  Try to refresh the role again. This can sometimes resolve temporary issues with the security creation date.
  
  
  
  Check Authorization Data:
  
  Verify the authorization data for the affected roles or users. Ensure that all necessary authorizations are correctly assigned.
  
  
  
  Review System Logs:
  
  Check the system logs for any additional error messages or warnings that might provide more context about the issue.
  
  
  
  Consult SAP Notes:
  
  Look for relevant SAP Notes that might address this specific error. SAP frequently updates its knowledge base with solutions for known issues.
  
  
  
  Contact SAP Support:
  
  If the issue persists after trying the above steps, consider reaching out to SAP Support for further assistance. They can provide more detailed guidance based on your specific system configuration.
  
  
  
  Related Information:
  
  SAP Security and Authorizations: Understanding how SAP handles security and authorizations can help in troubleshooting similar issues.
  Role Management: Familiarize yourself with the role management process in SAP, including how roles are created, modified, and refreshed.
  SAP Documentation: Refer to the official SAP documentation for detailed information on error messages and their resolutions.
  
  By following these steps, you should be able to address the LQ391 error and ensure that the security creation dates are correctly set in your SAP system.