Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

SAP Build OData Destination 404 Error

rbama
Explorer
0 Kudos

Hello Experts,

During my migration from SAP iRPA to SAP Build Apps , having issues as below:

1) Error 404 - Unable to Connect to Odata Services

I am having issue adding Destination in my SAP BTP Cockpit to connect to Odata services to use SAP Build Apps.

2) Email Notification Does not work - Do I need to add SMTP setup?

Anybody having same issue as me. Pls assist.

5 REPLIES 5

Dan_Wroblewski
Developer Advocate
Developer Advocate
0 Kudos

Where are you getting 404 error?

I see you do not have Appgyver.Enabled property for destination. Also, the question is not labeled as SAP Build Apps though you mention it in the question.

Can you explain a little more what are the issues with 404 and email? You do have to create your own SMTP service ( or use like Gmail) and then configure the destination for it for SAP Build Process Automation.




--------------
See all my blogs and connect with me on Twitter / LinkedIn

0 Kudos

Hi Daniel,

Error 404 i am getting at the SAP Build Automation when trying to connect to the Odata Service URL. Then I notice that we need to add Destination in BTP Cockpit in order to connect to the OData Services. So when I am trying to add Destination and check Connection it shows error as "Backend status could not be determined".

Appreciate if you could advise.

rgds,

bama

Dan_Wroblewski
Developer Advocate
Developer Advocate
0 Kudos

Ah, I see it's on-premise via Cloud Connector. Can you see this troubleshooting information: https://github.com/SAP-samples/s4hana-cloud-extension-process-automation/blob/main/documentation/set...




--------------
See all my blogs and connect with me on Twitter / LinkedIn

Venkat_Vyza
Active Participant
0 Kudos

Hello rbama

First of all, you are NOT migrating to Build Apps but to Build Process Automation - BPA (iRPA is part of the BPA)

1. To see your BTP Destination in Build Proces Automation, please add the below property to your Destination

sap.processautomation.enabled = true

2. Yes, you should work on SMTP setup to trigger the emails.

Please find the steps here Configure an SMTP Mail Destination | SAP Help Portal

Please mark the answer helpful if it's useful.

Thank you,

Venkat Vyza

rbama
Explorer
0 Kudos

Hi Karthik,

Added the field, but still no luck.

As suggested by David, I also added Appgyver. Still no luck. But I tried to follow the guideline on the link given, it shows error as below when I try to save the subaccount in Cloud Connector.

Get request to https://connectivitycertsigning.eu2.hana.ondemand.com:443/certificate/management/v1/trusted/ca/accou...

2023-11-22 22:10:13,205 +0800#INFO#com.sap.scc.security#https-jsse-nio2-8443-exec-7# #https://connectivitycertsigning.eu2.hana.ondemand.com:443/certificate/management/v1/trusted/ca/account/e5ff2046-5674-4150-a837-858036c3606b Returned Http Response with code 401

2023-11-22 22:10:13,206 +0800#INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-7# #Stopping service channels on e5ff2046-5674-4150-a837-858036c3606b@eu2.hana.ondemand.com

2023-11-22 22:10:13,225 +0800#INFO#com.sap.scc#https-jsse-nio2-8443-exec-7# #An error occurred when trying to connect. See ''Log And Trace Files'' and in particular ljs_trace.log for details.

com.sap.scc.servlets.RequestFailureExecution$InvalidConfiguration: An error occurred when trying to connect. See ''Log And Trace Files'' and in particular ljs_trace.log for details.

at com.sap.scc.ui.SubaccountControl.createSubaccount(SubaccountControl.java:122)

at com.sap.scc.servlets.ConfigurationServlet.addAccount(ConfigurationServlet.java:1370)

at com.sap.scc.servlets.ConfigurationServlet.dispatch(ConfigurationServlet.java:217)

at com.sap.scc.servlets.ServletUtilities.service(ServletUtilities.java:54)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:582)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:212)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:156)

at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:181)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:156)

at com.sap.scc.ui.rt.UTF8Filter.doFilter(UTF8Filter.java:22)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:181)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:156)

at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:167)

at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:90)

at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:609)

at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:130)

at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:682)

at com.sap.js.statistics.tomcat.valve.RequestTracingValve.callNextValve(RequestTracingValve.java:113)

at com.sap.js.statistics.tomcat.valve.RequestTracingValve.invoke(RequestTracingValve.java:59)

at com.sap.core.js.monitoring.tomcat.valve.RequestTracingValve.invoke(RequestTracingValve.java:27)

at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:93)

at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74)

at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343)

at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:617)