3. CONNECTION
The One Connect system provides the capability to extract information from SAP and its transfer it to Kafka. This facilitates the creation of a requisite database for analysis, which serves as the foundation for generating financial dashboards to make informed decisions.
The data acquired from SAP can be categorized into two significant groups:
Master data
This data type undergoes minimal changes throughout the business process and is not considered transactional. Examples include material master, customer details, and accounts.
Transactional data
These are temporal data points that hold importance within specific timeframes. They form part of a document flow, encompassing transactions like sales records, invoices, and others.
Disclaimer: The screens in the documents may be different based on the SAP GUI version or Operation System (Mac vs Windows) but the installation, configuration, and connection process remain consistent.”
3.1 CERTIFICATE UPLOAD
It will be needed to upload the Onibex certificate into SAP to be validated by Kafka.
1. Go to STRUST tcode.
Select SSL Client (Anonymous) and double click on it.
Click Edit.
You should see the new certificate has been installed, then press Save.
Repeat the above steps for SSL Client (Standard).
Execution One Connect application
Program: ZONRE_ONI_HIST_SPL
Transaction: ZONT_HIST_DL
If Direct Query is selected, you can input the name of the table and directly write the query in the box.
3.2 END POINT CUSTOMIZATION
Once you create your dashboard, the next step is to establish connections. 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.
STEP 1
Access Transaction SM59 in SAP:
Go to the Transaction field. Enter “SM59” in the input box. Press Enter or click the checkmark.
STEP 2
Expand the “HTTP Connections to External Server” node. If you already have an RFC created, please select it and proceed to step 5 to make any necessary changes. If you need to create one, please proceed to the next step.
STEP 3
Click on Create. In the case that you already have a connection, go ahead and select it.
STEP 4
Provide the name ONIBEX_D and select G – HTTP as the connection to the external server. Include the name of the destination, it is recommended to use “ONIBEX_DL”.
STEP 5
Fill next values on the technical settings tab:
- RFC Destination: ONIBEX_DL
- Description 1: 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]
Make reference to obtain the URL.
Example of a path:
https://{DOMAIN}:5051/api/v1/saplistener/{CLIENT}
Host: {DOMAIN}
Port: 5051
Path Prefix: /api/v1/saplistener/{CLIENT}
STEP 6
In the Logon & Security task, be sure to input the user and password that you previously selected on the One Connect site (as shown in the image below).
STEP 7
Once you have completed all the necessary fields, proceed by clicking on Connection Test.
An HTTP Response status of 200 indicates a successful connection. However, if you receive a different value such as 400, it suggests that the connection was unsuccessful due to a server not being detected. In the case of a status code 500, it signifies an authentication failure with the password or username. In such instances, kindly review the provided data and attempt the process again.