Fault Message Type

[Former Member]

Hi Experts,

For Fault Message Type, I have search some blogs or discussions in SCN, but i still have some doubts.

we can add fault message type into outbound/inbound service interface for Sync scenario.

And add fault message type into inbound service interface for Async scenario.

If it is Sync scenario,

(1) Create the fault message types for request and response.

(2) Add into outbound/inbound service interface.

(3) Create mapping for fault message types, not required if they are same.

(4) add the fault message mapping into operation mapping.

if there is any application error in target side, a fault message will be response and sent to PI, PI will sent it to source.

Is it correct?

****************************************************************

If it is Async scenario, and from 3rd partyto SAP ECC.

(1) Create fault message type and add into inbound service interface.

(2) Proxy program should be generated in ECC for main proxy message and fault message.

Now i have one doubt, if an application error occurs when the proxy program is executed to update table, an fault message should be generate.

We can find the fault message in the sxi_monitor of ECC server, right? we cannot find the fault message in PI side? so it is just helpful for ecc team to monitor?

If it is Async scenario, and from SAP ECC to 3rd party.

we can create the fault message and add into inbound service interface, but i don't know what will happen if an application error occurs in 3rd party.

I guess java program is created in 3rd party to generate the fault message, but also not helpful to PI team, i mean PI team cannot get the error, It is right?

***************************************************************

I will very appreciate you for any answer.

Thanks,

Sep

[rajasekhar_reddy14 · Accepted solution]

Fault message type mainly usefull at ABAP Proxy receiver scenarios.

http://scn.sap.com/people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1

[Former Member · Accepted solution]

This is a very helpful blog,

[ambrish_mishra]

Hi ,

My response below:

If it is Sync scenario,

(1) Create the fault message types for request and response.

(2) Add into outbound/inbound service interface.

(3) Create mapping for fault message types, not required if they are same.

(4) add the fault message mapping into operation mapping.

if there is any application error in target side, a fault message will be response and sent to PI, PI will sent it to source.

Is it correct?

fault messages in ABAP proxies are specific to application errors in ECC. It has nothing to do with the source system. Having said that, the fault messages can be mapped and sent to the target system and vice versa.

****************************************************************

If it is Async scenario, and from 3rd partyto SAP ECC.

(1) Create fault message type and add into inbound service interface.

(2) Proxy program should be generated in ECC for main proxy message and fault message.

Now i have one doubt, if an application error occurs when the proxy program is executed to update table, an fault message should be generate.

We can find the fault message in the sxi_monitor of ECC server, right? we cannot find the fault message in PI side? so it is just helpful for ecc team to monitor?

yes, that's correct.

If it is Async scenario, and from SAP ECC to 3rd party.

we can create the fault message and add into inbound service interface, but i don't know what will happen if an application error occurs in 3rd party.

I guess java program is created in 3rd party to generate the fault message, but also not helpful to PI team, i mean PI team cannot get the error, It is right?

It is an Async scenario so how can you expect third party to send back a fault message to PI. Since it is an application error at third party side, what benefit will PI get in having such a message

***************************************************************

Hope it helps!

Ambrish

[Former Member]

yes, Ambrish, this is helpful.

but for the sync scenario, you can check below blog

http://scn.sap.com/people/jin.shin/blog/2007/05/21/handling-web-service-soap-fault-responses-in-sap-...