Fault Messages

I have a Scenario:
HTTPS --> XI --> RFC
Now this is a sync scenario. The issue is that the RFC returns either a Response or an Exception.
My sender interface has request, response and an exception message. The exception message I have put into the fault message box.
Now I have done all of the mappings and have gone to do the interface mapping but... I can only include a request and response message in my tabs for the mapping. There is no option for the fault message.
Could you please let me knwo how I should include the fault message mapping or let me know if there shouldn't be a mapping.
Can someone explain how fault messages should be handled in Sync Scenarios....
Please no blogs unless they are relevant for this specific question...

OK... let me explain.
I have my sender message interface which is from the https client.
It contains Request, Response and FaultMessage.
I have my RFC Receiver interface.
It contains Request, Response and Exception.
No when I go to the interface mapping I dont see a Fault message tab.
Should this be the case? Or should I see a fault message tab

Similar Messages

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

Fault message in sender SOAP scenario

Hi mates,
I've a o/b synch MI which is exposed as a web service. I've specified the fault message with faultcode, faultstring, faultactor and detail. I've a BPM as the receiver for this synch infterface. This BPM implements synch-asynch bridge.
Now the question is...How can I specify that a particular fault message needs to be returned to the SOAP caller. I can send the response for the SOAP caller using the send step with mode 'Closes S/A bridge'.
I appreciate you inputs.
thx in adv
praveen

Moorthy,
I've the FM in my BPM. But...how can I append this to Response message as these have two different MTs?
Do you mean to say my response message should have a node for fault message data?
I'm trying to implement sth like in this blog <a href="/people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client">Propagation of meaningful error information to SOAP Client</a>
To achieve FM in SOAP scenario, should I be using only a non-BPM receiver like a R/3 system using FM with exception as the receiver? Can this be not possible if I use BPM as receiver?
thx in adv
praveen

Synchronous File- Soap scenario with fault message

Hi!
I have a File to Soap synchronous scenario.
All is right when no exception is returned by the web service.
I want to use fault messages to catch thoses exceptions, so I have added fault message in message interfaces and in the mapping program in the interface mapping.
Now, when the web service return an exception like :
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
 <soap-env:Body>
 <soap-env:Fault>
 <faultcode>soap-env:Client</faultcode>
 <faultstring xml:lang="en">NOT_CREATED</faultstring>
 <detail>
 <n0:Z_WS_CREATE_WAGON.Exception xmlns:n0="urn:sap-com:document:sap:rfc:functions">
 <Name>NOT_CREATED</Name>
 <Text> does not have packaging material type and is therefore not a pack.mat.</Text>
 <Message>
 <ID>HUSELECT</ID>
 <Number>041</Number>
 </Message>
 </n0:Z_WS_CREATE_WAGON.Exception>
 </detail>
 </soap-env:Fault>
 </soap-env:Body>
</soap-env:Envelope>
I get the following error :
<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>http://www.arcelormittal.com/radis/rad IM_RAD_to_ZWsCreateWagon</SAP:P1>
 <SAP:P2 />
 <SAP:P3 />
 <SAP:P4 />
 <SAP:AdditionalText />
 <SAP:ApplicationFaultMessage namespace="" />
 <SAP:Stack>Interface mapping http://www.arcelormittal.com/radis/rad IM_RAD_to_ZWsCreateWagon does not exist in runtime cache</SAP:Stack>
 <SAP:Retry>N</SAP:Retry>
</SAP:Error>
My mapping program for fault message is well defined (I tested it with the exception message received from the web service).
I have also refresh caches, but without success...
Can anyone help me ?
Thanks in advance,
Laurence

Hey Laurence,
A File adapter is aysnchronous u cant use for synchrous because it cant acknwlodge the response it gets or itt sends.
regarding two asynchoronus
1. file to SOAP asychn.
2. triggger the second one if SOAP has exception then pass the error from SOAP to New File.
using BPM we have to use Transportion level acknowledgments
please reward points if it helps
Regards
Sreeram.G.Reddy

Handling SOAP Fault messages in BPM

Hi,
My scenario is Sync-Async Bridge involving File to SOAP transformation. I have used BPM as 1 file has many records and each record is required to call the web service synchronously.
In the BPM I have
Receive ---> Transform (1:n multimapping ) -
> Block (Par for Each)
In Block I have Send Sync step to call Web service . I have an exception branch for the send step for catching Fault message that is sent back from webservice for Application Fault.
Problem:
Though the Fault message is sent from web service ,in the BPM the block goes in error saying : "No exception defined for fault message ". The Exception brach is not executed.
Please suggest if anyone has come across such a scenario and solution to this.

hi satesh
using "exception handler" in BPM we can handle the error messages
regards
kummari

Handling fault messages in an Integration Process (bpm)

I have a bpm in PI 7.11 which performs a synch call to an external webservice. In addition to the request/response, that webservice can also generate two faults: ObjectNotFoundFault and generalfault. I am having trouble handling these faults - when a fault occurs my handler is not being invoked and thus the bpm process stops/errors. When I look at the underlying process (via txn swi1), I see the exact error text:
"No exception defined for fault message ObjectNotFoundFault http://www.companyb.com/services/olsa_v1_0/"
From what I understand within the bpm synch call step to the webservice I need to do the following to handle the exception/fault:
- put the synch call (to the webservice) into a block
- add an exception branch to that block named let's say A & set the exception handler of that block to be A
- in the exception setting of that synch step, select A
In my case, I don't care about the fault details other than to ensure it does not stop the whole Integration Process, so in my exception branch I don't do anything. I did try adding a control step within it too (as per SAP Press text book).
Is there anything else I need to do here? I am not mapping the returned fault - does the fault need to be mapped (not sure how I would do this given that the synch step uses an abstract interface and therefore to my knowledge no fault mapping can be done)?
There are 2 Notes that describe my issue exactly:
https://service.sap.com/sap/support/notes/1484903
https://service.sap.com/sap/support/notes/1158699 <-- this one refers more to me, but we already have in 7.11
Can anyone let me know exactly the steps I would perform to handle these faults - does the exception name / handler A above need to be named the actual exception / fault ObjectNotFoundFault?
Any help appreciated.
Thanks,
Keith)?
Any help appreciated.
Thanks,
Keith

Thanks - my scenario I guess is #2 of that blog. But is your take that even if I don't care what is in the fault message, i.e. I don't care about the contents of it but rather I just want to continue on from it, that I still need to perform this java coding? It's not clear to me from what he says - it seems to me he does the java coding to actually capture the contents of the message. I am in fact using the soap axis adapter too, as he is. The screen shot showing the exception branch is basically what I have.
Regards,
Keith

Handling fault messages in BPM

Hi,
I am using BPM for a RFC to SOAP scenario to handle Fault messages. (Please have a look at my previous post also SOAP Fault message )
I have created an exception block in BPM to catch the fault message from SOAP service. Inside the exception block i need to map the fault message to RFC response. But fault message is not accessible in Exception block.
Let me know if you have any idea to solve this.
Thanks,
Uma

Uma:
Let me make clear the requiremt. You have RFC Import(aka Request message) and Export(aka Response + Exception) and you have Web Service with Request, Response, Fault messages. And you want to send the fault messages back to the RFC in addition to the response. I was wondering, If we do the following mapping without BPM, does that fulfill your requirement.
RFC-Import <----
> SOAP Request
RFC-Export <----
> SOAP Response
RFC-Export <----
> SOAP Fault
Can you let me know if you face any problems with this one. I have seen your other thread and was wondering, whats the problem is. May be I didn't understand the requirement properly. Please clarify me

Fault messages in target web service (microsoft visual studio) -experience?

Hi guys!
We use async scenario : SAP_R3 (ABAP Proxy) -> XI -> Web Service (SOAP). Target web service is created in microsoft visual studio. Standard scenario worx fine. We send data from r3, the web service processes them. However, we want to use also fault messages in case, there will be exception rised in the target web service and let operator in sxmb monitor know, that there's a problem. These fault messages should be used as acknowledgement. But we have serious problem with implementing fault messages in the target web service in the visual studio. Does someone have experience with this?
Thanx a lot for info!
Olian

Hi
see the below links
Consuming XI Web Services using Web Dynpro Part II-/people/riyaz.sayyad/blog/2006/05/08/consuming-xi-web-services-using-web-dynpro-150-part-ii
Consuming XI Web Services using Web Dynpro Part I -/people/riyaz.sayyad/blog/2006/05/07/consuming-xi-web-services-using-web-dynpro-150-part-i
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/0d7349b6-0901-0010-ddbe-ec43178a61ff
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ee5bc490-0201-0010-e9b5-a258cf083bca
Troubleshooting SOAP Message - XI - /people/varadharajan.krishnasamy/blog/2007/01/09/troubleshooting-soap-message--xi
Troubleshooting - RFC and SOAP scenarios-/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009
Regards
Chilla

PI 7.0 SOAP message reply HTTP 500 and after the fault message

Hello Everybody,
I have the scenario RFC -> XI -> SOAP in synchronous mode.
I use for the mapping XSLT because I have to put some dynamic data comming from the RFC in the header of envelope.
At level of adapter receiver SOAP , I flag the "do not use envelop"
In normal, that works .
When the is an fonctionnal error in SOAP service, it sends me back an error HTTP 500 and afterwards the fault message in a soap envelop format. In that case, how can I pass over this error to treat the envelop because in adapter, it is stopped and it returns a short dump to the RFC.
Is there somebody who can help me with this problem ?
Thanks in adavance for your answers .
Regards.
Eric.

Hi,
In case of a SOAP error while processing the request, the SOAP HTTP server MUST issue an HTTP 500 "Internal Server Error" response and include a SOAP message in the response containing a SOAP Fault element
Thanks,
RamuV

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

Fault message in BPM process

I have a bpm process with a sync send step. i have a default fault message strcuture and my sync interface ( a proxy) is using this as fault message format. In case of an fault in the proxy i get the fault message returned. In my bpm i have an exception handler installed for the exception. What i would like to do in my process is send the fault message to another step like a send step.
i m not looking to understand sync/async bridges or how to setup a bpm process. I am looking for help in how i can work with the fault message in my bpm process other then only let it trigger the exception routine

Hi Frank,
in the view of your BP an exception at proxy side is no reason to stop processing. The message will be put to your interface and it is your decision to put data into a container and to send it. For using a "global" container for every kind of message have a look to my weblog <a href="/people/udo.martens/blog/2006/04/28/bpm-container-for-any-message-type Container for any Message Type</a>. If your send step is not successful and you want to catch that: Define an exception branch for your block, where you send a senseful message to notice the error. You can refer in the original send step the exception, during runtime the process jumps into the exception branch and is doing that what you defined there.
Regards,
Udo

Sync/Async bridge via JMS with FAULT messages

Hello all, 
I set up a sync/async bridge scenario with using of JMS communication channel (SAP - JMSReceiverCC - JMSServer and application - JMSSenderCC - SAP). The normal communication works fine. 
But what we can not solve is the Fault Message handling. If there is a application error behind the JMS, a fault message is generated instead of proper application response and sent back to XI. Without any additional setup of JMS Sender CC the processing of the message ends with "MAPPING - EXCEPTION_DURING_EXECUTE", because normal "response mapping" is executed instead of "fault message mapping". This is correct behavior without any discussion. 
[SAPhelp|http://help.sap.com/saphelp_nw70/helpdata/en/45/202845de34072ce10000000a155369/frameset.htm] says that there are 2 module parameters to be set : fault, faultNamespace. The description is rather vague, so let's see, what the "NotifyResponseBean" does, when parameters fault/faultNamespace are filled: 
<pre>if(fault != null && faultNamespace != null)
if(faultNamespace.equals("http://sap.com/xi/XI/System"))
 ((XIMessage)message1).setMessageClass(MessageClass.SYSTEM_ERROR);
 ((XIMessage)message1).setError(fault, "no additional information");
} else
 ((XIMessage)message1).setMessageClass(MessageClass.APPLICATION_ERROR);
 ErrorInfo errorinfo = message1.createErrorInfo();
 errorinfo.setAttribute("ApplicationFaultInterface", fault);
 errorinfo.setAttribute("ApplicationFaultInterfaceNamespace", faultNamespace);
 errorinfo.setAttribute("ErrorCode", fault);
 errorinfo.setAttribute("AdditionalErrorText", "no additional information");
 message1.setErrorInfo(errorinfo);
} else
((XIMessage)message1).setMessageClass(MessageClass.APPLICATION_RESPONSE);
}</pre> 
The code is pretty straight forward so one could assume, that it's the name and namespace of inbound synchronnous message interface what is supposed to be filled in the values of each parameter. And from that kind of information SAP XI can evolve how to handle the response, actually the fault. 
Unfortunatelly the real situation is different - every time the fault message is generated and sent back to XI, the response is correctly corelated with the request message, "WaitResponseBean" and "NotifyResponseBean" are finished correctly and the processing crashes in messaging class on following exception: 
java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:592) at
com.sap.aii.messaging.mo.MessageContext.setAttribute(MessageContext.java:140) at
com.sap.aii.adapter.xi.ms.XIMessage.updateHeaders(XIMessage.java:4244) at
com.sap.aii.adapter.xi.ms.XIMessage.getTransportHeaders(XIMessage.java:570) at
com.sap.aii.af.ra.ms.impl.ServerConnectionImpl.request(ServerConnectionImpl.java:212) at
com.sap.aii.af.ra.ms.impl.core.transport.http.MessagingServlet.doPost(MessagingServlet.java:337) at ...
 
Is there anyone, who can put more light on JMS sync/async bridge fault handling ???
 
Thank you ... 
Regards
Tomas

Hello again,
I proceed in investigation little more, but the main problem has not been solved. I found that the problem is not even in WaitResponseBean (placed in JMCReceiverCC). This bean is woken up properly on base of proper CorrelationID. See the log:
2009-10-15 11:00:33 Success WRB: entering WaitResponseBean
2009-10-15 11:00:33 Success WRB: retrieving the message for f1ea1fc0-b96d-11de-9b68-00144f4acd86 ...
2009-10-15 11:00:46 Success WRB: retrieved the message: ApplicationError
2009-10-15 11:00:46 Success WRB: leaving WaitResponseBean
I think, that the problem is somewhere within main messaging functionality. I suppose that on base of exception message:
com.sap.aii.messaging.mo.MessageContext.setAttribute(MessageContext.java:140) at
which is generated.
Any ideas or comments ?
Thank you in advance.
Regards
Tomas

BPM Fault Message Exception error !

Hi here is what I am doing
Sync webservice-->Sync webservice call using ccBPM.
This is what I defined in the BPM
1.)Sync rec
2.)Block with Exception handler.
3.) Sync send inside the Block with Fault exception defined.
I defined fault messages for the interface. The Interface works fine when there is no exception but when there is a Fault exception I get the following error in SXMB_MONI_BPE "No exception defined for fault message Faultmessage urn:XXXXX:XXXXXXX ". Exception 8999, Error type 2, Area SWF_XI_ADAPTER Message 81. Variable1 Faultmessage and Variable2 the namespace".
I rechecked my BPM and could see the Fault Exception defined for the Sync send step and it has an exception defined for it too.
I checked SXI_CACHE and the return code is 00.
We are running on PI7 SP13. Did any one face this kind of problem .

Hi there,
I have the exact issue in PI 7.1. Have any of you guys could resolve it? Can you please share your responses.
Thanks.
Anshul

Fault message in synchronous send step in BPM

Hi,
When executing a synchronous send step in BPM it is possible to handle application errors (fault messages) with an exception branch. But how do you get hold of the actual data in the Fault message(faultText, faultURL, faultDetail etc) for further processing (mapping)?
Kind regards Johan

Johan,
u have to define another container element in integration process.
For that container element an Async Abstract interface has to created with falult message as the message.
Do u have the fault message defined already...
Also go through this thread.
Fault message handling in BPM
-Naveen.

BPM synchronous send step - Fault message extraction

Hello Experts,
I am developing a BPM with Asynch RFC -> synch Webservice -> Asynch RFC scenario.
I have defined fault message in the synchronous interface used in the send step for web service, and also defined
exception branch where an alert is thrown.
In the alert, i want to send the fault text from the fault message. How can i do that??
Thanks

Hi Mona,
SOAP adapter doesnt support fault messages.
check stephan's reply @ How catch the SOAP Fault Message ?
> SOAP adapter does not support fault message.
> Any fault is treated as error.
> fault messages are only supported for XI messages (ABAP or Java proxies) and RFCs.
Fault message handling is not possible inside BPM.

PI 7.1 Adapter Module Development - Identify SOAP Fault Message

Hi Experts,
here's a PI 7.1 Adapter Module Development issue I hope you can help me to resolve. It's about identifying SOAP fault messages.

Scenario at a glance:
Adapter Modules placed in the modules chain at request and response time in a synchronous Scenario:
- Request: SOAP Axis to RFC 
- Response and Fault Response: RFC to SOAP Axis

The issue is how to identify SOAP fault message in SOAP Axis Adapter Module in the response message:
The client gets SOAP fault messages like the follwong one:
 <SOAP:Body>
 <SOAP:Fault>
 <faultcode>SOAP:Server</faultcode>
 <faultstring>Server Error</faultstring>
 <detail>
 <ns1:exception xmlns:ns1="http://typen.geschaeftsstelle.pab.barmer.de">
 <ns1:errortext>bla bla bla ...</ns1:errortext>
 </ns1:exception>
 </detail>
 </SOAP:Fault>
 </SOAP:Body>


But when trying to access the tags faultcode and/or faultstring in the adapter module via xPath expressions I do not get them. Obviously the SOAP Fault tags are built AFTER the adapter module has been passed. So my question is:
How can I clearly/uniquely detect a SOAP fault response message (and distinguish it from a "normal" response message) in my SOAP Axis Adapter Module?

I tried it the following way:


// Check Message Payload for SOAP Fault Message via xPath expressions
...
// SOAP Fault Code
zv_xPression = zc_constXPattern.replaceFirst("&", "faultcode");
zv_soapFaultCode = XPathAPI.eval(zv_doc, (String) zv_xPression).toString();
// SOAP Fault String
zv_xPression = zc_constXPattern.replaceFirst("&", "faultstring");
zv_soapFaultString = XPathAPI.eval(zv_doc, (String) zv_xPression).toString();
// check for SOAP Fault Message
if (zv_soapFaultCode.equals("") && zv_soapFaultString.equals("")) {
 // Create Audit Log entry - NOT a SOAP Fault Message
 zv_msgText = zc_constModuleName + " 0190: xPath - OK! This message is NOT a SOAP Fault Message";
 zv_audit.addAuditLogEntry(zv_msgKey, AuditLogStatus.SUCCESS, zv_msgText);
 zv_faultCheck = false;
}
else {
 ...
 // Create Audit Log entry - SOAP Fault Message
 zv_msgText = zc_constModuleName 
 + " 0200: xPath - this message is a SOAP Fault Message. " 
 + " - Faultcode is: " + zv_soapFaultCode 
 + " - Faultstring is: " + zv_soapFaultString; 
 zv_audit.addAuditLogEntry(zv_msgKey, AuditLogStatus.ERROR, zv_msgText);
 ...
}
...

But zv_soapFaultCode and zv_soapFaultString are always empty (with other payload tags this coding works fine).

Any ideas? 
Thanx very much in advance!
Regards,
Volker

Hi Alex!
Like already mentioned I solved my problem by identifying the SOAP exception with the messageClass attribute of the PI message header. Acess code:
try {
String zv_msgClass = zv_piMsg.getMessageClass().toString();
} catch (Exception e) {
zv_msgText = zc_constModuleName
+ " E0110: Message processing terminated."
+ " Reason: Error while getting MessageClass "
+ zv_dataSource
+ e;
// create trace and audit log entry (severity ERROR) for exception
zv_location.errorT(ZV_SIGNATURE, zv_msgText);
zv_audit.addAuditLogEntry(zv_msgKey, AuditLogStatus.ERROR, zv_msgText);
ModuleException me = new ModuleException(e);
zv_location.throwing(ZV_SIGNATURE, me);
e.printStackTrace();
throw me;
} // end of try-catch-block
But I do not think this will solve your problem. I am almost sure, that something in your Axis configuration is wrong/missing. If a handler cannot be instatiated then it really may be missing. Have a look at defaultTrace.trc. Maybe you will find more suitable information about the root cause of your problem. Also have a look at NWA under software components and/or application modules if you can find/see your modules.
But there is a general issue when trying to catch PI fault messages. If e.g. the requestor tries to login with wrong userid/pasword, then you will have no chance to catch this kind of error - at least as far as I know. Because in this very early stage of PI message processing no module is called.
One last question: Did you develop your own Adapter or just an adapter module? In the first case: Is your adapter started and healthy? Have a look at RWB -> communication channel monitoring.
Regards,
Volker

Fault Messages

Similar Messages

Maybe you are looking for