SAP to Apache Kafka. REST-based, real-time, bidirectional.
The ASAPIO Integration Add-on connects SAP ECC, SAP S/4HANA and other SAP NetWeaver ABAP systems to Apache Kafka brokers via REST proxy – enabling event-driven analytics, stream processing and consistent data layers for cloud-native applications. Certified for Confluent Platform.
Real-time SAP events to Kafka
SAP business events – order creations, stock movements, financial postings – published to Kafka topics the moment they occur in SAP. ASAPIO supports RAP (RESTful ABAP Programming Model) events, BOR events, BTEs, Change Documents and IDocs as triggers: no polling, no lag, no custom ABAP for standard objects.
Batch mode & multi-threading
For initial data loads and large historical extractions, ASAPIO supports job-driven batch mode with multi-threading across SAP work processes. Paging prevents memory overflow on large datasets. Batch and event-driven modes can run side by side.
Bidirectional
Both outbound (SAP → Kafka) and inbound (Kafka → SAP) directions are supported. Inbound uses a pull mode via the REST proxy. ASAPIO delivers incoming Kafka messages into SAP via IDoc, BAPI or custom-code handlers – full process integration in both directions.
Certified for Confluent Platform
ASAPIO is certified as Source and Sink for Confluent Platform and Confluent Cloud since April 2021. For Confluent-based Kafka environments, use the dedicated ASAPIO Confluent Connector with direct V3 API support and full certification coverage.
Broad SAP system support
Works on SAP ECC 6.0 EhP 6 or higher, SAP S/4HANA On-Premise and Private Cloud Edition, SAP BW, SAP HCM and other SAP NetWeaver ABAP systems as per Minimum Requirements. Works with any database supported by SAP NetWeaver – including SAP HANA and AnyDB.
Code-less payload design
Use the ASAPIO Payload Designer to define Kafka message payloads from SAP tables, CDS views or IDocs – without writing ABAP. The same configuration approach applies across all ASAPIO connectors: learn it once, apply it everywhere.
Event-driven integration, no custom code required
The ASAPIO Kafka connector runs entirely within your SAP system as native ABAP code. This means there is no separate middleware server to deploy, no external runtime to monitor, and no new infrastructure to manage.
ASAPIO supports three integration patterns: event-driven for real-time updates (triggered by RAP events, BOR, BTE, Change Documents or IDocs), batch mode for large data extractions (configured via jobs), and hybrid scenarios combining both. Payload definition is code-less, using the visual Payload Designer to map SAP tables, CDS views or IDocs directly to Kafka messages without writing a single line of ABAP.
Five simple steps to get streaming
From transports to first message – the entire setup takes hours, not weeks. No custom development, no infrastructure complexity.
Get startedUse the standard SAP Transport Management System to deploy ASAPIO Integration Add-on objects into your SAP ECC or SAP S/4HANA system. No special tooling required – same process you use for all SAP components.
Point ASAPIO to your Kafka REST Proxy URL (or Confluent REST Proxy). Configure SASL/SCRAM, mTLS or other authentication credentials in the ASAPIO configuration screen. Test the connection with a single click.
Use the visual Payload Designer to map SAP business objects (tables, CDS views, IDocs) to Kafka message fields. Add filters, field transformations and custom logic via BAdI without touching ABAP code.
Attach the ASAPIO interface to a Business Object Repository event, Business Transaction Event, or Change Document trigger. When that event fires in SAP, the message automatically flows to Kafka – no polling, no custom code.
Activate the interface with a toggle switch. Monitor real-time message flow, event counts and delivery status from the ASAPIO Event Studio dashboard. Troubleshoot failures with detailed logs and replay capabilities.
Reliable Delivery with Dead Letter Queues
Learn how to handle message delivery failures using the ASAPIO Dead Letter Queue pattern to ensure zero data loss in your Kafka pipelines.
Native Support for Confluent Cloud
ASAPIO is a certified Confluent partner. The ASAPIO Kafka Connector supports direct integration with Confluent Cloud via the V3 REST API. Benefit from managed Kafka infrastructure while maintaining full control over your SAP data extraction and payload design.
- Fully compatible with Confluent V3 REST API
- Support for API Keys and OAuth integration
- Verified Sink and Source for Confluent Platform
Master Message Ordering with Kafka Keys
Ensure strict message ordering for your SAP entities in Kafka. ASAPIO allows you to map SAP fields (like Purchase Order Number or Material ID) directly to the Kafka Message Key. This guarantees that all events for a specific object are routed to the same partition, preserving sequence for your downstream consumers.
- Strict partition ordering for business objects
- Code-less mapping from SAP key fields
- Essential for consistent downstream state
Common questions
Can't find the answer here? Contact our team directly.