Categories
News

KaTe is now in Americas

KaTe now in Americas

Company News

KaTe Group Inc. Opens in Atlanta: SAP Integration Expertise for the Americas

With KaTe Group Inc. in Atlanta, KaTe is expanding its local presence for customers and partners across North and South America — bringing established SAP integration expertise closer to the region.

KaTe Group Inc. has officially been incorporated in Atlanta, Georgia. The new company presence marks an important step for KaTe: a stronger local connection for organisations, partners and SAP integration teams throughout North and South America.

KaTe has focused on SAP integrations since 2008. From its roots in Germany, the company has developed software solutions first for SAP integration landscapes — including dedicated SAP adapters and IntegraOps for integration operations. Core expertise spans SAP Integration Suite, SAP Edge Integration Cell, SAP PI/PO and SAP ERP/ABAP integration. Consulting and project services complement these products where organisations need architectural, implementation or operational support.

Software solutions for modern SAP integration. KaTe Group Inc. brings dedicated adapter products, IntegraOps for integration operations and practical SAP expertise closer to customers and partners across the Americas. Services are available where they add value — alongside a clear product focus.

A base in Atlanta for North and South America

The KaTe office is located in Atlanta Buckhead at Three Alliance Center. Atlanta is the base for the company’s activities in the Americas and supports closer collaboration across time zones, regional business contexts and individual integration roadmaps.

The goal is not simply a new address. It is to make KaTe’s software solutions, product knowledge and SAP integration experience more accessible to teams working with complex landscapes across North and South America.

Company presence
KaTe Group Inc., incorporated in Atlanta, Georgia, USA.
Regional focus
Customers, partners and the SAP community across North and South America.
Core expertise
SAP Integration Suite, SAP Edge Integration Cell, SAP PI/PO, SAP ERP/ABAP integration and dedicated SAP integration adapters.
KaTe’s solution for SAP integration operations: Monitoring, Transport Management and Disaster Recovery. Learn more about the monitoring capabilities with IntegraMon.

Software solutions for SAP integration and operations

KaTe is primarily a software solutions company. SAP integration landscapes are rarely static: teams run cloud integrations alongside on-premise systems, modernise SAP PI/PO, extend ERP processes through ABAP, connect business-critical systems and build new services on SAP BTP. KaTe develops software that helps organisations address these integration and operations requirements, with expert services available where a project needs additional support.

Solution areaWhat KaTe brings
Dedicated SAP adaptersSoftware products for connecting SAP and non-SAP systems in SAP Integration Suite, SAP PI/PO and hybrid integration scenarios.
SAP Integration SuiteIntegration solutions and adapter capabilities for cloud-based SAP integration architecture.
Edge Integration CellSupport for hybrid integration scenarios that combine cloud capabilities with local requirements.
SAP PI/POProducts and expertise for established middleware landscapes as organisations operate, modernise or evolve their integration architecture.
SAP ERP / ABAP integrationIntegration expertise for connecting SAP ERP processes, ABAP-based extensions and surrounding business systems.
IntegraOpsKaTe’s software solution for SAP integration operations: Monitoring, Transport Management and Disaster Recovery. The monitoring capabilities are available through IntegraMon.

For teams operating SAP Integration Suite and Edge Integration Cell, IntegraOps provides a product-led operations approach across integration environments. It combines Monitoring, Transport Management and Disaster Recovery; IntegraMon provides the central monitoring capabilities. Together with KaTe’s adapter portfolio, this creates a practical software foundation for connecting, operating and evolving SAP integration landscapes.

Building the next chapter together

Bernd Baier, Head of Americas, will represent KaTe from Atlanta and work with organisations across the region. Together with Sebastian Simon and Lars Albrecht, the team is looking forward to building new connections, supporting customers and contributing to the growing SAP integration community in the Americas.

The coming months will bring more conversations around SAP Integration Suite, SAP ERP/ABAP integration, Kafka, MQTT, Edge Integration Cell and the operational challenges that emerge as integration landscapes scale. KaTe looks forward to sharing product knowledge, discussing architectures and helping teams solve the integration problems that matter most to their business.

What the Atlanta presence means for SAP integration teams

For customers and partners in North and South America, KaTe Group Inc. creates a local starting point for conversations about software solutions, integration architecture, dedicated adapters, SAP ERP/ABAP integration, hybrid scenarios and IntegraOps. The experienced KaTe team remains connected across regions, while the Atlanta presence strengthens the company’s ability to engage locally.

Whether an organisation is modernising SAP PI/PO integrations, designing an Integration Suite architecture, evaluating Edge Integration Cell, connecting SAP ERP/ABAP processes or looking for more control in integration operations, the focus remains the same: fit-for-purpose software solutions, reliable operation and practical implementation support.

Frequently asked questions

Find answers to common questions about KaTe Group Inc., its SAP software solutions and its presence in the Americas.

Where is KaTe Group Inc. located in the United States?

KaTe Group Inc. is located in Atlanta Buckhead, Georgia, at Three Alliance Center.

Which regions does KaTe Group Inc. support?

The Atlanta presence supports KaTe’s work with customers, partners and the SAP community across North and South America.

What is KaTe’s primary focus?

KaTe primarily develops software solutions for SAP integration and operations. These include dedicated SAP adapters and IntegraOps. Consulting and project services complement the software portfolio where required.

Which SAP technologies are part of KaTe’s core expertise?

KaTe’s core expertise includes SAP Integration Suite, SAP Edge Integration Cell, SAP PI/PO, SAP ERP/ABAP integration and dedicated SAP integration adapters.

What is IntegraOps?

IntegraOps is KaTe’s solution for SAP integration operations. It combines Monitoring, Transport Management and Disaster Recovery. The monitoring capabilities are available through IntegraMon.

Who represents KaTe in the Americas?

Bernd Baier is Head of Americas. He works together with Sebastian Simon and Lars Albrecht as KaTe develops its presence across the region.

You can find even more news on our social media channels:

Categories
News

Scaling Kafka Consumption in SAP Integration Suite

Scaling Kafka Consumption in SAP Integration Suite

Product Update

From One Record per Message to One Batch per Run: Scaling Kafka Consumption in SAP Integration Suite

The KaTe Kafka Adapter can combine records returned by a Kafka poll into one batch payload — enabling SAP Integration Suite and Edge Integration Cell to process Kafka workloads with fewer repeated integration and network calls.

Kafka can deliver far more events than a conventional backend can process one request at a time. The bottleneck is often not Kafka itself. It is the repeated integration and network overhead created when every record starts its own SAP Integration Suite message and its own backend call.

The Sender Batch feature of the KaTe Kafka Adapter for SAP Integration Suite changes that equation. Instead of translating every polled Kafka record into a separate Cloud Integration message, the adapter can combine the records returned by a poll into one batch payload. One integration run can then validate, map and deliver many business records together.

Batching and partition parallelism complement one another: partitions provide concurrent work lanes, while batching makes each lane more efficient. The result can be substantially fewer integration and network round trips for Kafka workloads processed through SAP Integration Suite.

What changes in batch mode?

In single-record mode, 100 Kafka records create up to 100 Cloud Integration messages. In batch mode, the adapter can create one message containing up to the configured Max poll records. The backend receives fewer, larger calls, while Kafka offsets are committed only after the complete batch has been transferred successfully into Cloud Integration.

Two payload styles are available:

Simple batch format
Contains only the transformed record values under one configurable root element.
Detailed batch format
Also carries Kafka metadata such as topic, partition, key, offset, timestamp, headers and tombstone information for each record.

For continuous processing, the adapter collects available records up to the configured poll limit. If the batch is not full, it can wait for the configurable batch window before submitting the records already available. Interval processing creates one batch from the records returned by that interval’s poll.

An illustrative throughput model

Consider a topic with four partitions and enough parallel consumers to keep all four busy. Assume one single-record backend interaction takes 50 ms end to end: 25 ms of network and protocol latency plus 25 ms of backend work.

These are elapsed times including acknowledgement and commit where applicable. The model assumes four active processing lanes and excludes additional iFlow processing and batch-collection delays.

4 parallel partitions / 0.050 seconds = 80 records per second

Batching amortizes the integration and network cost. The exact gain depends on whether the backend has a true bulk operation or still performs most of its work record by record.

ModeIllustrative throughputGain vs. single record
Single record80 records/s1×
Batch of 10; whole batch handled in 50 ms800 records/s10×
Batch of 100; whole batch handled in 50 ms8,000 records/s100×
Batch of 10; 25 ms network per batch + 25 ms work per recordabout 145 records/sabout 1.82×
Batch of 100; 25 ms network per batch + 25 ms work per recordabout 158 records/sabout 1.98×

The optimistic case assumes that a backend can process the complete batch in roughly the same 50 ms as one record. The conservative case assumes that only the 25-ms network portion is shared while 25 ms of work remains for every record. Its speed-up is:

speed-up(B) = 50 × B / (25 + 25 × B) = 2B / (B + 1)

With these assumptions, eliminating repeated network round trips can approach 2× even when backend work remains linear. A real bulk API, bulk database operation or vectorised transformation can move the result much closer to the batch-size multiplier. These figures are a capacity-planning model, not a measured product benchmark; payload size, mapping cost, worker count, broker latency, retries and backend limits all affect production throughput.

Why a JDBC batch can finish close to a single insert

A 50-ms JDBC insert including network travel and commit is a plausible assumption for a remote database. A modest batch can finish close to that when fixed overhead dominates: JDBC batching reduces round trips, and one transaction shares commit overhead across rows.

For example, 49 ms fixed overhead + 1 ms per row gives 50 ms for one insert and 149 ms for 100 rows. Four concurrent lanes would then deliver approximately 2,685 records/s — 33.6× the single-record baseline. These are illustrative inputs; indexes, triggers and lock contention affect actual results. The earlier near-2× case assumes all backend work repeats per row, so it is not a general JDBC limit.

Fewer metered Integration Suite messages

Batching can also reduce SAP Integration Suite message consumption. At the time of writing, SAP’s public pricing definition counts a Cloud Integration message in 250 KB blocks — not 256 KB. An outbound message of up to 250 KB counts as one message; every additional 250 KB or fraction thereof counts as another. For synchronous receiver calls, SAP considers the request and response together, and special patterns such as splitters have separate counting rules. The exact commercial effect depends on the customer’s edition, included volume, contract and whether a message is chargeable. See the current SAP Integration Suite pricing definition and verify the deployed flow in the tenant’s Message Usage dashboard before using an estimate for budgeting.

For example, 20 individually processed records below 250 KB normally create 20 outbound backend messages and therefore at least 20 metered messages. If the same records form one outbound batch that remains at or below 250 KB — including its envelope and, for a synchronous call, its response — the batch can count as one metered message. If that batch grows to 600 KB, it counts as three rather than 20. Batching does not make payload volume free, but it removes the minimum one-message charge that otherwise applies to every small outbound call.

single-record units ≈ number of records × ceil(single outbound size / 250 KB) batch units ≈ ceil(total batched outbound size / 250 KB)

Treat this as a planning approximation. Headers, envelopes, receiver calls, synchronous responses, retries, splitters and the final deployed flow can change the metered total.

Where batching helps most

Sender Batching is particularly effective when the downstream system already supports bulk requests, database array operations, mass updates or file-oriented interfaces. It can also reduce the number of Cloud Integration message processing logs and repeated connection setups produced for the same business volume.

There is a deliberate trade-off: a batch is one processing unit. Larger batches improve amortisation but can increase per-record latency, memory use and the amount of work retried after a failure. Channel-level single-record deduplication is not available for variable batches, so downstream processing should be idempotent or deduplicate records using stable business identifiers. Batching is also not available for selective support-mode reads.

Decision matrix: should the sender use batching?

The decisive question is whether the connected backend can consume a collection efficiently. Merely wrapping single-record calls in one XML document does not create a bulk operation.

Backend or requirementFitGuidance
BI, data warehouse or data-lake ingestionStrongThese systems commonly prefer larger blocks, staged files or bulk-load APIs.
JDBC batch insert/upsert or set-based database procedureStrongUse a real bulk statement, array binding, staging table or mass-enabled procedure; looping over single inserts gives a smaller benefit.
OData $batchStrong when supportedConfirm that the service supports $batch, define whether operations belong in a transactional change set and map the Kafka batch to the required multipart request.
File, SFTP or object-storage deliveryStrongA batch maps naturally to a multi-record file when the receiver expects one; it is a poor fit if every event must remain a separate file.
Mass-enabled BAPI or SOAP operationConditionalUse batching only when the operation or a controlled wrapper accepts a table/list and defines partial-error behaviour.
Standard single-object BAPI or SOAP serviceUsually weakMany standard operations still execute one business transaction per call; batching may require a purpose-built wrapper and careful commit handling.
Per-record response, independent retry or very low latencyWeakSingle-record processing preserves granular acknowledgements and avoids waiting for a batch window.
Highly variable or very large payloadsConditionalSet conservative limits and test the combined request against CPI, adapter, backend and network size limits.
Backend cannot process collectionsDo not batchThe iFlow would have to split and loop, losing much of the throughput and metering advantage while adding complexity.

A practical starting point

Start with a moderate Max poll records value such as 10 or 25, align the number of parallel consumers with the available topic partitions and verify that the backend genuinely handles the batch efficiently. Then increase the batch size while watching end-to-end latency, metered message usage, payload size, memory, retry behaviour and backend saturation. A batch window should be long enough to form useful batches but short enough to meet the scenario’s latency target.

Batching and partition parallelism complement each other: partitions provide concurrent work lanes, while batching makes each lane more efficient. Together they let SAP Integration Suite process Kafka workloads with substantially fewer integration and network round trips.

What this update means for SAP integration teams

These concise answers preserve the technical scope of the update and make the page easier to navigate in conventional and AI-assisted search.

What is Kafka Sender Batching?

It is a KaTe Kafka Adapter feature that groups records returned by a Kafka poll into one batch payload and delivers that group as one Cloud Integration message for further processing.

Does Sender Batching guarantee a specific throughput increase?

No. The numerical examples above are capacity-planning models, not measured product benchmarks. The result depends on the bulk capability and limits of the downstream system as well as the complete deployed architecture.

What comes next?

A follow-up article will examine how Confluent Parallel Consumer can extend the sender-side design with controlled record-level concurrency, including ordering choices, offset management and the situations in which it complements — or replaces — classic partition-bound processing.

Scaling Kafka Consumption in SAP Integration Suite

You can find even more news on our social media channels: