Automizing error message with Fault Message Type

Question

(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?

Answer 1

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