Skip to Content
author's profile photo Former Member
Former Member

Fault Message from Sender System to Receiver System

Hi

I have a synchronous scenario

<b>SAP R/3 --> RFC Adapter -> XI -> SOAP Adapter --> Web Service</b>.

When web service returns successful response, it gets mapped properly to an internal table of RFC. But, when web service returns fault message (as parameters passed to the web service are incorrect), RFC gives dump. Below message is shown in sxmb_moni.

<i><?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Call Adapter

-->

- http://sap.com/xi/XI/Message/30" xmlns:SOAP=" http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">

<SAP:Category>XIAdapterFramework</SAP:Category>

<SAP:Code area="MESSAGE">GENERAL</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: java.io.IOException: invalid content type for SOAP: TEXT/HTML</SAP:AdditionalText>

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack />

<SAP:Retry>M</SAP:Retry>

</SAP:Error></i>

<b>{</b> Sometime AdditionalText has different message, depends upon what parameters Sender system is providing <b>}</b>

Now I would like to provide this message back to SAP RFC. Even if I will create the Fault message type, how exactly I can map this " Exception message " with my fault message type.

I have checked weblog <a href="/people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1 Message Types - A Demo</a> but this one talks more about proxy & Asynch scenario.

Can you pls. provide steps with which I can map exceptions message of WS to RFC.

Best Regards

- Lalit Chaudhary -

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Posted on Feb 26, 2007 at 04:53 AM

    Lalit,

    ><i><SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: java.io.IOException: invalid content type for SOAP: TEXT/HTML</SAP:AdditionalText></i>

    This is a standard error.Your webservice expects a APPLICATION / XML as the content type. This can be handled by the Message Transform Bean .

    Look into this Thread and Stefan's answerr on how to handle this,

    soap-receiver--how-to-convert-applicationxml-of-pa

    Regarding your other question~ Sending Fault Message Back to RFC,

    1. In your RFC , is a fault mesage defined?

    2. In the Wbeservice, is the Fault Message Defined?

    If yes for 1 and 2, then in your Inbound Message Interafce of the Webservice, select the fault message. Like wise do the same for the RFC also.

    Now, in the interface mapping you will find a new tab called "Fault" and you can map the Fault message of the webservice to the RFC fault message and this will trigger the messge back to the RFC.

    Regards

    Bhavesh

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Feb 26, 2007 at 05:26 AM

    Hi

    Please see the below links...

    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

    Chilla...

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.