Problem with SOAP Runtime

[Former Member]

Hi folks,

I've got an issue concerning the AS ABAP SOAP Runtime. The system is an ERP 6.0 with SP13.

At first I create a Web Service by using the context menue of an existing rfc-enabled function module. Afterwards the service is visible in SICF. If I try to test the service in WSADMIN by using the test-button I only get an exception in the opening internet browser:

Cannot download WSDL from http://serverurl:8027/sap/bc/srt/rfc/sap/ZSTMA_FUNKTIONSTEST2?sap-client=100&wsdl=1.1: Invalid Response Code: (400) Bad Request. The requested URL was:"http://ciswi.sap.swm.de:8027/sap/bc/srt/rfc/sap/ZSTMA_FUNKTIONSTEST2?sap-client=100&wsdl=1.1"

If I go onto the used url I get the following message:

Your request could not be processed

SRT: ASSERT failed: object reference not bound

What has happened?

A Soap Core Exception was raised in Method CL_SOAP_REGISTRY::generate_wsdl(6)

Technical Details of Soap Core Exception

Message Text: SRT: ASSERT failed: object reference not bound

Class: CL_SOAP_REGISTRY

Method: generate_wsdl

LocationID: 6

Program: CL_SOAP_REGISTRY==============CP

Include: CL_SOAP_REGISTRY==============CM00J

Line: 59

What can I do?

* Contact your system administrator and show him the technical details above.

Has anybody an idea how to resolve this issue?

I have read many threads concerning this error - everybody talked about an authorization issue. In my case both I and the communication user have got SAP_ALL.

Thank you very much

[David-Broughton]

I am having the same problem for some web service, but not for others. Do you have any news?

[Former Member]

Hi David,

I thought the web service doesn't work because of the error message I got doing the web service test in the ABAP Workbench.

I tested with SOAP UI 2.0 and it worked. Meanwhile we have installed EhP3 thus we have version ERP603 now with the latest SOAP runtime - and up till now there haven't been any problems using it.

So I would suggest try to download the wsdl file and import it into SOAP UI 2.0. Probably the test function doesn't work correctly in older SOAP runtimes.

There's also a topic with SAP standard BAPIs which aren't supposed for remote use - there you can also get an SOAP error (example: a function module capsulates screen elements).

I hope I could help you - if not, don't hesitate to tell me more about your issue.

With kind regards.

Martin Steinberg

[Former Member]

Just one error in my last statement: I didn't mean BAPI's which are not for remote use - I meant standard function modules provided by SAP without remote use.

Do you want to access an own function or a standard one?