‎2010 Mar 24 5:35 AM
Hello All,
We have a function module BAPI_EXCHANGERATE_GETDETAIL & web service created as ZBAPI_EXCHANGERATE_GETDETAIL.Testing the webservice is ok..But when the java team is checking it is giving error:
javax.xml.ws.soap.SOAPFaultException: Virtual Interface Method >BAPI_EXCHANGERATE_GETDETAIL::urn:sap-com:document:sap:rfc:functions< not supported
at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:146)
at $Proxy50.bapiEXCHANGERATEGETDETAIL(Unknown Source)
Can you please suggest
‎2010 Mar 24 6:45 AM
Hi Ashley,
Could you please provide more information like
1) When you say you tested the web service, how exactly did you test it? Did you use a 3rd party sofware like XMLSPY or MS WS Studio etc...
2) And is the Java team able to comsume the WSDL and create a client proxy? Do they get the error message while consuming the WSDL or while invoking the WS?
Regards,
Chen
‎2010 Mar 24 7:43 AM
Chen Yes the problem comes when they consume the WS..Please suggest.
‎2010 Mar 24 8:22 AM
Hi Ashley,
1) I suggest that you try comsuming the WSDL using XMLSPY or Microsoft Web Service Studio, and see if you are able to consume and invoke the call.
2) Alternatively, check with your Java team if they are consuming the WSDL directly using the WSDL URL provided by you or are they saving a local copy of the WSDL and trying to comsume this local file. If they are doing it directly using the WSDL URL, check if they have proper Proxy server settings on their app.
Also, since the error message is not descriptive enough, i would like to know more info on the BAPI (As i do not have access to an SAP system right now )
Does the BAPI have tables parameter? If yes, i suggest that you create a new Z RFC as a wrapper around this BAPI, and take all the table parameters under the export parameters of this new Z RFC. (Tables parameter is depracated and it is better to avoid it)
But before doing the above i suggest you try the first two points above.
All the Best !!!
Regards,
Chen