Folks,
In our application, we use standard BAPIs heavility. So far we used SAP .NET connector to generate the proxy code. However, as SAP is moving towards web services, we are changing our code to consume web services.
We now need to define guidelines for our customers to expose the BAPIs that we use as web services.
The web services wizard requires two names to be defined for each BAPI/RFC - 1) a virtual interface name and 2) a web service name
As part of our guidelines, we are proposing that the customer simply add VI and WS in front of the BAPI name. For example, BAPI_MATERIAL_SAVEDATA would have VIBAPI_MATERIAL_SAVEDATA as the virtual interface and WSBAPI_MATERIAL_SAVEDATA as the web service name.
Before we put that in the guidelines, I just wanted to check if there is any standard that is already in place. I would appreciate it if you could share your thoughts with me.
Thank you in advance for your help.
Regards,
Peter