Event-Driven Architecture with SAP — Event Mesh, Advanced Event Mesh and Business Events from S/4HANA
As of 2026-10-31
SAP offers two brokers for events: SAP Event Mesh (default plan on SAP BTP) and SAP Integration Suite, advanced event mesh, built on Solace. S/4HANA raises business events through Enterprise Event Enablement or Cloud Application Event Hub. This module teaches how to choose between event and API, design topics and queues, size against the published limits (1 MB message, 250 queues), build idempotent consumers for at-least-once delivery, and run a lab with wildcard routing on a Developer broker. It ends with the analytics and AI use of events: targeted refreshes of data products and event-triggered agents.
What you will learn
- Decide for a given requirement whether an event, an API call or both is the right mechanism, using the decision ladder
- Design a topic hierarchy and queue-per-consumer layout for sales order events
- Create a durable queue with a wildcard topic subscription on an advanced event mesh Developer broker and verify queue counts
- Configure the logical chain from S/4HANA channel and outbound binding to a queue subscription
- Implement an idempotent consumer with an event-ID unique key
- Size a scenario against the published default-plan limits
Concept overview
An event is a small, immutable statement that something happened: a sales order was created, a business partner changed, a goods receipt was posted. The producer does not know who listens. SAP offers two broker products for this in 2026: SAP Event Mesh (the BTP service, "default plan") and SAP Integration Suite, advanced event mesh (AEM, built on the Solace PubSub+ event broker). The SAP Architecture Center names both as SAP's offerings for asynchronous communication and positions AEM as a distributed, multi-broker mesh for SAP and third-party systems (Designing Event-Driven Applications on SAP BTP). Business events leave S/4HANA through Enterprise Event Enablement (on premise and private cloud) or through SAP Cloud Application Event Hub (S/4HANA Cloud Public Edition).
What you do with this on a project: you decide whether a requirement is an event or an API call, you design the topic names, you attach a queue per consumer, you make each consumer safe against duplicates, and you prove the chain with counts (published, queued, acknowledged). This module is the generic EDA pattern from M122 applied to SAP; connectivity to the brokers builds on M420, and the API side of the decision is M431 and M430.
Prerequisites
- Basic SAP BTP knowledge: subaccounts, service instances and service keys (see M420)
- Reading knowledge of JSON and HTTP
- Awareness of the generic event-driven pattern (M122)
Outcomes
- Explain the roles of topic, queue and subscription on SAP Event Mesh and advanced event mesh
- Quote the published default-plan limits and derive design consequences
- Predict queue message counts for a given set of topics and wildcard subscriptions
- Describe how an S/4HANA business event reaches a broker in each edition
- Justify an idempotency design for at-least-once delivery
- Place an event-driven refresh or agent trigger in an analytics landscape
Full module with the Consultant plan — €19.90/month. The full module adds: the decision framework · the end-to-end scenario walkthrough · the KPI scorecard · the anti-patterns · the code blocks · the knowledge check · the diagrams.