How To Fix ECATT_ODATA_ST_TST123 - Addressing changed to HTTP, destination &1

ECATT_ODATA_ST_TST123 - Overview

• Message type: E = Error

• Message class: ECATT_ODATA_ST_TST - eCATT - OData Smoke Test Testing - Messages

• Message number: 123

• Message text: Addressing changed to HTTP, destination &1

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 ECATT_ODATA_ST_TST123 - Addressing changed to HTTP, destination &1 ?

  The SAP error message ECATT_ODATA_ST_TST123 Addressing changed to HTTP, destination &1 typically occurs in the context of using eCATT (extended Computer Aided Test Tool) for automated testing of OData services. This error indicates that there has been a change in the addressing method for the OData service, and it is now using HTTP instead of the previously configured method.
  
  Cause:
  
  Configuration Changes: The destination configuration for the OData service may have been altered, leading to a change in the addressing method.
  Network Issues: There may be network-related issues that are causing the system to revert to HTTP addressing.
  Service Availability: The OData service might not be available over the previously configured protocol (e.g., HTTPS), forcing a fallback to HTTP.
  eCATT Script Changes: If the eCATT script was modified, it might not be compatible with the current addressing method.
  
  
  Solution:
  
  
  Check Destination Configuration:
  
  Go to transaction SM59 and check the configuration of the RFC destination that is being used