Skip to Content

Soap error 'Bad envelope tag: definitions'

Hi everyone,

I am currently doing some tests on web services going through PI and I got stuck upon an error that I can't find the cause. I am sending a synchronous web service using SOAP UI that goes to SAP PI, which maps it to my SAP ECC web service and then comes back. I am using SOAP for both request and response.

When I look into SXMB_MONI, both the resquest and the response shows as red(error) with this error message: org.xml.sax.SAXException: Bad envelope tag: definitions

My quality of service is set to Best effort in both ways. When I tried the Only Once option, the call did not show any error but I never received any response either.

If anyone has an idea on what could actually cause this issue, i'd be glad to hear it.


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • avatar image
    Former Member
    Apr 12, 2016 at 09:59 PM

    it looks the test message you are using is not in correct format/invalid. Try test with valid xml message.

    Add comment
    10|10000 characters needed characters exceeded

  • Apr 13, 2016 at 04:36 AM

    Hello Maxime,

    Seems to be a data issue.

    Check the payload if the tags are well formatted.

    Get the payload from monitoring and test it in mapping, wrong tags can be identified.

    Add comment
    10|10000 characters needed characters exceeded

  • Apr 13, 2016 at 08:14 AM

    To me it looks to be the case with the response. While both the request and response messages show error it is to show that the entire message is in error. In reality as the asynch went through to PI, it seems to be the case where when the response comes over from ECC something goes wrong.

    Can you check which step there error is in? Share more details on the error message from Trace?

    In all likelihood it could be the response XML being invalid or mapping failing but would need more info to look further.



    Add comment
    10|10000 characters needed characters exceeded

  • Apr 13, 2016 at 12:40 PM

    Thanks guys for the reply.

    Using the payload of the request call adapter, I am able to call the SAP ECC web service directly from soap ui, instead of going through PI.

    Here's my payload:

    If I take this, and put it in my soap request like this:

    My SAP ECC web service respond perfectly:

    When going through PI, the response doesn't even have a payload at all. The request has the error message but only in the response message:

    I hope these additional information can help. Thanks for the support!

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Bhavesh,

      Unfortunately there are no error log when calling the web service through PI. I tested using SOAP UI to call directly the SAP ECC web service including an error and the message showed up. But that's the only error message i can see there.