Skip to Content
author's profile photo Former Member
Former Member

ODATA Receiver adapter channel - Message could not be forwarded to the JCA adapter

Hi,

I am trying to configure ODATA receiver adapter channel on PI 7.4 SP 11 environment (Java -Single Stack). Message processing on that channel is throwing following error.

Message could not be forwarded permantely to the JCA adapter. Reason:

Message could not be forwarded to the JCA adapter. Reason: Permanent error: Adapter call failed. Reason: com.sap.aii.af.lib.ra.cci.XIAdapterException:

JPR failed to transfer the request message to the messaging system. Reason: com.sap.aii.af.lib.ra.cci.XIAdapterException:


I followed the instructions from SCN Doc-PI.SFSF Integration.DOC – SFSF OData Dynamic query “$filter" clause at runtime.


I am passing below structure as request data for ODATA receiver channel and have set property dynamicQuery to true.



<ns1:QueryStringOptions xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns1="http://sap.com/xi/XI/OData">

<top>0</top>

<skip>0</skip>

<filter>$filter=firstName eq 'yyyyyy'</filter>

</ns1:QueryStringOptions>


Can you please tell me what could be wrong here..

Thanks

-Pradeep


Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

7 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Jun 30, 2015 at 06:12 AM

    May I know why for you refering sfsf odata adapter configuration for ODATA adapter configuration?

    reg, avinash

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jun 30, 2015 at 11:21 AM

    we have ODATA adapter available in PO 7.4 SP11 please try with ODATA and see if it works.

    Thanks

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jun 30, 2015 at 06:28 PM

    Thanks for responding to my post. I am using ODATA adapter and SFSF. Below shows configuration of ODATA receiver channel. We are using the latest Connectivity add on 1.0. SP02. Is there release newer than this?


    odata.jpg (184.2 kB)
    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jul 01, 2015 at 06:55 PM

    Hi Avinash,

    Our BASIS updated the ODATA version to latest service pack and dynamic filters seems to work. However, When ODATA service returns HTTP return code of 404, adapter is not able to handle it properly.

    Using REST cleint when we try ODATA service, service returns following reponse.

    • ?xml version="1.0" encoding="utf-8"?>
    • <error xmlns="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata">
    • <code>SY/530</code>
    • <message xml:lang="en">No Business Partners found for the specified search criteria.</message>
    • <innererror>
    • <transactionid>55904B1F7F02C0DBE1000000AC15AB85</transactionid>
    • <timestamp/>
    • <Error_Resolution>
    • <SAP_Transaction/>
    • <SAP_Note/>
    • </Error_Resolution>
    • <errordetails>
    • <errordetail>
    • <code>/IWBEP/CX_MGW_BUSI_EXCEPTION</code>
    • <message>No Business Partners found for the specified search criteria.</message>
    • <propertyref/>
    • <severity>error</severity>
    • </errordetail>
    • </errordetails>
    • </innererror>
    • </error>

    For the same request ODATA adapter is not able handle the error response.

    In the developer trace log i see below error

    httpResponse Code : 404 : Not Found : HTTP/1.1: ReasonPhrase :Not Found,No Business Partners found for the specified search criteria. 404 : Not Found : HTTP/1.1 : Not Found

    java.util.NoSuchElementException
    [EXCEPTION]
    com.sap.aii.adapter.odata.ra.xi.util.OdataAdapterException: OData call failed.
    at com.sap.aii.adapter.odata.ra.xi.api.ODataAPICaller.processRequest(ODataAPICaller.java:190)
    at com.sap.aii.adapter.odata.ra.xi.api.ODataAPICaller.processRequest(ODataAP...


    Do you know how to handle both success and error response. looks like odata adapter not able to handle the errors.


    Thanks again..

    -Pradeep

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      OData adapter acts just like client. It makes request to endpoint and receives response(both success and error response).

      IF there is failure in the making request corresponding error log will be displayed in the channel monitoring.

      reg, avinash

  • author's profile photo Former Member
    Former Member
    Posted on Jul 02, 2015 at 05:37 PM

    I think, adapter should have handles 404 response gracefully instead of throwing exception. Do you know whether there are any new releases in near feature?

    Thanks again for all your responses.

    -Pradeep

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Mar 23, 2016 at 03:59 PM

    Hi Experts,

    I have a scenario using Odata receiver adpater and I get the following error in CC monitoring. I get Bad Request Error as below. I use a dummy file sender which is polled at every 60 secs and this eventually calls the Odata Receiver. I want to use a sync/async bridge to write the data to file when Odata adapater gives me the data.

    However its failing in the first step of getting data from Odata adapter.

    Message could not be forwarded permantely to the JCA adapter. Reason: {0}

    OData call failed.

    com.sap.aii.adapter.lib.component.odata.exception.OsciException: 400 : HTTP/1.1 : Bad Request

    Message could not be forwarded to the JCA adapter. Reason: Permanent error: Adapter call failed. Reason: com.sap.aii.af.lib.ra.cci.XIAdapterException:

    Odata Service URL:

    https://<host>/sap/c4c/odata/cust/v1/zcustomer/$metadata

    address : https://<host>/sap/c4c/odata/cust/v1/zcustomer/CustomerCommonCollection

    I have configured the Resource Path usning Ecilipse modeller:

    CustomerCommonCollection?$select=ZeitungText,Zeitung,VoordeelmailText,Voordeelmail,VestigingvanoorsprongText,Vestigingvanoorsprong,VestigingsmailText,Vestigingsmail,Uitschrijfdatum,UitnodigingenText,Uitnodigingen,TripolisID,SortingFormattedName,Roepnaam

    Modules on adapter:

    Regards,

    Amber


    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Nov 04, 2019 at 03:15 PM

    Hi,

    please I'm having the same issue!!! How did you solve it?

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.