/EACC/MSG_BTA060 - Accounting system not recognized

SAP Error Message - Details

• Message type: E = Error

• Message class: /EACC/MSG_BTA -

• Message number: 060

• Message text: Accounting system not recognized

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.

AnswerBot

• What is the cause and solution for SAP error message /EACC/MSG_BTA060 - Accounting system not recognized ?

  The SAP error message /EACC/MSG_BTA060 Accounting system not recognized typically indicates that the system is unable to identify or connect to the specified accounting system. This can occur in various scenarios, particularly when dealing with integration between different systems or modules within SAP.
  Causes:
  
  Configuration Issues: The accounting system may not be properly configured in the SAP system. This could be due to missing entries in the configuration tables or incorrect settings.
  Missing or Incorrect RFC Destination: If the accounting system is supposed to be accessed via Remote Function Call (RFC), the RFC destination may not be set up correctly or may be missing.
  Authorization Issues: The user may not have the necessary authorizations to access the accounting system.
  System Landscape Changes: Changes in the system landscape, such as system upgrades or migrations, may lead to discrepancies in the configuration.
  Network Issues: Connectivity problems between the SAP system and the accounting system can also lead to this error.
  
  Solutions:
  
  
  Check Configuration:
  
  Verify that the accounting system is correctly configured in the SAP system. This includes checking the relevant configuration tables and ensuring that all necessary entries are present.
  Use transaction codes like SPRO to access the configuration settings and ensure that the accounting system is defined.
  
  
  
  Verify RFC Destination:
  
  Check the RFC destination settings using transaction SM59. Ensure that the destination is correctly configured and that the connection test is successful.
  If the RFC destination is missing, create a new one with the correct parameters.
  
  
  
  Review Authorizations:
  
  Ensure that the user has the necessary authorizations to access the accounting system. This may involve checking user roles and profiles in transaction SU01.
  
  
  
  Check System Landscape:
  
  If there have been recent changes to the system landscape, review the changes to ensure that they have not affected the configuration of the accounting system.
  
  
  
  Network Connectivity:
  
  Check for any network issues that may be preventing communication between the SAP system and the accounting system. This may involve checking firewalls, network settings, and ensuring that both systems can communicate.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to the specific error message for additional troubleshooting steps or patches that may be required.
  
  
  
  Related Information:
  
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error message or provide additional troubleshooting steps.
  Transaction Codes: Familiarize yourself with transaction codes like SM21 (System Log), ST22 (Dump Analysis), and SLG1 (Application Log) to gather more information about the error context.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  
  If the issue persists after following these steps, it may be necessary to involve your SAP Basis team or SAP support for further assistance.