cancel
Showing results for 
Search instead for 
Did you mean: 

Error while consuming On-Premise OData Service in SAP Conversational AI

Aisurya
Participant

Hello Experts,

I am facing issue while consuming an On-Premise OData API in SAP Conversational AI. Below are the configs/steps.

-> I am working on both the enterprise accounts of SAP BTP and SAP Conversational AI.

-> Cloud connector is connected to On-Prem S/4 system and configured in a subaccount.

-> A destination of type Basic Auth is maintained in the BTP Subaccount.

Chatbot configs :-

-> Configured system Alias and selected the required destination of subaccount from the dropdown in Environment section.

->Maintained API Service Configs in the Actions

->While testing the chatbot getting 404 not found error. I could see in the logs the "virtual host" & "virtual port" are prepended to the OData API.

Note - The Same destination and OData API is consumed in one of a Fiori Application which is running in the same sub account and its returning values from the backend as expected.

Please guide me here.

Thanks in advance.

Aisurya Puhan

    Accepted Solutions (0)

    Answers (1)

    Answers (1)

    JonasB
    Contributor
    0 Kudos

    Hi Aisurya,

    please ensure you have the full URL path maintained either in the destination or in the API call. Is just „/sap“ really the full path to the OData service root?

    The response looks to me like it is coming from the backend system, so the Cloud Connector configuration should be fine. Also it’s correct that the virtual host is displayed.

    Regards
    Jonas

    Aisurya
    Participant
    0 Kudos

    Thanks Jonas.

    I have added missing path to the URL and it is as below :-

    /sap/opu/odata/sap/C_PURCHASEORDER_FS_SRV/C_PurchaseOrderFs?sap-client=030&$skip=0&$top=20

    API Service Configs

    Still the same error persists.

    I am not sure, what is missing here.

    Request your help here.

    Regards

    Aisurya

    JonasB
    Contributor
    0 Kudos

    Hi Aisurya,

    Does the response still contain the error „Service cannot be reached“?

    Did you test the API call before with Postman or a similar tool?

    Regards

    Jonas