You want to use an electronic form to call a BAPI. This is necessary, for example, if the user does not have access to SAPGUI. As the user has no technical know-how at all (and perhaps do not even know that they have called an R/3 System), a potential error message should not go back to the user, as would be the case with direct calling of a BAPI.

The use of IDocs would be suitable here as a recipient can be entered. In contrast to direct calling, it is then the recipient (for example an administrator) who has to correct the error.

This scenario is just one example of how IDocs can be used in conjunction with SAPforms. Naturally, the entire functionality of the IDoc interface can be leveraged with electronic forms.

In the process described here, it is assumed that you are using Visual Basic. This also applies to the individual sections in this chapter. However, you can also design forms with MS Outlook .

To call a BAPI from an electronic form using an IDoc, you must carry out the following steps:

• Generate the IDoc using a BAPI

• Defining a partner profile

• Design the electronic form

• Maintain the plug-ins.
• Open the IDoc structure

• Define the binding