How To Fix AA990 - Ch.of dep.-depend data from ch.of dep. &1 in asset class &2 was locked

AA990 - Overview

• Message type: E = Error

• Message class: AA - Messages for Asset Accounting

• Message number: 990

• Message text: Ch.of dep.-depend data from ch.of dep. &1 in asset class &2 was locked

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.

AA990 - Details

• The SAP error message AA990 indicates that there is a conflict or issue related to the change of depreciation data for an asset in a specific asset class. This error typically arises when you attempt to change depreciation data for an asset that is currently locked due to various reasons, such as ongoing transactions, user locks, or system processes.
  
  Cause:
  
  User Lock: Another user might be currently editing or processing the asset, which locks the depreciation data.
  System Lock: The system might have a lock in place due to batch jobs or background processes that are currently running.
  Transaction in Progress: There may be ongoing transactions related to the asset that prevent changes from being made.
  
  Configuration Issues: There could be configuration settings in the asset class that are causing the lock.
  
  
  Solution:
  
  Check User Locks: Verify if another user is currently editing the asset. You can use transaction code SM12 to check for user locks and