Question Re: Build Process Automation: Call Web Service with Desti... in Technology Q&A

Build Process Automation: Call Web Service with Destination Timeout Error

MioYasutake — Fri, 02 May 2025 05:22:14 GMT

Hi community,

I am configuring a standard process template "Supplier Invoice Status Check".

https://api.sap.com/package/eu10.storecontentdevacc.automaticsupplierinvoicestatuscheck2/overview

By following the configuration guide, I have created a communication user, communication arrangement, etc. in our S/4HANA Public Cloud tenant. The Destination has been configured as shown below:

I double-checked that this destination is accessible via SAP Business Application Studio.

However, when I test the process, it fails at the first "Call Web Service with Destination" step with the following error:

{ "code": "irpa_core.error.Timeout", "message": "Timeout error: call callHttpRequest" }

The following is the request object passed to the step:

{ "url": "/sap/opu/odata/sap/API_BUSINESS_PARTNER/A_BusinessPartnerAddress?$filter=BusinessPartner eq '15300002'&$format=json&$select=AddressID", "method": "GET", "responseType": "json", "resolveBodyOnly": true, "timeout": 30000, "encodeDestinationPath": true }

The URL is working fine from Postman (with the same user and password used in the destination).

Does anyone have an idea why this timeout error is occurring?

Re: Build Process Automation: Call Web Service with Desti...

Dennis_Suck85 — Thu, 08 May 2025 22:14:09 GMT

Hello MioYasutake

There could be several reasons for the timeout.

My suspicion is that there is a communication problem between SAP BPA and the destination in SAP BTP, meaning SAP BPA cannot access the destination that configured in SAP BTP.

Did you config the destination-name as the destination in SAP BPA or you use the link like in Postman?
A screenshot of the Destination configuration from SAP BPA would be helpful here.

Best regards
Dennis

Re: Build Process Automation: Call Web Service with Desti...

leon_potgieter — Mon, 09 Feb 2026 23:45:44 GMT

Hello MioYasutake,

Did you manage to fix this issue? I'm getting the same error.

Thanks

Leon