Connector for Confluent®


ASAPIO Connector for Confluent enables direct connectivity for SAP® systems to the Confluent universe


  • Certified, visit Confluent Hub for details
  • Supports a wide range of SAP NetWeaver based systems, including SAP ERP, S/4HANA, BW, HCM and many more
  • Out-of-the-box connectivity to Confluent® Platform and Confluent® Cloud
  • REST-based outbound communication via Confluent Kafka REST proxy (push)
  • Inbound interface via Confluent Kafka REST proxy (pull)
  • Choose between event-driven (single events) or batch mode (multiple events, also multiple events per REST proxy call)
  • Supported communication direction: Outbound, Inbound
  • Batch mode allows multi-threading with multiple SAP work processes


Confluent Connectivity

Workshop: Connecting SAP systems with Confluent

Book our free virtual 1-hour workshop for SAP customers:

  • FAQ on architecture and connectivity
  • Examples how to generate and consume events
  • Discuss use-cases and ideas with our expert

Martin Schöffler

Product Owner Event Messaging

Book Meeting

How does it work?

ASAPIO Connector for Confluent is based on ASAPIO Integration Add-on, a proven SAP-certified solution and robust framework for many integration use-cases.

The Connector communicates with a REST proxy, in a push mode for outbound messages and a pull mode for inbound messages. The REST proxy directly communicates with Confluent Platform or Cloud.

Confluent Connectivity
API Configurator

Create outbound event messages code-less

Easily configure your event message payload, code-less or low-code, based on following options

  • Built-in Event Notifications (compatible with S/4HANA notification messages for SAP Event Mesh)
  • Built-in Message Modeller - configure fields and tables, including joins/hierarchy structures
  • Use attributes from the linked SAP application business objects
  • Create a custom extraction handler, with ABAP® code

Built for performance

ASAPIO Integration Add-on is built for large data volumes and lowest system impact: e.g. use our multi-threading mode for batch loads, including a split function for micro-batching of large data chungs. The single-event-mode has close to zero latency. At our customer base we see only minimal system performance impact in daily operation.