XI Errors

[Former Member]

Hello,

We have a requirement to map the XI error to response.

for eg

XI Error:

<SAP:Error><SAP:Category>Application</SAP:Category><SAP:Code>MAPPING.EXCEPTION_DURING_EXECUTE</SAP:Code><SAP:P1>com/sap/xi/tf/__{</SAP:P1><SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2><SAP:P3>Fatal Error: com.sap.engine.lib.xml.parser.Parser}</SAP:P3><SAP:Stack>com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/___{: Fatal Error: com.sap.engine.lib.xml.parser.Parser}</SAP:Stack></SAP:Error>

to

HTTP Response:

<ErrorInfo><Code>XIError</Code><Description>Mapping Error</Description></ErrorInfo>

Is this possible?

It is synchronous scenario HTTP --> RFC.

Thanks,

Beena.

[Former Member]

hi

make use of

EXCHANGE LOG DATA

EXCHANGE FAULT DATA

regards

kummari

[Former Member]

One way is to catch the exception in BPM but it will not tell what type of error was thrown.

In our scenario, sender application handled it in their code.

Thanks,

Beena.

[ParvathyS_SAP]

Fault messages are provided for handling application errors.

You can create fault message types explicitly for message interfaces in the XI IR. You can use fault messages to handle errors triggered by the called application or persist them for monitoring purposes

Synchronous Communication (Inbound/Outbound/Abstract):

An error is triggered at the receiver that is providing a service; the error is handled by the sender that called the service.

Asynchronous Inbound Interface:

Fault messages are not used here to handle an error at the sender. The fault message generated by the triggered error is persisted for monitoring instead.

Fault message type:

__http://help.sap.com/saphelp_nw04/helpdata/en/dd/b7623c6369f454e10000000a114084/frameset.htm

For dealinf with exception:

http://help.sap.com/saphelpnw04/helpdata/en/33/4a773f12f14a18e10000000a114084/content.htm

[Former Member]

yes, it is possible to map the erro to response...by using fault message types.

u r using Sync case for eg if you want to return the XI error to HTTP,

Http will have a response message type.

so create a fault message type.

create a message mapping between these two MT as usually.

create message interface also and specify these in ID.

when you create the fault message type; XI automatically catchs the error in that, so mapping map fault message type to HTTP response message type.

Check this out.