Soap receiver fault message/acknowledgements

hi all,
i have configured a scenario....
now i want to recieve an error status through soap reciver...and scenario would like...webservice client->XI->Webservice. Soap sender->XI->Soap Reciever......how can I recieve the exception...as raised during execution of webservice....
It would really very helpful if someone could throw some light on this..

Hi,
Is your scenario like this?
SENDER SOAP ADAPTER (Calling XI)<-> XI <--> RECEIVER SOAP ADAPTER (calling webservice)
Now if exception is raised during execution of receiver webservice, does the response from the webservice contains the status? If so, then do a response Map, so as to send the response message back to the webservice client.
Regards
Suraj

Similar Messages

IDoc to SOAP Receiver Fault Message Handling?

Hi,
I am working on IDoc to SOAP Scenario (IDoc -> PI -> SOAP). It is in async mode without BPM. This works fine as long as there is no error on the SOAP receiver side. How to handle the falut message raised by the SOAP receiver and send it back the SAP ECC.
Do I need to use ALEAUD IDoc for this? If Yes, how to configure this to handle fault message? Is there any other way of doing it?
Could you please give steps to handle the fault message?
Thank you.
Regards,
Cdr.

Have a look into the below threads -
How to capture SOAPFault in an Async/Sync Scenario without BPM
Acknowledgement Handling in IDoc to SOAP Scenario in PI 7.3

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

SOAP receiver adapter message: PI payload in parameter or body

Hi,
We tried to send messages via the following way to an external partner: SAP --> IDoc > XI (7.1)> HTTP(s) --> external partner.
We tried 2 techniques:
1. using a HTTP receiver communication channel with HTTP destination (using certificate).
As the path prefix in the destination, including parameters, exceeds 256 characters, we had to search for another solution
2. using the SOAP receiver communication channel with a target URL (https string) and indicator 'Do not use SOAP envelope' set
When sending the message, the body of the message, the IDoc XML payload doesn't seem to be read by the partner, probably related to the fact that they do not use the right software to do so, as decribed in forum:
SOAP receiver adapter error (SOAP receiver adapter error.)
Is this the right interpretation and is there no other solution than try to append the payload to the parameterlist ?
Regards,
Jan Macken

The partner found a way to read the body correctly

SOAP Receiver Response Message

I have setup the following scenario:
Create PO in EBP --> XI --> Webservice
In the Repository I have set up both the outbound and inbound message interfaces as Synchronous. The interface mapping has been setup to map both the request and response messages.
In the Directory I have set up the SOAP receiver adapter and the receiver/interface determination and receiver agreement for EBP as the sender system and the external webservice as the receiver party/service.
When I create a purchase order in EBP the webservice is called successfully and the PO gets created on the target system. The webservice returns a response message which I am expecting to see via SXMB_MONI but is not currently showing!! Is there some Directory configuration that I am missing?
Any pointers would be appreciated.
Regards
Mark Briggs

Hi Mark,
>>>>n the Repository I have set up both the outbound and inbound message interfaces as Synchronous
is your scenario sync or async?
do the ID config with ID wizzard if you're not sure
if will guide you
if you have a sync scenario you shoudl see and error
if you have no response withint the timeout
do you see that in the calling application or in the XI ?
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

SOAP to RFC using fault message

Hi All,
I get a request from Web-service by using the SOAP adapter and pass the same to the SAP ECC for geting the response. I do not need a message mapping as i am passing the same data to SAP ECC. I need to track the errors in fault messages.
Q1. Can i use the fault message handling without using the message mapping.
Q2. If web-service is down and i can't send the response back then do i need to using the fault messageing concept or is there any other way i can get the details back in XI.
If we can use the fault message without using message mapping concept, can someone help me out.
Thanks,
JGD

You are using SOAP sender and Proxy receiver synchronous
>>Q1. Can i use the fault message handling without using the message mapping.
Request mapping, Response mapping and fault message mapping - all these three constitutes message mapping.
>>Q2. If web-service is down and i can't send the response back then do i need to using the fault messageing concept or is there any other way i can get the details back in XI.
If the webservice is down , you dont get message, then you dont need fault message. Fault message is used only for business exceptions and more. If your ECC is down due to some exceptions or errors, you can trace those messages in proxy coding and pass it up to soap as fault message as response.
In this case, you dont need at all.

SOAP receiver message failure

Hi,
Scenario is an async message from SAP to a third party (SOAP receiver)
This message staus is delivered in adapter logs of RWB.
Also there is the payload (before mapping and after mappings till technical routing also) can be seen from sxmb_moni.
Thre problem is that the message data is not uploaded to that third party.
The communication channel is having correct URL (tried with WSDL home page and URL pointing to WSDL file/code like with '?WSDL' ) and SOAP action is also provided (also tried without SOAP action and got an error related to SOAP action).
These are the only 2 places (target URL & SOAP action) are maintained in communication channel. There is no any proxy/authentication required.
What cld be the reason of this ?
The TP web service is working fine with soapUI.
Regards,
Sachchidanand

Hi Kulwant,
Thanks for ur help.
In sxmb_moni, message status is successful.
As ur suggestion I just checked with soapUI message structure and found that..
1. soapUI tool message structure contains empty header <soapenv:Header/> and in the <soapenv:Body> all the wsdl fields/heirarchy is there.
2. In sxmb_moni payload (@ tech routing) there is no any header , it shows the structure like its in <soapenv:Body> of soapUI or its like message mapping heirarchy.
And there is no any custom authentication part visible in soapUI also.
Thanks,
Sachchidanand

Automizing error message with Fault Message Type

(Request F6) (Request F6)
System -
> XI -
> SAP (Doesn't have F6)
 <-- XI <--
 SAP (Doesn't have F6)
 (Respons: error) (Respons. error)
(Problem) When the request message doesn't content sufficient information that is required for respons then the XI team will get the message error and the responsibility to solve the problem. In this scenario it is the XI team that sends the error respons to the System.
(Request (eg. F6) ) (Request (eg. F6))
System -
> XI -
> SAP (Doesn't have F6)
 <-- XI <--
 SAP (Doesn't have F6)
 (Respons: error) (Respons. error)
(Solution) We want to automatize the process so that the error message goes directly to the System via XI. In other words we only want an acknowledgment of the error in XI, we don't want to solve the error since we believe that it is the sender System that is responsible.
We have seen that there is a Fault Message Type in the Message Interface and we are wondering if that is the way to do it? And it that case, how?

Hi,
Fault message is a error meesage. Its like an exception in simple terms. The fault message is used to
store a log for application error. Fault messages is defined in IR.
To give a overview on Fault messages it is mostly used in synchronous communication. When an error
occurs at the inbound side instead of sending the response message back it sends a fault message back
to the sender system to handle error.
Fault Message are Msg type that provided whenever u create a namespace..they are usually used to get
the exception or error mapped which has occured while execution of Application at the sender/receiver
end....
One scenario where i had used it from Soap to RFC where i defined the exception in rfc source code at
r/3 end...I mapped that exception to Fault msg type that i created of my own type(didnt used the
default)..
Fault messages are used to propogate / send back the error message to the calling application. This is
used when there is a failure and the sending system needs to know what the error was. This is more of
catching Application Errors
check this nice blog also
/people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
http://help.sap.com/saphelp_nw2004s/helpdata/en/5d/a45c3cff8ca92be10000000a114084/content.htm
Asynchronus RFC exception handling
XI Alerts are not getting triggered from proxy servers
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ee5bc490-0201-0010-e9b5-
a258cf083bca
/people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client
Fault Message
Regards
Seshagiri
Edited by: N V Seshagiri on Feb 29, 2008 12:19 PM

Concept of Fault Message .

Hi ,
I need to implement fault in scenarios. and about which i have no idea .. How to capture application as well as system fault . and on anytype of fault i have to raise mail though alert monitoring ....
So kindly help me in the same ..
Regards
PS

Hi,
You sent the message successfully but you don't get acknowledgement back so at that time server waits for some time to take the response/acknowledgement, if the time exceeds it sends fault message back to sender.
So if receive fault message then some thing fail/problem at receiver side.
http://help.sap.com/saphelp_nw04/helpdata/en/56/b46c3c8bb3d73ee10000000a114084/frameset.htm
For more info
Fault Message Types - A Demo (Part 1)
http://help.sap.com/saphelp_nw04/helpdata/EN/75/a55c3cff8ca92be10000000a114084/frameset.htm
Handling Web Service SOAP Fault Responses in SAP NetWeaver XI
Regards,
Venkata Ramesh

What is fault message type in mapping

hi folks,
what is the use of fault message type in message mapping . where do we use them .please spare a little time to type rather to refer to other blogs. have a nice day

Hi Bose
Fault messages are used to propogate / send back the error maessage to the calling application. This is used when there is a failue and the sending system needs to know what the error was. This is more of catching Application Errors.
Also please go through the link below to get the details for fault messages...
http://help.sap.com/saphelp_nw04/helpdata/en/5d/a45c3cff8ca92be10000000a114084/content.htm
fault message is a message that describes an application-specific error situation
we have standardised fault message in XI.
Fault message types are designed for application-specific errors that occur on the inbound side and that are reported back to the sender or persisted in monitoring.
In the synchronous case, when an application-specific error occurs on the inbound side, instead of sending a response message back to the sender, the application can send a fault message to handle the error.
The fault message of the application for an asynchronous ABAP server proxy is persisted for monitoring. In the case asynchronous of Java server proxies, the fault message is part of a negative application acknowledgement
Application-specific means that the application on the inbound side triggers the error itself because, for example, the request message did not contain sufficient information
See the below links
http://help.sap.com/saphelp_nw2004s/helpdata/en/5d/a45c3cff8ca92be10000000a114084/content.htm
Asynchronus RFC exception handling
XI Alerts are not getting triggered from proxy servers
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ee5bc490-0201-0010-e9b5-a258cf083bca
/people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client
Fault Message
/people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
You can use Fault messages when you want to handle errors at the Inbound side ie at the destination side.
check this nice blog also
/people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
Fault Messages
http://help.sap.com/saphelp_nw04/helpdata/en/5d/a45c3cff8ca92be10000000a114084/frameset.htm
Usage of Fault Messages in Synchronous interfaces
/people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client
usage of fault messages in asynchronous interfaces
/people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
Have a look at "/people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client"
for more details have a look on these links

Fault messages - /people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
Also ref:
Handling Web Service SOAP Fault Responses in SAP NetWeaver XI -
/people/jin.shin/blog/2007/05/21/handling-web-service-soap-fault-responses-in-sap-netweaver-xi
check this out
http://help.sap.com/saphelp_nw04/helpdata/en/5d/a45c3cff8ca92be10000000a114084/content.htm
demo - /people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
/people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1 - this is sure to help you.
Thanks!!!
Regards
Abhishek Agrahari

About Fault messages?

Hi experts,
i have a senario where i have to create fault message,What is the use off fault message........To create the fault message sholud i create complete source structrue in data type of fault messsage.....can any one please send doc's and information on Fault message.
thanks & regards,
Phnani

Hi Phani,
Fault message is a error meesage. Its like an exception in simple terms. The fault message is used to store a log for application error. Fault messages is defined in IR.
To give a overview on Fault messages it is mostly used in synchronous communication. When an error occurs at the inbound side instead of sending the response message back it sends a fault message back to the sender system to handle error.
Fault Message are Msg type that provided whenever u create a namespace..they are usually used to get the exception or error mapped which has occured while execution of Application at the sender/receiver end....
One scenario where i had used it from Soap to RFC where i defined the exception in rfc source code at r/3 end...I mapped that exception to Fault msg type that i created of my own type(didnt used the default)..
Fault messages are used to propogate / send back the error message to the calling application. This is used when there is a failure and the sending system needs to know what the error was. This is more of catching Application Errors.
Also please go through the link below to get the details for fault messages...
http://help.sap.com/saphelp_nw04/helpdata/en/5d/a45c3cff8ca92be10000000a114084/content.htm
check this nice blog also
/people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
http://help.sap.com/saphelp_nw2004s/helpdata/en/5d/a45c3cff8ca92be10000000a114084/content.htm
Asynchronus RFC exception handling
XI Alerts are not getting triggered from proxy servers
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ee5bc490-0201-0010-e9b5-a258cf083bca
/people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client
Fault Message
Cheers...
Vasu
** REward POints if found useful **

Fault Message concept needed

Hi
I'm doing one file to Proxy scenario.. if the source file contain some mandatory fields then only my file should be processed.. otherwise i need to raise an exception.. for this.. how fault messages concepts can we apply.. because i does't know any thing abt falut messages.. how can we use.. and where can we define and where can we add these ..
plz give me the clear idea abt this..with basic steps
thanks
babu

Fault messages generally used for used for synchronous interfaces assume when a proxy is generated from a message interface an exception class is generated for a fault message type. You use this exception class to handle application errors at runtime.
The fault message of the application for an asynchronous ABAP server proxy is persisted for monitoring. In the case asynchronous of Java server proxies, the fault message is part of a negative application acknowledgement (see Acknowledgments).
Application-specific means that the application on the inbound side triggers the error itself because, for example, the request message did not contain sufficient information.
http://help.sap.com/saphelp_erp2005vp/helpdata/en/dd/b7623c6369f454e10000000a114084/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/5d/a45c3cff8ca92be10000000a114084/frameset.htm
Please see the below links
Asynchronus RFC exception handling
XI Alerts are not getting triggered from proxy servers
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ee5bc490-0201-0010-e9b5-a258cf083bca
/people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client
Fault Message
/people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1

Fault message handling in BPM

Hi again xi fighters
I created a business process with a synchronous sending step. I defined all interfaces and implemented also an own fault message type within the synchronous abstract interface. If the used RFC got the correct data the sync. sending step worked proper and also the business process worked fine. If I providing wrong data to the RFC to force him to throw an exception the Business process received the fault message. Then I just want to send the received fault message asynchronously to a file adapter within the defined exception branch. And now the question no-one answered in several discussion threads ;-<
How can I send the message? I am not able to implement a new variable in the container for the fault message type. Any advises here?????
Please help me, before I got inshane of SAP ;->>
Regards Oliver
Message was edited by: Oliver Bluhm
Hi everybody
any ideas, or is the question not clear. Please have a look and let me know you exlperience!
Regards Oliver

Hi Oliver,
how do you know, that is impossible to read the content of the fault message in the exception branch? Did someone from SAP say that? For days I read all the notes, blogs, help,.. and didn't find an answer.
It should work.
1. I have an integration process in XI sending a sync message to R3.
- OK
2. In the generated proxy class I raise an exception of the generated exception proxy class.
- OK
3. The exception message is shown in the message monitoring, containing also all our customer-data.
- OK
4. The integration process in XI activates the correct exception branch.
- OK
Missing: How do I get a grip on the data in the error message?
Kind regards Philipp
Message was edited by:
 Philipp Jakob

Catching Fault Messages when using a webservice

Hi all.
We are using a webservice that looks like this.
nonSAP-system <-> XI <-> SAP
A nonSAP-system asks for some information from a SAP-system. When we get an error of some kind we want to return the errormessage to the nonSAP-system so they will know what went wrong.
For first we want to try to return the errormessage generated in XI or the SAP-system and when we get that to work we want to be able to generate our own faultmessages so we specific what went wrong in the in the call.
We have looked around in the help pages and not getting a good picture on how to do this. Is there anybody who could help me out?
BR
Kalle

Hi,
Check these
/people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
http://help.sap.com/saphelp_nw04/helpdata/en/5d/a45c3cff8ca92be10000000a114084/frameset.htm
i have documented a fault message scenario through my blog;
/people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
Handling Web Service SOAP Fault Responses in SAP NetWeaver XI -
/people/jin.shin/blog/2007/05/21/handling-web-service-soap-fault-responses-in-sap-netweaver-xi
http://help.sap.com/saphelp_nw04/helpdata/en/5d/a45c3cff8ca92be10000000a114084/content.htm
check this nice blog also
/people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
http://help.sap.com/saphelp_nw2004s/helpdata/en/5d/a45c3cff8ca92be10000000a114084/content.htm
Asynchronus RFC exception handling
XI Alerts are not getting triggered from proxy servers
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ee5bc490-0201-0010-e9b5-
a258cf083bca
/people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client
Fault Message
Regards
Seshagiri

BPM: System_Error" SOAP fault message received

Hi,
We upgraded SAP system from 4.7 to ERP2004 on 09/17/05.
We have XI-3.0 version from last 9 months and this BPM was working good so far. We have not changed anything in it except we upgraded the SAP system.
We are using ABAP proxy from SAP to send "userid"
message to XI-BPM and then it would make a Synchonous call to SAP system to get roles of those "usrid".
In the first step when it is sending data to XI an exception is raised and in the second step when it tries to make synchronous call to SAP we are getting error:
<Trace level="3" type="T">Deserializing message object...</Trace>
<Trace level="3" type="System_Error">SOAP fault message received</Trac
<Trace level="3" type="System_Error">SOAP fault code: Client</Trace>
<Trace level="3" type="System_Error">SOAP fault string: Error during c
I noticed that the XML name tag looks different now
Before upgrade when message was successful.
<?xml version="1.0" encoding="utf-8" ?>
- <ns1:MT_ECA_USRID xmlns:ns1="http://bcm.edu/common"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<USRID>CLARKSON</USRID>
<USRID>2_MA140016</USRID>
</ns1:MT_ECA_USRID>
After upgrade when message is failed
<?xml version="1.0" encoding="utf-8" ?>
- <nr1:MT_ECA_USRID xmlns:nr1="http://bcm.edu/common">
<USRID>AABULIMI</USRID>
<USRID>AB147899</USRID>
<USRID>ACHALL</USRID>
</nr1:MT_ECA_USRID>
You would notice that
" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
missing after upgrade.
I would appreciate if anyone could help me.
Mrudula

Hi,
Can you paste the full error message. Also take a look at the default trace log in Visual Admin. Set the logging for soap to debug.
Naveen

Soap receiver fault message/acknowledgements

Similar Messages

Maybe you are looking for