How To Fix TE814 - Unable to save portfolio hierarchy due to database lock

SAP Error Message - Details

• Message type: E = Error

• Message class: TE - Market Risk Management

• Message number: 814

• Message text: Unable to save portfolio hierarchy due to database lock

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 TE814 - Unable to save portfolio hierarchy due to database lock ?

  The SAP error message TE814, which states "Unable to save portfolio hierarchy due to database lock," typically occurs when there is a conflict in accessing the database. This can happen when multiple users or processes are trying to access or modify the same data simultaneously, leading to a database lock.
  Causes:
  
  Concurrent Access: Multiple users or processes are trying to modify the same portfolio hierarchy at the same time.
  Long-running Transactions: A transaction that takes a long time to complete may hold a lock on the database, preventing other transactions from accessing the same data.
  Uncommitted Transactions: If a previous transaction has not been committed or rolled back, it may hold a lock on the data.
  System Performance Issues: High system load or performance issues can lead to delays in releasing locks.
  
  Solutions:
  
  Wait and Retry: Often, simply waiting for a few moments and then trying to save again can resolve the issue, especially if it was caused by a temporary lock.
  Check for Active Locks: Use transaction codes like SM12 to check for active locks in the system. You can identify the user or process holding the lock and take appropriate action.
  Release Locks: If you identify a lock that is no longer needed, you can manually release it using SM12. However, be cautious when doing this, as it may affect other users.
  Optimize Transactions: Review and optimize long-running transactions to ensure they complete quickly and release locks in a timely manner.
  System Monitoring: Monitor system performance and database locks regularly to identify patterns or recurring issues that may need addressing.
  Consult with Basis Team: If the issue persists, it may be necessary to consult with your SAP Basis team to investigate further, as they can provide insights into database performance and locking mechanisms.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM12 (to view and manage locks), SM21 (to check system logs), and ST22 (to check for dumps).
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions for common problems.
  User Training: Ensure that users are trained on best practices for accessing and modifying shared data to minimize the risk of database locks.
  
  By following these steps, you should be able to address the TE814 error and prevent it from occurring in the future.