IDoc to SOAP Receiver Fault Message Handling?

Hi,
I am working on IDoc to SOAP Scenario (IDoc -> PI -> SOAP). It is in async mode without BPM. This works fine as long as there is no error on the SOAP receiver side. How to handle the falut message raised by the SOAP receiver and send it back the SAP ECC.
Do I need to use ALEAUD IDoc for this? If Yes, how to configure this to handle fault message? Is there any other way of doing it?
Could you please give steps to handle the fault message?
Thank you.
Regards,
Cdr.

Have a look into the below threads -
How to capture SOAPFault in an Async/Sync Scenario without BPM
Acknowledgement Handling in IDoc to SOAP Scenario in PI 7.3

Similar Messages

Soap receiver fault message/acknowledgements

hi all,
i have configured a scenario....
now i want to recieve an error status through soap reciver...and scenario would like...webservice client->XI->Webservice. Soap sender->XI->Soap Reciever......how can I recieve the exception...as raised during execution of webservice....
It would really very helpful if someone could throw some light on this..

Hi,
Is your scenario like this?
SENDER SOAP ADAPTER (Calling XI)<-> XI <--> RECEIVER SOAP ADAPTER (calling webservice)
Now if exception is raised during execution of receiver webservice, does the response from the webservice contains the status? If so, then do a response Map, so as to send the response message back to the webservice client.
Regards
Suraj

Fault message handling in BPM

Hi again xi fighters
I created a business process with a synchronous sending step. I defined all interfaces and implemented also an own fault message type within the synchronous abstract interface. If the used RFC got the correct data the sync. sending step worked proper and also the business process worked fine. If I providing wrong data to the RFC to force him to throw an exception the Business process received the fault message. Then I just want to send the received fault message asynchronously to a file adapter within the defined exception branch. And now the question no-one answered in several discussion threads ;-<
How can I send the message? I am not able to implement a new variable in the container for the fault message type. Any advises here?????
Please help me, before I got inshane of SAP ;->>
Regards Oliver
Message was edited by: Oliver Bluhm
Hi everybody
any ideas, or is the question not clear. Please have a look and let me know you exlperience!
Regards Oliver

Hi Oliver,
how do you know, that is impossible to read the content of the fault message in the exception branch? Did someone from SAP say that? For days I read all the notes, blogs, help,.. and didn't find an answer.
It should work.
1. I have an integration process in XI sending a sync message to R3.
- OK
2. In the generated proxy class I raise an exception of the generated exception proxy class.
- OK
3. The exception message is shown in the message monitoring, containing also all our customer-data.
- OK
4. The integration process in XI activates the correct exception branch.
- OK
Missing: How do I get a grip on the data in the error message?
Kind regards Philipp
Message was edited by:
        Philipp Jakob

Soap fault message handling in XI

Hi,
I am using axis 1.4. SAP XI is my clinet. My wsdl file as below
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions targetNamespace="http://ws.example.com/service"
   xmlns:wns="http://ws.example.com/service"
   xmlns:tns="http://ws.exampleenterprise.com"
   xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
   xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<wsdl:types>
         <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
                targetNamespace="http://ws.exampleenterprise.com"
                elementFormDefault="qualified">
                 <xs:complexType name="SecrtySbj">
                         <xs:sequence>
                                 <xs:element name="usrname" type="xs:string"/>
                                 <xs:element name="pswrd" type="xs:string"/>
                         </xs:sequence>
                 </xs:complexType>
                 <xs:complexType name="AuthenticateRequest">
                         <xs:sequence>
                                 <xs:element name="secrtySbj" type="tns:SecrtySbj"/>
                         </xs:sequence>
                 </xs:complexType>
                 <xs:element name="authenticateRequest" type="tns:AuthenticateRequest"/>
                 <xs:complexType name="AuthenticateResponse" >
                         <xs:sequence>
                                 <xs:element name="sessnId" type="xs:string"/>
                         </xs:sequence>
                 </xs:complexType>
                 <xs:element name="authenticateResponse" type="tns:AuthenticateResponse"/>
                 <xs:complexType name="customFault">
                         <xs:sequence>
                                 <xs:element name="customCd" type="xs:int"/>
                                 <xs:element name="customMsg" type="xs:string" minOccurs="0"/>
                                 <xs:element name="customExcp" type="xs:string" minOccurs="0"/>
                         </xs:sequence>
                 </xs:complexType>
                 <xs:element name="customFault" type="tns:customFault"/>
         </xs:schema>
</wsdl:types>
<wsdl:message name="authRequest">
   <wsdl:part name="parameters" element="tns:authenticateRequest"/>
</wsdl:message>
<wsdl:message name="authResponse">
   <wsdl:part name="result" element="tns:authenticateResponse"/>
</wsdl:message>
<wsdl:message name="CustomFault">
   <wsdl:part name="CustomFault" element="tns:customFault"/>
</wsdl:message>
<wsdl:portType name="AuthenticateServiceInterface">
        <wsdl:operation name="authenticate">
    <wsdl:input message="wns:authRequest" />
        <wsdl:output message="wns:authResponse" />
    <wsdl:fault name="CustomFault" message="wns:CustomFault"/>
   </wsdl:operation>
</wsdl:portType>
<wsdl:binding name="AuthenticateServiceSoapBinding" type="wns:AuthenticateServiceInterface">
          <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
   <wsdl:operation name="authenticate">
    <soap:operation soapAction=""/>
    <wsdl:input>
     <soap:body use="literal"/>
    </wsdl:input>
        <wsdl:output>
                <soap:body use="literal"/>
        </wsdl:output>
        <wsdl:fault name="CustomFault" >
                   <soap:fault name="CustomFault" use="literal" />
           </wsdl:fault>
   </wsdl:operation>
</wsdl:binding>
<wsdl:service name="AuthenticateServiceService">
   <wsdl:port name="AuthenticateService" binding="wns:AuthenticateServiceSoapBinding">
    <soap:address location="http://10.236.14.6:8080/axis/services/AuthenticateService"/>
   </wsdl:port>
</wsdl:service>
</wsdl:definitions>
Axis generates the soap fault as below in detail tag as below
<ns1:customFault xmlns:ns1="http://ws.examplenterprise.com">
<ns1:customCd>123</ns1:customCd>
<ns1:customMsg>Password is wrong</ns1:customMsg>
<ns1:customExcp>CustomException</ns1:customExcp>
</ns1:customFault>
They are getting error like below while getting the fault message.
<SAP:ApplicationFaultMessage namespace="http://ws.exampleenterprise.com">customFault<SAP:ApplicationFaultMessage>
Question: Why it is throwing "ApplicationFaultMessage" for fault messages? is there any error in wsdl file in defining the elements? or style has to be different? or is it an namespace issue in the wsdl?
Note: They are able to do it sucessfull for the response message.

Hi,
The answer is in your Question itself.
XI Sequence
1.First step is to identify the wsdl:Message element with the namespace http://ws.example.com/service
2.The next step is to go to the part element in http://ws.exampleenterprise.com and map the fault message.
To be simple in your case http://ws.example.com/service is the namespace of Fault Message and http://ws.exampleenterprise.com is the namespace of the fault message payload (Fault XML Message).
So even though the Fault XML Message has the namespace http://ws.exampleenterprise.com ,but if the fault namespace doesnot come with http://ws.example.com/service then Fault will not be triggered and processed in XI.
I hope you get the difference between the two namespaces used and the implications of them.
Fault is entirely different from respone.
Its like exception in java. If you donot catch the correct exception, will the exception raised be caught? Similarly if your SOAP service doesnot invoke the fault message with correct namespace (http://ws.example.com/service ), you cannot invoke/catch the fault message in XI.
Regards,
Sudharshan N A

Fault message handling in abap client proxy

Hi experts,
i have scenario like this SAPECC---XI---WEBservice
i was decided to using the ABAP CLIENT proxy in sender side and soap adapter communication in receiver side
i will be get the wsdl file form client
problem is i am in bit of confusion like am i need to create fault message for this asychronous scenario?
how can i create the fault message for this scenario(that WSDL) and how the abaperwill handle those error
thanks in advance

Hi.
You can use fault message but it won´t return a error to your ABAP Proxy because your interface is ASSYNC. The fault message generated will stop in Adapter Engine.
If you need a return of the error, you have to change your interface to Sync mode.
To get more information, follow the link below:
Fault Message Type
http://help.sap.com/saphelp_nwpi711/helpdata/en/dd/b7623c6369f454e10000000a114084/frameset.htm
Best Regards.
Bruno

Synchronous SOAP: Get fault message on ABAP side

Hi,
I've a synchronous ABAP Proxy => PI 7.11 => SOAP scenario.
The SOAP receiver is a third party application using AXIS 1.4.
When I call the SOAP receiver with bad input via SOAP UI I receive an error message like that:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   <soapenv:Body>
      <soapenv:Fault>
         <faultcode>soapenv:Server.userException</faultcode>
         <faultstring>com.ZZZ.exception.ZZZException: Employee not found: 9999911111</faultstring>
         <detail>
            <com.ZZZ.exception.ZZZException xsi:type="ns1:ZZZException" xmlns:ns1="http://exception.ZZZ.com"/>
            <ns2:hostname xmlns:ns2="http://xml.apache.org/axis/">server.YYY.com</ns2:hostname>
         </detail>
      </soapenv:Fault>
   </soapenv:Body>
</soapenv:Envelope>
When I call the SOAP receiver through my ABAP proxy, I just get this exception message in SXI_MONI:
<?xml version="1.0" encoding="UTF-8"?>
<com.ZZZ.exception.ZZZException xmlns:ns1="http://exception.ZZZ.com"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns1:ZZZException"/>
Nevertheless I see the error in SXI_MONI:
<?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>Application</SAP:Category>
    <SAP:Code area="SOAP">FAULT</SAP:Code>
    <SAP:P1>http://schemas.xmlsoap.org/soap/envelope/</SAP:P1>
    <SAP:P2>Server.userException</SAP:P2>
    <SAP:P3/>
    <SAP:P4/>
    <SAP:AdditionalText>com.ZZZ.exception.ZZZException: Employee not found: 9999911111</SAP:AdditionalText>
    <SAP:ApplicationFaultMessage namespace="">com.ZZZ.exception.ZZZException</SAP:ApplicationFaultMessage>
    <SAP:Stack/>
    <SAP:Retry>M</SAP:Retry>
</SAP:Error>
In the WSDL of the SOAP receiver there's just the ZZZException without fields faultcode or faultstring:
<complexType name="ZZZException">
<sequence/>
</complexType>
Do I have to add the fields faultcode or faultstring to the WSDL myself?
I tried the following, but it didn't work:
<complexType name="ZZZException" abstract="true">
    <xsd:sequence>
        <xsd:element name="faultstring" type="soapenc:string">
    </xsd:sequence>
</complexType>
Thanks in advance!

Hi Eddie -
Do I have to add the fields faultcode or faultstring to the WSDL by myself?
>>> No. Even though you add - it doesn't work as it's the webservice which returns the message.
For sending the fault messages, Have a look at the below blog -
Handling Web Service SOAP Fault Responses in SAP NetWeaver XI

SOAP receiver adapter message: PI payload in parameter or body

Hi,
We tried to send messages via the following way to an external partner: SAP --> IDoc > XI (7.1)> HTTP(s) --> external partner.
We tried 2 techniques:
1. using a HTTP receiver communication channel with HTTP destination (using certificate).
As the path prefix in the destination, including parameters, exceeds 256 characters, we had to search for another solution
2. using the SOAP receiver communication channel with a target URL (https string) and indicator 'Do not use SOAP envelope' set
When sending the message, the body of the message, the IDoc XML payload doesn't seem to be read by the partner, probably related to the fact that they do not use the right software to do so, as decribed in forum:
SOAP receiver adapter error (SOAP receiver adapter error.)
Is this the right interpretation and is there no other solution than try to append the payload to the parameterlist ?
Regards,
Jan Macken

The partner found a way to read the body correctly

IDOC to SOAP asynchronous scenario Error handling

Need an expert!!!!!!!!! advise on error handling for IDOC--PI--
SOAP scenario.This is a asynchronous scenario where PI is calling a Legacy system using SOAP adapter.My question is how i can do error handling in this scenario.If i get an alert in pi with payload variable that would be fine, do i need to use BPM and if that is tthe case what will be steps.
Appreciate your help.
Manish

Hello Manish,
My question is how i can do error handling in this scenario.
Use the standard alert framework. Search on SDN / SAP Help for details.
do i need to use BPM and if that is tthe case what will be steps.
BPM is not required to raise alerts, as this is an async call.
Regards,
Neetesh

SOAP Receiver Response Message

I have setup the following scenario:
Create PO in EBP --> XI --> Webservice
In the Repository I have set up both the outbound and inbound message interfaces as Synchronous. The interface mapping has been setup to map both the request and response messages.
In the Directory I have set up the SOAP receiver adapter and the receiver/interface determination and receiver agreement for EBP as the sender system and the external webservice as the receiver party/service.
When I create a purchase order in EBP the webservice is called successfully and the PO gets created on the target system. The webservice returns a response message which I am expecting to see via SXMB_MONI but is not currently showing!! Is there some Directory configuration that I am missing?
Any pointers would be appreciated.
Regards
Mark Briggs

Hi Mark,
>>>>n the Repository I have set up both the outbound and inbound message interfaces as Synchronous
is your scenario sync or async?
do the ID config with ID wizzard if you're not sure
if will guide you
if you have a sync scenario you shoudl see and error
if you have no response withint the timeout
do you see that in the calling application or in the XI ?
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

Fault message handling in BPM workaround?

Okay so we all know by now that SAP does not support fault messages in their ccBPM implementation of the BPEL standard.
My question is this.
Does anyone have a viable work around for a SOAP (or any other) interface?
I have altered my calling interface to return either a success response or a fault response in the normal response message e.g.
<?xml version="1.0" encoding="UTF-8"?>
<ns0:Response xmlns:ns0="">
   <Success>
   </Success>
   <Fault>
   </Fault>
</ns0:Response>
but I still need a way to get the SOAP adapter to return a fault message when the <Fault> segment of the above mesage is populated.
Thanks,
Stephen

Hi,
if fault part of message is filled, just trigger an exception or an alert..
cheers,
André

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

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.

SOAP Receiver/Sender in IDOC- XI- SOAP receivers?

hi,
i have idoc-> xi-> soap receiver.
1. How can i get a response back from soap receiver?
2. in the above scenario is SOAP the receiver or agian the sender?
3. not sure how i can get a response back from the soap receiver?
any tips would be helpful.
thanks,
tirumal

Hi,
It should be
<i>
Under Target URL, enter the complete address (URL) of the Web service provider that you want to send the message to.</i>
http://help.sap.com/saphelp_nw04/helpdata/en/29/5bd93f130f9215e10000000a155106/content.htm
What are you specifying?
Can you give the entry in Target URL...
Regards
Suraj
Message was edited by: S.R.Suraj

SOAP receiver message failure

Hi,
Scenario is an async message from SAP to a third party (SOAP receiver)
This message staus is delivered in adapter logs of RWB.
Also there is the payload (before mapping and after mappings till technical routing also) can be seen from sxmb_moni.
Thre problem is that the message data is not uploaded to that third party.
The communication channel is having correct URL (tried with WSDL home page and URL pointing to WSDL file/code like with '?WSDL' ) and SOAP action is also provided (also tried without SOAP action and got an error related to SOAP action).
These are the only 2 places (target URL & SOAP action) are maintained in communication channel. There is no any proxy/authentication required.
What cld be the reason of this ?
The TP web service is working fine with soapUI.
Regards,
Sachchidanand

Hi Kulwant,
Thanks for ur help.
In sxmb_moni, message status is successful.
As ur suggestion I just checked with soapUI message structure and found that..
1. soapUI tool message structure contains empty header <soapenv:Header/> and in the <soapenv:Body> all the wsdl fields/heirarchy is there.
2. In sxmb_moni payload (@ tech routing) there is no any header , it shows the structure like its in <soapenv:Body> of soapUI or its like message mapping heirarchy.
And there is no any custom authentication part visible in soapUI also.
Thanks,
Sachchidanand

Automizing error message with Fault Message Type

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

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

IDoc to SOAP Receiver Fault Message Handling?

Similar Messages

Maybe you are looking for