2. One Connect - Setup

2. One Connect - Setup

2. SETUP

In addition to setting up entries and core modules, One Connect requires the configuration of specific customer tables. These tables play a crucial role in facilitating the application’s data retrieval process from SAP and its subsequent transmission to Kafka.  

By defining and populating these customer tables with relevant data, One Connect gains the ability to efficiently retrieve the necessary information from the SAP system. This data could include details about master data, transactional data, or any other crucial business information.  



Disclaimer: The screens in this document may be different based on the SAP GUI version or Operation System (Mac vs Windows) but the installation, configuration, and connection process remain consistent. 



2.1 CUSTOMIZING OF ONE CONNECT TABLES 

 
Once the data is retrieved from SAP and organized into the customer tables, One Connect can then effectively process and send the data to Kafka. The seamless communication between SAP, customer tables, and Kafka streamlines the data flow. This ensures the availability of accurate and timely data for further analysis, reporting, or integration with other systems. 
 
Proper setup and maintenance of the customer tables are fundamental to the successful functioning of One Connect. It enables the system to fulfill its intended function of facilitating data exchange and communication between SAP and Kafka. 
 
For your convenience, we have generated a transaction to facilitate the installation of One Connect. Please proceed to the transaction. ZONT_ONEC  One connect SPRO.






 
 

2.2 MAIN CUSTOMIZING TABLE 

 
The following table will serve as a critical component for configuring the primary objects utilized within One Connect. It will not only define the key objects, but it will also indicate whether they pertain to Master Data or Transactional Data. 
 
STEP 1 
Go to the Transaction field. Type “ ZONT_ONEC” in the input box. Press Enter or click the checkmark. 
Setup > One Connect Customizing > Select Main Customizing Table  
 



STEP 2

Enter table ZONTA_OBJ_DL and click Maintain.



STEP 3

Click on the New Entries field.



STEP 4

Make the following entries, then click Save.






2.3 BUSINESS PROCESS CUSTOMIZATION 

STEP 1

To ensure the seamless function of One Connect, the table responsible for managing the list of all the SAP tables utilized in the processes must be correctly set up along with its relationships. To access the table ZONTA_DATA_ LAKE to make the necessary changes, follow the steps below:

1. Go to TCODE ZONT_ONEC  Setup > One Connect Customizing > Select Business Process Customization 
2. Enter the table name ZONTA_DATA_LAKE.
3. Press the “Maintain” button.
4.  This will enable you to make the necessary configurations and relationships within the table for the efficient functioning of One Connect.



STEP 2

Click New Entries.



STEP 3

In this table, you will customize the specific SAP tables needed for the processes defined in the “ZONTA_OBJ_DL” table.
You can select from the following relations:



STEP 4

Create the entries below and click Save.





2.4 MESSAGE CUSTOMIZATION


STEP 1

This table will serve as the repository for maintaining the relationship between Objects and Output Types utilized for transactional data within One Connect. The following steps will demonstrate how to access the table ZONTA_CUST_DL to make the necessary changes.

1. Go to TCODE ZONT_ONEC  Setup > One Connect Customizing > Message Customization
2. Enter the table name ZONTA_CUST_DL.
3. Click on Maintain.

By following the previous instructions, the relationships between Objects and Output Types can be effectively managed to allow for the seamless handling of transactional data within One Connect.



STEP 2

Click on New Entries.



STEP 3

Make the following entries, then click Save.






2.5 COLUMNS DEFINITION

STEP 1

In this table, you have the option to select the columns that you want to transfer to Kafka. If you intend to transport the entire table, you may leave it empty. However, if you want to transport specific columns, enter the selected names into the table. It’s important to note that if the KEY fields for the table are not included in this configuration One Connect will automatically include them in the transfer along with the fields set up in this table.
The steps below will demonstrate how to access the table ZONTA_DL_COLUMNS to make the following changes:

1. Go to TCODE ZONT_ONEC  Setup > One Connect Customizing > Columns Definition
2. Enter the table name ZONTA_DL_COLUMNS.
3. Click Maintain.

By following the previous instructions, the desired columns for transmission can be selected and transferred accordingly by One Connect.



STEP 2

Click on the New Entries field.



For example, if you only intend to send a couple of fields from table KNA1, do the following:



2.6 SPECIFIC PARAMETERS
STEP 1

This table is used to specify the parameters indicated by the client.

1. You can set up the condition records to be read by PRCD_ELEMENTS/KONV.



ZONTA_DL_PARAM Table of Variant Variables (Client-Specific)

2. You can set up the partner type to be read for VBAK/VBRK tables.



To store the required “default” destination RFC to send transactional data automatically, follow the steps below:


1. Go to TCODE ZONT_ONEC  Setup > One Connect Customizing > Specific Parameters
2. Enter “ZONTA_DL_PARAMS” in the table maintenance view field, then click Maintain.
3. The system will open the maintenance view for the “ZONTA_DL_PARAMS” table, allowing you to add or edit entries.
4. Enter the necessary information for the mandatory record, including the following details:
Parameter Name (e.g. “Default_RFC_Destination”)
Value (e.g. “RFC_DESTINATION_NAME”) - The RFC destination name you want to set as the default for sending transactional data.
Description (e.g. “Default RFC Destination for Transactional Data”)
Other relevant parameters, if applicable.
Once you have provided all the required information, save the entry by clicking the “Save” button.

By completing the previous steps, you will have stored the mandatory record for the “default” destination RFC in the “ZONTA_DL_PARAMS” table. This default RFC destination will be automatically used when sending transactional data within the One Connect application, simplifying the process and ensuring that the data is properly transferred to its destination.



STEP 2

Click on New Entries.



STEP 3

Insert the entry below – the field value should be the Kafka server provided by the Onibex team.



2.7 CUSTOMIZING FOR REAL TIME INTEGRATION


As previously mentioned, One Connect enables the transfer of two types of data: master data and transactional data. The master data will be sent through the main One Connect program as needed, through either a single or periodical load. However, the transactional data can be sent in real-time while the user is creating different processes.
One Connect utilizes the standard Output Messages functionality provided by SAP, allowing the creation of triggers for processes and facilitating the data transmission to the defined RFC connection. 
For nearly every transaction document, SAP allows the configuration of Output Messages. To demonstrate the process of making configurations this document will focus on Output Messages for Sales Orders, Outbound Delivery, and Sales Invoices, enabling the seamless and timely transfer of each document's transactional data.

2.8 CUSTOMIZING FOR SALES ORDER REAL TIME INTEGRATION

Go to the Transaction field. Type “ ZONT_ONEC” in the input box. Press Enter or click the checkmark. 
Setup > General Customization > Customizing for real time integration
 




Select Application V1 - Sales and click on Output Types.



Click on Edit.



Then, select New Entries.



Fill in the General Data tab as follows:



Then, fill in the Default values tab as follows:



Now, double click on Processing Routines under the Dialog Structure field.



Click New Entries.



Fill in as indicated, then press Save.







Now, click on Partner Functions under Dialog Structure.



Click New Entries.



Click the New Entries button.

Fill in as indicated, then click Save.



Return to the Application screen and select the V1 – Sales field. Now select Procedures.



The ZPDL message will be found on the header level, this means that the procedures related to the Order Output – Header will need to be selected. Once this has been done, double click the Control folder.

Once the procedure is selected, double click the Control folder.



Click on the New Entries field and insert a line with the ZPDL message. To ensure proper function, follow the steps in the right order. 



In the example below, the last step is 100; to continue, create step 110.



Click Save.



Return to the previous screen and select V1 – sales. Then, click on Condition Records.



Select our message type “ZPDL”, then click the checkmark.



It is necessary to create condition records according to your organization. To demonstrate, the following scenario will use sales organization.



Input the Sales Organization. Then, click on the Output Condition field and select Create.



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



2.9 CUSTOMIZING FOR OUTBOUND DELIVERY REAL TIME INTEGRATION


Go to the Transaction field. Type “ ZONT_ONEC” in the input box. Press Enter or click the checkmark. 
Setup > General Customization > Customizing for real time integration
 







Choose Application – Shipping and click on the Output Types field.



Click on Edit.



Then, select the New Entries field.

Fill in the General Data tab as follows:



Then, fill in the Default values tab as shown below.



Now, double click on Processing Routines under Dialog Structure. 

Click New Entries.

 

Fill the New Entry as shown below, then press Save.



Now, click on Partner functions under Dialog Structure. Select New Entries.



Fill in as indicated, then click Save.



Go back to the Applications screen and click on V2 – Shipping and select Procedures.



The ZDDL message will be found on the header level, this means that the processes related to the Order Output – Header will need to be selected. Once this has been done, double click the Control folder to proceed with the configuration.



Click on New Entries and insert a line with the ZPDL message. To ensure proper function, follow the steps in the right order.



In the example, the last step is 60; to continue, create step 70.



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





Select our Message type: ZDDL and click the checkmark icon.

To continue, the condition records will need to be created according to their respective organization. To demonstrate, the following scenario will create records based on sales organization.

Begin by inputting the sales organization, then click on the Output Condition menu and select Create.



Once in the condition records field insert the delivery type, for which the Output message will be applied, as “SH”. Select “Function” as the processing type and choose “Immediate processing” to ensure the message is triggered promptly.



2.10 CUSTOMIZING FOR SALES INVOICE REAL TIME INTEGRATION


Go to the Transaction field. Type “ ZONT_ONEC” in the input box. Press Enter or click the checkmark. 
Setup > General Customization > Customizing for real time integration
 






Choose Application V3 – Billing and click on the Output types field.



Click Edit.



Then, select New Entries.



Fill in the General Data tab as follows:



Then, fill in the Default values as shown below.



Now, double click on Processing Routines under Dialog structure.



Select New Entries.



Fill in the fields as indicated, then click Save.



Now, select Partner functions under Dialog Structure. 
Click New Entries.



Fill in the fields as indicated, then click Save.



Return to the Application screen and select V3 – Billing, then click Procedures.



The ZFDL message will be included in the header level, this means that one of the procedures related to the Header Output will need to be selected.
Once the procedure is selected, double click on the Control folder.



Click on New Entries and insert a line with the ZFDL message. To ensure proper function, follow the steps in the right order.



In the example below, the last step is 200; to continue create step 210.



Click Save.

Return to the previous screen, select V3 – Billing, and click on Condition records.



Select ZFDL as the Output Type and click on the checkmark icon.



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

Indicate the Output Type and execute.

Type the billing type, as BP function and immediate processing, for which the Output message will be applied.


2.11 EXTRACTOR GENERAL DEFINITION

For the custom table setup, you will be working with the table ZONTA_CUST_DLEXT which is used for the general customizing of Extractors in One Connect.
In this table, you will configure the number of records that will be passed in a single call to Kafka for each of the BW Extractors. By customizing the table with the appropriate parameters, One Connect can efficiently determine the batch size or the number of records to be transmitted to Kafka in one data transfer operation for each specific BW Extractor.

To customize, follow the steps below.

Go to the Transaction field. Type “ ZONT_ONEC” in the input box. Press Enter or click the checkmark. 
Setup > One Connect Customizing > BW Extractor general definition
 

  1. Enter the table name “ZONTA_CUST_DLEXT”.
  2. Click on Maintain.



Select New Entries.



Enter the name of the Extractor and the number of records to be sent on a single call to Kafka and then press Save.



By following the previous instructions, you can customize the batch size for each BW Extractor, ensuring efficient data transfer to Kafka within One Connect.

2.12 CUSTOMIZING EXTRACTORS ZONTA_DL_EXTKEY GENERAL


In this table, you will define the configuration for the number of records to be passed in a single call to Kafka for each of the BW Extractors. By customizing this table, One Connect gains the ability to control the batch size or the number of records that will be transmitted to Kafka during each data transfer operation for every specific BW Extractor. Configuring the batch size is crucial for optimizing data transmission efficiency and performance. It allows you to fine-tune the data transfer process according to the requirements of each BW Extractor.
 
To perform the customizing, follow these steps:
1. Go to TCODE ZONT_ONEC  Setup > One Connect Customizing > BW Extractor general definition
2. Enter the table name ZONTA_CUST_DLEXT.
3. Click on Maintain.



Press New Entries.


}


2.13 CUSTOMIZATION  FOR  MONITORING  INTEGRATION  LOGS


STEP 1

Log Set up. One Connect offers a log that aligns with SAP’s standard logs format. This will help to monitor and track possible issues while sending the information. To customize the entries for the log go to TCODE: ZONT_ONEC Setup > General Customization > Customizing for real time integration logs




 STEP 2


Select New Entries.





STEP 3

Type “ZONE_CONNECT” under object and “One Connect” under object text.



STEP 4

The next step is to create sub-objects.



STEP 5

Select New Entries.



STEP 6

According to the core modules used in One Connect, entries must be set up from the following list:



The entries should appear as shown in the image below:





2.14 DISPLAY INTEGRATION LOG MONITORING


As previously mentioned, there is the option to utilize the SLG1 transaction since One Connect is based on standard SAP logs. Nevertheless, Onibex has introduced a custom program named ZONRE_ONI_DISPLAY_LOG which enhances the user experience and displays the One Connect log.
Through this program, you can easily select the sub-object based on the Core process. It also makes additional parameters available for filtering your selection as per your specific requirements. Overall, the program offers a more user-friendly approach to accessing and reviewing the One Connect log, allowing for improved monitoring and analysis.
After the execution, you will receive a similar screen with the total values obtained after the selection criteria.



2.15 QRFC REAL-TIME MESSAGE TRANSMISSION CUSTOMIZING

The following steps will help you activate SAP QRFC, a vital component that enables real-time message transmission within your SAP system

STEP 1
Access Transaction ZONT_ONEC in SAP:

Go to  Setup > General Customization > QRFC Real-Time Message Transmission Customizing


STEP 2

Navigate to the GOTO option in the upper menu, then select QIN SCHEDULER.



STEP 3

Please ensure that you complete the table with the following details:

  1. Queue name: ZON*
  1. Mode: D
  1. Max Runtime: 30
  1. Destination :
  1. Attempts: 10
  1. Pause: 120
  2. Scheduler Monitoring: 0


2.16 EXTRACTOR CUSTOMIZING


SAP Extractors facilitate the transfer of data from SAP to other systems. By enabling this feature, you can extract both master and transactional data from various SAP modules. Extractors can be activated either by module or by specific segments of a module, like document sections within subprocesses. It is also possible to employ standard SAP extractors or create custom, ad-hoc extractors tailored to specific tables and functions.

STEP 1
Access Transaction ZONT_ONEC in SAP:

Go to  Setup > General Customization > BW Extractor Standard Configuration


After you’ve entered the transaction, click on the plus symbol as shown in the image below.



STEP 2

You will see a comprehensive list of SAP modules. Please choose the module that corresponds to  your needs. In this instance, we will opt for the Finance module.



STEP 3

You’ll encounter a list of data sources. You can make your selection depending on the functionality you wish to enable. In this case, we will select 0FI_GL_4.



STEP 4

Activate Datasource

To activate a Datasource simply click on the icon depicted in the image below.





STEP 5

The configuration has to be transported through your DEV QAS and PRD system.



STEP 6

Create the transport and include a brief description. Replicate these steps for each extractor you wish to activate.






    • Related Articles

    • 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 ...

    • 3. One Connect - Connection

      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 ...

    • One Connect 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 ...

    • How to request RISE to establish communication with One Connect

      Spanish Paso 1 Accesar a Home en SAP for Me e ir a la sección de Services & Support. Paso 2 Abrir la pestaña de Service Requests y Selecciona New Service Request. Paso 3 Seleccionar ECS y selecciona +New Paso 4 Seleccionar el Template – Allow Squid ...

    • Cloud Connector Connection Manual

      Note For RISE with SAP customers, the Cloud Connector is provided at no additional cost as part of the RISE for SAP components. If installation is required, please refer to the SAP guideline for detailed instructions on setting up the Cloud ...