CANNOT_READ_PALOAD error with SOAP to PROXY Synchronous interface

Hi,
   Problem with SOAP to PROXY Synchronous interface.
In Production client, some times we are getting the below shown error in SXMB_MONI. There is no Inbound payload also.
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
  <SAP:Category>XIServer</SAP:Category>
  <SAP:Code area="MAPPING">CANNOT_READ_PAYLOAD</SAP:Code>
  <SAP:P1 />
  <SAP:P2 />
  <SAP:P3 />
  <SAP:P4 />
  <SAP:AdditionalText />
  <SAP:Stack>Unable to read payload from the message object</SAP:Stack>
  <SAP:Retry>N</SAP:Retry>
  </SAP:Error>
Please suggest me to resolve this.
Thanks in advance,
Hari.

Hi Hari,
In your case, check SAP Notes: 1082111 and  1060723.
Regards,
P.Rajesh

Similar Messages

  • SOAP - XI- PROXY synchronous  scenario

    Hi Experts,
    I have a
    SOAP -
    XI -
    PROXY  Synchronous Scenario
    I have done the following things ESR and ID
    ESR:
    1. Created DT and respective MT for Request and Response.
    2. Created Service Interfaces with Synchronous mode with respective MT's.
    3. Created Two separate MM with respective Request and Response MT's.
    4. Created Operation Mapping and call both Request and Response Mappings in it.
    Integration Directory (ID):
    1. Configured considering Sender SOAP and Receiver ECC Services.
    2. Configured CC with required parameters in Sender SOAP CC and Receiver XI CC.
    3. Generate wsdl from Sender agreement and save it as a local file.
    I am getting error in receiver agreement. Do I need to specify any Module parameters in Module TAB for Sender CC or Receiver CC to synchronous scenario.
    Please hep me out.
    Thanks

    Hi Ram,
    I am getting error in receiver agreement. Do I need to specify any Module parameters in Module TAB for Sender CC or Receiver CC to synchronous scenario.
    It looks like you did not create a receiver agreement, or if you did, it did not match the interface that is given or configured in Interface Determination. Can you recheck your configuration?
    Regards,
    Mark

  • SOAP to Proxy synchronous scenario

    Hi,
    Hope you are all doing well.
    I have a SOAP to Proxy synchronous scenario. As part of this scenario, the data structure of the response sent by SAP is different from the response sent back to the SOAP requester. Hence I have used request message mapping between the SOAP request sent by requester and the one passed on to SAP and response message mapping between the response sent by SAP and the one passed on to the requester. Both the message mappings are incorporated in a single Interface mapping.
    The problem is that the interface is behaving like a asynchronous one, i.e., request is passing over to SAP but though the proxy is giving a response back, the same is not coming over to XI.
    It would be really helpful if you can let me know what might have gone wrong.
    regards
    Debansu

    Hi,
    you should have that:
    1. Two Message Mapping:
    1.1. a Message Mapping for request    (called MM_request)    , from MT_SOAP_request     to   MT_Proxy_request.
    1.2. a Message Mapping for response (called MM_response) , from MT_Proxy_response   to   MT_SOAP_response.
    2. One Operation Mapping (in PI 7.1) or Interface Mapping (in PI 7.0) from SI_SOAP to SI_ Proxy with:
    2.1 in the tab "request", so from MT_SOAP_request     to   MT_Proxy_request    , give your Message Mapping "MM_request".
    2.2 in tab "response"   , so from MT_Proxy_response   to   MT_SOAP_response, give your Message Mapping "MM_response".
    3. In you Directory, you define a flow like that:
    from SI_SOAP to SI_ Proxy by using your Operation Mapping.
    If I missed nothing, that's all.
    MT = Message Type
    MM = Message Mapping
    SI =Service Interface in PI 7.1  or Message Interface in PI 7.0.
    regards.
    Mickael
    Edited by: Mickael Huchet on Oct 19, 2011 4:07 PM

  • Web Service u0096 ABAP proxy  synchronous interface

    hi experts,
    can you suggest me how to do this scenario?
    <i><b>Web Service – ABAP proxy  synchronous interface.</b></i>

    hi,
    you can create a web service on XI
    which will call ABAP proxy (on ERP, SRM etc)
    in a synchronous way (you just need to generate the proxy class
    in TCODE SPROXY)
    then you can fill the method of your generated proxy class
    and you will have WS - ABAP proxy interface
    have a look at this to undrstand server proxy:
    /people/siva.maranani/blog/2005/04/03/abap-server-proxies
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • Soap to proxy - synchronous error

    hi
    i am working on soap to proxy scenario.
    i am getting an error in message monitoring
    Exception caught by adapter framework: com.sap.aii.af.sdk.xi.srt.BubbleException: System Error Received. HTTP Status Code = 200: However System Error received in payload ErrorCode = DYNAMIC_CALL_FAILURE ErrorCategory = XIProxy Parameter1 =  Parameter2 = ZCL_SI_SALES_ORDER_CREATE1 Parameter3 = SI_SALES_ORDER_CREATE Parameter4 =  Additional text =  ErrorStack = Error during proxy processing
    Message E TD 604 cannot be processed in plugin mode HTTP
    [http://sap.com/xi/XI/Message/30^Error "DYNAMIC_CALL_FAILURE"]
    what could be the issue in it ?

    Hi
    It is data issue, you need to debug the proxy for more detail about this error. Take the payload and debug the proxy in SPROXY. Also check below sap note.
    1876952 - XI runtime: Determining dump in receiver system
    Regards,
    Praveen.

  • SET_PAYLOAD_FAILED error in SOAP to Proxy scenario

    Hi PI Experts,
    We have an inbound syncronus interface (Non sap system to SAP) using the SOAP to Proxy scenario.
    When we test the interface using any soap tool like soapui it is working fine but when the interface is triggered end to end from source system then the below error is getting dispalyed on source system.
    500 Internal Server Error
    In XI below is the error message -
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Inbound Message
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIProxy</SAP:Category>
      <SAP:Code area="ABAP">SET_PAYLOAD_FAILED</SAP:Code>
      <SAP:P1>IN</SAP:P1>
      <SAP:P2>REQUEST</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Internal error when completing the message object (setting the payload, direction: IN message: REQUEST)</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Can any please let me know what is the issue here?
    Appreciate your help.
    Regards,
    Jitender

    We had a similar issue with a Synchronous Interface
    The interface worked perfectly when sending the request directly to the integration server, but when sending it using SOAP the issue appeared.
    It was very tricky to solve it because we had similar interfaces that worked without any issues.
    SOLUTION: Create a new Service interface with a new name different from the one failing. And make sure The Message Types are in the same namespace as the service interface.
    Why?:
    The issue turned out to be in the sender agreement, and name-spacing issues.
    Our Outbound Service Interface belonged to one SWCV and ns, We will call it "ns1:SI_A_OUT".
    In PI 7.3, and I believe 7.11 also, the you no longer assign a default interface in the to the SOAP communication channel sender agreement pair.
    Therefore the SOAP adapter determines the soap method from the payload. If The internal message type in the soap message belong to different namespace, the the java method  getMessage() does not find the correct XML node, therefore does not find the payload.
    <"ns1:SI_A_OUT">
    ...<ns2:MT_element>
    getMessage( ns1:MT_element)
    We are not sure if the issue is the implementation of the SOAP protocol or in the WSDL generation. But this issues seem to create orphan object during runtime, and even if you re-implement the complete interface, the sender agreement seems to be corrupt.
    Therefore the only was we could solve this, was to move our MT to the same namespace as the service interface and rename the interface "ns1:SI_A2_OUT"
    Hope this helps someone.
    Juan Francisco Zurita Duque
    NNIT A/S

  • SAP PI 7.4 SOAP - ABAP Proxy Synchronous Webservice

    Hi Everyone,
    I am developing the following scenario:
    3rd party makes a SOAP call to SAP (via PI) to determine whether a vendor exists or not in the SAP system. The link for the call is provided by us from the Integrated Configuration.
    The request comes in, calls an ABAP Proxy to check if a vendor exists and sends a response back to the SOAP call with a 'Y' or an 'N'.
    I've read a lot about various scenarios but I'm having trouble connecting the dots as I'm fairly new to PI. I'd appreciate any help.
    I've made the following set-up based on assuming I need separate Service Interfaces for the SOAP Request & Proxy Response
    ESR
    1. Message Types
         SOAP (MT_SOAP_REQ & MT_SOAP_RESP) - PROXY (MT_PRXY_REQ & MT_PRXY_REQ)
    2.  Message Mappings
         MM_REQUEST    which maps MT_SOAP_REQ   to  MT_PRXY_REQ)
         MM_RESPONSE which maps MT_PRXY_RESP   to MT_SOAP_RESP)
    3. Service Interfaces (Synchronous)
        (SOAP Request)
        SI_IN (Inbound Interface)       with Request = MT_SOAP_REQ and Response = MT_SOAP_RESP
       (Proxy Response)
        SI_OUT (Outbound Interface) with Request = MT_PRXY_REQ and Response  = MT_PRXY_RESP 
    4. Operation Mapping
        OM_LOOKUP which maps SI_IN to SI_OUT with Request    (MT_SOAP_REQ  to MT_PRXY_REQ)
                                                                        and  Response (MT_SOAP_RESP to MT_PRXY_RESP)
    I create the ABAP Proxies for each Service Interface. SI_IN contains the required coded method to check if there is a vendor.
    I create the webservice and binding for SI_IN in SOAMANAGER
    At this point I'm somewhat unsure - what do I need to do for SI_OUT ? Do I need to create a logical port ? how is SI_OUT associated to SI_IN (apart from the Operation)  to get the response.
    ID
    In the Integration Directory I've created a SOAP_SENDER communication channel for System A and SOAP_RECEIVER channel for SAP.  For the SOAP Receiver I need to specify a URL - what should this be ? Is it meant to point to the web service for SI_IN in SICF or just to the generic http://host:8000/sap/xi/engine?type=entry 
    Do I need to use the HTTP_AAE adapter for the receiver instead of SOAP ?
    I created an Integrated Configuration for the SI_IN Service Interface with comm channel SOAP_SENDER from System A and SOAP_RECEIVER for SAP backend.  I then got the WSDL for this to provide to the 3rd Party to test (via SOAP UI)  . Again my concern is how is the SI_IN linked to the SI_OUT to achieve the response ?
    I appreciate you taking the time to go through this .  Any help is greatly appreciated.
    Thanks very much
    Gary

    I create the webservice and binding for SI_IN in SOAMANAGER
    At this point I'm somewhat unsure - what do I need to do for SI_OUT ? Do I need to create a logical port ? how is SI_OUT associated to SI_IN (apart from the Operation)  to get the response.
    >>>>No need to do anything in SOAMANAGER
    Do I need to use the HTTP_AAE adapter for the receiver instead of SOAP ?
    >>> No. Soap adapter is fine. Configure your receiver channel as explianed in the below blog (section 4.3)
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70066f78-7794-2c10-2e8c-cb967cef407b?overridelayout=t…
    Again my concern is how is the SI_IN linked to the SI_OUT to achieve the response ?
    >>>>Your receiver determination and interface determination takes care of this.(receiver interface  & outbound processing tabs in ICo)

  • Error with Soap sender channel

    I have a scenario SOAP->Proxy ..whenever I send a message through SOAP its giving error as below:
    com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Connection SOAP_http://sap.com/xi/XI/System is currently not started.
    Please help me in rectifying this...

    Kiran,
    strange thing is that when we remove the standard module from the channel then its workign fine..
    Well, you can try couple of things more -
    1. Re-start the java engine.
    2. If step 1 doesn't work, delete the channel -> activate the change list -> create a new channel and try again.
    I feel that after step 1, it should work. Let us know how it goes.
    Regards,
    Neetesh

  • Time out at communication channel type SOAP and RFC(synchronous interface)

    Hello Experts.
    I have a some interfaces here that have a Sender SOAP channel and Receiver RFC channe. We have problens with Timeout with soap channel and expiration with RFC time channel. I need a way to keep de connection alive in these interfaces, someome can indicate a way to do it?
    Thanks a lot.

    The error that ocurred is that one:
    SOAP: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: XIAdapterFramework:GENERAL:com.sap.aii.af.ra.ms.api.MessageExpiredException: Message 4f451ed1-db17-11e0-ab5d-00001e05f032(INBOUND) expired: com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapterFramework:GENERAL:com.sap.aii.af.ra.ms.api.MessageExpiredException: Message 4f451ed1-db17-11e0-ab5d-00001e05f032(INBOUND) expired
    The RFC inbouc channel expired.
    Thanks.

  • "NO_RECEIVER_CASE_BE" error with SOAP Sender assigned to a Business Service

    Hi all,
    we have a strange error with XI3.0
    We created a configuration scenario where the initial step is done by a Business System, that uses a SOAP Sender communication channel to send its request. And this works great when testing it with XMLSpy.
    But we then needed to shift from a Business System to a Business Service, as the machine sending the SOAP request changed and was not anymore part of the landscape, but elsewhere.
    Hence we recreated a SOAP sender which we assigned to this new business service, doing absolutely the same configuration work as for the other soap sender of the former business system.
    Yet when testing it through XMLSpy, we everytime get a NO_RECEIVER_CASE_BE error back, stating that "No receiver could be determined". Yet when checking in sxi_cache, receiver determination is clearly there. All the blogs I went into are only refering to Business System for a SOAP sender, so I was wondering if any of you already managed to assign a SOAP sender to a business Service.
    Regards,
    Cedric

    hi,
    so you sue SOAP to make a query ? (sync)
    or to send the data to XI ? (async)?
    if async then make sure
    you use <b>Quality of Service</b> other then BE
    in your soap adapter channel
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • Error with JPR(Java Proxy Runtime) in Adapter Monitor of RWB

    Dear Experts,
                 I am implementing scenario with Client Java Proxy(Outbound) and Server ABAP Proxy(Inbound). We have done all the designing in IR and configurations in ID. We have deployed the EAR successfully. But when we go to RWB(Runtime Work Bench) to monitor the inital status of JPR in RWB->Adapter Monitor. It shows the following error.
    Status     Name                                Text
    Error        SLD Access                     SLD host:port = yhsapi01.yashsap.com:50000
    Error getting JPR configuration from SLD. Exception: Connect to SAP gateway failed
    Connect_PM TYPE=A ASHOST=yhsapi01 SYSNR=00 GWHOST=yhsapi01 GWSERV=sapgw00 PCS=1
    LOCATION CPIC (TCP/IP) on local host with Unicode
    ERROR max no of 100 conversations exceeded
    TIME Wed Jun 03 19:42:45 200
    RELEASE 700
    COMPONENT CPIC (TCP/IP) with Unicode
    VERSION 3
    RC 466
    MODULE r3cpic.c
    LINE 10713
    COUNTER 5521
    No access to get JPR configuration

    Hi!
    Obviously there are more than 100 connections opened in your system.
    ERROR max no of 100 conversations exceeded
    Please check your gateway settings (in ABAP you can check the parameters using transaction SMGW).
    Regards,
    Volker

  • Error with SOAP Request to calendar web service

    Hi
    I'm sending the following SOAP request to a calendar web service to create an appointment in the calendar. The response returns what seems to be a syntax error ("The Create method did not have a proper element in the request") but I can't see the cause of the fault. Any suggestions on what it may be? It's an 11g DB.
    Many thanks
    -x-POST-x-
    POST /ocws-bin/ocas.fcgi HTTP/1.0
    Content-Type: text/xml; charset="utf-8"
    Content-Length: 993
    SOAPAction: SOAPAction: "http://www.oracle.com/WebServices/Calendaring/1.0/Create"
    Connection: close
    <SOAP-ENV:Envelope
    xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
    <SOAP-ENV:Header><auth:BasicAuth xmlns:auth="http://soap-authentication.org/2002/01/">
    <Name>CalendarName</Name><Password>CalendarPassword</Password>
    </auth:BasicAuth> </SOAP-ENV:Header>
    <SOAP-ENV:Body><cwsl:Create xmlns:cwsl="http://www.oracle.com/WebServices/Calendaring/1.0/"><CmdId>ITS APPOINTMENT</CmdId><iCalendar>
    <vcalendar prodid="-//Oracle//Calendaring//Calendarlet//EN" version="2.0">
    <vevent><class>PUBLIC</class>
    <description>Calendar Body</description>
    <dtstart value="DATE-TIME">20102905T120000</dtstart>
    <duration>P00DT0H30M00S</duration>
    <location>Location of user</location>
    <summary>Incident ID - (name of user])</summary>
    <uid>XGjRVnpReQALNsILlBlvcyXGCoUyXF</uid>
    <x-oracle-eventtype>APPOINTMENT</x-oracle-eventtype>
    <priority>5</priority>
    </vevent>
    </vcalendar>
    </iCalendar></cwsl:Create></SOAP-ENV:Body></SOAP-ENV:Envelope>
    -x-RESPONSE-x-
    HTTP/1.1 500 Internal Server Error
    Date: Thu, 27 May 2010 08:22:16 GMT
    Server: Apache/2.2.4 (Unix) mod_ssl/2.2.4 OpenSSL/0.9.7a mod_fastcgi/2.4.6
    OCAS-ProcTime: 407
    Connection: close
    Content-Type: text/xml; charset=utf-8
    <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
    <soap:Body>
    <soap:Fault>
    <faultcode>soap:Server.Error::System::SOAPRequest</faultcode>
    <faultstring>The Create method did not have a proper element in the request</faultstring>
    <detail>
    <cwsl:Error xmlns:cwsl="http://www.oracle.com/WebServices/Calendaring/1.0/">
    <Class>Error::System::SOAPRequest</Class>
    <Code>0020-00-00-00000034</Code>
    <Line>3180</Line>
    <FileName>SOAPRequestHandler.cpp,v</FileName>
    <Version>1.57</Version>
    <LastMod>2007/05/30 21:13:25</LastMod>
    <Author>pscattol</Author>
    <Date>Thu May 27 09:22:16 2010</Date>
    <PID>26152</PID>
    <TID>3044838304</TID>
    <Level>Error</Level>
    </cwsl:Error>
    </detail>
    </soap:Fault>
    </soap:Body>
    </soap:Envelope>

    Hi,
    I am having problem using dii client, while sending a
    request to c# webservice. error follows
    QName QNAME_TYPE_STRING = new QName(NS_XSD,
    "string");
    call.setReturnType(QNAME_TYPE_STRING);
    call.setOperationName(new QName(BODY_NAMESPACE_VALUE,
    "GetDetails"));
    call.addParameter("String_1", QNAME_TYPE_STRING,
    ParameterMode.IN);Do you need another call to addParameter here?
    String[] params = { "02", "2004" };
    String result = (String)call.invoke(params);

  • ABAP Proxy synchronous interface - access to payload

    Hi,
    I have a scenario from ABAP Proxy -> XI -> Web Service.
    On occassion, there is an issue with calling the Web Service (unavailable for instance) and an exception is returned to the ABAP Proxy for a SystemError.
    I am able to catch this exception in the proxy and output the error - for example HTTP.Exception.HTTP.Adapter.
    However, I also want to use information in the response payload to output on the error as the payload contain infrmation on why the error was thrown in the target application - for example - Format of data xxx is incorrect.
    I can get access to the request payload using interface/class IF_WSPROTOCOL_PAYLOAD=>GET_SENT_REQUEST_PAYLOAD but there does not seem to be an equivalent for GET_RECEIVED_RESPONSE_PAYLOAD !
    Have anyone done this before - use payload information in an ABAP proxy from the response payload ?
    Kind regards
    Colin.

    Hi,
    I will need the actual payload info not the status.
    I will have to debug SXI_MONITOR in CRM to see how it is obtained.
    Thanks
    Colin

  • File to Proxy Synchronous interface help

    Hi guys/experts,
    I have file to proxy scenario.
    I have created the objects in IR. When coming to ID, i got stopped in receiver agreement.
    Followings are the IR objects
    Data Types
    DT_File_Send - Sending data
    DT_File_Receive - Receive response data
    DT_Prxy_Receive - Proxy receive
    DT_Prxy_Response - Proxy response data
    Messsage Types
    MT_File_Send - Sending data
    MT_File_Receive - Receive response data
    MT_Prxy_Receive - Proxy receive
    MT_Prxy_Response - Proxy response data
    Message Interfaces
    MI_File - Outbound - Synchronous
          OUtput Message - MT_File_Send
          Input Message - MT_File_Receive
    MI_Proxy - Inbound - Synchronous
          Input Message - MT_Prxy_Receive
          Output Message - MT_Prxy_Response.
    Message Mapping
    MM_File_2_Proxy
    MM_ProxyResponse_2_File
    Interface Mapping
    IM_File_Proxy
    When coming to the intergration directory, i am able to create the objects for File to Proxy direction, but for the resposne from the proxy, when i try to create the receiver agreement, i am not able to select the message interface.
    Can anybody pls advise me how to complete the response direction..
    Thanks in advance
    Mani.

    When coming to the intergration directory, i am able to create the objects for File to Proxy
    direction, but for the resposne from the proxy, when i try to create the receiver agreement, i am not able
    to select the message interface.
    check if your development is as per this wiki:
    https://www.sdn.sap.com/irj/scn/wiki?path=/display/xi/file-rfc-file%2528without+bpm%2529&
    In this wiki the flow is FILE <-->XI <-> RFC .....while yours is FILE <> XI <---> PROXY......so the sender is the same....just replace the RFC with your Proxy and check.
    Regards,
    Abhishek.
    Edited by: abhishek salvi on Jun 9, 2009 4:00 PM

  • Error with receiver java proxy

    for a XI type communication channel for receiver Java proxy I see following error in SXMB_MONI.
    <i>Unable to read user password from communication channel of type Error when accessing the secure store (access ID = 3650CAFA1FBAA04E8F260C6C4C1923FA) Error while reading from the secure store: ERROR_UNKNOWN: Cannot find entry in secure store (SECSTORE,023).</i>
    I have specified the correct credentials for the non sap system in authentication data i.e. XIAPPLUSER and its password.
    Any pointers?

    Hi Amol
    Did you solved this problem? I am also getting the same error when calling receiver java proxy with Adapter type XI.
    If you have solved the problem pl let me know.
    Regards
    Prahllad

Maybe you are looking for