SAP Community - SAP Event Mesh

Java App Event Mesh client

2025-10-10T16:08:12.457000+02:00

Hi,

I try to develop Java based client deployed on my notebook, which will consum messages from BTP Event Mesh (not AEM, but simple Event Mesh)? This event mesh service was already activated on the BTP, so I just try to generate a new xsuaa service, which I would like to use as OAuth Provider...

1. I'm using Event Mesh and not Advanced Event Mesh... and plan to use xsuaa service as OAuth provider...

2. I have create a new xsuaa instance (even there are two other xsuaa services), using a xs-security.json config file.

3. Since we are using old plain Event Mesh I have seen that it should trust all xsuaa services... means I do not do any extra config, which xsuaa service should be used by Event Mesh... (not even sure If this is even possible)

4. Have generated service key for xsuaa service and use it to generate the token. Once I check the token in jwt.io, I see that the token contains the scope to consume and push messages (attached picture)

5. But once I try to use this token and consume messages from Queue, I receive 401 Unauthorized error. I'm using

qpid-jms-client 2.5.0 version

String amqpUrl = "amqpwss://enterprise-messaging-messaging- gateway.cfapps.eu10.hana.ondemand.com:443/protocols/amqp10ws";

JmsConnectionFactory factory = new JmsConnectionFactory(amqpUrl);

factory.setUsername("Bearer");

factory.setPassword(accessToken);

factory.setClientID("sb-m24-xsuaa!t154317");

Connection connection = factory.createConnection();

connection.start();

Session session = connection.createSession(false, Session.CLIENT_ACKNOWLEDGE);

Destination destination = session.createQueue(messagingSpace + ":" + queue);

MessageConsumer consumer = session.createConsumer(destination);

Message message = consumer.receive(10000);

and this code responde by this error:

jakarta.jms.JMSException: Invalid handshake response getStatus: 401 Unauthorized
at org.apache.qpid.jms.provider.ProviderException.toJMSException(ProviderException.java:34)
at org.apache.qpid.jms.exceptions.JmsExceptionSupport.create(JmsExceptionSupport.java:80)
at org.apache.qpid.jms.exceptions.JmsExceptionSupport.create(JmsExceptionSupport.java:112)
at org.apache.qpid.jms.JmsConnection.connect(JmsConnection.java:176)
at org.apache.qpid.jms.JmsConnectionFactory.createConnection(JmsConnectionFactory.java:214)
at org.apache.qpid.jms.JmsConnectionFactory.createConnection(JmsConnectionFactory.java:201)
at com.example.EventMeshClient.main(EventMeshClient.java:32)
at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:279)
at java.base/java.lang.Thread.run(Thread.java:1474)

Any hints how could I manage this issue?

Many Thanks,

Milan

Trigger Equipment Replication (Event Mesh) from S/4HANA Public Cloud to Service Cloud V2

2025-10-14T08:51:19.643000+02:00

Dear Experts,

I set up the integration of Equipments based on the SAP Standard guide to replicate Equipments from S/4HANA Public Cloud to Service Cloud V2. The integration is done via SAP Event Mesh, configured on BTP.

The replication works fine when equipments are created or changed in S4, but I would need to trigger an initial load of all (incl. old) equipments. The guide does not provide any information how this can be done, and since there is no replication model for this event based integration, I cannot trigger it like the other master data interfaces.

Does anyone have a hint on how this can be achieved without having to change every single equipment in S4?

Thanks in advance!
BR,
Richard

Connecting Non-SAP Systems with SAP BTP: APIs, Event Mesh & Integration Suite

2025-10-15T16:03:00.455000+02:00

Connecting Non-SAP Systems with SAP BTP: APIs, Event Mesh & Integration Suite

Integration is one of the top priorities for SAP customers in 2025. As hybrid IT landscapes grow , combining SAP S/4HANA, legacy systems, and modern SaaS, the SAP Business Technology Platform (BTP) has become the central layer enabling these systems to talk to each other securely and in real time.

SAP’s Integration Suite, Event Mesh, and API Management together form the backbone of this connected ecosystem.

1. Why Integration Matters More Than Ever

Businesses rarely run fully on SAP alone. You might have Salesforce for CRM, Workday for HR, or custom-built logistics apps. These need to work seamlessly and tirelessly with SAP without faults, sharing customer data, triggering workflows, and ensuring real-time visibility across the value chain.

BTP helps unify all this through open connectors, APIs, and event-driven communication, without touching the core of SAP S/4HANA.

2. Integration Suite: The Foundation Layer

SAP Integration Suite offers a unified set of capabilities to design, manage, and monitor integrations between SAP and non-SAP systems.

Cloud Integration
For process-based, message-driven integration between SAP and non-SAP systems. It enables data flow through pre-built integration packages (for example, SAP → Salesforce → SAP), reducing development time.

API Management
Expose custom APIs from CAP-based apps or legacy systems, and consume REST APIs from third-party platforms. You can control access, apply rate limits, and ensure security via OAuth and API policies.

Integration Advisor
Suggests mappings and interface structures automatically, saving time and improving consistency during design.

Together, these tools simplify how business processes flow across a hybrid landscape.

3. Event Mesh: Making Systems Talk in Real Time

SAP Event Mesh introduces an event-driven architecture (EDA) , enabling systems to communicate through business events rather than constant API calls.

External systems can exchange data with SAP applications
When a customer creates an order in a non-SAP app, Event Mesh can instantly notify SAP S/4HANA or a CAP app to start fulfillment.

Processes stay synchronized in real time
Inventory changes, shipment updates, or status alerts are instantly propagated to every connected system , keeping everyone on the same page with standardized information and data.

You avoid modifying S/4HANA directly
By handling custom logic in BTP extensions and event subscribers, you reduce technical debt and simplify upgrades. The clean-core principle stays intact.

Event Mesh therefore acts as the “nervous system” of the landscape, transmitting business signals instantly across applications.

4. APIs + Events = The Future of Integration

Modern integration combines APIs for control and events for awareness.
APIs handle structured, request-driven interactions (“get order details”), while events handle spontaneous updates (“order created”).

Together, they enable loosely coupled architectures, where systems are connected, but not dependent.

5. Real-World Example: A Logistics Scenario

A German manufacturing company runs SAP S/4HANA for order processing, an on-premises warehouse management system (WMS), and a third-party shipping service that provides delivery tracking via REST APIs.

They use SAP BTP to integrate these three worlds, ensuring data consistency, real-time visibility, and a clean SAP core. Let’s see how the three pillars of integration make it work together.

Cloud Integration: The Process Connector

SAP Cloud Integration (part of Integration Suite) acts as the central traffic controller for data between S/4HANA and the warehouse system.

Whenever a sales order is created in S/4HANA, Cloud Integration picks up the outbound IDoc or OData event (for example, “SalesOrder.Created”).
It maps this order data into the format expected by the warehouse system, handling data transformations, enrichments, and protocol conversions (like IDoc → REST).
The integration flow (iFlow) then securely transmits this data over HTTPS to the warehouse’s REST endpoint or message queue.
At the end of the day, the same flow also synchronizes stock levels or order confirmations back into S/4HANA.

This ensures both systems always have the same view of orders and inventory, without manual file transfers or custom scripts.

Result:
Process-based data exchange between SAP and non-SAP systems, fully automated and monitored from BTP.

Event Mesh: The Real-Time Messenger

While Cloud Integration handles batch or process-oriented data, Event Mesh ensures real-time responsiveness across the landscape.

When the warehouse system marks an order as “Delivered,” it publishes an event (for example, “DeliveryCreated”) to the SAP Event Mesh topic.
Event Mesh then pushes this event to all subscribed systems, such as the customer portal and CAP-based tracking app on BTP.
The subscriber apps instantly receive this update and can trigger follow-up actions, like sending a push notification or updating the customer’s order status on the web.

Unlike APIs that require constant polling, Event Mesh delivers updates asynchronously and only when needed, making the system more efficient and scalable.

Result:
Real-time synchronization without point-to-point dependencies, enabling instant reactions across systems.

API Management: The Secure Gateway

Now that multiple systems generate and consume data, API Management provides a unified and secure access layer for external consumption.

The company creates a custom “Order Tracking” API that aggregates order and delivery data from both S/4HANA (via Cloud Integration) and the warehouse (via Event Mesh events).
This API is managed through SAP’s API Management service, where policies handle:

Security: OAuth 2.0, API keys, and JWT validation
Traffic Control: Rate limits, quota management
Monitoring: API usage analytics and latency reports

The customer portal or mobile app consumes this API securely, allowing users to track their orders end-to-end from a single interface.

Result:
A governed, standardized entry point for all external consumers hence reducing complexity while protecting sensitive business data.

6. Key Takeaway

Connecting SAP and non-SAP systems doesn’t have to mean complex middleware landscapes anymore.
With SAP BTP, Integration Suite, APIs, and Event Mesh provide a unified, scalable, and governed way to achieve cross-system connectivity, without sacrificing your clean-core principles.

Start with one process, make it event-driven, and expand from there.
Integration is no longer a project phase, it’s an ongoing capability that defines how modern enterprises operate.

#SAPBTP #IntegrationSuite #EventMesh #APIManagement #SAPArchitecture #CleanCore #SAPIntegration #EnterpriseArchitecture #DigitalTransformation #SAPDevelopers

Do standard business events exist for SAP PPM (Project and Portfolio Management)?

2025-10-20T01:31:34.602000+02:00

Hi Community,

I would like to know if standard business events are available for SAP PPM (Project and Portfolio Management), specifically for Portfolio Item Decision Point status changes? None seem to be listed in SAP Business Accelerator Hub, nor are any listed in the PPM Help Documentation.

The use case involves triggering an SAP Build Process Automation Workflow via Event Mesh, when the status of a Portfolio Item Decision Point is changed.

In the absence of a standard business event, what is the recommended approach for creating a custom event for this scenario?:

Use SAP NetWeaver Add-On for Event Enablement; or
Use a RAP Business Event. The issue I see with this approach is that we would need to create a custom RAP Business Event for a standard business object (Portfolio Item Decision Point), when a corresponding RAP Business Object does not seem to exist. Creating a Derived Business Event is also not an option because there is no standard Business Event to reference.

Any suggestions would be greatly appreciated.

Thanks,
Mustafa.

SAP Event Mesh & Integration Suite iFlow – Webhook Handshake Problem

2025-10-24T15:50:29.564000+02:00

Hello everyone,

Is it possible to manage the handshake process within SAP Integration Suite?

Specifically, how do you handle HTTP OPTIONS requests within the iFlow?

We’ve noticed that when triggering a handshake via a webhook, the Integration Suite logs capture the OPTIONS request, but we’re unsure how to properly handle or respond to it within the flow logic.

Any insights or best practices would be highly appreciated.

Thank you in advance.

error while creating event mesh instance plan default

2025-10-28T17:00:36.834000+01:00

Hello,

I have added Event Mesh service in entitlement by selecting default plan. Now I am trying to create instance and it gives me error as "Couldn't create service instance <name>."

I am following all steps mentioned in discovery steps.

Event Mesh not visible

2025-10-28T22:38:23.313000+01:00

Hello,

I am trying to do the exercise for SAP BTP integration developer and currently going through the course module Introducing Event-Driven Architectures - https://learning.sap.com/learning-journeys/developing-with-sap-integration-suite/introducing-event-driven-architectures

I am trying to do the exercise for adding 'Manage Business Event' capability in my integration Suite. But I cannot add that capability as that capability is not present in my Integration Suite. I am using trial account.

I tried to check if its role missing and I can see that I am not able to see any role related to event mesh in ‘Assign Role collection’ section against my userid.

After researching a bit, I thought may be the entitlement for event mesh is missing in my sub account and I was trying to add the entitlement, and I cannot see event mesh in entitlements as well

Please help me resolve this issue.

Creating custom events in SAP Event Mesh

2025-10-29T13:43:52.099000+01:00

Hello,

In this step-by-step guide, I would like to show how to create a custom event in SAP to make an availability filter events.

For this guide, I will presenta solution for event raised during the creation of the document material

1. Make a function module (for now, w/o logic)

2. Make a reference in business objects

Go to the SWE2 transaction and make a new configuration like below:

3. Open Eclipse and create the following objects:

1. View Entity:

2. Abstract Entity:

3. Behaviour definition

4. Create a class for behaviour definition: you will get a prompt in the first line about missing implementation

5. Event Binding

4. After activating all of the objects from point 3, you can go back to the function module from point 1 and add the logic

5. Go to transaction /IWXBE/CONFIG to make a configuration for the newly created channel

You can check that in SE38 by executing report /IWXBE/R_EVENT_MONITOR

Deliver RAP events in a sequence from Event mesh

2025-10-29T15:37:12.170000+01:00

Hello Team,

Is it possible in Event Mesh or Advanced Event Mesh to group different RAP events in a specific sequence and deliver them to the consumer in that order?

I have a requirement where my application performs operations such as CREATE and UPDATE on a RAP BO, which triggers Created and Changed events. While publishing these events through Event Mesh or Advanced Event Mesh, I want to ensure that the Created event is always consumed first, followed by the Changed event.

SAP Event Mesh

Regards,

Ratheesh BS

How to access failed messages from AEM Dead Message queue (DMQ) in Cloud Integration?

2025-11-17T12:03:45.317000+01:00

I have a scenario where i am connecting iFlow in CI to AEM via the AdvancedEventMesh adapter and as per the current design, i need to retry a failed message a few times (intermittent connectivity issue) before moving the message to a Dead message queue (DMQ) in AEM. My question here is

How do i access the message from DMQ later and move it to the original queue for my iFlow to reprocess the message towards the target system?
Should I create a separate queue for DMQ in the Broker manager?
How do i make sure the retry process doesn't go on a loop if the message i retry from the DMQ doesn't get delivered to the target?

RAISE_EVENT_BD

2025-11-19T14:16:54.448000+01:00

Hi,

In SAP S/4HANA, the method IF_SD_BIL_EVENT_HANDLING~RAISE_EVENT_BD of the class CL_SD_BIL_EVENT_HANDLING is no longer used in the standard billing document creation process. Has it been replaced by another method?

Tanks,

When will CALM supports SAP Integration Suite (Event Mesh) in data center eu10?

2025-11-20T08:28:57.422000+01:00

Following the documentation it is said that "At the moment only the following SAP Integration Suite (Event Mesh) data centers are supported: eu12, eu13, eu21, jp20, us30, us31".
Are there any plans that datacenter "eu10" will be supported soon?

Thanks for an information and best regards,

Dirk

Error in Equipment Replication from S4HANA to SAP Sales Cloud

2025-11-20T18:43:04.596000+01:00

We currently have a requirement to replicate Equipment from SAP S4Hana to SAP Sales Cloud version2. We have setup event mesh default plan in btp , and create channel via service key in Tcode /o/IWXBE/CONFIG. But during activation the channel there is error displayed “ AMQP connection setup error for channel 'S4HANANEVENTMESH'”.

Kindly advise on the required configuration to enable activation channel in S4Hana

note : we are using cloud connector

RAP events feasibility after advance event mesh available for client

2025-12-09T14:36:48.208000+01:00

We have implemented Restful application programming (RAP) for delivery business objects and it is working as expected. Now AEM (Advance event mesh) will be available in client landscape. So we need to know what kind of retrofitting we need to do when the RAP solution is working with AEM. Please suggest some sap links which can be useful to understand the basic of advance event mesh.

Integration Suite Event Mesh - Management API

2025-12-16T13:31:13.387000+01:00

Hi Gurus,

I have noticed that Integration Suite Event Mesh is now offering an API that was previously only available for Standalone Event Mesh: the EM Management API.

Standalone EM APIs

https://api.sap.com/package/SAPEventMeshDefaultPlan/rest

This API is leveraged by SAP CALM for health monitoring of the Integration Suite broker.

Unfortunately, SAP has kept the details to themselves, and the API Business Hub does not show the new API for Integration Suite.

Integration Suite Event Mesh API

https://api.sap.com/package/EventMeshinSAPIntegrationSuite/rest

In the API Business Hub, there are no details about the Management API being leveraged by SAP CALM, but we know it is there.

We have not been able to determine the BasePath for this API yet, as it has changed compared to the Standalone version (https://XXX:YYYY/hub/rest/api/v1/management/...).

Has anyone found the BasePath for this API?

Best regards,
Mikel

Events from SuccessFactors to SAP Event Mesh (EMIS)

2025-12-23T17:20:44.764000+01:00

Dear Community

Has anyone successfully connected SAP Event Mesh (EMIS) with SuccessFactors using Intelligent Service Center?

I've encountered an issue with URL encoding of the topic/queue component in the REST messaging protocol endpoint URL, which occurs in both Integration Center (Custom Integration) and Event Connector. The proper URL construction for REST endpoints is documented here: https://help.sap.com/docs/event-mesh/event-mesh/use-rest-apis-to-send-and-receive-messages

Here's what I'm experiencing:

Event Connector: The URL is decoded prematurely during editing of the endpoint URL field
Integration Center: The URL is decoded at runtime, which is visible in the error logs

Both approaches fail with a 404 error (URL not found). This behavior is consistent with what happens when sending a non-URL-encoded queue/topic component via Bruno/Postman—also resulting in a 404 error.

This problem is referenced in SAP's knowledge base, but no solution has been provided: https://userapps.support.sap.com/sap/support/knowledge/en/3120396

best regards,

Mateusz

Topic filtering in advanced event mesh

2026-01-05T17:01:39.416000+01:00

We receive thousands of events per hour from external partner and it is received by Cloud Integration. Cloud Integration is sending these events to AEM. The events need to be distributed over 2 queues (1 queue has replay function and the otherone does not need a replay).

Topic that is being used now is: {partnerfunction}/{partner}/{status}. This is constructed in the AEM receiver channel.

We have e.g. 2 partner functions / 10 partners / 4 statuses

What is the best way to create something like this

Queue 1 --> both partner functions / 4 partners / 3 statuses

Queue2 --> both partner functions / other 6 partners / same 3 statuses

status4 is not being used at this moment.

Do I need to create subscriptions in the queues per combination or are there other options?

I see that wildcards can be used ... but is it also possible to exclude data?

e.g. I want all statuses except status4

e.g. in queue 2 I want all other partners then those configured queue 1.

Best regards

Ron

SAP Event Mesh

2026-01-06T06:58:47.181000+01:00

I am having an SAP Trail Account I want to access the SAP Event Mesh and create a small task, which will help me understand how the event mesh actually works, but I don't think trail accounts have the Event Mesh capability right?

I think event mesh was included in the trail account until last year or so, but right now I don't think trail accounts include event mesh service anymore right?

Please help me clarify this doubt, if I can access SAP's event mesh service on trail accounts or not

Producer Event Mesh IFlow

2026-01-27T13:58:08.521000+01:00

Hi,

I would like for your opinion regarding designing producer's iflow for asynchronous data publishing and consumption.
The general idea is to have integration flow that will iterate every 15 minutes over the list of datacenters and query Prometheus logs for every datacenter and then publish the data to the event mesh queue. That would be the producer iflow. Then, the consumer iflow would use the event mesh queue as the sender and push the messages to the FAST API application.

So far I have been focusing on the producer design. It has the following steps:
1. Timer (trigger every 15 minutes)
2. Content Modifier (body with the landscape list)
3. Groovy script that reads the list
4. Iterator splitter (sequentially processing each landscape from the list)
5. Query Prometheus for each landscape id and build the topic property corresponding to the current landscape
6. Request Reply from the query
7. Publish the message to the event mesh queue
8. AMQP receiver adapter to connect to the queue
I would like your humble opinion on this design. I tested it and it works fine, the messages arrive to the queue and I can use Postman or Bruno to consume them.
This is the setup with one queue and multiple topic subscriptions within the queue corresponding to each landscape id.
What do you think of this setup? I am using SAP Event Mesh and average message size can be from 2-5 MB depending on the size of the datacenter.

Thank you!

IDocs vs Event-Driven Integration in SAP

2026-02-16T08:33:18.706000+01:00

We are currently using IDocs for system integration in SAP and are exploring the possibility of moving to an event-driven architecture using SAP Event Mesh. How can IDocs be replaced with events in such a scenario, and what are the recommended best practices for implementing event-driven integration in SAP?