Can't create proxy for web service (error "Unknown QName")

[Former Member]

Hi SOA experts,

I want to create a web service proxy object for an external web service, to call from within my ABAP reports. So I started the web service wizard from SE80 and entered the WSDL for the web service to call, but at the end of the wizard I get the following error:

Incorrect value: Unknown QName http://schema.company.de/Base:TechnicalFault

I am not sure why this error occurs, this may be the relevant section from the WSDL file:

 <types>
  <schema xmlns="http://www.w3.org/2001/XMLSchema">
   <import namespace="http://schema.company.de/Service/Customer_Accounting_BLS" 
      schemaLocation="Customer_Accounting_BLS.xsd" />
  </schema>
  <schema xmlns="http://www.w3.org/2001/XMLSchema">
   <import namespace="http://schema.company.de/Base" 
      schemaLocation="http://qrz1275.company.de:8888/orabpel/1.3.0/Base.xsd" />
  </schema>
 </types>

Any ideas why SAP is complaining with this?

Thanks in advance for your help!

Kind regards, Matthias

[Former Member · Accepted solution]

i'd bet that the namespace http://schema.company.de/Base doesn't contain an element TechnicalFault.

enter http://qrz1275.company.de:8888/orabpel/1.3.0/Base.xsd into your browser, hopefully you get the xsd if this is a valid location and find the field TechnicalFault.

if you do, I'm wrong, if you don't your WSDL is.

anton

[Former Member · Accepted solution]

Hi Anton,

thanks for your hint -- it seems you're right, there is indeed not such field "TechnicalFault" in the xsd file. Could you please explain what this field is used for and why SAP expects it in this xsd file?

Thanks again!

Kind regards, Matthias

[Former Member · Accepted solution]

Hi Anton,

you were right, this "TechnicalFault" field is indeed not within the XSD file you mentioned. But, this XSD file itself refers to another XSD file, were the "TechnicalFault" field is defnied. May it be that SAP can't follow this reference?

Kind regards, Matthias

[Former Member · Accepted solution]

well,

your base WSDL contains some definitions and it imports some other WSDL fragments. your WSDL seems to define parameters based on data types of the imported schema.... which do not exist.

this is what I would suspect not seeing much of your WSDL actually.

[Former Member · Accepted solution]

>

> Hi Anton,
> 
> you were right, this "TechnicalFault" field is indeed not within the XSD file you mentioned. But, this XSD file itself refers to another XSD file, were the "TechnicalFault" field is defnied. May it be that SAP can't follow this reference?
> 
> Kind regards, Matthias

hi matthias,

didn't know that, but AFAIK a lot of frameworks do not crawl WSDLs ad inifinitum and many resolve only one step. probably WAS ABAP wizards do this as well. it's up to you to decide if you open a customer message to SAP.

of course there's a (painful) manual workaround, which is to download all parts, get an overview, what is important and what isn't and simply create an analogue WSDL yourself. this means you try to find the definition of TechnicalFault for instance and simply define that data type locally. finally you adapt the referencing parameter and voila.

hope it helps,

anton