I recently participated in an SAP Code Jam focused on building event-driven processes using SAP Integration Suite (Advanced Event Mesh) and SAP Build Process Automation. The Session was ably conducted and managed by @ajay_soreng and @Rekha_DR .
Codejams are my favorite community events. It pure code with access to the best of SAP in terms of tools, license and expertise. In this session we had a hands-on and walkthrough of a realistic end-to-end scenario rather than a theoretical demo.
The core use case was triggered by a Business Partner creation event in a simulated SAP S/4HANA Cloud system. Once the Business Partner was created and tagged, an event was published to SAP Advanced Event Mesh, where I configured topics, queues, and subscriptions to reliably route the event.
As you see in the below soln. diagram, an event is triggered by App. The advanced event mesh is configured to handle these events and appropriately route it to the build process and finally allow user to act on it.Â
Event Triggered from a Mock UI:Â
Configure the Broker Manager – The best part of this code jam:
The plethora of options of Event mesh were made available to us. The Queues, RDPs, Connectors, Tyr me’s etc. was a learning experience. Â
As for the use case,Â
using a REST Delivery Point, the event was forwarded from Advanced Event Mesh to SAP Build Process Automation, which automatically triggered a business process. From there, the flow combined event-driven automation with human interaction—a user approval step in the SAP Build Inbox—followed by an asynchronous call to a simulated third-party badge system.
The process paused, waited for a callback, and then resumed to complete the flow with a final notification and badge ID.
Â
Â
What stood out most was seeing how cleanly systems were decoupled. The event producer had no awareness of the consumers, and SAP Build acted purely as an orchestrator reacting to events. Configuring and testing this live made the benefits of event-driven architecture very tangible.
Overall, I enjoyed the Code Jam as it was a great practical deep dive into how SAP Advanced Event Mesh and SAP Build Process Automation.
Thanks to all the developer advocates, especially @ajmaradiaga for compiling the content on integration suite and adv. event mesh.
Until the next code jam – Ciao !Â
Â
​ I recently participated in an SAP Code Jam focused on building event-driven processes using SAP Integration Suite (Advanced Event Mesh) and SAP Build Process Automation. The Session was ably conducted and managed by @ajay_soreng and @Rekha_DR .Codejams are my favorite community events. It pure code with access to the best of SAP in terms of tools, license and expertise. In this session we had a hands-on and walkthrough of a realistic end-to-end scenario rather than a theoretical demo.The core use case was triggered by a Business Partner creation event in a simulated SAP S/4HANA Cloud system. Once the Business Partner was created and tagged, an event was published to SAP Advanced Event Mesh, where I configured topics, queues, and subscriptions to reliably route the event.As you see in the below soln. diagram, an event is triggered by App. The advanced event mesh is configured to handle these events and appropriately route it to the build process and finally allow user to act on it. Event Triggered from a Mock UI: Configure the Broker Manager – The best part of this code jam:The plethora of options of Event mesh were made available to us. The Queues, RDPs, Connectors, Tyr me’s etc. was a learning experience.  As for the use case, using a REST Delivery Point, the event was forwarded from Advanced Event Mesh to SAP Build Process Automation, which automatically triggered a business process. From there, the flow combined event-driven automation with human interaction—a user approval step in the SAP Build Inbox—followed by an asynchronous call to a simulated third-party badge system.The process paused, waited for a callback, and then resumed to complete the flow with a final notification and badge ID.  What stood out most was seeing how cleanly systems were decoupled. The event producer had no awareness of the consumers, and SAP Build acted purely as an orchestrator reacting to events. Configuring and testing this live made the benefits of event-driven architecture very tangible.Overall, I enjoyed the Code Jam as it was a great practical deep dive into how SAP Advanced Event Mesh and SAP Build Process Automation.Thanks to all the developer advocates, especially @ajmaradiaga for compiling the content on integration suite and adv. event mesh.Until the next code jam – Ciao !    Read More Technology Blog Posts by Members articlesÂ
#SAP
#SAPTechnologyblog
