How To Fix ECATT559 - System &1 client &2 allows eCATT command &3 when using 'Trusted RFC'

ECATT559 - Overview

• Message type: E = Error

• Message class: ECATT - eCATT Messages (Middleware and GUI)

• Message number: 559

• Message text: System &1 client &2 allows eCATT command &3 when using 'Trusted RFC'

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 ECATT559 - System &1 client &2 allows eCATT command &3 when using 'Trusted RFC' ?

  The SAP error message ECATT559 indicates that there is an issue with the execution of an eCATT (extended Computer Aided Test Tool) command due to restrictions in the system or client configuration. The message typically states that the specified system and client do not allow the execution of the eCATT command when using 'Trusted RFC'.
  
  Cause:
  
  Client Configuration: The client you are trying to execute the eCATT command in may not be configured to allow the execution of eCATT commands via Trusted RFC. This can be due to security settings or restrictions in the client profile.
  Authorization Issues: The user executing the eCATT command may not have the necessary authorizations to perform the action in the specified client.
  Trusted RFC Settings: The Trusted RFC connection may not be properly set up or may not have the required permissions to execute eCATT commands.
  
  
  Solution:
  
  
  Check Client Settings:
  
  Go to transaction SCC4 and check the settings for the client