OneConnec 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 by the Onibex SAP team on your Basis.

Note: If you have not recieved the transport provided by Onibex, please get in touch with our technical team.

Setup One Connect in one transaction:

• Access Transaction ZONT_ONECM in SAP:
• Go to the “Transaction” field. Type “ZONT_ONECM” into the input box. Press Enter.
  

If you have already installed and configures your OneConnect V2 component within SAP, please refer to this documentation to start customizing your data modeler: Data Modeler

The One Connect system provides the capability to extract information from SAP and transmit 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.

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.

Uploading SSL Certificate

It will be needed to upload Onibex certificate into SAP to be validated by Kafka.

Go to STRUST tcode.

Select SSL Client(Anonymous) and double click on it.

Click on Edit button.

Click on import button and select the local path where you have the Certificate (if your Kafka workspace is hosted in Onibex Cloud, our technical team should share this certificate with you).

You will se the new certificate installed, then press Save.

Repeat above steps for SSL Client (standard)

Establishing RFC Connection

To establish a connection with the subsequent system, SAP must define the destination Remote Function Call (RFC). The RFC serves as an exclusive interface for communication between SAP systems and external applications.

Path: IDOC Interface / Application Link Enabling (ALE) > Communication > Create RFC Connections Transaction: SM59

Expand the node HTTP Connections to External Server.

Click on the Create button.

Provide the name ONIBEX_DL and the Connection type G – HTTP connection to external server. Include the name of the Destination: We recommend naming it ONIBEX_DL.

Fill in the following values on the technical settings tab:

• RFC Destination: ONIBEX_DL
• Description: 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

https://{DOMAIN}:5051/api/v1/saplistener/{CLIENT}
Host: {DOMAIN}
Port: 5051
Path Prefix: /api/v1/saplistener/{CLIENT}

Note: The Host, Port and Path Prefix information is obtained after successfully creating a workspace in OneConnect web, please refer to this documentation to obtain that: Workspace

Under Logon & Security Task

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.

Customizing Output Types

As described before, One Connect will allow to send two different types of data (master and transactional data). The master data will be sent through the main One Connect program as initial load or periodically if needed. However, the transactional data must be sent on real time while the user is creating the different processes.

One Connect uses standard Output type functionality provided by SAP which will allow to create a trigger to the process and send the data to the defined RFC connection.

In this document we will describe how to set up the Output types for Sales Processes:Sales Order

Go to the TCODE NACE

Choose Application V1 – Sales and click on Output types button. ( Be aware you will have to scroll down )

Click on Edit button.

Then, click on New Entries button.

Fill the General Data tab as follows:

Then, Default values tab:

Now, double click on Processing Routines under Dialog structure

Click New Entries button.

Fill as follows and press Save button.

Now, click on Partner functions under Dialog Structure.

Click on New Entries button.

Fill as follows and click on Save button.

Go back to the Application screen and click on V1 – Sales and button Procedures.

Message ZPDL will be included on the header level, so we need to select those procedures related to the Order Output – Header. Once the procedure is selected, double click on Control folder

Click on New Entries button and insert a line with the ZPDL message. Make sure the Step is subsequent step to the current activities.

In this example, the last step is 100. Then, we need to create step 110.

Click on SAVE button.

Go back one screen, select V1 – sales and Click on Condition records.

Select our Message type: ZPDL and click the green mark.

You will need to create the condition records according to your organization. In this scenario we will create according to the sales organization.

Input the Sales organization and click on the Menu Output Condition – Create.

Insert the order types for which the Output message will be applied, SP as function and immediate processing.

• Related Articles

• IDOC Configuration Manual

  1. Output Message Creation for IDOCS STEP 1 Access SAP STEP 2 Go to the Transaction field and enter “NACE” in the input box. Press Enter or click the checkmark. STEP 3 Select the application that you want to configure. For this manual, we will choose ...

• Sap Basis Version

  Step 1 In the Top Bar, click on "System". Then click on Status. Step 2 In the Product version section, click on the button to see the details. Step 3 Inside Component is “SAP_BASIS".

• 1. One Connect - Installation

  Step by Step SAP Integration Manual. The following information provide a condensed overview of the comprehensive SAP Integration Manual. In this manual, you'll find detailed step-by-step instructions for seamless SAP integration. Here's a glimpse of ...

• BTP confirmation

  1. Install cloud connector Step 1 Make sure you download Virtual Java Version 8 (either for Windows or Linux) andBinary Installation Files. 2. Connect the cloud connector to BTP Step 1 Cloud connector Sign in to Cloud Connector.Enter the default ...

• PowerBI - Sales Dashboards

  Sales Invoices Introduction Welcome to the guide for configuring Power BI for your Sales Dashboard. This manual will help you connect Power BI to SAP tables and create effective sales visualizations. This guide focuses on two views: the Sales Silver ...