cancel
Showing results for 
Search instead for 
Did you mean: 

Publish Function Group as SOAP Web Service

Former Member
0 Kudos

In previous versions of SAP it was easy to mark a function module as RFC-enabled and, when the function group was generated as an enterprise web service, it was automatically visible in SICF under.

http://mysapserver.com/sap/bc/srt/rfc/sap/zmyservice

Our older function groups are still available and we get a functioning WSDL if we do this:

http://mysapserver.com/sap/bc/srt/rfc/sap/zmyoldservice?wsdl

[This article|http://blog.mindsquare.de/tobias_harmes/2011/01/abap-webservices-mit-dem-soa-manager-anlegen/] describes the easy process we are used to.

However, all new function groups generate useless services with no bindings:

http://mysapserver.com/sap/bc/srt/rfc/sap/zmynewservice?wsdl

We've tried various things in SOAMANAGER but not found out how to create the bindings or understood why this extra work is even required. When we click "Display selected Binding's WSDL URL" we get "Error: No data for binding key """ but there is no "create binding" or list of bindings. What to do?

Accepted Solutions (1)

Accepted Solutions (1)

mahesh_madhavan
Participant
0 Kudos

Hi,

Try this:

Run SOAMANAGER transaction. Goto 'Business Administration' tab -> Web Service Administration. Now here in 'Search pattern' field enter the name of the webservice you've created and click on 'Go' button.

Now select your web service that appears below and click on 'Apply selection'.

From the screen that appears in bottom, go to 'Configurations' tab and check whether a service has been already created or not.

If not, click on 'Create Service' and create a new service making the necessary configurations.

Hope this works

Regards,

Mahesh M.S.

Former Member
0 Kudos

In our installation the wording is slightly different. Instead of

'Business Administration' tab -> 'Web Service Administration'

we have

'Application and Scenario Communication' -> 'Single Service Administration'

But that solved it.

Interestingly the old services work fine and have neither "service" nor "binding" under "Configuration".

mahesh_madhavan
Participant
0 Kudos

Hi,

Yes. The wordings and environment differs in each system depending on the R/3 version etc. Anyway how did you solve it? Could you elaborate it.

Cheers,

Mahesh

Former Member
0 Kudos

I did exactly what you said: under "Configurations" I clicked "Create Service", called it "A" and also the binding name "A". After saving I could click on "Display selected Binding's WSDL URL" and I got this:

http://mysapserver.com/sap/bc/srt/wsdl/bndg_E0DE851E6D72E2F1B2B1231B789239EE/wsdl11/allinone/ws_poli...

I guess this long binding ID is SAP's idea of security...

mahesh_madhavan
Participant
0 Kudos

Hi,

Hey you can award points if i was of any help!

Cheers,

Mahesh

Former Member
0 Kudos

Sorry, I thought points were automatically awarded when I replied and said "answered".

Former Member
0 Kudos

Hi,

To both parties concerned, please get acquainted with the [Rules of Engangement|http://wiki.sdn.sap.com/wiki/x/FgQ] on SCN.

There are very clear instructions there on how to award points where necessary.

There are also very clear instructions on how NOT to solicit points, for example the statement below is prohibited, please refrain from it:

Hey you can award points if i was of any help!

Regards, Trevor

Answers (0)