logo

Are you need IT Support Engineer? Free Consultant

Connecting SAP S/4HANA with SAP Integration Suite,…

  • By sujay
  • 12/05/2026
  • 9 Views

This blog post intends to complement the existing information on the following blog posts:

SAP S/4HANA integration with SAP Integration Suite, Advanced Event Mesh

SAP S/4HANA and SAP Integration Suite, Advanced Event Mesh (AEM) direct integration

 

Whenever a proxy server is configured for SAP S/4HANA outbound traffic, certain configuration changes must be made, while other changes must be requested through a Service Request.

If your customer landscape uses a proxy server for outbound traffic that must be maintained in the SM59 destination, and you receive the following error when activating the AEM channel, this means that your RFC destination of type G does not support TCPS connectivity through a proxy server. In this case, the procedure for routing outbound traffic for your Event channels will be different. One possible solution is to implement a load balancer to route events from SAP S/4HANA, while using the proxy configuration only for the authentication service.

 

 

Requesting a Hyperscaler Load Balancer for Outbound Traffic

The TCPS protocol is required for the AMQP connectivity configured in the Event Channel. So, a solution is to establish this connection directly using a Hyperscaler Load Balancer. 

For that open a Service Request using the template Create Hyperscaler LB for OUTBOUND traffic to an EXTERNAL source(Azure/AWS/GCP).

Screenshot 2026-05-04 At 23.31.03.Png

 

Select the SAP S/4HANA system that needs to be connected with the AEM broker and insert the requested parameters:

Customer ID – the SAP S/4HANA system that needs to be connected.

Select Hyperscaler – the hyperscaler where the selected SAP S/4HANA system is hosted.

Primary or DR Site – if the service is to be performed on the Primary or the DR site.

Source IP Addresses – the IP address of the selected SAP S/4HANA system.

Destination IP Addresses – the Solace broker instance IP address or the host specified with protocol prefix: tcps://

Destination Ports – 5671 (port used for AMQP connectivity)

 

Screenshot 2026-05-04 At 23.44.21.Png

26Q6T3Js.png

Confirm and schedule service.

 

Updating the OAuth profile in SAP S/4HANA

You have created a AEM channel using a service key and the activation fails with the following error:

Screenshot 2026-05-12 At 17.47.03.Png

You have checked the OAuth configuration using the report OA2C_GENERIC_ACCESS, as described in KBA 3444844, and you are receiving the following error:

>> lcl_oa2c_app->EXECUTE_ATR
granttype Client Credentials configured.

HTTP failure, processing failed, invalid state, invalid timeout or others
oa2c_error
Client configuration error or network problems. See kernel traces.

 

Run transaction OA2C_CONFIG:

1. Select the Configuration Name created by your channel.

2. Under tab Administration – Access Settings – Add the values for proxy host and proxy port:

6Xzj8Tse.png

Save the OAuth2 Profile.

 

Run transaction SM59:

1. Select the type G destination created by your channel for the BTP AEM Validation Service.

2. Under Technical Settings – HTTP Proxy Options – Add the values for Proxy Host and Proxy Service:

E930Zoub.png

Save and close.

 

3. Select the type G destination that you created for the Solace broker.

4. Under Technical Settings – Target System Settings – Maintain the same Host and Port used in Destination IP Addresses and Destination Ports requested in the SR Template Create Hyperscaler LB for OUTBOUND traffic to an EXTERNAL source(Azure/AWS/GCP).

6L4N6Mni.png

 

5. Under Technical Settings – Target System Settings – HTTP Proxy Options – Remove the values for Proxy Host and Service:

Screenshot 2026-05-08 At 14.48.45.Png

Save and close.

 

Go to transaction SE38 and execute the report OA2C_GENERIC_ACCESS again. Then confirm that you receive the following message:

Screenshot 2026-05-12 At 16.04.28.Png

 

 

Activating the AEM Channel in SAP S/4HANA

Run transaction IWXBE/CONFIG and activate your channel. Once the channel has been activated, perform a connectivity test.

If your channel activation fails, go to transaction SMICM and check the error in the Trace File.

 

 

Source link

Leave a Reply

Your email address will not be published. Required fields are marked *