why sap client id does not work in web service call from .net

[former_member231528]

I use web service to call sap RFC function from .net, and the web service wsdl address is http://172.18.95.104:8000/sap/bc/soap/wsdl11?services=some_rfc_function&sap-client=130 , which is get the data from sap client 130 , now I want to get the data from client 180 , and I set the wsdl address to http://172.18.95.104:8000/sap/bc/soap/wsdl11?services=some_rfc_function&sap-client=180 , and the returned wsdl is the same as sap client 130 , in .net program, I get the data is from 130, not from 180, how can I do?

[Former Member · Accepted solution]

regarding your question :

WSDL is the same, but the connexion not :

SAP SIDE

1 - Check on your SAP client 180 that your RFC is available.

2 - Check that the SAP WebAS service soap/rfc is activated with transaction SICF (normally yes)

3 - Check that the RFC are exposed by SAP Soap/rfc service on the SAP WebAS.

4 - to test it you can create a alias with SICF and hardcode a user+password

.Net side.

WSDL describes the service. That's normal that the same because sap client is just a parameter. On your .net project search in the code generated by Visual Studio when you add a webreference the url of your connexion. And you just have to modify it... Can also do it in your own code... URL of the webservice should be modified by an attribute....

[Former Member]

Just a remark, regarding performance and security, it is alway better to connect SAP with a JCo, .Net Co and RFC proxy than with the Web services exposed by the SAP WebAS. The reason is that to do sap uses a specific services SOAP/RFC on the WebAS...

An other reason is that you develop you own webservices with .net connector you could aggregate datas and calls of BAPI to reduce the number of connexion (each costs a lot) and improve the performance.

To manage connexion to webservices provided by SAP WebAS, it depends of the setting of the SAP WebAS (http, htts, etc...) ... On codeproject you will find some examples.

Or I can post some C# codes if you need it

[Former Member]

Hi,

have you exposed the BAPI/RFC only in client 130 or also in client 180? If not log in to client 180 and expose here the BAPI/RFC, then try to get the WSDL again, this time form client 180, that should do the trick.

- Juergen

[Former Member]

You should activate the Client 180 web service and get the WSDL again from client 180 web service. the major issue was you change the WSDL directly.