PI 7.11: Adapter Framework caught exception: null

Question

Hi,
I've a ABAP Proxy - to  - SOAP scenario.
Message mapping works.
In the communication channel monitor I get the following error:
MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException
Adapter Framework caught exception: null
In the log viewer in NWA I see the following two messages:
Marked transaction for rollback for meesage 516e304f-b083-8e3e-e100-00000a01095f(INBOUND). Reason: <null>
Caught exception com.sap.engine.interfaces.messaging.api.exception.MessagingException from application code with msgKey: 516e304f-b083-8e3e-e100-00000a01095f(INBOUND)
The payload for calling SOAP receiver looks like that:
<m:setEmployee xmlns:m="http://test.com" xmlns:fo="http://www.w3.org/1999/XSL/Format">
         <ns1:e xmlns:ns1="http://test.com">
            <address_Mail_Incoming_Type>
               <email>test.com</email>
               <phone>7890</phone>
            </address_Mail_Incoming_Type>
            <badge_ID>123</badge_ID>
            <cost_Center>321</cost_Center>
            <date_Hired>1980-01-01T00:00:00.000Z</date_Hired>
            <date_Of_Birth>1950-01-01T00:00:00.000Z</date_Of_Birth>
            <department>123</department>
            <division>ABC</division>
            <employee_Category>A</employee_Category>
            <employee_Code>1000</employee_Code>
            <employee_Id>1000</employee_Id>
            <employee_Status>ACTIVE</employee_Status>
            <first_Name>A</first_Name>
            <last_Name>B</last_Name>
            <letter_code_3>FRI</letter_code_3>
            <location>123</location>
            <position>123</position>
         </ns1:e>
      </m:setEmployee>
When I copy this payload into SOAP UI (surrounded by <soapenv:Envelope>, <soapenv:Header> and <soapenv:Body>), the WS call works.
The URL for the receiving CC should be ok (same as in SOAP UI), the "Do not use SOAP Envelope" checkbox is not flagged.
What can be the reason for that error message?
Thanks in advance!

Answer 1

I've now changed the setting of the external definition to "Using RPC style", but I'm still running into the same error than before:
10.02.2012 14:51:03 Information SOAP: sending a delivery error ack ...
10.02.2012 14:51:03 Error Adapter Framework caught exception: null
10.02.2012 14:51:03 Error MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException
10.02.2012 14:51:03 Information SOAP: sent a delivery error ack
10.02.2012 14:51:03 Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException.
The payload of the CC looks exactly the same than before:
<?xml version="1.0" encoding="UTF-8"?>
<m:setEmployee xmlns:m="http://test.com" xmlns:fo="http://www.w3.org/1999/XSL/Format">
     <ns1:e xmlns:ns1="http://test.com">
          <address_Mail_Incoming_Type>
               <email>test.com</email>
               <phone>123</phone>
          </address_Mail_Incoming_Type>
          <badge_ID>123</badge_ID>
          <cost_Center>123</cost_Center>
          <date_Hired>1990-01-01T00:00:00.000Z</date_Hired>
          <date_Of_Birth>1950-01-01T00:00:00.000Z</date_Of_Birth>
          <department>123</department>
          <division>ABC</division>
          <employee_Category>PERM</employee_Category>
          <employee_Code>1000</employee_Code>
          <employee_Id>1000</employee_Id>
          <employee_Status>ACTIVE</employee_Status>
          <first_Name>A</first_Name>
          <last_Name>B</last_Name>
          <location>ABC</location>
          <position>123</position>
     </ns1:e>
</m:setEmployee>
If I copy that payload (without <?xml version="1.0" encoding="UTF-8"?>) into SOAPUI (surrounded by SOAP envelope), the WS call works without any problem.
Why doesn't it work from PI?
Another question:
Why is it putting <ns1:e> into the payload of the new interface and <ns0:e> for the existing interface (which is working, see Re: PI 7.11: Adapter Framework caught exception: null)?
Could that be the reason why data is not sent properly to the SOAP receiver?