Sending Data via BW Extractors

Sending Data via BW Extractors

Sending Data via BW Extractors

Using One Connect for SAP

 

Overview

One Connect for SAP supports data extraction through SAP BW (Business Warehouse) Extractors, allowing you to leverage existing BW DataSources to extract and transmit data to your target platform via the One Connect Smart Gateway.

This guide walks through the end-to-end process: creating the required entity in the Data Modeler, selecting and configuring a BW DataSource, executing the extraction, and verifying the results.

Prerequisites

Before you begin, ensure the following are in place:

•       One Connect for SAP is installed and configured in your SAP system

•       The One Connect Smart Gateway is deployed and accessible

•       An RFC destination for the Smart Gateway has been created and tested in transaction SM59

•       You have authorization to execute custom transactions and maintain Data Modeler entities

 

Step 1: Create the BW Extractor Entity

Open the Data Modeler and create a new entity with the following configuration:

 

Field

Value

Entity

BW_EXTRACTOR

Tag Data

Checked

Tag MetaData

Checked

Tag1

ANY

Type of data

T

Description

BW_EXTRACTOR

Number of Records

100

EventIDAct

Checked

 

Important

This entity must be created without tables. It serves as a container for the BW extraction process, not as a standard table-based entity.

 

Figure 1: Entity configuration in the Data Modeler showing the BW_EXTRACTOR setup with Tag1 set to ANY.

 

Step 2: Select the BW DataSource

1.     Run transaction ZONT_ONEC_BW — the dedicated transaction for BW Extractor operations in One Connect.

2.     In the DataSource field, enter the name of the BW extractor you want to use (e.g., 0FI_AR_4 for FI Accounts Receivable line items).

Figure 2: The ZONT_ONEC_BW transaction screen with DataSource 0FI_AR_4 entered.

3.     Press Enter. The system automatically populates the extraction parameters, including the Settings fields (Request-ID, Data Records / Calls, Display Extr. Calls) and the Selections (Internal Format) filter fields for the selected DataSource.

Figure 3: After pressing Enter, the system loads the available selection fields (BUKRS, FISCPER) for the chosen DataSource.

 

Step 3: Configure Filters and Execute

3.1 Set Filter Criteria

In the Selections (Internal Format) section, populate the filter fields with the values relevant to your extraction:

 

Field

Description

Example

BUKRS

Company Code

1000

FISCPER

Fiscal Period

2026002

 

3.2 Specify the Remote Connection

In the Remote Connection field under Settings, enter the RFC destination name configured for your One Connect Smart Gateway (e.g., ONIBEX_NEW).

Figure 4: The extraction screen with FISCPER set to 2026002 and Remote Connection set to ONIBEX_NEW.

3.3 Execute the Extraction

Choose one of the two available execution modes:

 

Button

Use Case

Extract & Send

Immediate foreground processing — suitable for smaller data volumes or testing

Background extract & Send

Asynchronous background processing — recommended for large data volumes in production

 

Tip

For initial testing, use Extract & Send to see results immediately. Switch to Background extract & Send for scheduled or large-volume production extractions.

 

Step 4: Monitor and Verify

After execution, the system displays two confirmation messages in sequence:

4.1 Record Count

An information dialog confirms the total number of records extracted from the DataSource.

Figure 5: The system confirms the number of data records selected for the current extraction.

4.2 Transmission Confirmation

A second information dialog confirms the number of HTTP requests sent to the Smart Gateway and the total data size transmitted (in bytes).

Figure 6: Confirmation showing the number of sent requests and the total data size transmitted.

4.3 Verify in Target Platform

As a final step, verify that the extracted data has arrived in your target platform (e.g., Confluent, Databricks, or Snowflake) by checking the relevant topic or table for the newly transmitted records.

 

Troubleshooting

 

Symptom

Possible Cause

Resolution

No selection fields appear after pressing Enter

Invalid or inactive DataSource

Verify the DataSource name is correct and activated in your SAP system

Connection error on Extract & Send

RFC destination misconfigured or Smart Gateway unreachable

Test the RFC destination in SM59 using Connection Test and HTTP Test

Zero records selected

Filter criteria too restrictive or no data for the period

Broaden the selection criteria or verify data exists for the specified filters

Data not visible in target platform

Latency or topic/table mismatch

Allow time for processing; confirm the correct topic or table name

 



    • Related Articles

    • Sending Z Tables via SAP Data Modeler and Custom Z Program - For ABAP RAP

      Manual: Sending Z Tables via SAP Data Modeler and Custom Z Program In the SAP Data Modeler, create an “ANY” Entity including the desired Z tables. Ensure the Domain is set to ANY. Inside the entity, select the desired columns to send in the Column ...

    • Sending Z Tables via SAP Data Modeler and Custom Z Program - For Classic ABAP

      Manual: Sending Z Tables via SAP Data Modeler and Custom Z Program In the SAP Data Modeler, create an “ANY” Entity including the desired Z tables. Ensure the Domain is set to ANY. Inside the entity, select the desired columns to send in the Column ...

    • Onibex SAP Data Modeler - Functionalities

      Introduction The following table outlines key functionalities offered by the SAP Data Modeler, highlighting features designed to enhance data extraction, customization, and integration within SAP environments. No Function Description 1 Direct Data ...

    • RFC Data Sending Guide – ZONCL_FETCH_DATA_V2

      RFC Data Sending Guide – ZONCL_FETCH_DATA_V2 This guide describes how to send data from a custom Z table in SAP to a remote system using the class ZONCL_FETCH_DATA_V2. The process supports optional filters and allows update/delete operations on the ...

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