SOAP Fault Problem for WAS 6.20 System

Hi,
We are exposing some RFC enabled ABAP function modules as web services in a WAS 6.20 system.
We are trying to have all consumers of our web services use the SOAP faults to handle errors.
It works great when we raise exceptions from the function module.
However, we are having an issue when an ABAP dump occurs. It sets the SOAP fault properly,
but the XML return has extra data at the end that is causing our .NET developers problems when
trying to handle the SOAP fault.
Here is the Original(raw) XML:
<?xml version="1.0"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/">
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode> SOAP-ENV:Client </faultcode>
<faultstring> Internal Server Error </faultstring>
<detail>
<rfc:Error xmlns:rfc="urn:sap-com:document:sap:soap:functions">
<type> RABAX_STATE </type>
<message> Divide by 0 (type 1). </message>
</rfc:Error>
</detail>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
sword" value="" size="8"/>
</td>
<tr>
<td> Language:</td>
<td>
<selectname="sap-language" class="pulldown">
<optionvalue="EN"> English</option>
<option value="DE">Deutsch</option>
</select>
</table>
<input type="submit"value="Anmeldung">
</form>
</body>
</html>
The HTML data at the end is causing the problems for our .NET guys.
We have a 6.40 system in development for roll out sometime next year and we don't have this
problem on that system. However, since we are exposing web services on our 6.20 system, we'd
like to get our standards in place now, so that our consumers won't have to change after
the upgrade.
Any information on how to turn off this extra data on a 6.20 system would be appreciated.
Thanks,
Jeff

Hi Andreas,
SOAP 1.2 is not supported, neither in WebAS 6.20 nor in 6.40 as far as I know support is not planed even for next magor release...
The only what I can propose you is to create an OSS and check what shall SAP answer you,
or to downport your applicaiton.
Regards, Angel

Similar Messages

A sample web service to return SOAP fault message for application error

Hi,
I need to test behavior of XI, in case of application error (using <detail> tag in soap:fault) from web service in nosoap mode.
If any one is aware of a free web service, which can raise application soap fault message, Kindly provide the details.
Thanks in Advance,
Rahul..

Hi,
What is the URL to which you are posting the SOAP message?
Is it?
http://<host>:<j2ee-port>/XISOAPAdapter/MessageServlet? channel=<party>:<service>:<channel>
If yes, then like mentioned the QOS is picked from the Sender SOAP adapter.
But, if the URL is ,
http://<server>:<ABAP-port>/sap/xi/engine?type=entry&version=3.0&Sender.Service=<YourService>&Interface=<YourNamespace>%5E<YourInterface>
Then you need to give the QOS as <b>,&QualityOfService=ExactlyOnce</b> appended to the above URL.
More, /people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine
Regards
Bhavesh

SOAP fault propagation for Direct Binding

Hello.We have following set-up
Composite A --- OSB -- Composite B
Composite A exposes HTTP interface (one-way operation) and refers to one-way operation of OSB (over direct binding) which again calls one-way operation of Composite B (again over soa-direct)
Error in composite B is propagated properly to the OSB. I've tested same also with HTTP proxy on OSB, HTTP 500 returned in case of error in Composite B
But Composiet A never raises error to the HTTP service. Thus Consumer is getting HTTP 200, regardless downstream error

try with a non blocking invoke. That will cause a new invoke message to be generated, and a commit of the currently active transaction. So, while the new invoking transaction will be rolled back, a catchable fault will be thrown, and the running tx will commit.
However, if you are not intending to use a transactional system integration, you could go the soap route as well.
your call, my 2cents.

Corrupted regsutry recovery problems for Windows XP on system restore

Hi. Had a spyware (Trojan) killed by the virus cleaner but upon restart it gave me a famous lsass.exe error about an application, which could not be terminated. Went on and read http://support.microsoft.com/kb/307545 but when tried to start recovery from Windows XP CD-ROM, the command "copy c:\windows\repair\system c:\windows\system32\config\system" did not work. Eventually was able to load the system from the CD-ROM but then could not pass part 2 (safe mode after rebooting) as the administrator password has been changed. I have run NT Password and Registry Bootdisk from USB to remove the administrator password but when tried go back to recovery console from Windows XP CD-ROM, the computer powers off right before I select "R"-option to start the recovery console. When I do not use the CD-ROM and try to power on in a safe mode, it gives BSOD. How do I get to corrupted registry if I cant get to recovery console and system restore?
Any help is appreciated. I have run a system diagnostics and start-up test has passed but on hard disk test I get to 10% of comprehensive only and then it seems to take indefinite.
This question was solved.
View Solution.

How to do a Manual SYSTEM RESTORE in XP, this should fix the missing or corrupt config file.
A. Connect your non-bootable hard drive to another computer, as a secondary drive or use a usb adapter or enclosure, If you can see your data on the drive, back it up Now, then follow the rest of these instructions.
B. Open Windows Explorer. Click on Tools|Folder Options|View. Check the box beside "Show hidden files and folders". Apply your change.
NOTE
D: may not represent the hard drive you connected to your PC, it may be E: or F: or G:, it all depends on how many other drives (including cd/dvd) you have in your host PC, So substitute the appropriate drive letter in the instructions below.
C. Navigate to the D:\System Volume Information folder. You will see a folder named something like _restore{.........} the dots represent an alpha-numeric sequence.
In this folder you will see folders named RP0....RPnn. Find the one with the highest number.
These are your System Restore points. In the highest numbered folder you will see a folder named snapshot. In this folder are registry hive files which you need to recover your system:
_registry_user_.default
_registry_machine_security
_registry_machine_software
_registry_machine_system
_registry_machine_sam
D. Create a subdirectory; i.e, D:\Windows\TMP. Copy these files to the TMP subdirectory. Rename them to:
default
security
software
system
sam
Note Be sure to lose the period (.) in the file named _registry_user_.default
E. Delete the files in the D:\windows\system32\config subdirectory with the same short names.
F. Copy the D:\windows\tmp files to the D:\windows\system32\config. subdirectory.
G.Put your drive back in its original system. Your system should start normally. If you get the same error repeat the procedure and choose another folder ( RPnn) (next highest number).
You can repeat this procedure choosing lower RPnn numbers until you get it booting again.
If you are denied access to any folders you will have to take "Ownership" of the folders first. http://support.microsoft.com/kb/308421
If this procedure fails to work you need to repair or reinstall Windows.

'BAPI_INCOMINGINVOICE_PARK' - problems for Jurisdiction code based systems.

Hi Guys,
I am trying to park a po invoice using the bapi 'BAPI_INCOMINGINVOICE_PARK'. The TAXDATA table provided in the bapi doesn't work properly when I work with the US based company codes that require Tax Jurisdiction codes in the ITEMDATA table.
I am able to park the invoice properly. But, when I see the invoice through the MIR4, only 1 tax line retains the tax amount.
Any help would be appreciated.
Thanks,
Hardik Shah.

Hi,
Please check tax lines in table RBTX for that parked invoice. Also check if note 1296374 "MIR4: tax amount displayed incorr. as 0 for second tax code" is applicable and helpful to you.
Kind Regards,
Suneet

Handling of SOAP Faults in SOAP Clients consuming PI Web services

Hi there,
the following is in regards to SOAP fault error handling in a SOAP client that consumes a Web Service published by PI.
I have been reading a number of threads and blogs in regards to this topic and I am still left with some open questions which I hope to get some final answersclarifications through this thread.
In particular the blogs
Handling Web Service SOAP Fault Responses in SAP NetWeaver XI      - Handling Web Service SOAP Fault Responses in SAP NetWeaver XI
XI: Propagation of meaningful error information to SOAP Client     - XI: Propagation of meaningful error information to SOAP Client
have caused by attention.
Both of these threads are realating to the Fault Message type one can use to return errors back to a SOAP Client (.Net, Java, etc.).
In our scenario we published a number of Web Services through PI that provide functionality to integrate with an R3 back-end system using inbound ABAP Proxies.
The services are standardised and will be consumed by a number of .NetJava applications and systems. The reason for the use of ABAP proxies is the customer specific application logic that is executed in the backend system. The Web services are synchronous and don't use ccBPM in the middle. Transformations are performed in PI combined with various lookups to set default values before the message is passed into the ABAP Framework of the R3 back-end system. The lookups are done against the R3 back-end system using the PI RFC Lookup feature.
The inbound proxies currently return application errors as part of the response message back to the SOAP client. For more critical errors we introduced the use of Fault message types as the method to return the information back to the SOAP Client. This is all working satisfactory.
The questions I have are as follows.
1. When an error occurs at the IE level (e.g. mapping error), ABAP Proxy framework level (e.g. conversion from XML to ABAP format) or Adapter Framework level (Adapter releated error) a different SOAP fault message structure is returned to the SOAP Client than the one    used for the application errors. The SOAP fault message structure used in this case is the standard SOAP fault used by PI to return system errors back to the caller. For those SOAP fault messages there is no payload generated that could be mapped to the SOAP fault structure used for the application errors. This would be preferrable as there would be only one Fault message structure used for both inbound ABAP proxy generated fault messages and PI generated fault messages.
Also the error messages generated by PI can be quite cryptic and difficult to interpret at the client end and could be filtered     ranslated during message mapping if the payload of the PI generated SOAP fault message could be accessed in a message mapping.
Point 3 of the above thread 2759 indicates that this would be possible but doesn't outline how. Could somebody please clarify this for me as I don't believe that this is really possible ???.
My idea instead was to use the PI SOAP fault message structure to also return application errors. Therefore I would create a Fault message type that matches the PI SOAP fault structure. This would enable the SOAP Client to handle only one SOAP Fault error structure. Would that be something to look into instead ?????.
2. We have been looking at using the integrated WEB AS SOAP adapter instead of using the AF Sender SOAP adapter. While playing with this we encountered differences in the content returned through the SOAP fault generated by PI. A sample is below. Shouldn't the content of these SOAP faults be the same if the error that caused it is the same. Also the SOAP fault returned by the IE SOAP adapter is much more    useful in this particular case. Both errors below are the same, a conversion error from XML to ABAP took place in the inbound ABAP proxy framework of the back-end system.
SOAP fault returned when using SOAP Sender adapter of AF
<!see the documentation>
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
   <SOAP:Body>
      <SOAP:Fault>
         <faultcode>SOAP:Server</faultcode>
         <faultstring>Server Error</faultstring>
         <detail>
            <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
               <context>XIAdapter</context>
               <code>ADAPTER.JAVA_EXCEPTION</code>
               <text>com.sap.aii.af.ra.ms.api.DeliveryException: XIProxy:PARSE_APPLICATION_DATA:
     at com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:455)
     at com.sap.aii.af.ra.ms.impl.core.queue.consumer.CallConsumer.onMessage(CallConsumer.java:134)
     at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:916)
     at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)</text>
            </s:SystemError>
         </detail>
      </SOAP:Fault>
   </SOAP:Body>
</SOAP:Envelope>
SOAP fault using integrated SOAP adapter of PI IE
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
   <SOAP:Body>
      <SOAP:Fault>
         <faultcode>SOAP:Server</faultcode>
         <faultstring>System Error</faultstring>
         <detail>
            <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
               <context/>
               <code>ABAP.PARSE_APPLICATION_DATA</code>
               <text>Error during XML => ABAP conversion (Request Message; error ID: CX_ST_DESERIALIZATION_ERROR; (/1SAI/TXSBE20FF604BAFEF8D990A XML Bytepos.: 564 XML Path: ns1:CreatePORequest(1)POHEADER(2)COMP_CODE(1) Error Text: Data loss occurred when converting ############################## Kernel ErrorId: CONVT_DATA_LOSS))</text>
            </s:SystemError>
         </detail>
      </SOAP:Fault>
   </SOAP:Body>
</SOAP:Envelope>
I have been reading threads for hours without being able to find one that answers questions 1 or provides a blog that outlines the approach one should take for error handling in SOAP clients that consume PI Web Services (and covers both PISystem generated faults and faults raised in Proxies).
There may already be a blog or thread and I just missed it.
Any comments are welcome.
Thanks. Dieter

Hi Dieter,
As Bhavesh already mentioned fault messages are used for application errors. The same is described in SAP XI help:
http://help.sap.com/saphelp_nw04/helpdata/en/dd/b7623c6369f454e10000000a114084/frameset.htm
In case of system error (e.g. field length too long in proxy call or error in XI/PI mapping) there seems to be no standard way of handling it and propagating the response to the consumer of webservice.
Each system error is not recognized by SOAP adapter and SOAP adapter exception is raised.
The only bizzare solution that I can see is developing an adapter module and transport wrong message to standard fault message before delivering it to adapter engine:
http://help.sap.com/saphelp_nw04/helpdata/en/a4/f13341771b4c0de10000000a1550b0/frameset.htm
Kind regards,
Wojciech
btw nice thread

SMD agent for VMW-based SAP systems

SAP talents:
We have hard time to configure SMD agents for VMW-based SAP systems.
We have followed some SAP documents for non-VMW-based SAP systems, but seems that SMD agent cannot
differentiate the individual system on VMW.
Our SMD agent has no problem for non-VMW-based systems.
Thanks!

Sorry to reply late because we have attempted a lot of fixes but all failed
For example, we have QAX, QAY and QAZ on VMW.
On Wily Introscope:
1) QAZ simply does not show up even we deployed/configured the agents as the procedure specified;
2) under the node QAX, we see QAY's entry as a sub-entry.
Does each SAP system need an agent OR only one agent is enough? We have tried both ways but
seems not working properly either way.
Please help, thanks a lot!

SOAP Fault for Application errors

Hi,
I would like to know whether it is OK to raise a SOAP fault for Application or system level exceptions. For example, I'm searching for a user with an ID as request , If the ID is invalid(User is not found) is it OK to raise the SOAP Fault.
Let me know your views regarding the same.

Hi,
With the above explination , please see the below links..
http://help.sap.com/saphelp_nw04/helpdata/en/d0/d4b54020c6792ae10000000a155106/content.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/7521a237-0701-0010-499b-b3285b789c0d
/people/thomas.jung3/blog/2005/01/11/publishing-abap-webservices-to-an-external-uddi-server
/people/sap.user72/blog/2005/11/17/xi-how-to-publish-wsdl-generated-from-xi-to-uddi
Alert rule for SOAP adapter
Monitoring problem in async SOAP receiver adapter
Trapping AF errors using Alert framework in XI 3.0 SP13
Alert Configuration
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2f2a9fa2-0a01-0010-32ac-d281db722b86
SOAP Lookup - /people/bhavesh.kantilal/blog/2006/11/20/webservice-calls-from-a-user-defined-function
Regards
Chilla..
<i>Points rewarded if it is useful..</i>

Error:SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to read request. --- There is an error in XML document (1, 447). --- Input string was not in a correct format.

Hi All,
We have a scenario of FTP-->PI---> Webservice. While triggering the data in the FTP, it is failing in the PI with the below error
SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to read request. ---> There is an error in XML document (1, 447). ---> Input string was not in a correct format.
Can you please help?

Hi Raja- It seems to be a data quality issue.
Check for the value @ 1447 position in the xml message that you are trying to send to web service..
may be a date filed/decimal value which is not in expected format.

Error "soap fault: No operation available for request" in proxy to soap Scenario

Hi Experts,
Unable to trace the below error when pushing the message from RWB while testing the PROXY to SOAP interface
Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: No operation available for request {http://schemas.xmlsoap.org/soap/envelope/}Envelope.
Thank you very much if any one provided the solution
Regards,
Yugandhar

Hi Yugandhar,
Check the below thread,
Connecting from SAP PI To Salesforce
Regards
RK N.

Synchronous RFC -- SOAP Scenario: problem with SOAP Response/Fault Mapping

Hi,
I've a synchronous RFC --> PI --> SOAP Scenario. The problem is that the message structure of the sending RFC doesn't match the Webservice Structure.
The (SAP standard) RFC has just a Request / Response message structure. Part of the Response Message structure is a exception structure.
The Webservice has a Request / Response message structure and in case of an error I get a SOAP:Fault.
Problem now is that I cannot configure that scenario without usage of BPM as I will have to map SOAP:Response or SOAP:Fault to the RFC Response structure.
Has anybody another idea to do that synchronous scenario (with usage of message mapping) without BPM?
BR
Holger

1)
you maus define 3 mapping.
1)request
2)response
3)Fault
in Interface mapping define at response boths (2-3) mapping. its clear??
2)
otherwise sometjhing is not clear, why do you want fault?? why dont you get only response message. we implement this kind of response:
<response_MT>
<ID> (error ID)
<system> (target system)
<error> (Error Description)
</response>
by this way fault message is not needed. but if you must have it just follow the top of message else, propose second.
Thanks
Rodrigo
Thanks
Rodrigo
Edited by: Rodrigo Pertierra on Feb 25, 2008 11:52 AM

Problem with SOAP FAULT messages

Hi,
I'm developing the flash interface for a .NET application.
The client side (flash) communicate with server side (.NET) by web
services. The problem is that when the server side send a Fault
message flash breaks telling "Unable to connect to
endpoint........". In this case I need to know the error message
send by the server but the fault.faultstring is undefined.
Here the server Fault message:
HTTP/1.1 500 Internal Server Error.
Date: Wed, 23 Aug 2006 09:07:10 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 1.1.4322
Cache-Control: private
Content-Type: text/xml; charset=utf-8
Content-Length: 419
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="
http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="
http://www.w3.org/2001/XMLSchema">
<soap:Body>
<soap:Fault>
<faultcode>SoapHeader</faultcode>
<faultstring>The userid: xxxx is
invalid</faultstring>
<detail />
</soap:Fault>
</soap:Body>
</soap:Envelope>
And this the code that handle the fault case:
pendingcall.onFault = function (fault:Object){
rootObj.gbl_logger.log("WS Fault: "+ fault.faultstring ,
10);
As you can see the real faultstring is "The userid: xxxx is
invalid" but in the faultstring property of the fault object I
found "undefined".
I've read many posts that report that the problem can be
solved in the server side modifing the HTTP HEADER from 500 to 200.
Unfortunately I can't access the server side code. Exists a way to
resolve the problem in the client side? Seems it is a Flash bug as
the SOAP 1.1 specs tells that all SOAP Fault messages must carry a
HTTP 500 header. Exists some patch that solve the problem?
Thanks.

Hi ,
Thanks for joining the Community.
Please get in touch so we can resolve this issue for you.
Click here for contact details.
Thanks
James

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

Receiver SOAP Adapter Problem-soap fault: Server did not recognize the valu

I have a scenario for service orders using async call : IDOC-XI-SOAP.
I used the XML Spy tool to test the Service order's web services and it works fine. I imported the same WSDL file in XI. When I send a SOAP message from XI, I get a following error in the adapter engine.
<i>MP: exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server did not recognize the value of HTTP Header SOAPAction: AddUpdateCostObjectLevel1.</i>
Can someone please help me...
Thanks in advance!
Mrudula

This problem is resolved by me by passing the "http://company's URL/AddUpdateCostObjectLevel1" in the SOAP action.
Thanks to all for your input.
Mrudula

OSB: Attach SOAP Header for SOAP Fault

Hi,
Is there a way to return OSB SOAP Fault with custom SOAP Header?
Currently, when SOAP Fault happens, SOAP Header is not returned. I would like to insert some elements in the SOAP header and return when SOAP Fault happens.
Thanks.

Hi Eric,
Thanks for your tips. It was helpful!
I've managed to insert custom SOAP header to a SOAP fault.
In service error handler,
1. Construct custom header and replace header variable content
2. Replace body content with fault variable
3. Reply with failure
Thanks.

SOAP Fault Problem for WAS 6.20 System

Similar Messages

Maybe you are looking for