PI 7.11 SOAP to SOAP: Cannot create target element /ns0:e

[Former Member]

Hi there,

I've created an asynchronous SOAP to SOAP scenario (SAP ECC to Third-Party) using one external definition.

When I import the WSDL from PI into SoapUI, it works fine, but when I use an ABAP proxy it gives me the following error:

Runtime exception occurred during application mapping com/sap/xi/tf/_MM_Employee_OUT_; com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns0:e. Values missing in queue context.

This is definitely not a mapping issue, because I'm just loopthroughing the same external message.

In the payload everything is correct except the outer wrapping tags:

In ABAP proxy it's "<nr1:p2.setEmployeeRequest xmlns:nr1="urn:employee.soap">".

But it should be (as used in SoapUI from the imported WSDL) "<ns0:e xmlns:ns0="http://source.employee">".

I've already recreated the ABAP proxy, but it's still the same.

How can I solve that issue?

I've called PI WS via ABAP proxy before without such problems...

Thanks in advance!

[markangelo_dihiansan]

Hello,

In ABAP proxy it's "<nr1:p2.setEmployeeRequest xmlns:nr1="urn:employee.soap">".
But it should be (as used in SoapUI from the imported WSDL) "<ns0:e xmlns:ns0="http://source.employee">".

Can you paste your wsdl here (just remove the endpoints)? Did you use the WSDL in generating the proxy?

Hope this helps,

Mark

[Former Member]

Here it is:

[WSDL|http://www.file-upload.net/download-4035703/Employee_Master_ServiceSDN.wsdl.html]

This is the original WSDL which could not be imported to SAP ECC because it contains extension tags:

[WSDL original|http://www.file-upload.net/download-4035711/Employee_Master_ServiceSDN2.wsdl.html]

Yes, the WSDL has been imported from XI repository when creating the proxy.

[Former Member]

Those are the two payloads:

[From ECC|http://www.file-upload.net/download-4035747/SOAP_Payload_ECC.xml.html]: evokes error message "Cannot create target element /ns0:e"

[From SoapUI|http://www.file-upload.net/download-4035748/SOAP_Payload_SOAPUI.xml.html]: works as expected