Skip to Content
avatar image
Former Member

Handling SOAP fault

Hi,

we call a web service from Netweaver 7.0 ABAP system through PI.

So the scenario is Netweaver 7.0 ABAP -> PI -> Web service (HTTP SOAP)

When the web service gives a SOAP Fault, it returns an error message which we want to be able to get in the ABAP calling system. However , when a SOAP Fault happens the mapping fails and the only exception we get back in the abap system is

<SAP:Category>XIServer</SAP:Category>

<SAP:Code area="MAPPING">CANNOT_READ_PAYLOAD</SAP:Code>

How can we actually get the real fault message back to the abap system ... ?

Thanks.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    avatar image
    Former Member
    Jul 14, 2009 at 09:37 PM

    Dagnino,

    Can you please see shabharish blog on this:

    /people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1

    Regards,

    ---Satish

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi,

      I had seen this blog already... please note the scenario is ABAP XI Proxy Consumer -> PI => Web service

      It is a synchronous scenario .

      Thanks.

  • avatar image
    Former Member
    Jul 15, 2009 at 04:12 AM

    I hope you are using a mapping program in your scenario...

    When you define your SYNC OB and IN message interfaces you have the option of specifying the Fault message type in the MI....in this section specify the fault message for both the MIs......then build a Message Mapping between these two fault messages....then you will have one more option of Fault mapping in the Interface Mapping when you say Read Interfaces alongwith Request and Response mappings....in this fault mapping give the above developed fault message mapping.....in this way your fault message should go the Proxy......check if this is what you are looking for...

    Regards,

    Abhishek.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Its from a provider...

      I've done the interface part , imported the wsdl into external definition. The problem is for the fault. The wsdl of the provider does not describe the fault message structure.

      Thanks.