Data provision code patterns are designed specifically for developers implementing data provider classes on the OData Channel. Developers can generate data provision code patterns by using the Generate Backend Operation Proxy option, which is based on the generation tool, Backend Operation Proxy (BOP). You can also use the BOP tool to generate local types for an RFC. The Generate Backend Operation Proxy provides a link to the BOP tool and generates the code to invoke the RFC based on the corresponding BOP generated local types.
This document guides you to generate Backend Operation Proxy:
To use the code patterns, you must install the component IW_BEP in your system.
The Backend Operation Proxy Generator is supported only from SAP NetWeaver 7.0 version and above.
To Generate Backend Operation Proxy and use the generated source code in your data provider class, proceed as follows:
Start the ABAP Workbench in transaction SE80.
Open a local report, for example, ZHS_TEST and choose the Edit button. After you have switched to editing mode, the Pattern push-button in the application toolbar becomes active.
Place your cursor at the position in the source code where you want the RFC to be called.
Choose the Pattern push-button. The Ins. statement dialog box is displayed. Alternatively you can also press Ctrl+F6. .
Select the Other Pattern radio button and enter the technical name of the OData Channel pattern in the corresponding input field /IWBEP/FM_MGW_PATN. Input help is available for this field.
In the dialog box ODC Code Pattern Selection Screen, select the radio button Generate Backend Operation Proxy under Data Provision.
After you have specified where you want to implement the generated code in your data provider class and selected the Generate Backend Operation Proxy, you need to provide details for generating the BOP in the OData Channel : Generate RFC BOP NG screen. To generate BOP, proceed as follows:
In the RFC Destination field, enter the RFC Destination. Input help is also available that displays a list of system IDs as possible RFC destinations together with a suitable description from which you can select the relevant entry.
In the RFC Name field, enter the technical name of the RFC, for example, BAPI_FLIGHT_GETLIST. You can use the input help to select from a list of existing RFCs, but this can be very performance intensive due to the potentially high number of possible RFCs available.
In the BOP Interface Name field, enter the technical name of a suitable Backend Operation Proxy (BOP) class that will be generated. This interface will contain the types declarations for the parameters of the Remote-Enabled Function Module.
Enter the package name to which the object belongs to in the Target Package.
Enter a valid Transport number.
Now you have two options:
Click Execute to generate the BOP without any customizations.
Select the Customize RFC Call Parameters check box to customize the BOP generation.
The row(s) for the mandatory parameters in the RFC will be non-editable.
On selecting to customize the rfc call parameters, the RFC Call Parameters window displays.
Click the tabs Importing, Exporting, Changing and Tables to navigate between them. The selected tab will be highlighted.
Select/Unselect the parameters to be displayed in the RFC call using the check boxes.
Once done with the selections; click Execute or press F8 to generate the BOP.
A message window displays if the BOP Interface Name already exists. Click Yes to overwrite, and No to stop the generation process and change the BOP Interface name.
On successful BOP generation the code gets generated in the ABAP Editor. Also the message RFC BOP Generated displays in the status bar.
The Call RFC code pattern generates source code and inserts it at the position you placed your cursor. Choose Save to save your changes.
For a step-by-step guide about how to use the data provision code patterns, see Using Data Provision Code Patterns.