Faulty WSDL Generated by SOAMANAGER

[Former Member]

Hi,

I have created a service for the service definition "ECC_SALESORDER009QR" in SOAMANAGER. After that, I tried to open the generated WSDL from the link "Open WSDL document for selected binding". Unfortunately, it contains only the following data:

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
 <soap:Body>
   <soap:Fault>
       <faultcode>soap:Server</faultcode> 
       <faultstring>Unexpected error: Incorrect value: Location URL for subject IF 
{http</faultstring> 
       <detail xmlns:slibfault="http://xml.sap.com/2005/11/esi/slib/fault/">
        <slibfault:timestamp>Mon, 14 Sep 2009 22:42:38 GMT</slibfault:timestamp> 
        <slibfault:exception>
           <slibfault:text>Incorrect value: Location URL for subject IF 
{http://sap.com/xi/APPL /Global2}:
SalesOrderERPBasicDataByElementsQueryResponse_In not found</slibfault:text> 
  <slibfault:position program="CL_SIDL_SUBJECT_ADAPTER=======CP"
include="CL_SIDL_SUBJECT_ADAPTER=======CM006" line="47" /> 
      </slibfault:exception>
     </detail>
  </soap:Fault>
  </soap:Body>
</soap:Envelope>

To further investigate the problem, I created few additional services for the other service definitions and discovered that only those with the namespace "http://sap.com/xi/APPL/Global2" have the same problem, while the others with the namespace "http://sap.com/xi/APPL/SE/Global" are free of the faulty WSDL.

Could anyone shed some light into this matter?

Regards,

Joon Meng

[Former Member · Accepted solution]

There is a note 1351078 regarding this issue. Some of the services in Ehp3 and ehp4 are faulty. You need to install supp pack 5 of the Ehp3 or run them through the old transactions wsconfig and then wsadmin instead where it is working.

[Former Member · Accepted solution]

Hi Peter,

Thanks for the reply. I think this is most probably the cause of the problem. Could you please provide me some good information how to configure a service in WSCONFIG and WSADMIN?

Thanks,

Joon Meng

[Former Member · Accepted solution]

Goto t-code WSCONFIG, search for the service in field service definition, then add a variant name ( same name as service ) and save. Goto wsadmin , there just browse for the service and click on button "WSDL file" to extract and open wsdl file in ypour webbrowser. This file can then be implemented into your portal environment or soapui as I use to test them with before development starts on portal.

[Former Member · Accepted solution]

Hi Peter,

thanks. The problem is temporarily solved with the use of WSCONFIG & WSADMIN.

Regards,

Joon Meng

[Former Member]

Hi,

This is because of some coding errors exist, Refer to SAP Note : 1166013 and install menioned correction (ask your SAP BASIS guy to help).

Regards,

Gourav Khare