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

SAP Error Message - Details

• 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 in question. Ensure that the client is configured to allow eCATT commands.
  If necessary, adjust the settings to enable eCATT execution.
  
  
  
  Review User Authorizations:
  
  Ensure that the user executing the eCATT command has the necessary authorizations. You can check this using transaction SU53 after the error occurs to see if there are any missing authorizations.
  If needed, assign the appropriate roles or authorizations to the user.
  
  
  
  Verify Trusted RFC Configuration:
  
  Check the Trusted RFC settings in transaction SM59. Ensure that the RFC destination used for the eCATT command is correctly configured and that the user credentials have the necessary permissions.
  If the Trusted RFC connection is not set up correctly, you may need to create or modify the RFC destination to allow the execution of eCATT commands.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to eCATT and Trusted RFC for any specific configurations or known issues that may apply to your version of SAP.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for further assistance. They may provide additional insights or solutions based on your specific system configuration.
  
  
  
  Related Information:
  
  eCATT: Extended Computer Aided Test Tool is used for automated testing in SAP environments.
  Trusted RFC: A Trusted RFC connection allows for secure communication between SAP systems without requiring user credentials for each call.
  Transaction Codes:
  
  SCC4: Client Administration
  SM59: RFC Destinations
  SU53: Authorization Check
  
  
  
  By following these steps, you should be able to resolve the ECATT559 error and successfully execute your eCATT commands.