Quellenstraße 7 - 70376 Stuttgart - Germany

KaTe GmbH – Bilingual Mega Menu

SAP ABAP

Kafka Adapter for ABAP

Native, bidirectional connectivity between your ABAP applications and Apache Kafka — over TCP/TLS, without a separate Kafka REST proxy.

Integration architecture

ABAP applications
Publish / Consume
KaTe GmbHKaTe Kafka Adapter for ABAPNative TCP/TLS
Kafka records
Apache Kafka
TCP/TLSConnectionAvroSchema RegistryJSONData formats
Technical building blocks
IDocs
Custom ABAP types
JSON
Avro
Schema Registry

Architecture overview

ABAP applications, KaTe Kafka Adapter for ABAP and Apache Kafka

ABAP applications
KaTe GmbHKaTe Kafka Adapter for ABAPNative ABAP integration
Apache Kafka
Publish / ConsumeNative TCP/TLS
Direct connection between ABAP and Kafka

Features

All features at a glance

Bring native Kafka connectivity into your ABAP applications with native producer and consumer APIs, configurable data binding and central administration.

Core functions: publish and consume

Publish application data as Kafka records and consume incoming records directly in standard S/4HANA and ECC functions and ABAP.

  • Flexible publishing: publish Kafka records from IDocs, RAP Events (TBA) or custom ABAP programs, using blocking sends or non-blocking outbox enqueueing with Kafka broker acknowledgements (acks).
  • Controlled consumption: read Kafka records and submit them to SAP integration objects, such as IDocs and ABAP calls, through managed consumer channels with consumer groups. Consumers process partitions in parallel and commit Kafka offsets only after successful SAP receiver processing, with retries for failed records within their partition.
  • Configurable setup: use one or more topics, control offsets and work with Kafka keys, values and headers.

Security and connection management

Secure your Kafka connections with TLS encryption, protected credentials and centrally managed connection profiles.

  • Native TCP/TLS connectivity with SASL/PLAIN authentication.
  • Encrypted credentials for Kafka brokers and Schema Registry.

Advanced features: SAP integration, data formats and error handling

SAP integration, data formats and error handling

SAP integration and data formats

Integrate SAP objects with Kafka

  • IDocs: exchange complete IDocs as Kafka records, with SAP acting as sender or receiver.
  • Custom ABAP data types and tables: bind application data to explicitly configured or generic ABAP types, structures and internal tables.
  • RAP Events (TBA): integration with events and powerful reference data lookup from the ABAP RESTful Application Programming Model.

Supported serializers and deserializers

  • Standard Kafka formats: String, Boolean, Short, Integer, Long, Float, Double, UUID, Void and binary formats (ByteArray, ByteBuffer and Bytes).
  • Confluent Avro: native binary encoding and decoding, Schema Registry integration and supported schema evolution.
  • Confluent JSON Schema: serialization and validation with Schema Registry integration within a documented Draft 7 subset.

Key and Value formats can be freely configured with respective serializers/deserializers and binding to data structures.

Configurable error handling and retries

Keep processing failures visible and control how failed records are retried.

  • Configure retry limits and delays.
  • Review retry status and failure details in monitoring.
  • Retry failed records within their partition while other partitions continue.
  • Review uncertain producer delivery outcomes before deciding on recovery.

Advantages

Why connect to Kafka directly from ABAP?

1 · Connect directly to Kafka brokers

Use Kafka’s binary protocol from ABAP. A separate Kafka REST proxy is unnecessary for broker communication; Schema Registry uses its own HTTPS API.

2 · Work with your application’s data

Integrate IDocs and RAP Events (TBA), or use generic and typed interfaces for custom ABAP data. Select the serialization format independently for keys and values.

3 · Keep configuration and diagnostics together

Manage connection profiles and channels in one user-friendly web console, and investigate operational failures through correlated runtime diagnostics.

Comparison

Choose the integration approach that fits your scenario

Kafka Adapter for ABAP

Direct ABAP APIs and SAP data binding

Application-controlled table extraction

Integration logic within your SAP application

Kafka Adapter for SAP Integration Suite

Integration through Cloud Integration iFlows

Orchestration of data exposed by SAP interfaces

Central transformation and routing across systems

Setup

Set up your Kafka integration in three steps

1

1 · Discuss your scenario

Identify your SAP environment, Kafka topics, data formats and processing requirements with our team.

2

2 · Configure the adapter

Prepare the SAP prerequisites, configure protected connection profiles and define producer or consumer channels with the required data bindings.

3

3 · Validate and start processing

Check connectivity, test your application integration and use the administration console to control and monitor processing.

Compatibility

Find the right setup for your SAP environment

Contact us to discuss your SAP release, Kafka environment and installation prerequisites. Avro, Schema Registry and JSON Schema support follow documented mapping, schema and resource limits.

Administration console

More control during setup and operations

Operations and monitoring

Manage Kafka channels centrally and investigate processing issues with runtime status, application logs and targeted diagnostics.

  • Start, stop, pause and resume managed channels from the administration console, with consumer startup from the beginning or latest position of the stream.
  • Inspect consumer group offsets, processing progress and partition status.
  • Monitor producer outbox entries and review uncertain delivery outcomes.
  • Investigate failures through correlated application logs and temporary Kafka protocol traces.

FAQ

Frequently asked questions

Answers to common questions about the Kafka Adapter for ABAP.

What is the Kafka Adapter for ABAP?

The adapter connects SAP applications directly to Kafka using native ABAP producer and consumer APIs. It brings IDocs and custom ABAP data into Kafka integration, with configurable serialization and a web console for administration. RAP Events integration is TBA.

How are Kafka connections secured?

Broker communication uses TCP/TLS with SASL/PLAIN authentication. Broker and Schema Registry credentials are stored under separate encrypted aliases, keeping connection configuration separate from secrets.

How does the adapter preserve processing order?

Records are processed in order within each assigned partition. A failed record is retried before later records in that partition proceed, while other partitions can continue. Ordering across different partitions is determined by your application design.

Can consumers process records in parallel?

Managed consumer groups distribute partitions across configured consumers. This allows parallel processing across partitions while retaining ordered processing within each partition. Capacity depends on partition count, SAP resources and receiver workload.

Can I choose where consumption starts?

You can configure consumption from the beginning or latest position of the stream. Explicit-offset read APIs also support selected stream positions. Existing consumer-group offsets affect where an established group resumes.

How can I monitor and troubleshoot my integration?

The web console brings channel controls, processing progress, consumer offsets and producer outbox inspection together. Application logs show error and retry details; temporary Kafka protocol traces support targeted troubleshooting. Retry limits and delays are configurable.

When should I use the ABAP adapter instead of a Kafka adapter on middleware?

Use the ABAP adapter when integration logic belongs in SAP — for example, application data integration or custom ABAP extraction of table data to Kafka. Publish and consume Kafka records directly within your ABAP applications, with control over data binding and processing, without routing each exchange through a middleware layer. Use the KaTe Kafka Adapter for SAP Integration Suite when you need central orchestration, transformations or routing across multiple systems. The two adapters complement each other within your integration landscape.

Do I need a Kafka REST proxy?

Unlike other solutions, no separate Kafka REST proxy is needed for broker communication. The adapter speaks Kafka’s binary protocol directly over TCP/TLS from ABAP. Schema Registry integration uses HTTPS separately.

Can I replicate tables to Kafka?

Yes. Publish table data to Kafka using generic or explicitly typed ABAP serialization and a simple custom ABAP program that reads and sends data through a Kafka channel. This enables straightforward data integration tailored to your requirements.

Can I exchange IDocs through Kafka?

Yes. Send and receive complete IDocs as Kafka records using standard SAP IDoc integration. Outbound IDocs are confirmed after Kafka acknowledges the record.

Which Confluent serializers are supported?

The adapter provides serializers and deserializers compatible with Confluent Avro and Confluent JSON Schema, including Schema Registry integration. Avro supports schema evolution; JSON Schema supports validation within a documented Draft 7 subset.

How does the adapter support reliable delivery?

The adapter commits Kafka consumer offsets only after successful receiver processing. Failed records are retried before processing continues within their partition, helping ensure records are not skipped when processing fails.

Contact

Planning Kafka integration from ABAP?

Tell us about your SAP environment, data formats and processing requirements. We can discuss the integration approach and supported configuration with you.