Fault Message in Asynchronous

Dear Friends,
In Message interface there is a option to select synchronous or asynchronous. If we select synchronous the fault message appearing and if select assynchronous the fault message disappearing, then in this case how can we do fault handling.
Thanks
Prem

hi
A fault message is a message that describes an application-specific error situation.
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 (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_nw04/helpdata/en/dd/b7623c6369f454e10000000a114084/content.htm

Similar Messages

Fault message in asynchronous ABAP Proxy

Hi,
I have a question about fault messages in asynchronous ABAP proxy server.
The configured scenario is SOAP XI ABAP Proxy. Between XI and the ABAP Proxy I have configured an inbound asynchronous interface with a fault message, and then I have generated all the classes and implemented some code for exception handling in the ABAP Proxy side successfully.
When I tested negative cases, the exception raises and it is visible in the SXMB_MONI transaction in the R/3 side, but this exception is not displayed in the SXMB_MONI of XI it just displays a successful delivery to the ABAP Proxy message.
According the XI documentation it says <i>In the asynchronous case, you can see a fault message in the monitoring of the Exchange Infrastructure.</i> But this is not working.
Am I missing something?

Hi,
This parameters are form group RUNTIME.
Please check it:
http://help.sap.com/saphelp_nw04/helpdata/en/d6/49543b1e49bc1fe10000000a114084/content.htm
Regards,
Wojciech

Fault message in Asynchronous messages - SXMB_MONI in PI problem

Hello,
I am working on File to Proxy asynchrnous interfaces. I am using fault message type on inbound message interfaces.
I have done all the configuration according to below link
/people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
After raising the exception, I can see messages are being failed in ECC , but in PI moni, message status is successfully status.
I want PI message status "Application Error".
Any idea.
Thanks in advance.

Just letting you know fault message is not something message could not be processed or due to system error mesg failed or so.
Using fault message to show business errors for the application. Example if the request message does not have purchase order number, then fault mesg could be "Purchase order is missing". In this case, Pi will respond with fault message. But this is successful processing end to end.
Basically you get response from ECC as fault message not wrong in it. SO PI will show only success log.
Dont confuse messages failing due to system downtime or network issues or firewall issue with application or business logic errors. Hope that helps.

Fault Messages in SAP XI 3.0

Hi all,
I have implemented few basic scenarios in XI
I have a doubts as follows..
What are the fault messages (while defining Interfaces in Designing)for?Where in Live Scenarios i can utilize there functionality?
Any answers will really be very helpful.
Regards,
Gavin

Hello,
Look at the following blogs for more practical implementation of fault messages.
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
Cheers,
Naveen

Exception using fault message in java server proxy.

Hi All,
I am trying to use Fault message inside my server proxy code in Asynchronous java server proxy. I am referring the below mentioned link :
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d06315a6-e66e-2910-039c-ba8bbbd23702?quicklink=index&overridelayout=true
I successfully deployed my SDA file but while running the scenario(http-XI-ftp in PI7.11) i am getting the folowing exception under MDT:
com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error processing inbound message. Exception: Cannot locate proxy bean ServerProxyFTTest3.
I am using the following library refernces under application-j2ee-engine.xml file: com.sap.aii.af.sdk.lib, com.sap.aii.proxy.svc, com.sap.xi.util.misc,com.sap.guid,com.sap.exception all of type "weak".
I have checked almost all the forums related to fault messages in asynchronous java server proxy but couldn't find much help.
Request you all to help me.
Thanks
Amit

Hi Rajesh,
I am deploying my SDA file on Non Central Adapter Engine.
I have also registered my interface using:
http://ISVSAPPISB:51000/ProxyServer/register?ns=http://infosys.com/poc&interface=SI_Proxy_IA&bean=localejbs/ServerProxyFTTest3&method=sIProxyIA
But still i ma getting the same exception.
Hi Gabriel,
I implemented my scenario using the same. But in addittion to the librarry referneces mentioned over there i have added one more refrence in it "com.sap.exception" of type "weak". My structure is like this:
<?xml version="1.0" encoding="UTF-8"?>
<application-j2ee-engine xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="application-j2ee-engine.xsd">
<reference reference-type="weak">
<reference-target provider-name="sap.com" target-type="library">com.sap.aii.af.sdk.lib</reference-target>
</reference>
<reference reference-type="weak">
<reference-target provider-name="sap.com" target-type="service"> com.sap.aii.proxy.svc</reference-target>
</reference>
<reference reference-type="weak">
<reference-target provider-name="sap.com" target-type="library">com.sap.xi.util.misc</reference-target>
</reference>
<reference reference-type="weak">
<reference-target provider-name="sap.com" target-type="library">com.sap.guid</reference-target>
</reference>
<reference reference-type="weak">
<reference-target provider-name="sap.com" target-type="library">com.sap.exception</reference-target>
</reference>
</application-j2ee-engine>
Please help.
Thanks
Amit

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
<b>
Fault messages -</b> /people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
Also ref:
<b>Handling Web Service SOAP Fault Responses in SAP NetWeaver XI -</b>
/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

Are fault messages applicable to synchronous messages also?

Hi Experts,
I have been trying to understand FAULT messages in XI.
The blogs I have seen so far discuss FAULT messages in Asynchronous scenarios only.
This makes we wonder if it cannot be used for Synchronous RFC scenarios.
Can somebody confirm this?
Thanks
Gopal

Fault messages can be used for Synchronous scenarios also.
To do a self-check create a Synchronous Message/ Service Interface....you will observe that the Fault message type section gets enabled.
For reference: http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3414700)ID1964483350DB02509562514351735296End?blog=/pub/wlg/2759
Regards,
Abhishek.

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

Handling Fault Messages

Hi,
I have this synchronous scenario : RFC > (XI without Integration Process) > SOAP.
Imagine that there is a problem with SOAP System and i get (don't worry about the error itself):
<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.aii.af.ra.ms.api.DeliveryException:
invalid content type for SOAP:
TEXT/PLAIN; HTTP 400 Bad Request</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I tried to add ExchangeFaultData into SOAP Interface, and mapping it but it didn't work.
Can i get this exception mapped into RFC exception?

The usage of your fault message is not correct, since it is designed to handle application error, in your case, it is technical error, it should be handled by alert framework.
Liang
===========SAP Definition================
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.
u2022 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.
u2022 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.
========= End of SAP Definition================

Fault Message generated in ABAP Inboud Async Proxy not visible XI Moni

Hi
    I developed a ABAP Inbound AsyncProxy, which raises an exception using a fault message type. The SMB_MONI in the Business System is displaying the message as Application Error. But the XI Monitor is showing it as sucesfully processed.
    How do I monitor application errors from XI Monitor when I am sending Asynchronous Messages using ABAP Proxies?
    The business system in context is R/3 Enterprise System which is has got the APINT patch on it.
Thanks in advance...
Regards
KP

I'm developing a Java Proxy and I'm experiencing the same problem. The exception is raised by my Java Proxy and it can be checked in RWB Message Monitoring of my central adapter engine. It can alse be checked in the MessagingSystem.
Unfortunately, no message is returned to SAP XI, at least, I cannot see anything in SXI_MONITOR (SXMB_MONI).
The point is: does ir make sense to generate a fault message in xml just to be checked in an html monitor? The xml tags don't appear correctly in html format and I had to debug my application in order to find out that the exception was correctly returned.
If anyone here have advanced in this issue, please let me know.
Best regards,
Ricardo Bochner.

SOAP adapter engine with system error, problem with fault message.

HI,
I have IDOC -> PI -> SOAP scenario.
Idoc to PI is async. I have no problem in receiving the idoc in PI. The message mapping is carried out and sent to the adapter engine. I can also see the technical routing payload. It is sucessful at XML monitoring in SXMB_MONI.
The error is at PI -> SOAP.
I have wsdl provided by the receiver webservice. Which I have imported.
And created a service interface against this wsdl. I tried changing it to both sync and async.
I have also provided fault message.
I have set a receiver soap communication channel and provided the target URL like "http://xxx/services" and soap
action = processDocument. Also provided user id and password.
I have a
Sender Agreement
Receiver determination
Interface determination
Receiver Agreement
I check in RWB adapter engine, this message goes to system error. The error log is as shown at the bottom.
When I see the message content, the SOap document shows me the details about IDOC, Instead I feel it should match
with the wsdl, where they have specified the corresponding interface name and address location etc.Please correct me.
How does the receiver know which service interface is it? The Service Interface which I created in the ER is
different from the WSDL, Does this have to be same? I see that the soap document in the adapter engine has the
Service interface name which I created in the ER. Where in the document the Reciever interface name is sent?
Where can I see the generated soap document for the receiver?
Is there some setting/configuration required in PI for this to work?
I tried using the tcpgw to see the error. If I dont provide the service interface name in the communication channel
then I get the following error in the TCPGW. "The service cannot be found for the endpoint reference"
When I provide the service interface name in the communication channel I get a valid fault message.
Similarly
When I use SOAPUI, I can see the fault exception being return. The adapter engine doesnot show an equivalent message
instead it goes into system error as shown at the bottom. I guess this is expected, if so what is the work around? (I found this weblog /people/alessandro.guarneri/blog/2011/01/10/soap-fault-in-sap-pi-hijack-it, do I need to implement this? Or use ALEAUD?
The fault message what I see in SOAPUI has the below format.
<soapenv:Fault xmlns:axis2ns1="http://schemas.xmlsoap.org/soap/envelope/">
         <faultcode>axis2ns1:Server</faultcode>
         <faultstring>nested exception is: psdi.util.MXApplicationException: BMXAA7136E - Validation failed when the
                            database default values were set. See the associated message for more information.
           BMXAA4190E - Country NZ is not in the value list.</faultstring>
         <detail>
            <Exception>org.apache.axis2.AxisFault: nested exception is: psdi.util.MXApplicationException: BMXAA7136E
                      - Validation failed when the database default values were set. See the associated message for more information.
     BMXAA4190E - Country NZ is not in the value list.
            /Exception>
         </detail>
</soapenv:Fault>
And the fault message in my ER service interface is stanadard datatype ExchangeFaultData, which is different from
the above. Is this the problem? Can I change the data type here to be the same as above?
Audit log in the RWB adapter engine.
Time Stamp Type Description
30.09.2011 15:10:57 Information MP: processing local module Localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
30.09.2011 15:10:57 Information SOAP: request message entering the adapter with user J2EE_GUEST
30.09.2011 15:10:57 Information SOAP: completed the processing
30.09.2011 15:10:57 Information SOAP: sending a delivery error ack ...
30.09.2011 15:10:57 Information SOAP: sent a delivery error ack
30.09.2011 15:10:57 Error MP: exception caught with cause
com.sap.engine.interfaces.messaging.api.exception.MessagingException
30.09.2011 15:10:57 Error Adapter Framework caught exception: null
30.09.2011 15:10:57 Error 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.
30.09.2011 15:10:57 Information The message status was set to WAIT.
30.09.2011 15:10:57 Information The asynchronous message was successfully scheduled to be delivered at Fri Sep 30
15:15:57 NZDT 2011.

I tried changing it to both sync and async.
I have also provided fault message.
dont feel that you need to do above steps.
I have a
Sender Agreement
ideally you dont need a sender agreement (and a channel) for IDOC --> PI flow.
When I see the message content, the SOap document shows me the details about IDOC
this is fine...you may see fields as seen in EDI_DC40 of the IDOC...
How does the receiver know which service interface is it?
receiver need not know about the SI created in PI.
The Service Interface which I created in the ER is
different from the WSDL, Does this have to be same?
you should the WSDL (external definition) as the Request Message in your service interface.
Is there some setting/configuration required in PI for this to work?
nothing specific...AFAIK
I have set a receiver soap communication channel and provided the target URL like "http://xxx/services" and soap action
can you open the URL from Internet explorer...from your machine or from the machine which is in the same network as your PI server?
Things to check:
WSDL structure in PI and in target system is exactly the same.
does the target system require mesage in SOAP format (SOAP envelope - SOAP Header + SOAP body)?
target system is up and running?

Fault Handling in Asynchronous process

Hi,
I want to know how to throw fault from an Asynchronous process to the calling process. In a synchronous process we generally throw faults using fault message in 'process' port type. But Im not sure how to throw a fault from Asynchrnous process to the calling process that can be caught in the catch block of the calling process.
Can some one update me with the feasibility of this.
Thanks,

Hi,
Look inside the Oracle® BPEL Process Manager Developer's Guide at http://download-uk.oracle.com/docs/cd/B31017_01/integrate.1013/b28981/faults.htm#BABIBAFC
8.8.2 Returning a Fault in an Asynchronous Interaction
In an asynchronous interaction, the client does not wait for a reply. The reply activity is not used to return a fault. Instead, the BPEL process returns a fault using a callback operation on the same port type that normally receives the requested information, with an invoke activity.
Example
    <portType name="BPELFaultHandling">
        <operation name="initiate">
            <input message="client:BPELFaultHandlingRequestMessage"/>
        </operation>
    </portType>
    <portType name="BPELFaultHandlingCallback">
        <operation name="onResult">
            <input message="client:BPELFaultHandlingResponseMessage"/>
        </operation>
        <operation name="onError">
            <input message="client:BPELFaultHandlingErrorMessage"/>
        </operation>
    </portType>On the caller side you have to use one invoke followed by a pick activity waiting for onResult or onError callback.
Best Regards,
Harald Reinmueller

How to read fault message in async soap receiver

Hi experts,
I have an asynchronous scenario IDOC->XI->SOAP.
I've defined a SOAP fault message as part of the Inbound Message Interface.
When an error occurs on the SOAP Server, the error description is returned in the form of the fault message.
E.g.
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" >
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Client</faultcode>
<faultstring>Cannot find the required parameter [lastName] in request message content.</faultstring>
<detail>
<ns1:com.sap.engine.services.webservices.additions.soaphttp.exceptions.ProcessException xmlns:ns1='http://sap-j2ee-engine/error'>Cannot find the required parameter [lastName] in request message content.</ns1:com.sap.engine.services.webservices.additions.soaphttp.exceptions.ProcessException>
</detail>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
My question is how do I use this message in XI?
I cannot seem to read this fault message.
Please help.
Thanks.
Ron

> > Fault messages are specially designed for Proxies
> and
> > RFC's only..............ASFAIK Fault messages wont
> > work for SOAP reciever side...
>
> They actually also work with SOAP scenarios.
>
> Your WSDL will contain the fault message and in such
> cases ( if you are using a BPM with exception handler
> ) , in case a fault message is sent back, you will be
> able to access this as well.
>
> Regards
> Bhavesh
Bhavesh,
I'm not using BPM and I'm using a asynchronous mode for invoking the WebService.
My WSDL has fault message defined, and I've assigned this fault message to the "Fault" portion of the Inbound Message Interface.
How can I access my fault message in this case?
Please help
Thanks.
Ron

Fault Message for inbound asynch ABAP proxy

Hi All,
I've got scenario File -> XI -> ABAP proxy all asynchronous.
Inside a proxy I'm throwing an exception using fault message.
I don't see application error in SXMB_MONI on XI, I can see that only in SXMB_MONI on receiving system.
Is it possible to have flag Application Error on XI monitor as well ?
Best Regards,
Tomasz

Jai,
I've checked that many times.
I'll describe my scenario in more details.
1. From the file I'm receiving a lot of items and trying to process as much as possible in one proxy call.
2. Those ones which are causing errors are sent out to XI (outbound proxy) one by one. XI sends them to the same interface which is used in 1. step where I have condition which checks for single item and when it's wrong then exception is thrown.
One SCM box is sender and receiver which my cause that problem.
Tomasz

Fault message monitoring

I have an asynchronous scenario of HTTP-> XI -> RFC. In my RFC function application errors may occur. I defined fault message type in my asychron inbound interface corresponding to exceptions of my RFC function.I tried to raise exception in my RFC function in following way:
message e001(CJ) with msg1_hlp raising UPDATE_NOT_POSSIBLE.
But I could not get fault message displayed in XI message monitor (SXMB_MONI).
Could somebody tell me what is the easiest way to show error messages in my case?
As far as I understand either I need to use BPM, or I need to use ABAP server proxy for raising exceptions. Must I use ABAP Proxy instead of RFC function? Then I may need to generate a ABAP Proxy to use as a wrapper for my RFC function, correct?
Thanks,
Hongbo

Hi,
Have you checked this blog, It will help,
<a href="/people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1">Fault Message Types - A Demo</a>
Regards
Bhavesh

Fault Message in Asynchronous

Similar Messages

Maybe you are looking for