‎2012 Nov 29 3:30 PM
Dear SCN USers,
I was recently looking for this problem in this network and found out that lot of users have this issue, but till now I found nowhere a helpful answer.
So as I have now spent quite some time resolving this issue, therefore, would let you know what did happen in our case.
We had Generated WebServices with SOAP RFC Adapter. This can be done easily in SE80.
And the services worked perfectly fine in the Dev system. But after the transport in the Q-System, we started getting the Above error while calling these
services from the Consuming App.
After a lot of trial and error I decided to debug the SOAP API's and found out the issue as follows:
The Virtual Interfae definition is read from the Table VEPGENCLASS and this table had no entries for the Services in question in the Q-System.
So first step for you would also be to check the Entries in this table for your WebServices.(VEPNAME = Service Interface Name).
In case you do not find the entries then the issue is clear that the generated objects are missing in this system.
In our case the Generation of these objects failed during the Import of the WebServices... R3TR Entries:
Virtual End Point R3TR WEBI CRM_IC_ANALYTICS_MD_WS
The details of the Transport show that the generation happens in the Post-import method execution: WEBI_AFTER_IMPORT.
Hope this helps some of you who face the same problem.
Thanks and Regards,
Sumit
‎2013 Jul 08 5:20 PM
But, in your case how to solved this issue ?, we have the same problem in our system, thanks.
BS.
‎2013 Jul 10 2:05 PM
Hi Alberto,
Please retransport the WebServices definitions to the respective system. Check the Transport log, if it is free of errors, then everything should be fine.
If in case you see in the transport that the Generation failed, then ask the IT to generate these services in the target system.
There is a report in the system, which can do so, but has to be run with a proper user. For further details please check the IT/IBC message no. 0004848663 2012.
Hope this helps.
Cheers,
Sumit
‎2013 Jul 10 2:08 PM
Hi,
Another related internal message to this problem is, 4213140 2012, where the solution to the original problem has been provided.
Cheers,
Sumit
‎2013 Aug 19 5:29 PM
‎2013 Aug 20 7:17 PM
Hi Sumit,
We are experianceing the same issue - i was wondering how you resolved it. We would like to continue with the transport path verus setting up the service in each client.
Regards,
NP
‎2013 Aug 22 8:17 AM
Hi NP,
Please refer to the IT/IBC message no. 0004848663 2012, as mentioned in my second reply here.There you would also find the Note provided from Basis colleagues.
Thanks and Regards,
Sumit
‎2025 Mar 06 2:18 PM
Can you please provide the NOTE number to resolve this issue