topic Re: May 2026 Developer Challenge — Week 1: Getting familiar with the events in Integration Forum

May 2026 Developer Challenge - Week 1: Getting familiar with the events

ajmaradiaga — Mon, 25 May 2026 13:03:22 GMT

Welcome to the first week of the May 2026 Developer Challenge! 🎉

This month we are going to build something that bridges two worlds that are becoming increasingly intertwined: event-driven architectures and AI. By the end of the four weeks, you will have built an end-to-end pipeline that takes events from a broker, extracts and vectorizes the data in their payloads, and stores those vectors so they can be used for Retrieval Augmented Generation (RAG).

Links:
May's developer challenge blog post: https://community.sap.com/t5/integration-blog-posts/may-2026-developer-challenge-from-events-to-intelligence-building-an-event/ba-p/14386772
Week 1: Getting familiar with the events
Week 2: Connecting to the broker and consuming events
Week 3: Vectorizing the event payload

But before we can build any of that, we need to understand the data we'll be working with. This week, we focus on the events themselves — what they look like, what data they carry, and how to publish them to a broker.

ℹ️ Reminder: The goal of the challenge is to learn the concepts, architect a solution and implement it using whatever tools you have access to — SAP, open-source, trial, paid products, use your favourite programming language or whatever agent you fancy using.

The scenario

Throughout this challenge, I will work with Business Partner events. A Business Partner event is published whenever a business partner (a customer, supplier, or employee) is created or changed in a system. These are common, well-understood events in enterprise landscapes, and their payloads contain rich, structured data that is well-suited for vectorization.

The standard Business Partner event, available out of the box in SAP S/4HANA Cloud, is a notification type event which contains minimal information. For simplicity purposes I will be using a custom "data type" Business Partner event, which just contains more data than usual.

We will use the CloudEvents specification as the format for our events. If you haven't worked with CloudEvents before, don't worry — we'll cover what you need to know. CloudEvents is a specification for describing event data in a common way. Its goal is to simplify event declaration and delivery across services and platforms. SAP has adopted it across its products, but it is also widely adopted across the open-source ecosystem.

Here is an example of a custom Business Partner Created data type event following the CloudEvents specification:

{
  "specversion": "1.0",
  "type": "sap.s4.custom.BusinessPartner.Created",
  "source": "/sap/s4/erp/business-partner",
  "id": "c54267d5-6318-488c-854a-c051602cde75",
  "time": "2026-04-29T15:32:38.947Z",
  "datacontenttype": "application/json",
  "subject": "1003770",
  "data": {
    "BusinessPartner": "1003770",
    "BusinessPartnerUUID": "89aa681d-5faf-4366-a813-e2d58445aea5",
    "BusinessPartnerFullName": "Manuel Abreu",
    "BusinessPartnerCategory": "1",
    "BusinessPartnerGrouping": "BP02",
    "FirstName": "Manuel",
    "LastName": "Abreu",
    "IsNaturalPerson": "X",
    "CreationDate": "/Date(1518393600000)/",
    "CreatedByUser": "CC0000000002",
    "BusinessPartnerAddress": {
      "Country": "PT",
      "Region": "",
      "CityName": "Praia da Vitória",
      "PostalCode": "6539-865",
      "StreetName": "Praça de Valente, 401",
      "HouseNumber": "12",
      "AddressTimeZone": "WEST"
    }
  }
}

You'll notice this event is a data event — unlike a pure notification event (which would only carry the BusinessPartner ID), this one includes fields that describe the business partner itself. That's intentional: richer data in the payload means more signal for our vectorization step later in the challenge.

Your task this week

👉 Publish at least three Business Partner events to a message broker of your choice.

The events should:

Follow the CloudEvents specification (pay attention to the required context attributes: specversion, type, source, id, time, datacontenttype, data)
Include meaningful data in the data field — not just an ID. Think name, region, country, type, etc.
Be published to a topic that follows a sensible naming convention. For example: sap/s4/custom/BusinessPartner/Created/PT/1003770

Broker options — use whatever you have access to:

SAP options: SAP Integration Suite, advanced event mesh (AEM), SAP Cloud Application Event Hub, Event Mesh capability in SAP Integration Suite (EMIS).
Open-source options: Solace PubSub+ (free tier), RabbitMQ, or any other you might have available.

You can publish the events programmatically (recommended) or manually via a broker's management UI or REST API.

Generate events

To help you generating events, I've published a simple web app (Business Event Generator 📡) that can connect to an AEM broker or EMIS. With it, you can publish some Business Partners Create data events with the same structure as the one above. In case you don't have access to an AEM or EMIS instance, you can just copy the Business Partner data available in the repo and use it programatically to generate your own events.

The data published is not real data. It was all generated using the awesome 🐍 Python Faker library 😃

To complete this week's challenge, add a comment in this discussion with:

A screenshot or code snippet showing your events being published to your broker
A sample of one of the CloudEvents you published (mask any sensitive data)
Which broker you used and why you chose it

SAP solution note — I'm sharing in the comments below how I solved this using SAP Integration Suite + Advanced Event Mesh.

Re: May 2026 Developer Challenge — Week 1: Getting familiar with the events

ajmaradiaga — Mon, 04 May 2026 09:25:54 GMT

I'm a bit biased and I'm using the Business Event Generator shared above to send events :-). You can see that it will generate events exactly as the one shown above. In my case it is connected to AEM but I think I might switch to EMIS for next week.
Event generator connected to AEMSample event payload

Re: May 2026 Developer Challenge — Week 1: Getting familiar with the events

KanishkaDeshak — Thu, 07 May 2026 12:51:28 GMT

Hello!!

Thanks for this challenge.

I have tried the event generator with Solace platform, connected it to sap CPI for publishing the event.

Using the solace PubSub+ platform as SAP AEM is powered by solace and both of them have similar UI. here are the steps Ive followed.

1. generated events.

2. consumed them by subscribing to the below topic

Consuming only the events associated with India(IN).
QUEUE:

Now consuming these in CPI.

{
"specversion": "1.0",
"type": "sap.s4.custom.BusinessPartner.Created",
"source": "/sap/s4/erp/business-partner",
"id": "154054a3-fed0-48fe-951b-3548bff57a59",
"time": "2026-05-07T10:51:21.455Z",
"datacontenttype": "application/json",
"subject": "1003775",
"data": {
"BusinessPartner": "1003775",
"BusinessPartnerUUID": "1b2eb535-324a-4555-922e-8b1cde0abd13",
"BusinessPartnerFullName": "Anaya Rajagopal",
"BusinessPartnerCategory": "1",
"BusinessPartnerGrouping": "BP02",
"FirstName": "Anaya",
"LastName": "Rajagopal",
"IsNaturalPerson": "X",
"CreationDate": "/Date(1518393600000)/",
"CreatedByUser": "CC0000000002",
"BusinessPartnerAddress": {
"Country": "IN",
"Region": "",
"CityName": "Ajmer",
"PostalCode": "742814",
"StreetName": "56/16\nTank Chowk",
"HouseNumber": "H.No. 051",
"AddressTimeZone": "IST"
}
}
}

Any corrections/suggestions are welcome

Thanks,

Kanishka

Re: May 2026 Developer Challenge — Week 1: Getting familiar with the events

ajmaradiaga — Thu, 07 May 2026 13:40:35 GMT

Excellent @KanishkaDeshak , you are actually getting ahead and have nearly completed week 2 hehe. Great job!

Re: May 2026 Developer Challenge — Week 1: Getting familiar with the events

MioYasutake — Fri, 08 May 2026 20:42:57 GMT

My submission for week1:

1. A screenshot of my event being published to my broker

2. A sample of one of the CloudEvents I published

{ "specversion": "1.0", "type": "sap.s4.custom.BusinessPartner.Created", "source": "/sap/s4/erp/business-partner", "id": "a7b2c3d4-e5f6-47a8-b9c0-d1e2f3a4b5c6", "time": "2026-05-09T06:15:22.845Z", "datacontenttype": "application/json", "subject": "1004823", "data": { "BusinessPartner": "1004823", "BusinessPartnerUUID": "f8e9d0c1-b2a3-4567-8901-234567890abc", "BusinessPartnerFullName": "Yasutake Mio", "BusinessPartnerCategory": "1", "BusinessPartnerGrouping": "BP02", "FirstName": "Mio", "LastName": "Yasutake", "IsNaturalPerson": "X", "CreationDate": "/Date(1715241600000)/", "CreatedByUser": "CC0000000002", "BusinessPartnerAddress": { "Country": "JP", "Region": "13", "CityName": "Tokyo", "PostalCode": "100-0001", "StreetName": "1-1-1 Chiyoda", "HouseNumber": "", "AddressTimeZone": "JST" } } }

3. I used Solace PubSub+ (free tier). Initially, I considered using EMIS, but that option was unavailable with the trial account. Therefore, I chose this option. Additionally, it has many similarities with AEM.

Re: May 2026 Developer Challenge — Week 1: Getting familiar with the events

JMV — Sat, 09 May 2026 14:20:31 GMT

Hi,

Many thanks for this Challenge. So relevant for our upcoming requirement and lot of learning opportunity .

1) Generated the events from a simple standalone ABAP program using client post method.

2) Set the up broker in Solace (Used Solace AI to build the end to end)

Re: May 2026 Developer Challenge — Week 1: Getting familiar with the events

fjaviergar07 — Sun, 10 May 2026 13:22:40 GMT

Hi there,

I have chosen AEM since it has been a while since I use it and also wanted to have a look to your tool to generate the events, pretty useful.

And the events I received in the broker:

looking forward to the next weeks.

Best regards

Javier

Re: May 2026 Developer Challenge — Week 1: Getting familiar with the events

Joery — Sun, 10 May 2026 11:46:29 GMT

Hi,

I chose RabbitMQ as my broker because it is lightweight, reliable, and highly portable and I could run locally via Docker. Since I am building this on a personal Linux environment, I wanted a stack that allows for full offline development while remaining compliant with the Cloud Events specification.

Using the MQTT plugin for RabbitMQ allows bridging traditional messaging with a Python-based pipeline.
This setup feeds directly into my workflow using Ollama (which I already had from previous experiments) for local embeddings and ChromaDB for vector storage, demonstrating how SAP-style event patterns can be implemented with an entirely local, open-source toolchain.

Here is the schema that I am using, I intentionally kept it simple.

When I had everything running in background I could launch the events:

These were then picked up and processed

And I can find those in the DB

Kind Regards,
Joery

Re: May 2026 Developer Challenge — Week 1: Getting familiar with the events

Andrii — Sun, 10 May 2026 22:01:31 GMT

Week1

1. I've created in solace -> cluster manager -> service and used “Try Me!” messaging interface.

2. Published cloud event

{
"specversion": "1.0",
"type": "sap.s4.custom.BusinessPartner.Created",
"source": "/sap/s4/erp/business-partner",
"id": "ab2c3d4-e5f6-47a8-b9c0-d1e2f3a4b5c6",
"time": "2026-05-09T06:15:22.845Z",
"datacontenttype": "application/json",
"subject": "1003770",
"data": {
"BusinessPartner": "1003770",
"BusinessPartnerUUID": "89aa681d-5faf-4366-a813-e2d58445aea5",
"BusinessPartnerFullName": "Manuel Abreu",
"BusinessPartnerCategory": "1",
"BusinessPartnerGrouping": "BP02",
"FirstName": "Manuel",
"LastName": "Abreu",
"IsNaturalPerson": "X",
"CreatedByUser": "CC0000000002",
"BusinessPartnerAddress": {
"Country": "PT",
"CityName": "Praia da Vitória",
"PostalCode": "6539-865",
"StreetName": "Praça de Valente, 401",
"HouseNumber": "12",
"AddressTimeZone": "WEST"
}
}
}

3. Broker used: SAP Advanced Event Mesh (AEM)

Re: May 2026 Developer Challenge — Week 1: Getting familiar with the events

ajmaradiaga — Mon, 11 May 2026 06:34:37 GMT

Very nice solution! Looks like you've implemented the entire scenario already hehe. I look forward to see how it evolves in the next couple of weeks :-).

Re: May 2026 Developer Challenge — Week 1: Getting familiar with the events

ajmaradiaga — Mon, 11 May 2026 06:35:24 GMT

Nice! Thanks for sharing

Re: May 2026 Developer Challenge — Week 1: Getting familiar with the events

ajmaradiaga — Mon, 11 May 2026 06:36:26 GMT

That's correct... AEM is powered by Solace technology so getting familiar and using Solace PubSub+ is a great way for learning AEM 🙂

Re: May 2026 Developer Challenge — Week 1: Getting familiar with the events

Swathi_SAP_Philomath — Mon, 11 May 2026 13:03:44 GMT

I tried using Business Event Generator (AEM broker) :

Business Event Generator (AEM broker)

Solace:

Re: May 2026 Developer Challenge — Week 1: Getting familiar with the events

nethrashivendra60 — Mon, 11 May 2026 18:33:16 GMT

Week 1:

1. Used Try Me to publish the below payload

{ "specversion": "1.0", "type": "sap.s4.custom.BusinessPartner.Created", "source": "/sap/s4/erp/business-partner", "id": "c54267d5-6318-488c-854a-c051602cde75", "time": "2026-04-29T15:32:38.947Z", "datacontenttype": "application/json", "subject": "1003770", "data": { "BusinessPartner": "1003770", "BusinessPartnerUUID": "89aa681d-5faf-4366-a813-e2d58445aea5", "BusinessPartnerFullName": "Manuel Abreu", "BusinessPartnerCategory": "1", "BusinessPartnerGrouping": "BP02", "FirstName": "Manuel", "LastName": "Abreu", "IsNaturalPerson": "X", "CreationDate": "/Date(1518393600000)/", "CreatedByUser": "CC0000000002", "BusinessPartnerAddress": { "Country": "PT", "Region": "", "CityName": "Praia da Vitória", "PostalCode": "6539-865", "StreetName": "Praça de Valente, 401", "HouseNumber": "12", "AddressTimeZone": "WEST" } }

2. Created queue in AEM

Also did a mistake by using wildcard at a wrong place 😄
sap/s4/custom/BusinessPartner/Created/PT*.

But I figured it out and the event is in the Queue.

Re: May 2026 Developer Challenge — Week 1: Getting familiar with the events

ajay_soreng — Wed, 13 May 2026 10:45:45 GMT

My submission for week1 . Sent the event via Business Event Generator app and received via Solace AEM broker.

Another one via try me feature. I choose solace because SAP Integration Suite AEM is solace under the hood.

Re: May 2026 Developer Challenge — Week 1: Getting familiar with the events

umberto_panico — Thu, 14 May 2026 10:52:21 GMT

WEEK 1

Re: May 2026 Developer Challenge — Week 1: Getting familiar with the events

Chaimae_Chairi27 — Thu, 14 May 2026 23:59:15 GMT

Better late than never:) Week 1 of the May challenge done!

Sample CloudEvent published:

{
"specversion": "1.0",
"type": "sap.s4.custom.BusinessPartner.Created",
"source": "/sap/s4/erp/business-partner",
"id": "c54267d5-6318-488c-854a-c051602cde75",
"time": "2026-04-29T15:32:38.947Z",
"datacontenttype": "application/json",
"subject": "2055633",
"data": {
"BusinessPartner": "2055633",
"BusinessPartnerUUID": "89aa681d-5faf-4366-a813-e2d58445aea5",
"BusinessPartnerFullName": "Chaimae CHAIRI",
"BusinessPartnerCategory": "1",
"BusinessPartnerGrouping": "BP02",
"FirstName": "Chaimae",
"LastName": "CHAIRI",
"IsNaturalPerson": "X",
"CreationDate": "/Date(1518393600000)/",
"CreatedByUser": "CC0000000002",
"BusinessPartnerAddress": {
"Country": "MA",
"Region": "Casablanca-Settat",
"CityName": "Casablanca",
"PostalCode": "20000",
"StreetName": "Boulevard Mohammed Zerktouni",
"HouseNumber": "20",
"AddressTimeZone": "GMT"
}
}
}

Broker used: Solace PubSub+ Cloud (free tier / Developer plan)

Business Event Generator web app to publish Business Partner Created events to my Solace broker

Thank you for this challenge !

Re: May 2026 Developer Challenge — Week 1: Getting familiar with the events

Ihor_Haranichev — Sat, 16 May 2026 15:36:45 GMT

Thanks for the challenge!

A sample:

{
"specversion": "1.0",
"type": "sap.s4.custom.BusinessPartner.Created",
"source": "/sap/s4/erp/business-partner",
"id": "bp-1001",
"time": "2026-05-16T10:00:00Z",
"datacontenttype": "application/json",
"subject": "100001",
"data": {
"BusinessPartner": "100001",
"BusinessPartnerFullName": "Anna Novak",
"BusinessPartnerCategory": "1",
"Country": "CZ",
"City": "Prague",
"Region": "Prague",
"CreatedByUser": "DEV_USER"
}
}

Solace Cloud was chosen as a free tool to implement event-driven messaging without the need for local infrastructure.

Re: May 2026 Developer Challenge — Week 1: Getting familiar with the events

reury — Wed, 20 May 2026 07:18:30 GMT

My submission for week 1:

Broker used: Solace PubSub+ Cloud (Free Tier). I chose it because SAP Advanced Event Mesh is powered by Solace under the hood, making the learning experience identical!
Event Generator: I used the Business Event Generator web app to successfully simulate and publish the S/4HANA Business Partner events.
Sample CloudEvent:{"specversion":"1.0","type":"sap.s4.custom.BusinessPartner.Created","source":"/sap/s4/erp/business-partner","id":"4deab3e2-8472-4a89-8da0-885d467d3853","time":"2026-05-20T07:10:58.552Z","datacontenttype":"application/json","subject":"1003787","data":{"BusinessPartner":"1003787","BusinessPartnerUUID":"36f8993d-66ce-4536-829d-cb5f5a41a09b","BusinessPartnerFullName":"Prof. Stjepan Lehmann","BusinessPartnerCategory":"1","BusinessPartnerGrouping":"BP02","FirstName":"Prof.","LastName":"Stjepan","IsNaturalPerson":"X","CreationDate":"/Date(1518393600000)/","CreatedByUser":"CC0000000002","BusinessPartnerAddress":{"Country":"DE","Region":"","CityName":"Wiedenbrück","PostalCode":"14593","StreetName":"Neuschäferweg 8","HouseNumber":"3/7","AddressTimeZone":"CEST"}}}

Re: May 2026 Developer Challenge — Week 1: Getting familiar with the events

sharanjee_186716 — Mon, 25 May 2026 06:03:14 GMT

Finally I am able to publish and subscribe. great learning.

1. Broker used: Solace PubSub+ Cloud (free tier)

2. Event Generator: I used the Demo Business event Generator Web App.

topic Re: May 2026 Developer Challenge — Week 1: Getting familiar with the events in Integration Forum

May 2026 Developer Challenge - Week 1: Getting familiar with the events

The scenario

Your task this week

Generate events

Share your work

Further reading

Re: May 2026 Developer Challenge — Week 1: Getting familiar with the events

Re: May 2026 Developer Challenge — Week 1: Getting familiar with the events

Re: May 2026 Developer Challenge — Week 1: Getting familiar with the events

Re: May 2026 Developer Challenge — Week 1: Getting familiar with the events

Re: May 2026 Developer Challenge — Week 1: Getting familiar with the events

Re: May 2026 Developer Challenge — Week 1: Getting familiar with the events

Re: May 2026 Developer Challenge — Week 1: Getting familiar with the events

Re: May 2026 Developer Challenge — Week 1: Getting familiar with the events

Re: May 2026 Developer Challenge — Week 1: Getting familiar with the events

Re: May 2026 Developer Challenge — Week 1: Getting familiar with the events

Re: May 2026 Developer Challenge — Week 1: Getting familiar with the events

Re: May 2026 Developer Challenge — Week 1: Getting familiar with the events

Re: May 2026 Developer Challenge — Week 1: Getting familiar with the events

Re: May 2026 Developer Challenge — Week 1: Getting familiar with the events

Re: May 2026 Developer Challenge — Week 1: Getting familiar with the events

Re: May 2026 Developer Challenge — Week 1: Getting familiar with the events

Re: May 2026 Developer Challenge — Week 1: Getting familiar with the events

Re: May 2026 Developer Challenge — Week 1: Getting familiar with the events

Re: May 2026 Developer Challenge — Week 1: Getting familiar with the events