Well those two messages are completely different from a SOAP and xML point 
of view. To tell which is the correct one you'd need to see the WSDL for the 
service. As the namespaced message works I suspect that one is correct and 
SAP is building the request incorrcetly.

-- 

Joe Fawcett (MVP - XML)
http://joe.fawcett.name

"farenka" <farenka@h...> wrote in message 
news:1190037616.570286.224800@5......
> Hi,
>
> I developed a web service in .Net 2.0. It works fine using clients
> written in .net (C# or Vb)
>
> I'm experiencing some problems when a SAP application tries to connect
> to my web service.
>
> I analyzed the SOAP request and I noticed the following:
>
> The correct SOAP  request looks like:
>
> <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
>  <SOAP:Header />
> <SOAP:Body>
>    <m:My_Function xmlns:m="http://www.dummy.com/">
>      <m:Header>
>         <m:ID>AAF002</m:ID>
>      </m:Header>
>    </m:MT_CreateCustomer_RES>
>  </SOAP:Body>
> </SOAP:Envelope>
>
> The SOAP request built by SAP is:
>
> <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
>  <SOAP:Header />
> <SOAP:Body>
>    <m:My_Function xmlns:m="http://www.dummy.com/">
>      <Header>
>         <ID>AAF002</ID>
>      </Header>
>    </m:MT_CreateCustomer_RES>
>  </SOAP:Body>
> </SOAP:Envelope>
>
> The only difference is the missing "m:" prefix in the tags beneath the
> declaration of the namespace "m:".
>
> The result is My_Function receiving empty parameters.
>
> Since it should not a bug on the SAP side (I found other examples on
> the web, with requests without prefix in the inner tags) do you know
> any way to accept such kind of request using .net, or you have some
> suggetions?
>
> Thank you in advance!
>
> Frk
>