SAP Event Mesh

An event is a notification that something happened. When a new purchase order is created in SAP, that is an event. When a customer updates their shipping address, that is an event. When a machine on the factory floor detects abnormal heat, that is an event.

Traditional integration waits for a schedule — run the transfer every hour, every night, every Monday. Event-driven integration reacts immediately. The moment the event happens, the integration fires. No waiting, no delays, no unnecessary transfers when nothing has changed.

What Is SAP Event Mesh

SAP Event Mesh is the message broker service inside SAP Integration Suite. It provides a central place where systems publish events and other systems subscribe to receive them. The publisher and subscriber never connect directly — they communicate only through Event Mesh. This decoupling makes systems more flexible and resilient.

Think of a radio station. The station broadcasts music (publishes events). Anyone with a radio (subscribers) can listen. The station does not need to know who is listening. A new listener can tune in without the station making any changes. SAP Event Mesh works the same way.

Core Concepts

Event Publisher

The system that detects something happened and sends a notification. SAP S/4HANA, for example, can publish an event every time a new sales order is created.

Event Consumer (Subscriber)

The system that wants to know about events and takes action when it receives one. A warehouse management system might subscribe to "sales order created" events so it can start picking goods immediately.

Topic

A named channel where events of a specific type are published. Publishers send to a topic. Subscribers listen to a topic. Topic names follow a hierarchical pattern:

sap/s4/beh/salesorder/v1/SalesOrder/Created/v1
 │    │    │    │         │          │       │
 │    │    │    │         │          │       └── Version
 │    │    │    │         │          └── Action
 │    │    │    │         └── Object type
 │    │    │    └── Business area
 │    │    └── Business event handling
 │    └── Source system
 └── Organization prefix

Queue

A queue is a holding area for events. When a subscriber is temporarily unavailable, events accumulate in the queue. When the subscriber comes back online, it processes all the queued events. This ensures no event is ever lost, even during system downtime.

Publish-Subscribe Pattern

PUBLISHER                   EVENT MESH                 SUBSCRIBERS
─────────                   ──────────                 ───────────

[SAP S/4HANA]               [Topic: SalesOrder.Created]
Creates sales   ──publish──→     ┌──────────────┐     ──→ [Warehouse System]
order                            │  Event stored│     ──→ [Billing System]
                                 │  and routed  │     ──→ [Analytics Tool]
                                 └──────────────┘

One publisher → one event → many subscribers react independently

Without a message broker, every system that cares about new sales orders needs a direct connection to SAP. Three interested systems means three connections to maintain. With Event Mesh, SAP connects to Event Mesh once. Any number of systems can subscribe without SAP needing to know about them.

Event Mesh vs Cloud Integration (CPI)

Both Event Mesh and CPI move data between systems. The key difference is the interaction pattern:

CPI is best for complex, multi-step data transformations that run on a schedule or in response to a direct call. It transforms data, maps fields, routes conditionally, and applies business logic.
Event Mesh is best for immediate, lightweight event notifications. It does not transform data. It simply routes the event from publisher to subscriber as fast as possible.

In practice, they often work together. An event from Event Mesh triggers a CPI iFlow that does the transformation and delivers data to the target system.

SAP S/4HANA Business Events

SAP S/4HANA can publish business events natively. When you activate event publishing in S/4HANA configuration, the system automatically sends events to Event Mesh whenever specific business objects change. This requires no custom code.

Pre-configured event types in S/4HANA include:

Sales Order Created, Changed, Deleted
Purchase Order Created, Changed
Goods Receipt Posted
Customer Master Changed
Vendor Invoice Posted

These events follow the SAP CloudEvents specification — a standard format that ensures compatibility with any modern event processing platform, not just SAP tools.

CloudEvents Standard

SAP Event Mesh supports the CloudEvents specification — an open industry standard for event data format. Every event has a standard envelope containing:

id – A unique identifier for this specific event
source – Which system produced the event
type – The event category (e.g., salesorder.created)
time – When the event occurred
datacontenttype – The format of the event data (usually application/json)
data – The actual event payload (the business data)

Using an open standard means any application that understands CloudEvents can connect to SAP Event Mesh, regardless of technology stack.

Message Acknowledgment and Delivery Guarantees

Event Mesh guarantees message delivery through an acknowledgment mechanism. When a subscriber receives an event and processes it successfully, it sends an acknowledgment back to Event Mesh. Event Mesh then removes the event from the queue. If the subscriber crashes before sending the acknowledgment, Event Mesh re-delivers the event when the subscriber reconnects.

This at-least-once delivery guarantee means your subscriber might occasionally receive a duplicate. Your integration code must handle duplicates gracefully — usually by checking whether the event was already processed before acting on it again.

Real-World Example: Automated Order Fulfillment

1. Customer places order on website
          ↓
2. Shopify publishes "order.created" event to Event Mesh
          ↓
3. Event Mesh routes event to TWO subscribers simultaneously:
   ├──→ [SAP CPI iFlow] → creates SAP sales order (SD module)
   └──→ [Email Service] → sends order confirmation to customer
          ↓
4. SAP SD posts order, publishes "salesorder.created" event
          ↓
5. Event Mesh routes to warehouse system
   └──→ [Warehouse WMS] → starts picking process immediately

The entire chain happens in seconds. No scheduled batch job. No manual trigger. Each system reacts to events that it cares about. Adding a new subscriber — say, a fraud detection service — requires no changes to any existing system.

Previous lesson

Back to course

Next lesson