How To Fix ACC_AA070 - Only transaction type "*" is allowed for acct assignment type "Depr.Run"

SAP Error Message - Details

• Message type: E = Error

• Message class: ACC_AA - Message Class for Function Group ACC_AA

• Message number: 070

• Message text: Only transaction type "*" is allowed for acct assignment type "Depr.Run"

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 ACC_AA070 - Only transaction type "*" is allowed for acct assignment type "Depr.Run" ?

  The SAP error message ACC_AA070 indicates that there is a restriction on the transaction types that can be used with a specific account assignment type, in this case, "Depr.Run" (Depreciation Run). This error typically occurs when you are trying to execute a transaction that is not permitted for the specified account assignment type.
  Cause:
  The error is caused by attempting to use a transaction type that is not allowed for the depreciation run. In SAP, each transaction type is associated with specific account assignment types, and the system enforces these rules to ensure that financial transactions are recorded correctly.
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Transaction Type: Ensure that you are using the correct transaction type for the depreciation run. The transaction type should be "*", which indicates that it is a general transaction type that can be used for various purposes.
  
  
  Review Configuration: If you are using a custom transaction type, check the configuration settings in the SAP system. You may need to adjust the settings in the configuration to allow the desired transaction type for the depreciation run.
  
  
  Consult Documentation: Refer to the SAP documentation or help files related to asset accounting and depreciation runs. This can provide insights into the allowed transaction types and any specific configurations that may be required.
  
  
  Check User Authorizations: Ensure that the user executing the transaction has the necessary authorizations to perform the depreciation run. Lack of proper authorizations can sometimes lead to unexpected errors.
  
  
  Contact SAP Support: If you are unable to resolve the issue through the above steps, consider reaching out to SAP support or your internal SAP team for further assistance. They may have additional insights or solutions based on your specific system configuration.
  
  
  Related Information:
  
  
  Transaction Codes: Familiarize yourself with relevant transaction codes related to asset accounting, such as:
  
  AFAB: Depreciation Run
  AS01: Create Asset
  AS02: Change Asset
  AS03: Display Asset
  
  
  
  Configuration Path: The configuration for transaction types can typically be found in the following path:
  
  SPRO > Financial Accounting > Asset Accounting > Integration > Define Transaction Types.
  
  
  
  SAP Notes: Check for any SAP Notes related to this error message, as they may provide specific fixes or updates that address the issue.
  
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.