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

TE814 - Overview

• 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