on ‎2023 Mar 06 8:49 PM
Hello Experts.
We are having a problem with an App that is Deployed in BTP, this herd calls an Odata that is hosted in the Odata provisioning, which works without a problem, showing the Metadata.

But when opening the app, a 500 error appears and it does not show Odata data.

Reviewing the Error Log, I get the following message.
GET request to ...0.0.1/odata/SAP/.../$metadata?sap-language=ES
completed with status 500 Error while retrieving destination SAP_HCM_ODP from destination service. HTTP status code: 404, token details:
{"subdomain":"cross-prd-conecta-u8rodjdd",
"serviceInstanceId":"84aa3622-cf06-474d-aee6-0171ddf58acc",
"clientId":"sb-clone84aa3622cf06474daee60171ddf58acc!b60514|destination-xsappname!b62",
"expiration":1678174796,"roleCollections":[]}<br>
(the points are to cover the url for confidentiality issues)
Honestly we are very lost, we don't know why it may be failing, so I turn to you for any help or suggestion that could help us solve this problem.
We already reviewed everything that occurred to us, between the destination, the server deployment, the roles and profiles in the users.
We appreciate each and every one of your responses.
Greetings.
Edson.
Request clarification before answering.
Hii Edson,
Have you added routes in the xs-app.json file?
if not, add the below code and, please fill the pattern with your URL pattern in blank space, which defines if the URL includes odata/SAP then it will call the destination mentioned in the destination.
"source": "^/__________/(.*)$", // odata/SAP
"target": "/_______/$1", // odata/SAP
"authenticationType": "xsuaa",
"destination": "SAP_HCM_ODP"
}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Fatema.
Thank you for your answer, yes, everything was already configured, both in the files as you tell me, fortunately yesterday we were able to solve it, it turns out that we needed to configure a Destination in the subaccount to which the application was pointing.
It had been configured in another account, so it could not work and therefore, it did not generate the call correctly.
I appreciate your time in answering my question.
Have a great day.
Greetings.
ebz
| User | Count |
|---|---|
| 13 | |
| 8 | |
| 7 | |
| 5 | |
| 4 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.