Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Unexpected namespace change after mapping change

Unexpected namespace change after mapping change

Posted: Apr 18, 2006 5:17 AM Reply

Hi all

We developped a mapping about one year ago on XI SP9.

The source of the message was an Idoc and the target an XML sample (and not a xsd!) of what our customer expected.

Everything was working fine at that point.

Here is an extract of the output we had:

<?xml version="1.0" encoding="UTF-8" ?>

<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/ http://schemas.xmlsoap.org/soap/envelope/">

<env:Header xmlns:p="http://localhost/webs/msgDetails.xsd">

<p:msgDetails xmlns:p="http://localhost/webs/msgDetails.xsd">

<p:sender>

<p:senderId>XXX</p:senderId>

<p:senderName>AUSTRALIA/NEW ZEALAND</p:senderName>

</p:sender>

...

We are now running SP14 and we had to change the mapping. Since we changed it the namespaces defined in the sample XML we use as a target structure are not used anymore, instead they are replaced by ns0, ns1...

Now the output looks like this:

<?xml version="1.0" encoding="UTF-8" ?>

<ns0:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns0="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://www.w3.org/2001/XMLSchema-instance" ns1:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/ http://schemas.xmlsoap.org/soap/envelope/">

<ns0:Header>

<ns2:msgDetails xmlns:p="http://localhost/webs/msgDetails.xsd" xmlns:ns2="http://localhost/webs/msgDetails.xsd">

<ns2:sender>

<ns2:senderId>21873</ns2:senderId>

<ns2:senderName>XXX</ns2:senderName>

</ns2:sender>

...

Any idea what has happened here?

Thanks in advance

Gregory

Not what you were looking for? View more on this topic or Ask a question