Backend Operation Proxy (BOP) is the standard way to communicate with the backend. It encapsulates a single RFC call or a web service operation call and consists of two or more classes, with a BOP Data Object (BOP DO) class per BOP. BOPs for a specific business entity is grouped in an EDP.
To generate BOP for RFC, proceed as follows:
In transaction SPRO open the SAP Reference IMG and navigate to: and click the Activity icon.
Enter the following parameters:
Field |
Description |
System Alias |
System alias of the SAP Business Suite system. See Configurations on SAP Gateway for SAP ERP section for information on Managing SAP System aliases. |
RFC Name |
The name of the RFCs (remote—enabled function module) in the SAP Business system |
Base Class Prefix |
The name of the main BOP class containing the type information of the request and response structure of the RFC. This name is used as the prefix for the data object and default proxy classes. This class name must contain a namespace, if applicable. The base class name is used as the BOP ID. Note
Make a note of this BOP ID. This is required while Implementing EDP. |
Target Package |
The name of the package to which the BOP is added. The package must already exist. To add BOPs to your local objects, enter '$TMP'. |
Transport |
If the BOP will be transported, create a workbench transport and provide the transport number. For local objects no transport request has to be entered. Note
The user who generates the BOP must be the owner of the request. |
Node in the SAP GW CCMS Context |
The default option is BE OUTB SERV. |
To generate BOP for Web Service (WS), proceed as follows:
In transaction SPRO open the SAP Reference IMG and navigate to: and click the Activity icon.
Create a Web service consumer proxy by using the transaction SPROXY.
Enter the following parameters:
Field |
Description |
Proxy Class |
The name of the proxy class generated by SPROXY. |
WS Operation (Method) |
The name of the Web service operation. Enter the name of the corresponding proxy class method. |
ESR-based outbound proxy |
Select this option if the proxy class is ESR-based outbound proxy. |
Base Class prefix |
'Base class prefix' is used as a prefix for the data object. The base class name is used as the BOP ID. Note
Make a note of this BOP ID. This is required while Implementing EDP |
Target Package |
The name of the package to which the BOP is added. The package must already exist. To add BOPs to your local objects, enter '$TMP'. |
Node in the SAP GW CCMS Context |
The default option is BE OUTB SERV. |
Transport |
If the BOP will be transported, create a workbench transport and provide the transport number. For local objects no transport request has to be entered. Note
The user who generates the BOP must be the owner of the request. |
Continue with Implementing Metadata Providers.
Back to Developing Content on SAP Gateway OData Channel Using IWBEP.
For information on BOPs, see the IMG activity documentation in transaction SPRO open the SAP Reference IMG and navigate to: and click the IMG activity documentation icon.
See Deleting an RFC or a Web Service BOP for deleting BOPs.