Endpoint Customization
SAP uses the Remote Function Call (RFC) to establish connections with external systems. This RFC serves as an exclusive interface for communication between SAP systems and external applications, enabling SAP to function as both a client and a server in familiar RFC scenarios.
To customize this asset in SAP, it is crucial to know the parameters governing the web connection to which SAP will be linked. Essential details such as the URL, port, and RFC type are required for its successful integration.
📋 Prerequisites: Before starting, make sure you have the host, port, path prefix, and credentials of the destination created before in the Smart Gateway.
Step 1 — Access Transaction SM59 in SAP
Go to the Transaction field, enter SM59, and press Enter or click the checkmark.

Step 2 — Locate HTTP Connections
Expand the HTTP Connections to External Server node.
- If you already have an RFC created, select it and skip to Step 5 to make any necessary changes.
- If you need to create one, continue with the next step.

Step 3 — Create or Select the Connection
Click Create. If you already have a connection, select it instead.

Step 4 — Define the Connection Name
Fill in the following values:
| Field |
Value |
| Connection Type |
G – HTTP Connection to External Server |
| Destination Name (recommended) |
ONIBEX_ONECONNECT / ONIBEX_POC |

Fill in the following values on the Technical Settings tab:
- Descriptions (optional):
Onibex One Connect
- Host: IP address of the server where data is sent from SAP
- Port: Port number used to connect with the host
- Path Prefix: The path where the web/app is located

💡 Example — How to split a URL:
Full URL: https://{DOMAIN}:5051/api/v1/saplistener/{CLIENT}
- Host:
{DOMAIN}
- Port:
5051
- Path Prefix:
/api/v1/saplistener/{CLIENT}

In the Logon & Security tab, enter the username and password that you previously set up on the One Connect site (as shown in the image below).

Step 7 — Test the Connection
Once all required fields are completed, click Connection Test.
Interpreting the HTTP Response Status
| Status Code |
Meaning |
Action |
| 200 |
Successful connection ✅ |
No action needed |
| 400 |
Server not detected |
Review host, port, and path prefix |
| 500 |
Authentication failure |
Review username and password in Logon & Security |


✅ You're done! Your SAP system is now configured to communicate with the external endpoint via RFC.
Related Articles
SAP Data Modeler - Set Up High Availability for One Connect for SAP
How to Set Up High Availability for One Connect for SAP Overview One Connect's Data Modeler transmits data and metadata to the Smart Gateway via an HTTP endpoint configured in SAP transaction SM59 as an RFC destination (Connection Type G). To ensure ...
Sending IDocs Using One Connect for SAP
Sending IDocs Using One Connect for SAP Output Message, EDI/ALE, and Distribution Model Configuration Overview One Connect for SAP supports data extraction through SAP IDocs (Intermediate Documents), allowing you to leverage standard and custom IDoc ...
SAP Data Modeler - Customizing Parameters
OneConnect Parameter Adjustments The OneConnect solution includes a parameter table used for sending information—especially real-time data. It is important to configure this table beforehand, prior to sending any data, to ensure proper communication ...
OneConnect V2 SAP Manual
OneConnect V2 SAP Integration The following manual configuration considers the fact that you have installed the version 2 of OneConnect in SAP, please make sure that you are using this version Install the Transport Install the transport request sent ...
SAP Data Modeler - Execute an entity in batch mode
Batch Mode Entity Sending Pre-execution Requirements Before executing an entity and sending information in batch mode, ensure that the entity is correctly created and configured. Likewise, confirm that the endpoint configuration is properly set up ...