StreamSets Connector

SAP data into StreamSets® pipelines. Event-driven and real-time.

The ASAPIO Integration Add-on connects SAP ECC and SAP S/4HANA to StreamSets® data pipelines – bidirectional, event-driven, and without custom ABAP code. SAP events trigger pipeline runs in real time. Inbound data from StreamSets arrives in SAP via IDoc or BAPI. No middleware required.

Book a demo Connector Docs

Real-time event delivery

SAP business events – a goods movement, a purchase order change, a material master update – trigger StreamSets pipeline runs the moment they occur. No polling, no scheduled batch exports.

Bidirectional

Outbound sends SAP data to StreamSets in real-time or batch mode. Inbound delivers StreamSets pipeline output back into SAP via IDoc or BAPI – closing the loop for data enrichment and write-back scenarios.

Code-less payload design

Use the ASAPIO Payload Designer to map SAP data fields to StreamSets messages – no ABAP development for standard SAP objects. The same configuration approach works across all ASAPIO connectors.

IDoc, RAP events & ATP

Native support for IDocs, RAP event triggers and real-time inventory (ATP) events. Whatever SAP generates, ASAPIO can route it into StreamSets – without touching the sending application.

Any SAP ABAP system

Works with SAP ECC 6.0 EhP 6 or higher, SAP S/4HANA On-Premise, SAP S/4HANA PCE, SAP BW, SAP HCM and other SAP NetWeaver ABAP systems. One connector, the full SAP landscape.

Monitoring & error handling

Delivery status, message counts and error details are visible in the ASAPIO Event Studio dashboard. Failed messages can be replayed directly – no manual intervention in SAP required.

Integration

SAP as a first-class data source for StreamSets pipelines

StreamSets is a DataOps platform for building, running and monitoring data pipelines across hybrid and multi-cloud environments. With the ASAPIO connector, SAP becomes a native data source and target within those pipelines – without requiring custom development or middleware.

The connector connects to the StreamSets REST endpoint directly from SAP, using the standard ASAPIO framework already deployed in your system. Once configured, any SAP event can feed a StreamSets pipeline in real time – and pipeline results can be written back into SAP through the same connection.

SAP to StreamSets integration architecture

Setup

Four steps to SAP–StreamSets integration

From installation to first event in StreamSets – deployment is straightforward and fully documented. No custom code, no middleware to operate.

Get started

Install the ASAPIO Integration Add-on

Deploy the Framework and the StreamSets Connector package into SAP via the standard Transport Management System – just like any other SAP component. No special procedures.

Connect to the StreamSets REST endpoint

Point ASAPIO to your StreamSets REST endpoint via an HTTP connection in SAP. The endpoint must be reachable from your SAP server – on-premises, cloud or hybrid.

Link the REST connection to a named StreamSets instance in the ASAPIO configuration. Set the encoding and confirm the connection with a test call – done in minutes.

Design your payload and activate

Use the Payload Designer to map SAP data to your StreamSets message format. Link a SAP event trigger, choose real-time or batch mode, and activate. Monitor delivery from the Event Studio dashboard.

FAQ

Common questions about the SAP StreamSets connector

Can't find the answer here? Contact our team directly.

What is StreamSets and what does integrating it with SAP enable?

StreamSets is a DataOps platform for building, running and monitoring data pipelines across cloud, on-premises and hybrid environments. Integrating SAP with StreamSets means that SAP business data – purchase orders, goods movements, inventory levels, master data changes, financial postings – becomes a real-time, first-class input to those pipelines. Without the ASAPIO connector, organisations typically resort to custom ABAP development or scheduled file exports; with it, SAP events trigger StreamSets pipeline runs automatically the moment they occur in SAP.

Does the ASAPIO StreamSets connector support bidirectional messaging?

Yes, the connector is fully bidirectional. Outbound (SAP → StreamSets) supports both real-time single-event delivery and batch mode – events are sent to the StreamSets REST endpoint as they occur in SAP or collected and forwarded on a schedule. Inbound (StreamSets → SAP) delivers pipeline output back into SAP via IDoc or BAPI, enabling write-back and data-enrichment scenarios. Both directions are configured and monitored independently using the same ASAPIO tooling.

Which SAP systems and versions are supported?

The ASAPIO StreamSets connector works with any SAP system running on SAP NetWeaver ABAP, including SAP ECC 6.0 EhP 6, SAP S/4HANA 2020+ On-Premise, SAP S/4HANA Private Cloud Edition (PCE), SAP BW, SAP HCM and other NetWeaver-based applications. See Minimum Requirements for detailed version support. No additional SAP middleware or separate integration server is required – the connector runs entirely within the SAP system.

Is a separate middleware server or integration platform required?

What SAP events and data types can be sent to StreamSets?

How does the StreamSets connector differ from the ASAPIO Kafka or Confluent connector?

The StreamSets connector communicates directly with the StreamSets REST endpoint, whereas the Kafka connector targets a generic Kafka REST proxy and the Confluent connector uses either the Confluent REST Proxy or the Confluent Cloud V3 API. All three connectors are built on the same ASAPIO Integration Add-on framework, share the same Payload Designer and Event Studio monitoring, and are configured and operated the same way. Organisations running ASAPIO for Kafka or Confluent can add the StreamSets connector without any additional SAP-side training or infrastructure changes.