Exposing RFC as Web Service and Consuming Web Service in Interactive Forms in ABAP Applies to: SAP Interactive Forms by Adobe and Web Service in ABAP. For more information, visit SAP Interactive forms by Adobe Home page. For more information, visit the Web Services homepage. Summary This document explains step by step procedure to expose RFC Function module as web service and consuming that web service in Adobe interactive forms for offline use. Author: Sanjeeva Reddy Gujjula Company: Yash Technologies Pvt Ltd Created on: 08 October 2009 Author Bio Sanjeeva Reddy Gujjula is currently working with Yash Technologies Pvt Ltd as Consultant. He has over four years of experience in SAP technologies like ABAP, Enterprise Portal, WebDynpro for JAVA and WebDynpro for ABAP and Adobe interactive forms. 2009 SAP AG 1
Table of Contents Introduction... 3 Creation of Web Service... 3 Creation of Interface... 9 Creation of Form Layout... 9 Related Content... 11 Disclaimer and Liability Notice... 12 2009 SAP AG 2
Introduction Adobe forms can be used for online and offline purpose. In the case of offline usage we can integrate web service, so user can save adobe form locally and can fill data and submit data by clicking button. By calling Web Service on clicking submit button, it will connect to SAP System and process data. For this purpose we can use RFC enabled function modules as web service. If we provide logon details while configuring Web Service, user will not prompt for password other user will be prompted for password. Based on the application usage proper security can also be implemented here. This document is divided into 3 steps and explained with screen-shots. 1. Creation of Web Service 2. Creation of Interface 3. Creation of Adobe Layout Creation of Web Service Go to SE80 and select Package in Dropdown and right click on package and choose Create->Enterprise Service/Web Service->Web Service Web Service Wizard will open as shown below 2009 SAP AG 3
Give Service Name and Short Text and specify Endpoint Type (This case it is Function Module) Enter Function Module and choose check box Maping der Namen 2009 SAP AG 4
Leave Basic Authorization as it is and select Check box Release for Runtime 2009 SAP AG 5
Finally Complete Create or assign to a request number in pop-ups after complete Go to WSCONFIG and provide Service Definition and Variant Double click on Service and screen will look like as fallows and click on ICF Details in new screen 2009 SAP AG 6
In new screen double click on the service opened Change from display mode to Change mode and provide Logon Data (Client user id and password) and save the changes. 2009 SAP AG 7
Go to WSADMIN and Select your Service in Tree and press button WSDL on tool Bar, pop up will come as show on screen Shot and leave as it is and press ok. Browser will start with URL like: http://<fqdn>:8000/sap/bc/srt/rfc/sap/zbankdetails1?sap-client=900&wsdl=1.1 2009 SAP AG 8
Creation of Interface Create one dummy interface using SFP without any parameters. Creation of Form Layout Create form using Interface created in above step In data view Palette right click and choose New Data Connection Specify Data Connection name and choose radio button WSDL as shown below Enter URL Generated in End of Step1 and press next Choose Operation and Press Finish 2009 SAP AG 9
After Finishing, Data View Palette will get updated with some data along with one button. That button used to execute Function Module wrapped in Web Service Design Layout with Import and Export Parameters and Button as shown above. Now By executing the form in Form Builder you can get PDF Generated and by saving locally use that PDF for Offline Interactive form. 2009 SAP AG 10
Related Content SAP Interactive Forms by Adobe Creating a Web Service PDF-Based Print Forms For more information, visit the Web Services homepage. For more information, visit SAP Interactive forms by Adobe Home page 2009 SAP AG 11
Disclaimer and Liability Notice This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document. 2009 SAP AG 12