The Connection Test from a HTTP Destination (transactions SM59 or SOAMANAGER) targeting the SAP Integration Suite, managed gateway for spend management and SAP Business Network servers, results in the below error: Status HTTP Response 500 internal server error

The connection test function in SAP transactions like SM59 and SOAMANAGER works by sending a basic, empty HTTP request to the target server's URL. This is intended to verify network-level connectivity only.

However, the SAP Business Network and Ariba application endpoints are designed to process specific business documents (e.g., cXML payloads). They are not configured to respond to the generic test request sent by SM59.

When the server receives this unexpected and empty request, it cannot process it and returns an HTTP 500 Internal Server Error. This is the server's standard way of indicating an application-level failure.

Crucially, receiving any HTTP response code (including 500) confirms that the lower-level connection was successful:

1. DNS resolution of the hostname worked.
2. A TCP/IP connection was established through any firewalls or proxies.
3. The target server's web service is active and responded.

The Status HTTP Response 500 error can be ignored, as this means that the connectivity (TCP/IP layer) is working.

To check the supported target system URLs by the Integration Suite Managed Gateway for Spend Management and SAP Business Network refer to the link from the guide: Creating an RFC Destination for SAP Integration Suite, Managed Gateway for Spend Management and SAP Business Network.

SAP Integration Suite Managed Gateway > Managed Gateway - Platform > Managed Gateway - Buy side Connectivity