How To Fix ACC_AA351 - Project &1/Company Code &2: No Support for Account Approach

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 351

• Message text: Project &1/Company Code &2: No Support for Account Approach

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_AA351 - Project &1/Company Code &2: No Support for Account Approach ?

  The SAP error message ACC_AA351 indicates that there is no support for the account approach in the context of asset accounting for a specific project and company code. This typically arises when the system is configured to use a different method for asset accounting, such as the cost center approach, and the transaction you are trying to execute is not compatible with the current configuration.
  Cause:
  
  Configuration Settings: The company code or project may be configured to use a different asset accounting approach (e.g., cost center approach) rather than the account approach.
  Project Settings: The project may not be set up to support the account approach for asset accounting.
  Asset Class Settings: The asset class associated with the asset may not be configured to allow the account approach.
  
  Solution:
  
  
  Check Configuration:
  
  Go to the configuration settings for Asset Accounting (Transaction code: SPRO).
  Navigate to Financial Accounting (New) > Asset Accounting > Integration > Define Account Approach.
  Ensure that the company code and project settings are correctly configured to support the account approach.
  
  
  
  Review Project Settings:
  
  Check the project settings in the Project System (PS) module to ensure that the project is set up to allow the account approach.
  You can do this by using transaction code CJ02 (Change Project) and reviewing the settings.
  
  
  
  Asset Class Configuration:
  
  Verify the asset class settings (Transaction code: OAOA) to ensure that it is configured to support the account approach.
  Make sure that the asset class is linked to the correct account determination settings.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or help files related to asset accounting and project accounting to understand the implications of the account approach and how to configure it properly.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the configuration and settings, consider reaching out to SAP support for further assistance.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SPRO: Access to the SAP Reference IMG for configuration.
  CJ02: Change Project in Project System.
  OAOA: Configuration of Asset Classes.
  
  
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance.
  
  
  Documentation: Review the SAP Help Portal for detailed information on Asset Accounting and Project System integration.
  
  
  By following these steps, you should be able to identify the cause of the error and implement the necessary changes to resolve it.