How To Fix J5720 - Risk hierarchies are locked by user &

SAP Error Message - Details

• Message type: E = Error

• Message class: J5 - External Data Transfer

• Message number: 720

• Message text: Risk hierarchies are locked by user &

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 J5720 - Risk hierarchies are locked by user & ?

  The SAP error message J5720, which states "Risk hierarchies are locked by user &," typically occurs in the context of SAP GRC (Governance, Risk, and Compliance) when a user attempts to modify or access risk hierarchies that are currently locked by another user. This locking mechanism is in place to prevent concurrent modifications that could lead to data inconsistencies.
  Cause:
  
  User Locking: The risk hierarchy is locked by another user who is currently making changes or has an active session that has not been properly closed.
  Session Timeout: Sometimes, a user may have left a session open, causing the lock to persist even after they have stopped working on it.
  System Error: Occasionally, system errors or crashes can lead to locks not being released properly.
  
  Solution:
  
  Identify the Locking User: Check the user who has locked the risk hierarchy. This can often be done through transaction codes like SM12 (for lock entries) or SM21 (for system logs).
  Contact the User: If possible, contact the user who has the lock and ask them to release it by either completing their task or logging out of the system.
  Release the Lock: If the user is unavailable or the session is stale, an administrator can manually release the lock using transaction SM12. However, this should be done with caution to avoid data loss.
  Check for System Issues: If locks are persisting without a clear user, investigate for any system issues or errors that may be causing the locks to not be released.
  Review Configuration: Ensure that the configuration for risk hierarchies is set up correctly and that there are no issues with the underlying data model.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM12 (to view and delete lock entries), SM21 (to check system logs), and SU01 (to manage user accounts).
  User Roles and Authorizations: Ensure that users have the appropriate roles and authorizations to access and modify risk hierarchies.
  Documentation: Refer to SAP documentation or support notes related to GRC and risk management for more detailed troubleshooting steps and best practices.
  SAP Support: If the issue persists and cannot be resolved internally, consider reaching out to SAP support for assistance.
  
  By following these steps, you should be able to resolve the J5720 error and regain access to the risk hierarchies in SAP.