Channels response on SA520

Hi
A customer of mine is asking of SA520 supports channel response for integration into SMS Passcode. I have tried searching the datasheet on information about this but with no luck. Can anyone shed some light on this?
Kind Regards,
Michael

Are you able to see a contact person for this vendor under Surrogate bidding tab? If not, then pl create one and check again.
Nikhil

Similar Messages

Synchronous message stops at inbound channel response

Hi,
We have an outstanding issue in PI where our synchronous messages stops after receiving the response from the Receiver system. This is an ABAP proxy - JDBC scenario. We already increased the ICM Keep Alive timeout from 600 to 900 seconds but still the issue persist. Also, the processing timeout is already 900 seconds. Do you know the issue why this issue is occuring? On the R/3 side, when the abap proxy is executed it is throwing an error "Error while receiving.. HTTP 402".
Regards,
Geoff
Edited by: Geoffrey Mendoza on Jun 15, 2011 7:26 PM

Hi Geoff,
The error 402 means "Payment Required".
This code is reserved for future use and does not give us a good hint.
Is it possible for you to enter more details so we may be able to point out a specific cause?
Regards,
Caio Cagnani

Request timed out while waiting for response!!

Hi All,
My scenario is PROXY to SOAP. I am getting below error while posting to WEBSERVICE.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
<ns1:stackTrace xmlns:ns1="http://xml.apache.org/axis/">Failed to deliver inbound WS message, code=503 and reason=Request timed out while waiting for response. at com.sonicsw.net.http.ws.WSHttpProtocolHandler$HttpInBrokerHandler.invoke(WSHttpProtocolHandler.java:833) at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32) at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118) at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83) at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:453) at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281) at com.sonicsw.net.http.ws.WSHttpProtocolHandler.sendToSOAPStack(WSHttpProtocolHandler.java:630) at com.sonicsw.net.http.ws.WSHttpProtocolHandler.dispatch(WSHttpProtocolHandler.java:537) at com.sonicsw.net.http.ws.WSHttpProtocolHandler.servicePost(WSHttpProtocolHandler.java:284) at com.sonicsw.net.http.ws.WSHttpProtocolHandler.service(WSHttpProtocolHandler.java:609) at com.sonicsw.net.http.HttpProtocolHandler.handle(HttpProtocolHandler.java:471) at progress.message.net.http.server.HttpConnectionHandler.handle(HttpConnectionHandler.java:170) at progress.message.net.https.server.SonicHttpsConnection.service(SonicHttpsConnection.java:156) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:981) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:831) at progress.message.net.https.server.SonicHttpsServer.handleConnection(SonicHttpsServer.java:449) at progress.message.net.https.server.SonicHttpsServer.handle(SonicHttpsServer.java:364) at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)</ns1:stackTrace>
Any Idea ? Do I need to change anything in my SOAP Channel or BAsis should change the Time Parameter?
Thanks,
Pushkar Patel

Hi,
>>>>>>>Request timed out while waiting for response.
See the below link, it might be helpful to you for timed out issue.
[Link1|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c059d583-a551-2c10-e095-eb5d95e03747?quicklink=index&overridelayout=true]
Regards,
Rajesh

Presence of multiref tag in soap response message

We are having a problem when we try to call a web service in PI. The web services called is provided by an Axis server.
We tried to use the plain HTTP protocol in the definition of the communication channel as shown here:
Adapter type: SOAP
Transport protocol: HTTP
Message protocol: SOAP 1.1
Adapter engine: Central Adapter Engine
We got the followong error response in SXMB_MONI:
The payload shown in SXNB_MONI is:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<ns1:cedstr_obt_cle_elem_v2_Response xmlns:ns1='urn:CEDSTR' soapenv:encodingStyle='http://schemas.xmlsoap.org/soap/encoding/' xmlns:soapenv='http://schemas.xmlsoap.org/soap/envelope/' xmlns:xsd='http://www.w3.org/2001/XMLSchema' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'>
<tab_cle soapenc:arrayType='ns1:cedstr_cle_elem_v1[3]' xmlns:soapenc='http://schemas.xmlsoap.org/soap/encoding/' xsi:type='soapenc:Array'>
<item href='#id0'/>
<item href='#id1'/>
<item href='#id2'/>
</tab_cle><nb_cle xsi:type='xsd:int'>3</nb_cle><stat_elem href='#id3'/>
<cdr href='#id4'/>
</ns1:cedstr_obt_cle_elem_v2_Response>
The expected payload is:
<?xml version="1.0" encoding="UTF-8" ?>
- <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
- <soapenv:Body>
- <ns1:cedstr_obt_cle_elem_v2_Response soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="urn:CEDSTR">
- <tab_cle xsi:type="soapenc:Array" soapenc:arrayType="ns1:cedstr_cle_elem_v1[3]" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
<item href="#id0" />
<item href="#id1" />
<item href="#id2" />
</tab_cle>
<nb_cle xsi:type="xsd:int">3</nb_cle>
<stat_elem href="#id3" />
<cdr href="#id4" />
</ns1:cedstr_obt_cle_elem_v2_Response>
- <multiRef id="id0" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns2:cedstr_cle_elem_v1" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns2="urn:CEDSTR">
<id_structure_det xsi:type="xsd:int">118406</id_structure_det>
<ordinal xsi:type="xsd:int">2648545</ordinal>
<appareil xsi:type="xsd:string">C3D1E</appareil>
<type_cable xsi:type="xsd:string">H</type_cable>
</multiRef>
- <multiRef id="id1" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns3:cedstr_cle_elem_v1" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns3="urn:CEDSTR">
<id_structure_det xsi:type="xsd:int">984806</id_structure_det>
<ordinal xsi:type="xsd:int">2723425</ordinal>
<appareil xsi:type="xsd:string">O5C3X</appareil>
<type_cable xsi:type="xsd:string">H</type_cable>
</multiRef>
- <multiRef id="id2" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns4:cedstr_cle_elem_v1" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns4="urn:CEDSTR">
<id_structure_det xsi:type="xsd:int">1163686</id_structure_det>
<ordinal xsi:type="xsd:int">3144641</ordinal>
<appareil xsi:type="xsd:string">Y0A6B</appareil>
<type_cable xsi:type="xsd:string">H</type_cable>
</multiRef>
- <multiRef id="id3" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns5:cedstr_stat_elem_v1" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns5="urn:CEDSTR">
<tension xsi:type="xsd:string">MT</tension>
<nb_concess xsi:type="xsd:int">0</nb_concess>
<nb_restr xsi:type="xsd:int">0</nb_restr>
<localisation xsi:type="xsd:string">DEVILLERS EST DE BEAUREGARD</localisation>
<remarque xsi:type="xsd:string" />
</multiRef>
- <multiRef id="id4" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns6:utlgen_cdr" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns6="urn:CEDSTR">
<succes xsi:type="xsd:int">1</succes>
<code xsi:type="xsd:int">0</code>
<message xsi:type="xsd:string" />
</multiRef>
</soapenv:Body>
</soapenv:Envelope>
</ns1:cedptr_obt_cle_di_v1_HResponse>
What I can see is that PI seems to ignore the multiref tag in the SOAP response message. Does anybody knows if there is an issue with the mutiref tag in PI ?
Thanks for your help.

The SOAP adapter does not support more than one body child.
If a SOAP message with several body childs arrive, then only the first body child is considered, all other body childs are ignored.
Regards
Stefan

Equalization and Symbol Rate

Despite my number of posts on this board...I swear that I am happy with my NI devices....
I noticed a peculiar thing today. I am using some of the example programs to do some channel characterization. The investigation is meant to be relatively simple. I am using no baseband filtering, and since my transmitter and receiver are static I desire no equalization (in fact, right now, the up and down converters are connected via a short SMA as I do some "sanity checks".)
I am interested in utilizing as much of the 20MHz real time bandwidth as possible...so I went into the transmitter code (for example, the PSK Generate.VI located in the Modulation Toolkit Example folder) and hardwired 20MHz in for the bandwidth. With no baseband filtering, the original code determines BW by scaling the symbols/sec by some number (10 I think) which would limit the symbols/sec to 1MSym/sec.
Anyway...with my 20Mhz BW...I set the symbol rate at 100kHz. Using the PSK Demod VI in the same example directory, I observe the constellation and other measurements. No problems here. 1Mhz symbol rate....OK. Increase to 5Mhz...a little noisier, but OK. Higher than that (say 10MHz symbol rate) and the MER and EVM start going way up. Note that this is independent of the scheme (BPSK, QPSK, 8-PSK...whatever).
I noticed that if I then turn on equalization (on both the Tx and Rx sides of course), that the MER and EVM goes way down....especially at the high symbol rates.
So my question....I thought equalization was only necessary if the channel response changes over time (multi-path,etc.). Why then would equalization improve things when the symbol rate gets higher? Is it possible I'm seeing the frequency/phase offset of the upconverter and downconverter LO's? Or, maybe I'm just approaching the limit of the hardware and the equalization routines actually help clean up non-idealities of the hardware at those rates? For the channel I'm characterizing, I am actually interested in seeing the effect of potential multipath, so I'd rather not use the equalization routines at this time. Maybe I'm looking at having to make a tradeoff here?
Brandon

Hello Brandon,
The behavior you are seeing is expected. The equalization filter is used to correct the amplitude and phase of the signal so that after it passes though the 5610 you have a flat passband. There is a section of the RFSG help called IF Response and Software Equalization and it can be found under Devices >> NI 5671 Overview >> Advanced Topics >> IF Response and Software Equalization.
I copied the typical magnitude response of the 5610 upconverter with the equalization filter disabled (upper graph) and with it enabled (lower graph) from the manual. You can see it below. I hope this answers your question.
Regards,
Jesse O.
Applications Engineering
National Instruments
Message Edited by Jesse O on 07-19-2007 02:59 PM
Jesse O. | National Instruments R&D
Attachments:
equal.jpg ‏20 KB

XSLT Mapping Error while receiving Base64Binary content

Dear Experts,
I am new to SAP PI and working on PI 7.11. In our project we had a requirement to receive PDF file content in Base64 format from third party system by consuming the service provided by third party system with synchronous communication. The adapter we need to use is SOAP
The reason to use XSLT mapping is as our third party system used some tokens in both the request and response header, I used XSLT mapping to add the required details in request header after receiving the request from ECC system and skip the details in response to send the response to ECC system.
I have build two XSL files with XSLT mapping programs one for request and another for response using Oxygen XML editor tool. Both are checked, validated without any errors and also tested in ESB – Operation mapping which is successfully executed without errors.
The third party is sending the PDF content in Base64Binaryformat. I have also tested the WSDL from Oxygen to check the whether the service is working fine, which also successfully receiving the response from third party system.
The thing I do not understand and not able to figure out the problem is, when executing the service from ECC by sending a sample request, there is no response coming back and receiving an error saying
“TransformerException occurred during XSLT mapping Response_03 (URN:COM.XYZ_GET_ABSENCE_DETAILS, aa3a6491-e318-11e2-c1d7-c14948250cb4, -1)”
I have checked the Communication Channel which working fine. And also the message status in message monitoring wherein Request message has “Cancelled with errors” status and Response has “To Be Delivered” Status.
Could you please any of you help to figure out the issue and resolve the same.
Thank you in advance.....
Regards,
Govardhan Duvva.

The response am receiving is like below

<html><head><title>Apache Tomcat/6.0.18 - Error report</title><style>

</style> </head><body>
<h1>HTTP Status 415 - </h1>
<HR size="1" noshade="noshade"><p>
<b>type</b> Status report</p><p><b>message</b>
<u></u></p><p><b>description</b>
<u>The server refused this request because the request entity is in a format not supported
by the requested resource for the requested method ().</u>
</p><HR size="1" noshade="noshade"><h3>Apache Tomcat/6.0.18</h3></body></html>
And also in SXMB_MONI, there are two call adaptor nodes as in below picture, which means our request is going to the third party system ?

Soap Fault mapping issue

Hi,
I have a synchronous scenario of (request) Proxy --> XI --> SOAP and (response) SOAP --> XI --> Proxy. I am having an issue returning the application soap faults back to the sender system. When I enter invalid data while testing this webservice call with a soap client directly without XI I get a soap fault response:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   <soapenv:Body>
      <soapenv:Fault>
         <faultcode>soapenv:Server.generalException</faultcode>
         <faultstring>Login failed</faultstring>
         <detail>
            <LoginFault xmlns="NAMESPACE">
               <exceptionCode>710</exceptionCode>
               <exceptionMessage>Login failed</exceptionMessage>
            </LoginFault>
            <ns1:exceptionName xmlns:ns1="http://xml.apache.org/axis/">NAMESPACE</ns1:exceptionName>
         </detail>
      </soapenv:Fault>
   </soapenv:Body>
</soapenv:Envelope>
When testing this through XI, the response message after the Soap call is returning the following soap fault in XI payload:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<LoginFault xmlns="NAMESPACE">
<exceptionCode>710</exceptionCode>
<exceptionMessage>Login failed</exceptionMessage>
</LoginFault>
Notice just the detail body exists in the payload instead of the soap evelope and body, which I read is stripped off within XI in the case of application errors. I have setup a fault message mapping to tie the wsdl login fault with the standard fault message type and included this in the service interfaces and operations mapping. When the soap fault happens within XI I am getting the following mapping error:
NO_MAPPINGPROGRAM_FOUND: Mapping program is not available in runtime cache:
I am expecting the fault mapping to be executed in this case but doesn't seem to be found. Any ideas why this mapping error is occuring and not being directed to my fault message mapping? Is the mapping expecting the soap envelope and body to be included in the payload?
Any suggestions would be appreciated.
Thanks,
Nate

Here are the errors I am seeing within the sxmb_moni transaction:
Call adapter exception:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <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">NO_MAPPINGPROGRAM_FOUND</SAP:Code>
<SAP:P1>Object ID 35F8008AA0A830FC93FC221572A15ABD Software Component DC6FB8300EDE11DC8E05DB6DA3E77028</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Mapping program is not available in runtime cache: Object ID 35F8008AA0A830FC93FC221572A15ABD Software Component DC6FB8300EDE11DC8E05DB6DA3E77028</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Response Message Error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="UNKNOWN">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>application fault</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="NAMESPACE REMOVED">LoginFault</SAP:ApplicationFaultMessage>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
and response message payload:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <LoginFault xmlns="NAMESPACE REMOVED">
<exceptionCode>710</exceptionCode>
<exceptionMessage>Login failed</exceptionMessage>
</LoginFault>

SOAP scenario "Do not use SOAP Envelope" check problems

Hi Gurus!
I'm again here.
I've an scenario with SOAP Receiver, the WS do I need consume, looks like:
POST /SumTotalws1/services/Authentication.asmx HTTP/1.1
Host: xxx.xxx.xxx.xxx
Content-Type: text/xml; charset=utf-8
Content-Length: length
SOAPAction: "http://www.sumtotalsystems.com/sumtotal7/sumtotalws/Authentication/Login"
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
    <Login xmlns="http://www.sumtotalsystems.com/sumtotal7/sumtotalws/Authentication/">
      <credentials>
        <Username>string</Username>
        <Passcode>string</Passcode>
        <AuthenticationType>NotSpecified or Anonymous or NTAuthentication or Passport or LDAP</AuthenticationType>
        <AccountType>NotSpecified or WebService or WebUI</AccountType>
      </credentials>
    </Login>
</soap:Body>
</soap:Envelope>
but the response looks like:
HTTP/1.1 200 OK
Content-Type: text/xml; charset=utf-8
Content-Length: length
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Header>
    <UserToken xmlns="http://www.sumtotalsystems.com/sumtotal7/sumtotalws/">
      <Value>string</Value>
    </UserToken>
</soap:Header>
<soap:Body>
    <LoginResponse xmlns="http://www.sumtotalsystems.com/sumtotal7/sumtotalws/Authentication/" />
</soap:Body>
</soap:Envelope>
when I create my communication channel with "Do not Use SOAP Envelope" uncheck it, all run ok, but I only get in response message "<LoginResponse>" and I need <UserToken>
When I check it "Do not use SOAP Envelope" and I use XSLT mapping to add SOAP Env to request message, I get response message empty.
I tried the web Service with the message that I obtained from de XSLT mapping in the program SOAPUI. I get ok response with the <UserToken> value.
some idea to solve this problem??
Thanks in advance.
Edited by: KrlosRios on Sep 30, 2011 8:07 PM

Hi, thanks for your answer.
Can I use AXIS to execute any WS?
The WS that I tried execute looks like this:
POST /xxxx/services/Authentication.asmx HTTP/1.1
Host: xxx.240.106.39
Content-Type: text/xml; charset=utf-8
Content-Length: length
SOAPAction: "http://xxx/Authentication/Login"
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
    <Login xmlns="http://xxxxAuthentication/">
      <credentials>
        <Username>string</Username>
        <Passcode>string</Passcode>
        <AuthenticationType>NotSpecified or Anonymous or NTAuthentication or Passport or LDAP</AuthenticationType>
        <AccountType>NotSpecified or WebService or WebUI</AccountType>
      </credentials>
    </Login>
</soap:Body>
</soap:Envelope>
and for the response:
HTTP/1.1 200 OK
Content-Type: text/xml; charset=utf-8
Content-Length: length
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Header>
    <UserToken xmlns="http://www.sumtotalsystems.com/sumtotal7/sumtotalws/">
      <Value>string</Value>
    </UserToken>
</soap:Header>
<soap:Body>
    <LoginResponse xmlns="http://www.sumtotalsystems.com/sumtotal7/sumtotalws/Authentication/"></LoginResponse>
</soap:Body>
</soap:Envelope>
also I found in Trace node in SXI_MONITOR, jus before execute response mapping :
<Trace level="1" type="B" name="PLSRV_MAPPING_RESPONSE"></Trace>
<Trace level="1" type="Timestamp">2011-11-01T19:33:34Z UTC-6 Start of pipeline service processing PLSRVID= PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification... </Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS    = CL_MAPPING_XMS_PLSRV3</Trace>
<Trace level="3" type="T">P_IFNAME   = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD   = ENTER_PLSRV</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"></Trace>
<Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV"></Trace>
<Trace level="2" type="T">......attachment XI_Context not found </Trace>
<Trace level="3" type="T">Das Mapping wurde bereits in der Interface-Ermittlung bestimmt. </Trace>
<Trace level="3" type="T">Objekt-Id des Interface-Mappings 8594D8C2E6DA3C008F45B112FFCC86B8 </Trace>
<Trace level="3" type="T">Versions-Id des Interface-Mappings C3BB8FB0A1D511E0A688E9FCB9F06E16 </Trace>
<Trace level="1" type="T">Interface-Mapping http://xxxxx.net/pi/lms/Authentication OM_LMS_Authentication </Trace>
<Trace level="3" type="T">Mapping-Schritte 1 XSLT Response_LMS_Auth5 </Trace>
<Trace level="3" type="T">MTOM-Attachments werden nicht in die Payload überführt. </Trace>
<Trace level="1" type="T">Payload is empty. </Trace>
<Trace level="3" type="T">Dynamische Konfiguration ist leer. </Trace>
<Trace level="2" type="T">Modus 0 </Trace>
<Trace level="2" type="T">Call XSLT processor with stylsheet Response_LMS_Auth5.xsl. </Trace>
<Trace level="3" type="T">Method fatalError called, terminate transformation, because of
Thrown:
javax.xml.transform.TransformerException: java.io.IOException: Parsing an empty source. Root element expected!
     at com.sap.engine.lib.jaxp.TransformerImpl.transform(TransformerImpl.java:250)
Say Payload is empty.
and in left directory tree, not exist "payload" node, only existe SOAP Body and in "Manifest" node looks like this:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<SAP:Manifest wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<SAP:Payload xlink:href="cid:att-60c3078b066911e1bc1500000093b25a @sap.com">
<SAP:Name>MainAttachment</SAP:Name><
SAP:Description>Main document</SAP:Description>
<SAP:Type>Application</SAP:Type></SAP:Payload>
</SAP:Manifest>
Thanks for your help.

Error: java.lang.NullPointerException

Hi,
In my File - RFC - File scenario (PI 7.1), i am facing the error in the communication channel
File processing failed with java.lang.NullPointerException
But in SXMB_MONI it the status shows Processed Successfully.
From File to RFc it displays all the details like Sender Namespace, Sender Interface, Receiver component etc.
         RFC to File it doesn't display any details other than Message ID.
The following steps are executed in RFc to File message:
    Inbound Message ( CENTRAL )
   XML Validation Inbound Channel Response
   Request Message Mapping
   XML Validation Outbound Channel Response
these steps also contain the output file format in xml structure:
<?xml version="1.0" encoding="UTF-8" ?>
- <ns1:MT_LOTUSNOTES_UNIFORM_FILE_RESP xmlns:ns1="http://lotusnotes.uniform.com">
- <ITAB_OUT>
- <item>
<STR>20000000|3022|-10.25|09.11.2009|Testing 1111|</STR>
</item>
- <item>
<STR>20000000|3022|800.99|10.11.2009|Testing 22222|</STR>
</item>
- <item>
<STR>20000015|3022|200|09.11.2009|Testing 333333|</STR>
</item>
</ITAB_OUT>
</ns1:MT_LOTUSNOTES_UNIFORM_FILE_RESP>
pls let me know how to solve this error

Hi,
Please see the audit log
Audit Log for Message: 3c5fbcee-4b17-4afe-0ea5-a6064f47d377
Time Stamp Type Description
2009-12-08 07:18:21 Information Channel CC_LOTUSNOTES_UNIFORM_SND_FILE: Converted complete file content to XML format.
2009-12-08 07:18:21 Information Send text file "/home/ftp/home/ftpusr/test/in/20091109PYI_UNIFOR.txt", size 402, encoding ISO8859-1with QoS BE.
2009-12-08 07:18:21 Information MP: entering1
2009-12-08 07:18:21 Information MP: processing local module localejbs/AF_Modules/RequestResponseBean
2009-12-08 07:18:21 Information RRB: entering RequestResponseBean
2009-12-08 07:18:21 Information RRB: passing through ...
2009-12-08 07:18:21 Information RRB: leaving RequestResponseBean
2009-12-08 07:18:21 Information MP: processing local module localejbs/CallSapAdapter
2009-12-08 07:18:21 Information The application tries to send an XI message synchronously using connection File_http://sap.com/xi/XI/System.
2009-12-08 07:18:21 Information Trying to put the message into the call queue.
   Page 1 / 4 *
Audit Log for Message: 3c5fbcee-4b17-4afe-0ea5-a6064f47d377
Time Stamp Type Description
2009-12-08 07:18:21 Information Message successfully put into the queue.
2009-12-08 07:18:21 Information The message was successfully retrieved from the call queue.
2009-12-08 07:18:21 Information The message status was set to DLNG.
2009-12-08 07:18:22 Information The message was successfully received by the messaging system. Protocol: XI URL: http://sdnpi1.sap.spoolzgroupit:50800/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
2009-12-08 07:18:22 Information Using connection RFC_http://sap.com/xi/XI/System. Trying to put the message into the request queue.
2009-12-08 07:18:22 Information Message successfully put into the queue.
2009-12-08 07:18:22 Information The message was successfully retrieved from the request queue.
2009-12-08 07:18:22 Information The message status was set to DLNG.
2009-12-08 07:18:22 Information Delivering to channel: CC_LOTUSNOTES_UNIFORM_RCV_RFC
2009-12-08 07:18:22 Information MP: entering1
   Page 2 / 4 *
Audit Log for Message: 3c5fbcee-4b17-4afe-0ea5-a6064f47d377
Time Stamp Type Description
2009-12-08 07:18:22 Information MP: processing local module localejbs/RfcAFBean
2009-12-08 07:18:22 Information RfcAdapter received a synchronous message. Trying to send sRFC for Z_PI_LOTUSNOTES_UNIFORM.
2009-12-08 07:18:22 Information RfcAdapter received a synchronous message. Trying to send sRFC for J2EE_GUEST.
2009-12-08 07:18:22 Information MP: leaving
2009-12-08 07:18:22 Information The message was successfully delivered to the application using connection RFC_http://sap.com/xi/XI/System.
2009-12-08 07:18:22 Information The message status was set to DLVD.
2009-12-08 07:18:22 Information The application sent the message synchronously using connection File_http://sap.com/xi/XI/System. Returning to application.
2009-12-08 07:18:22 Information MP: processing local module localejbs/AF_Modules/ResponseOnewayBean
2009-12-08 07:18:22 Information The message was successfully transmitted to endpoint http://sdnpi1.sap.spoolzgroupit:50800/sap/xi/engine?type=entry using connection File_http://sap.com/xi/XI/System.
2009-12-08 07:18:22 Information The message status was set to DLVD.
   Page 3 / 4 *
Audit Log for Message: 3c5fbcee-4b17-4afe-0ea5-a6064f47d377
Time Stamp Type Description
2009-12-08 07:18:22 Information MP: leaving
*2009-12-08 07:18:22 Error File processing failed with java.lang.NullPointerException: *
   Page 4 / 4
Edited by: jjma1706 on Dec 8, 2009 9:05 AM

RFC to SOAP sync error

Hi All,
I am doing the RFC to SOAP sync scenario. request R3 data is coming to XI and its triggering to SOAP receiver.
Information SOAP: continuing to response message e9598290-a14f-11df-969a-00145e474044
Error SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault
i have tried to test the File to SOAP sync scenario to test the SOAP and its working fine. from file request to soap request and soap response to file response.
the same way i have done the RFC request to soap request and soap response to rfc response.
in sxmi_moni i can see the request from RFC but i did't find the request mapping to SOAP.
I have tested the test mapping and its working fine.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="UNKNOWN">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>application fault</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="http://www.webMethods.com/2001/10/soap/encoding">exception</SAP:ApplicationFaultMessage>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
the r3 request stacture is:
<filed1>
<filed2>
<filed3>
<ITEM>
<ITEM1>
<ITEM22>
</ITEM>
the soap request stacture is:
<filed1>
<filed2>
   <Header>
    <filed1>
    <filed2>
    <filed3>
   </header>
   <Item>
    <item1
    <item2>
    <item3>
   </Item>
</field2>
</field1>
is there any issue with mapping?
RFC sender CC error is Error in processing caused by: com.sap.aii.adapter.rfc.core.server.RfcServerException: got unexpected document type:DOC_TYPE_UNKNOWN
Can you pls let me know the some inputs to reslove this issue
Thanks,
Venkat

have tried to test the File to SOAP sync scenario to test the SOAP and its working fine. from file request to soap request
and soap response to file response. the same way i have done the RFC request to soap request and soap response to rfc
response.
FILE to SOAP Sync scenario....did you use RequestResponseBean and are you using the same to process RFC to SOAP Sync scenario? If yes, then you dont need the RequestResponseBean for RFC <--> SOAP.
in sxmi_moni i can see the request from RFC but i did't find the request mapping to SOAP. I have tested the test mapping
and its working fine. - - Application APPLICATION_ERROR application fault exception M the r3 request stacture is: the soap
request stacture is: is there any issue with mapping?
I hope you have included a mapping program for Request Mapping and also for Response Mapping in the Interface/ Operation Mapping and included the same in Interface Determination!
Regards,
Abhishek.

File-RFC Syncronous interface with out BPM

Hi experts,
i have a scenario syncrhonous: file to rfc and get back response rfc to other file. I have 3 communication channel: 1 sender file, 1 receiver file, 1 receiver RFC, sender aggrement, receiver aggrement, interface determination and receiver determination.
I also placed module parameters in the sender file CC as:
Processing sequence:
Module name Module type Module key
AF_Modules/RequestResponseBean Local Enterprise Bean 1
CallSapAdapter Local Enterprise Bean 2
AF_Modules/ResponseOnewayBean Local Enterprise Bean 3
Module configuration:
Modulekey parameter name parametervalue
1 passThrough true
3 receiverChannel <File receiver CC>
3 receiverService <Receiver service name>
File is processed and got response from RFC but I dont see any file in the required folder. I successful message in SXMB_MONI.
both FCCs in RWB is in green status.
Where would be the issue, any inputs.
Thanks
Rajeev.

HI All,
For response back from RFC to File in SXMB_MONI i see the successful message and the pipe line steps are as follows:
Inbound Message (Central)
XML Validation inbound channel respose
Request Message Mapping
XML Validation outbound channel response
Thats it.. I can see request and respose message successful but I dont see the file on the file server.
I created
Service Interface wtih request and respose message types
RFC is imported it contains request and respose
Created two Message mapping
created one Operation mapping with request and response
Created File sender Communicaton channel, receiver communication channel, RFC receiver Communication channel
Sender Communciation channel(Best effort) is updated with receiver communciaiton channel paramters
Receiver determination
sender aggrement
receiver aggrement
inerface determination
AM I missing some thing?
I can see the payload as required in response message of RFC but unable to see the file on the file server.
Any inputs are appreciated.
Thanks
Rajeev

Error capturing SOAP fault for Sync Messages

Hi
We have a Sync interface which makes a Proxy call from ECC to PI and then PI makes Soap Sync call to Web application. We are having issues when handling Exceptions. Sender is getting misleading errors in response, even though they are application errors the proxy sender is getting error like MappingObjectNotFound.
When debug the PI system, PI is truncating error info when it return the reponse.
Below is the scenario of Synchronous interface:
ECC(Proxy) -> PI(Soap Receiver Adapter) -> MasterDataApp-(Webserver)
Below is the actual response from Webserver (Extracted via TCPGW sniffer):
<?xml version="1.0" encoding="utf-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server.userException</faultcode>
<faultstring>*java.rmi.RemoteException: No Messages Found*</faultstring>
<detail>
<ns1:hostname xmlns:ns1="http://xml.apache.org/axis/">hostname.com</ns1:hostname>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
But PI receives this response payload like this :
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
<ns1:hostname xmlns:ns1="http://xml.apache.org/axis/">hostname.com</ns1:hostname>
and then Sync Request mesasge fails with below error because of the unexpected response payload as shown above:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">NO_MAPPINGPROGRAM_FOUND</SAP:Code>
<SAP:P1>Object ID B0CC6B27847A368AA04F4171EF6460F4 Software Component 86524CE0304911DEAE48CC6C83461631</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Mapping program is not available in runtime cache: Object ID B0CC6B27847A368AA04F4171EF6460F4 Software Component 86524CE0304911DEAE48CC6C83461631</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Also in the response message see this error message:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="UNKNOWN">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>application fault</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="http://xml.apache.org/axis/">hostname</SAP:ApplicationFaultMessage>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please let me for any clues how to handle this error response.
Thanks,
laxman

Hi Laxman,
SOAP Adapter cannot handle fault responses. I understand your issue. You even want to send the errorneous response from the Webservice as a payload back to the sender. But because of application error from Webservice, you are getting an error in the response message (Mapping Not found). SOAP Adapter cannot handle application error (i.e you will not get the errorneous response in form of payload) . For details please read below:
The receiver adapter expects a SOAP message as response. For synchrnous calls, a successful response should be returned with HTTP 200. In this case, the content of the SOAP body will be returned to the caller as the response payload. When some error occurs, the SOAP message may contain the SOAP fault element. In this case, when the fault detail element is not empty, its content will be returned as the fault payload in an application error message. For others, a system error message will be returned to the caller.
HTTP/1.1 200 OK
Content-Type: text/xml; charset="utf-8"
<SOAP:Envelope
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
<m:GetLastTradePriceResponse xmlns:m="Some-URI">
<Price>34.5</Price>
</m:GetLastTradePriceResponse>
</SOAP:Body>
</SOAP:Envelope>
will result in an application response message with response payload
<m:GetLastTradePriceResponse xmlns:m="Some-URI">
<Price>34.5</Price>
</m:GetLastTradePriceResponse>
HTTP/1.1 500 Internal Server Error
Content-Type: text/xml; charset="utf-8"
<SOAP:Envelope
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
<SOAP:Fault>
<faultcode>SOAP:MustUnderstand</faultcode>
<faultstring>SOAP Must Understand Error</faultstring>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
will result in a system error message.
HTTP/1.1 500 Internal Server Error
Content-Type: text/xml; charset="utf-8"
<SOAP:Envelope
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
<SOAP:Fault>
<faultcode>SOAP:Server</faultcode>
<faultstring>Server Error</faultstring>
<detail>
<e:myfaultdetails xmlns:e="Some-URI">
<message>My application didn't work</message>
<errorcode>1001</errorcode>
</e:myfaultdetails>
</detail>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
will result in an application error message with fault payload
<e:myfaultdetails xmlns:e="Some-URI">
<message>My application didn't work</message>
<errorcode>1001</errorcode>
</e:myfaultdetails>
In order to send the erroneous response as a payload to the sender, you should develop flow in below manner:
ECC(Proxy) -> PI --> ECC(Proxy)
In PI make a SOAP lookup. The response of the SOAP lookup will contain the response given by the WebService (it can be a vaid response or an application error in WebService). Now map this response to the proxy...In this way you can handle the application error msgs from webservice..
I hope this helps you...
Regards,
Rakesh Sharma

Synchronous SOAP: Get fault message on ABAP side

Hi,
I've a synchronous ABAP Proxy => PI 7.11 => SOAP scenario.
The SOAP receiver is a third party application using AXIS 1.4.
When I call the SOAP receiver with bad input via SOAP UI I receive an error message like that:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   <soapenv:Body>
      <soapenv:Fault>
         <faultcode>soapenv:Server.userException</faultcode>
         <faultstring>com.ZZZ.exception.ZZZException: Employee not found: 9999911111</faultstring>
         <detail>
            <com.ZZZ.exception.ZZZException xsi:type="ns1:ZZZException" xmlns:ns1="http://exception.ZZZ.com"/>
            <ns2:hostname xmlns:ns2="http://xml.apache.org/axis/">server.YYY.com</ns2:hostname>
         </detail>
      </soapenv:Fault>
   </soapenv:Body>
</soapenv:Envelope>
When I call the SOAP receiver through my ABAP proxy, I just get this exception message in SXI_MONI:
<?xml version="1.0" encoding="UTF-8"?>
<com.ZZZ.exception.ZZZException xmlns:ns1="http://exception.ZZZ.com"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns1:ZZZException"/>
Nevertheless I see the error in SXI_MONI:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
    <SAP:Category>Application</SAP:Category>
    <SAP:Code area="SOAP">FAULT</SAP:Code>
    <SAP:P1>http://schemas.xmlsoap.org/soap/envelope/</SAP:P1>
    <SAP:P2>Server.userException</SAP:P2>
    <SAP:P3/>
    <SAP:P4/>
    <SAP:AdditionalText>com.ZZZ.exception.ZZZException: Employee not found: 9999911111</SAP:AdditionalText>
    <SAP:ApplicationFaultMessage namespace="">com.ZZZ.exception.ZZZException</SAP:ApplicationFaultMessage>
    <SAP:Stack/>
    <SAP:Retry>M</SAP:Retry>
</SAP:Error>
In the WSDL of the SOAP receiver there's just the ZZZException without fields faultcode or faultstring:
<complexType name="ZZZException">
<sequence/>
</complexType>
Do I have to add the fields faultcode or faultstring to the WSDL myself?
I tried the following, but it didn't work:
<complexType name="ZZZException" abstract="true">
    <xsd:sequence>
        <xsd:element name="faultstring" type="soapenc:string">
    </xsd:sequence>
</complexType>
Thanks in advance!

Hi Eddie -
Do I have to add the fields faultcode or faultstring to the WSDL by myself?
>>> No. Even though you add - it doesn't work as it's the webservice which returns the message.
For sending the fault messages, Have a look at the below blog -
Handling Web Service SOAP Fault Responses in SAP NetWeaver XI

Newline problem with soap

I'm having these weird problems with newlines. I'm sending \n in a message because I have a multi lined message i want parsed. Axis is receiving the message and throwing exceptions. I printed out the line it's parsing and it's giving this error that it can't parse:
'2.5
PID'
The parser is not supposed to parse past the \n but it seems to be trying to. I've tested this without webservices and it works fine, adding webservices into the equation gives me these errors.

Additional info: The problem is the same in the entire environment here (PI DEV, QAS and PRD) and on another PI machine.
So I doubt very much if it's cache related.
Edit: This is the 'application error':
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="UNKNOWN">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>application fault</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="http://xml.apache.org/axis/">hostname</SAP:ApplicationFaultMessage>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Edited by: Frederik-Jan Roose on Dec 7, 2009 11:11 AM

NO_MAPPINGPROGRAM_FOUND & HTTP 500

Hi expert!
I have this landscape *r3 PROXY < -> PI 7.1 < - > WS* legacy, the issue is when the WS try to answer. In moni I show the pipeline complete. But with errors, I probe this landscape in two ways:
*1.- Not using envelope in cc soap the error in the answer is :*
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Error Interno del Servidor</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
*2.- Do not selecting any "conversion parameter" on CC:*
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <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">NO_MAPPINGPROGRAM_FOUND</SAP:Code>
<SAP:P1>Object ID 16EDD7F8F2113308861CB29AC2E92725 Software Component 5C91AF30B1D711DE883CD8090A060A2A</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Mapping program is not available in runtime cache: Object ID 16EDD7F8F2113308861CB29AC2E92725 Software Component 5C91AF30B1D711DE883CD8090A060A2A</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
+and on the response message id is: +
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="UNKNOWN">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>application fault</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="http://xml.apache.org/axis/">hostname</SAP:ApplicationFaultMessage>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Hi,
Is your interface is synchronous at receiver ( that is at SOAP) side?
If not, then in receiver URL you have to mention 'QualityOfService=ExactlyOnce'
Regards,
Supriya.

Channels response on SA520

Similar Messages

Maybe you are looking for