As more and more organizations modernize their integration landscapes whether they are SAP or non-SAP eco systems, Event-Driven Architecture (EDA) is becoming an essential approach to achieving real-time, scalable, and loosely coupled data exchange. Traditional master data distribution—often based on scheduled or API-driven replication—can no longer keep up with the dynamic needs of digital ecosystems that demand instant synchronization across hybrid SAP and non-SAP environments.
By leveraging SAP Integration Suite, Advanced Event Mesh (AEM), and ERP event-on for AEM, enterprises can easily shift toward event-based master data distribution to ensure that updates in systems of records are propagated intelligently, only where and when they are needed. This trend not only reduces system load and redundancy but also enables fine-grained control through mechanisms like source-side filtering and dynamic topic filtering within brokers, which together make EDA a cornerstone for next-generation integration strategies.
Three years ago, I shared a blog on the SAP Event Enablement Add-On for SAP Event Mesh. Since then, SAP Advanced Event Mesh (AEM) has rapidly gained growth as an enterprise-grade event broker with the capability to connect applications, data, and devices across diverse landscapes.
In this blog, I would like to revisit the ASAPIO Add-On, specifically in the context of integration SAP Advanced Event Mesh. While the add-on continues to be powered by ASAPIO technology, its usage patterns and relevance have evolved alongside AEM’s growing adoption. Most of the functionalities are similar but with the ability to build custom payloads and to connect to AEM, it unlocks the value of moving data in real-time from large to very large use cases.
@Benedikt_Sprung has already published an excellent step-by-step guide on setting up and using the add-on with AEM. Instead of duplicating that content, my focus here will be on a key design consideration: the filtering options available with the add-on and AEM and how they can be applied effectively in real-world scenarios.
Why filtering matters?
Typically, Event-driven architectures (EDA) topics define how events are organized. The way we design and manage topics has a profound impact on scalability, governance, and maintainability.
In the context of SAP Integration Suite, Advanced Event Mesh (AEM) with ASAPIO add-on, two patterns come into discussion with event filtering: source-side filtering (on sender SAP applications) and Dynamic Topics & Filtering (within AEM brokers).
This post explores the difference between these two approaches, when to use each, and how AEM enables more intelligent event distribution in enterprise landscapes.
Option 1: Source-Side Filtering on Event Producer
Source-Side filtering usually means the producer (event source) decides dynamically at publish time whether an event should be triggered. Often, a filter based on payload data will be applied to the event liberation.
With ASAPIO add-on, you can use a check function module in header attributes to filter on attributes of the Business Object. For example, you can add the Attribute ID to your Header Attribute customizing in event add-on for ERP: BOR_ATTRIBUTE_<BOR Attribute from SWO1>
In this case, only the material data with material group 004 will be triggered. The event broker (AEM) will not receive any data outside of material group 004.
Option 2: Dynamic Topics & Filtering on Event Broker
With this option, the producer (event source) decides at publish time which topic an event should be sent to. Often, topic names are built using runtime data (e.g., customer ID, region, product type).
With ASAPIO add-on, you can set up dynamic topics easily with Field Mapping. It helps you define different layers of the topics and make dynamic filtering easier later during consumption.
Based on event context, events can be published to different topics into SAP AEM. Consumers then subscribe only to the events they care about. In above example, topics are built dynamically with the Sales Org ID. If a consumer wants all the data of Sales Order update of Org 1000, it can subscribe to topic /UPDATE/V1/JSON/sap-bo-event/ERD100/1000/BUS2032/>.
In this case, all events are still published to the broker but they can be sorted/routef based on the structure of the topics.
When to Use Which?
Source Side Filtering typically works well when consumers are highly specialized and fixed. You don’t expect new applications to be added in the future. And in the case when broker load and network traffic is a concern, you can use this option to reduce overhead.
In contrast, dynamic topics & filtering helps you operate at enterprise scale (hundreds of apps, regions, business lines). You want to use this option when you want producers to stay simple and consumers to self-serve. with SAP AEM, it can support very large scale use cases. Using this option will help you have better governance and discoverability on events.
Dynamic topics & filtering is recommended in most of the use cases as it supports better scalability and flexibility in an EDA integration. To support this option, SAP AEM has its Smart Topics feature to organize event topics. The Topic Taxonomy can be described with none+verb+properties. AEM relies on hierarchical topic structures(using “/” separators) to enable dynamic routing, filtering, and fine-tuned subscriptions.
An Example of master data event topics could be:
materialmaster / updated / <materialgroup> / <materialtype>materialmaster / created / <materialgroup> / <materialtype>
With a defined structure, subscribers can filter based on dynamic topics that they are interested in:
This allows flexibility of subscription and allows consumers to self-serve as well.
Conclusion and key takeaways
While source-side filtering gives flexibility, it often leads to topic sprawl and tighter coupling. With SAP Integration Suite, Advanced Event Mesh, enterprises can adopt Smart Topics with Dynamic Topics & Filtering — a governance-friendly, scalable way to manage events. This approach keeps producers simple and empowers consumers at enterprise scale.
In most of the use cases, master data distribution is a fan-out pattern, in this case Dynamic Topics & Filtering will provide more flexibility to distribute the data based on needs without tight coupling with producers. Below is a reference architecture for a fan-out scenario and with dynamic topic filtering and multiple integration options, you will be able to easily send to the relevant data to consumers.
Happy Eventing!!
As more and more organizations modernize their integration landscapes whether they are SAP or non-SAP eco systems, Event-Driven Architecture (EDA) is becoming an essential approach to achieving real-time, scalable, and loosely coupled data exchange. Traditional master data distribution—often based on scheduled or API-driven replication—can no longer keep up with the dynamic needs of digital ecosystems that demand instant synchronization across hybrid SAP and non-SAP environments.By leveraging SAP Integration Suite, Advanced Event Mesh (AEM), and ERP event-on for AEM, enterprises can easily shift toward event-based master data distribution to ensure that updates in systems of records are propagated intelligently, only where and when they are needed. This trend not only reduces system load and redundancy but also enables fine-grained control through mechanisms like source-side filtering and dynamic topic filtering within brokers, which together make EDA a cornerstone for next-generation integration strategies.Three years ago, I shared a blog on the SAP Event Enablement Add-On for SAP Event Mesh. Since then, SAP Advanced Event Mesh (AEM) has rapidly gained growth as an enterprise-grade event broker with the capability to connect applications, data, and devices across diverse landscapes. In this blog, I would like to revisit the ASAPIO Add-On, specifically in the context of integration SAP Advanced Event Mesh. While the add-on continues to be powered by ASAPIO technology, its usage patterns and relevance have evolved alongside AEM’s growing adoption. Most of the functionalities are similar but with the ability to build custom payloads and to connect to AEM, it unlocks the value of moving data in real-time from large to very large use cases.@Benedikt_Sprung has already published an excellent step-by-step guide on setting up and using the add-on with AEM. Instead of duplicating that content, my focus here will be on a key design consideration: the filtering options available with the add-on and AEM and how they can be applied effectively in real-world scenarios. Why filtering matters?Typically, Event-driven architectures (EDA) topics define how events are organized. The way we design and manage topics has a profound impact on scalability, governance, and maintainability. In the context of SAP Integration Suite, Advanced Event Mesh (AEM) with ASAPIO add-on, two patterns come into discussion with event filtering: source-side filtering (on sender SAP applications) and Dynamic Topics & Filtering (within AEM brokers).This post explores the difference between these two approaches, when to use each, and how AEM enables more intelligent event distribution in enterprise landscapes. Option 1: Source-Side Filtering on Event ProducerSource-Side filtering usually means the producer (event source) decides dynamically at publish time whether an event should be triggered. Often, a filter based on payload data will be applied to the event liberation.With ASAPIO add-on, you can use a check function module in header attributes to filter on attributes of the Business Object. For example, you can add the Attribute ID to your Header Attribute customizing in event add-on for ERP: BOR_ATTRIBUTE_<BOR Attribute from SWO1> In this case, only the material data with material group 004 will be triggered. The event broker (AEM) will not receive any data outside of material group 004.Option 2: Dynamic Topics & Filtering on Event BrokerWith this option, the producer (event source) decides at publish time which topic an event should be sent to. Often, topic names are built using runtime data (e.g., customer ID, region, product type).With ASAPIO add-on, you can set up dynamic topics easily with Field Mapping. It helps you define different layers of the topics and make dynamic filtering easier later during consumption. Based on event context, events can be published to different topics into SAP AEM. Consumers then subscribe only to the events they care about. In above example, topics are built dynamically with the Sales Org ID. If a consumer wants all the data of Sales Order update of Org 1000, it can subscribe to topic /UPDATE/V1/JSON/sap-bo-event/ERD100/1000/BUS2032/>.In this case, all events are still published to the broker but they can be sorted/routef based on the structure of the topics. When to Use Which?Source Side Filtering typically works well when consumers are highly specialized and fixed. You don’t expect new applications to be added in the future. And in the case when broker load and network traffic is a concern, you can use this option to reduce overhead.In contrast, dynamic topics & filtering helps you operate at enterprise scale (hundreds of apps, regions, business lines). You want to use this option when you want producers to stay simple and consumers to self-serve. with SAP AEM, it can support very large scale use cases. Using this option will help you have better governance and discoverability on events. Dynamic topics & filtering is recommended in most of the use cases as it supports better scalability and flexibility in an EDA integration. To support this option, SAP AEM has its Smart Topics feature to organize event topics. The Topic Taxonomy can be described with none+verb+properties. AEM relies on hierarchical topic structures(using “/” separators) to enable dynamic routing, filtering, and fine-tuned subscriptions.An Example of master data event topics could be:materialmaster / updated / <materialgroup> / <materialtype>materialmaster / created / <materialgroup> / <materialtype>With a defined structure, subscribers can filter based on dynamic topics that they are interested in:This allows flexibility of subscription and allows consumers to self-serve as well. Conclusion and key takeawaysWhile source-side filtering gives flexibility, it often leads to topic sprawl and tighter coupling. With SAP Integration Suite, Advanced Event Mesh, enterprises can adopt Smart Topics with Dynamic Topics & Filtering — a governance-friendly, scalable way to manage events. This approach keeps producers simple and empowers consumers at enterprise scale.In most of the use cases, master data distribution is a fan-out pattern, in this case Dynamic Topics & Filtering will provide more flexibility to distribute the data based on needs without tight coupling with producers. Below is a reference architecture for a fan-out scenario and with dynamic topic filtering and multiple integration options, you will be able to easily send to the relevant data to consumers. Happy Eventing!! Read More Technology Blog Posts by Members articles
#SAP
#SAPTechnologyblog
