cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Build Process Automation: Call Web Service with Destination Timeout Error

MioYasutake
SAP Champion
SAP Champion
0 Likes
531

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:

MioYasutake_0-1746162849129.png

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"
		}

MioYasutake_1-1746162935640.png

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?

Accepted Solutions (0)

Answers (1)

Answers (1)

Dennis_Suck85
Participant
0 Likes

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

leon_potgieter
Participant
0 Likes

Hello MioYasutake,

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

Thanks 

Leon