Fault message mapping

Hello,
I have following scenario.
Synch, RFC Sender -
> XI----
>JDBC receiver.
Also I have defined Fault message data type, message type and also createed Message Interface in which I specified Fault Message type. Now my question is.
When an error occurs I want to get error message to be captured in fault message and map the fault message elements to RFC ---> Rerutn item elements. I was wondering how would I accomplish this?
Thank you,
Balaji

For sender RFC:
http://help.sap.com/saphelp_nw04/helpdata/en/67/6d0540ba5ee569e10000000a155106/frameset.htm
You must to create a in sm59 in R/3 and XI an R3 conection.
You can see this very interesting blog: /people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
Regards.

Similar Messages

Fault Message Mapping for SOAP Scenario

Hi ,
I have configured a Proxy to SOAP synchronous scenario. The scenario is working fine. Now I need to map the fault message and display the message in SAP in case of any errors. I have used the standard Fault message. But I dont have any message from the WSDL which I can map to the standard fault message. Is it that we need to tell the wenservice team to modify the WSDL to include the fault message or is there any other way out to acheive the same.
Thanks
Amit

>>> Is it that we need to tell the wenservice team to modify the WSDL to include the fault message or is there any other way out to acheive the same?
Fault message is to provide meaningful message to the other end if there is a validation error or business exceptions or so...
a) You are importing WSDL of the third party and using it in soap receiver target side.
b) Normally it is best practice to create a WSDL which contains request, response and fault message. if your wsdl has fault message type declared then you can map the wsdl fault message with your proxy side fault message(which you can create). Please note you rely on the third party wsdl. Third party WSDL must have application logic coded to support fault message in case of application error occurs. Example if there is a validation that does not go through then their application logic must populate data in the fault message of wsdl. Then only if we map the wsdl fault msg to our proxy fault msg, we get meaningful fault details.
If your target WSDL does not support fault mesg, it is not going to be helpful at all.

Interface-Mapping with a Fault Message Type

Hi,
we have an abap-proxy and some messages generated errors. The errors can be displayed via sxmb_moni. The proxy raises an "Application Error (Restart possible)".
Now I wanna transform the generated fault message (of the proxy) with a message mapping and send the output to a file.
My problem is, that it is not possible to define an interface mapping with the fault message as well as it is not possible to define a receiver determination.
Any ideas?
Thanks a lot
Regards
Wolfgang Hummel

Hello
As far as I know you can propogate the application error back to the calling application only in case of a Synch Interface? Are you making a Synch call where the proxy triggers a fault message, if yes then all you need to do is to make the change in XI to have the fault message for both the outbound and inbound message interfaces and then a corresponding fault message mapping and select this in the Interface Mapping and then the fault message will be sent to the source / calling application.
In the case of Asynch calls I don't think this is possible until you use a BPM. Have not tried this myself though.
Regards,
Bhavesh

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

SOAP Adapter - Using Fault Message

Hi all,
I have developed a Synchronous Integration Scenario which receives a SOAP request to the SOAP adapter, calls an ABAP proxy in SAP ECC to post some information and return a response or a fault to the sender.
This all works fine, I am using a fault message in the ABAP proxy to record errors and return them to the SOAP adapter using the fault mapping. Again this all works fine. However when an application error is identified and a fault message returned to thre SOAP adapter, I had expected that the error details in the fault message to be packaged up in a standard SOAP fault and returned to the sender. Instead the fault message details are sent as the payload in the SOAP body of the response.
Can anyone provide information on if it is possible to return the fault message as a standard SOAP fault instead of in the SOAP body of the response.
Thanks
Gary

Dont think this is possible in standard.
As an alternate, maybe you can select option Do not use SOAP Enevlope int he sender SOAP Adapter and thereby the entire SOAP Message will enter the mapping and you would need to use a XSL or Java mapping to strip the SOAP Envlope in the mapping for the request and like wise in the response mapping you would need to add the SOAP Enevlope to the response.
For the fault message mapping you need not add the SOAP Envelope.
Not a standard solution, but can be tried if the requirement is really worth it. Otherwise I think the Fault Message will continue to be sent as the payload in the the SOAP Enevlope as this is how the SOAP adapter works.
Regards
Bhavesh

Fault message handling in syn proxy

Hi Experts,
I have implemented Proxy to Web service synchronization scenario and implemented request response and fault message mapping.
But when the scenario is getting the Application error the fault message is visible in sxmb_moni but not visible in the proxy or not being forward to proxy ?
Can you help if there is any more config or any other follow up is required, all the mapping and other part of fault message is as per PI standard only including the proxy ABAP code?
regards,.

Hi,
But when the scenario is getting the Application error the fault message is visible in sxmb_moni but not visible in the proxy or not being forward to proxy ? - In your R/3 system by transaction SXMB_ADM, then integration engine configuration - specific configuration - in RUNTIME add parameter for logging and tracing and set it to maximum level...........also LOGGING_SYNC parameter should be enabled................
then re-run your scenario..........then for a application fault msg in SXMB_MONI of XI, you should see a fault msg in SXMB_MONI of your r/3 system.
Regards,
Rajeev Gupta

JMS: Fault message

Hi,
I have a synchronous SOAP to JMS (using sync/async bridge without BPM) scenario.
What I now want is to be able to return an application fault message to the sender system (SOAP).
To test the setup Ive made I'm sending a message to XI. It successfully processes the message and puts it on my request JMS (MQ) queue.
I then manually put a fault message (as defined in my repository) on my response JMS (MQ) queue.
Messages are correlated fine and message arrives in Integration Engine where it fails in my response mapping. So issue is it does not realise a fault message has arrived and thus doesn't use my fault message mapping.
Anybody got some ideas as to why this is?
Best Regards,
Daniel

Hi,
I believe SOAP adapter supports fault messages fine too. To my knowledge however these are the only 2 adapters that support fault messages.
Best Regards,
Daniel

Send Fault message from SAP XI

I have scenario: get async file from FTP. Starting BPM. From BPM I send message to SOAP service(sync). Where I recieve Fault Message. In BPM I have exception handler.
Could any body tell how send parced Fault message to FTP.
As I understand we need mapping somthing like "Fault message type" to "Inbound message type"

Hi Anton,
Its not possible to catch the data of fault message in BPM with the standard design.Since you can't make an abstract interface of the fault message.
The option available is to parse the XML in the fault message mapping and do a call using UDF's (RFC, SOAP, JDBC calls are supported).
cheers
Sunil.

How to send back the soap fault message without details tag to the sender

Hello Expert,
Is it possible to send the soap fault message(fault String element value) without details tag as shown below to the sender in synchrounous scenario.
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
 <soapenv:Body>
 <soapenv:Fault>
 <faultcode>soapenv:Client</faultcode>
 <faultstring>autorizarComprobanteRequest.comprobanteCAERequest.arrayOtrosTributos.otroTributo(1).codigo - El Código de Tributo es obligatorio.</faultstring>
 <detail></detail>
 </soapenv:Fault>
 </soapenv:Body>
</soapenv:Envelope>
I have to send the faultstring element value in one of the element in response message back to sender? Is it possible using BPM?The above fault response does not have a fault payload (no detail element) and would result in a system error message.So how to handle this?
If yes .Please tell me the BPM design
faultstring value will be dynamic.
Thanks in advance

Thanks Yzanagi,
I have gone through the index.htm file.
In my scenario that is RFC -PI-soap(using http(Axis) protocol).when the webservice provider is sending the soap fault as.
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
 <soapenv:Body>
 <soapenv:Fault>
 <faultcode>soapenv:Client</faultcode>
 <faultstring>autorizarComprobanteRequest.comprobanteCAERequest.numeroComprobante - El Número de Comprobante debe ser mayor o igual a 1</faultstring>
 <detail></detail>
 </soapenv:Fault>
 </soapenv:Body>
</soapenv:Envelope>
In PI sxmb_moni it is converting to the error (system not application error)as shown below when using receiver soap adapter with https(Axis) transport protocol and Message protocol:Axis.
<?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>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1></SAP:P1>
<SAP:P2></SAP:P2>
<SAP:P3></SAP:P3>
<SAP:P4></SAP:P4>
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: autorizarComprobanteRequest.comprobanteCAERequest.numeroComprobante - El Número de Comprobante debe ser mayor o igual a 1.</SAP:AdditionalText>
<SAP:Stack></SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
As my requirement was (I have mentioned in my first question) that I want to pass
SAP:AdditionalText tag
value back to sender in one of the elements of response message payload or handle using fault message mapping if this error could be converted to application error and map to the RFC exception but unfortunately which is not possible even using AXIS adapter.
so other option to inform the sender RFC is mentioned here http://help.sap.com/saphelp_nw70/helpdata/en/22/0425e0488911d189490000e829fbbd/content.htm
but while handling the SYSTEM_FAILURE exception from PI at sender in report program and displaying the msg variable ,I am not getting complete error message..It is getting truncated.Is there a limit to the no of character the msg variable contains which is set by system.Even if we declare msg variable with more length(for example char length 500) it is just displaying part of the error message from PI.
Any Idea to read complete system error message from PI in report program at RFC sender..
Kind Regards,
Kubra fatima

Unable to retreive the fault message returned by web service

Hi,
We are working on Proxy to SOAP synchronous scenario. The WSDL provided by the third party has 3 messages - 1. for request structure, 2. response structure and 3. Error message to track the exceptions, if any. The interface working fine for positive test cases but we are facing issues when trying to capture the error message returned by the web service.
We have configured the error message(provided in WSDL) as fault message in our Inbound interface. In the outbound interface, we have configured standard Fault message type provided by XI. we have mapped the two structure.
Now when error is returned by the web service, we are able to see the blank response structure in the payload in MONI in XI. Also the SOAP Error Message structure is there in XI.
But when we trying to retrieve the same in our proxy, it is giving the blank structure.
Please help how to get the error message returned by the web service in proxy....
Please help..
Thanks in advance.

>>>I am getting the error message as the fault message, in the response from the web service.
>>>Now I want to forward the same message to SAP R/3 system. For this I have configured the standard fault message in the >>>outbound interface and have mapped the same with the web service error message. So if I am not wrong, the transformed >>>>structure according to the rules in message mapping should be sent to SAP R/3 system. But I am unable to see the result >>>>of this mapping in XI MONI. Neither is this passed to Client proxy.
You are consuming the third party webservice. Third party webservice WSDL has request, response and fault message. if the third party application logic capture the exception and pass the response as fault mesg, then the above specified target fault mesg mapping with your Standard fault message mapping will be sent to sender or client proxy.
Suggestions:
Having fault message in WSDL does not mean that target system sends fault message during application exception. Check in the SXMB_MONI whether your response during exception is occuring in the fault message structure publised as WSDL. If not then doing mapping will not help. It gives only blank.
If you notice response in fault message structure from third party in SXMB_MONI, then you need to check that at the client proxy side, are you handling/done coding for fault message methods similar to response strucutre for capturing data.
Hope that helps.

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.

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

Mapping SOAP Fault Message on PI

Hi there,
I'm trying to map a SOAP Fault Response From a Legacy system on PI, but i have some doubts on how to create the Data Type and the fault message Type,
Basically the response will look like this:
<SOAP-ENV:Body>
 <SOAP-ENV:Fault>
 <faultcode>SOAP-ENV:Client</faultcode>
 <faultstring>Data failed validation</faultstring>
 <detail>
 <fault xsi:type="ns1:Fault">
 <ns1:code>1002</ns1:code>
 <ns1:errorMessage>Data failed validation</ns1:errorMessage>
 <ns1:detailMessage>Invalid (does not exist) Zone Identity...</ns1:detailMessage>
 </fault>
 </detail>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
so basically i defined a data type detail ( named detail aswell in pi ), with a fault element and code errorMessage and detailMessage xsd:String attributes ( i dont know what to do with that ns1 xsi type )
but when i want to creat the whole message PI only allows me to have 1 outter element like this:
<FaultMessage>
 <faultcode>
 <faultstring>
 <detail>
so pretty much i want to have a data type with 4 independent elements cause i know the SOAP-ENV tags wont get to the mapping, im almost sure i'm missing something very dumb here but i dont see it ,
Thanks in advance for all the help you guys can provide,
Regards,
Roberto.

Thanks for the documention it was really helpful,
now i have another problem, i alredy created the data type for the detail tag to match the soap response, but when creating de Fault Message Type on the Data Type Used area, PI inserts me some standard data that is mandatory and does not correspond with the structure im going to receive, it only allows me to import the detail data type as Additional data :S.
Regards,
Roberto.

SOAP fault - How to log error in response message map

Hi,
I have a scenario ABAP Proxy <-> XI <-> SOAP.
Occassionally there is an issue with communication to the destination system and an HTTP 500 Error is returned. I assume this is due to a system related error and it is returned as a SOAP Fault as opposed to a SOAP response with payload.
How do I get this "HTTP-500" error into my message map to return to the calling system ?
I have looked at Fault Messages but need to know if these are relevant for the SOAP Adapter and how they can be utilised ?
Thanks for any help.
Kind regards
Colin.

SOAP fault message not in correcto format to allow an application error to be caught.

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

Fault message mapping

Similar Messages

Maybe you are looking for