How To Fix ACC_AA035 - A restriction on company codes takes place in an update run

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 035

• Message text: A restriction on company codes takes place in an update 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_AA035 - A restriction on company codes takes place in an update run ?

  The SAP error message ACC_AA035 indicates that there is a restriction on company codes during an update run, typically related to asset accounting. This error can occur when you are trying to execute a transaction that involves asset postings or updates, and there are certain restrictions or configurations that prevent the operation from being completed.
  Cause:
  
  
  Company Code Restrictions: The error often arises when there are restrictions set on the company codes in the asset accounting configuration. This could be due to:
  
  The company code being locked for postings.
  The asset accounting settings not allowing certain types of transactions for the specified company code.
  The company code being in a closed fiscal year.
  
  
  
  Authorization Issues: The user executing the transaction may not have the necessary authorizations to perform actions on the specified company code.
  
  
  Configuration Issues: There may be inconsistencies or misconfigurations in the asset accounting settings for the company code.
  
  
  Solution:
  
  
  Check Company Code Status: Verify if the company code is locked for postings. You can do this by checking the configuration in the Asset Accounting (AA) module:
  
  Go to the transaction code OAOA (for company code settings) and check if the company code is set to allow postings.
  
  
  
  Review Fiscal Year Settings: Ensure that the fiscal year is open for the company code. You can check this in the transaction code OB52 (for fiscal year variant settings).
  
  
  Authorization Check: Ensure that the user has the necessary authorizations to perform the transaction. This can be checked in the user roles and profiles assigned to the user.
  
  
  Configuration Review: Review the configuration settings in the Asset Accounting module to ensure that there are no restrictions set that would prevent the transaction from being executed.
  
  
  Consult Documentation: If the issue persists, consult the SAP documentation or support for specific details related to the error message ACC_AA035.
  
  
  Related Information:
  
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  OAOA: Company Code Settings for Asset Accounting
  OB52: Maintain Fiscal Year Variants
  AS01/AS02: Create/Change Asset
  S_U0_02000001: Authorization object for Asset Accounting
  
  
  
  SAP Notes: Check for any SAP Notes related to this error message in the SAP Support Portal, as there may be specific patches or updates that address known issues.
  
  
  Testing: After making any changes, perform a test run to ensure that the error does not occur again.
  
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.