
To expose a BAPI as a callable object, you must first configure a connection to the back-end system where the relevant function module resides. For this purpose, you must create an RFC destination and specify the required connection properties.
In this example, you are defining a connection to a system identified as RFC_tst_1.
The data for the user and for the system supplied in the examples below is for demonstration purposes only. You should use the credentials of a user who is authorized to execute BAPIs in the relevant system.
To configure the endpoint:
More information: SAP NetWeaver Administrator
Destination Configuration: Basic Data
| Parameter | Description | Sample Value |
|---|---|---|
|
Destination Name |
Enter a name for the destination.
You can use the following characters for the endpoint alias name:
|
RFC_tst_1 |
|
Destination Type |
Choose RFC. |
RFC |
Destination Configuration: Properties
| Parameter | Description | Sample Value |
|---|---|---|
|
System ID |
Enter the SAP System ID. |
<TST> |
|
Message Server |
Enter the message server name. |
<demo>.wdf.sap.corp |
|
Logon Group |
Enter the server group, to which you log on. |
PUBLIC |
|
Mode of Security Network Communication (SNC) |
Set the SNC mode. For our example, we disable SNC. If you want to use it, you need to configure it appropriately. |
Inactive |
|
Client |
Enter the client that you connect to. |
000 |
|
User Name |
Enter the user name of a user who holds the required permissions to access the system. |
<DEMO> |
|
Password |
Enter the user's password. |
More information: Maintaining RFC Destinations
You have configured the connection to the back-end system. Now you can import the BAPI as a callable object in GP design time.