Introduction
Event-driven architectures are increasingly shaping modern SAP landscapes. Many customers started their journey using the NetWeaver add-on for event enablement (component ASANWEE) to publish business events from their SAP systems to SAP Event Mesh.
While this setup works well for basic SAP BTP scenarios, growing enterprise requirements — such as hybrid integration, advanced routing, and high availability — often require a more powerful event broker.
This is where the Event Add-On for ERP (ASAAEMEE) in combination with SAP Advanced Event Mesh becomes highly relevant.
This article applies to:
SAP ERP (ECC 6.0 and higher)
SAP S/4HANA (on-premise, private cloud, all versions)
and explains the technical migration steps from component ASANWEE to ASAAEMEE.
Prerequisits:
NetWeaver Add-On for Event Enablement is installed (component ASANWEE).Event Add-on for ERP is installed (component ASAAEMEE, installed on top of ASANWEE).SAP Advanced Event Mesh service instance is provisioned.Service Key from the BTP is available.Ensure that the erp_event_add_on entitlement is added to your subaccount in the SAP BTP cockpit.The SAP Integration Suite, Advanced Event Mesh instance must be of type standard plan, not default plan. For details on migrating to the standard service plan, refer to the SAP Advanced Event Mesh migration guide.
Migration Steps
Step 1: Create RFC-Destinations.
To establish the connection to the SAP Advanced Event Mesh, we will create three RFC-Destinations in transaction SM59.
1. Create RFC-Destination pointing to the REST endpoint of the Advanced Event Mesh (Available inside the AEM broker).
Type: G (HTTP Connection to External Server).
Target Host: AEM REST endpoint host.Basic Authentication: Add credentials, listed in the AEM broker for the REST endpoint.SSL: Active.Connection test should return in a 405 Method Not Allowed.
2. Create RFC-Destination for the Handshake (Available inside the SAP BTP Service Key).
Type: G
Target Host: Handshake URL from the SAP BTP Service KeyPath Prefix: /handshakeSSL: Active.
3. Create RFC-Destination for the Token (Available inside the SAP BTP Service Key).
Type: G
Target Host: Token endpoint from Service KeyPath Prefix: /oauth/tokenSSL: Active.
Step 2: Add Certificates to the Trust Store.
To enable secure communication with SAP Advanced Event Mesh, the server certificate must be trusted in your SAP system.
Open transaction STRUST.Select the SSL Client PSE that is used in the RFC destination created in SM59 (usually SSL Client (Anonymous) unless a specific PSE was assigned).Click Import Certificate.Upload the certificate file (.cer / .crt).Click Add to Certificate List and save.
Step 3: Enable the Event Add-On for ERP.
Inside your SAP Advanced Event Mesh, navigate to Event Add-On for ERP.
After enabling the service, the component can be installed on your SAP system.
Step 4: Activate BC-Set.
Business Configuration Sets contain customizing and configuration-related table entries required for proper communication with SAP Advanced Event Mesh.
Transaction: SCPR20
Enter BC-Set name:/ASADEV/ACI_BCSET_FRAMEWORK_AEMChoose Activate.
Step 5: Copy Instance for SAP Event Mesh to new Instance for SAP Advanced Event Mesh.
Go to SPRO -> IMG -> Integration with Other SAP Components -> SAP NetWeaver AddOn for Event enablement -> Connection and Replication Object Customizing Or go directly to transaction /ASADEV/ACI_SETTINGS.Copy the existing SAP Event Mesh instance to create a new SAP Advanced Event Mesh instance:
Replace RFC destinations with the ones created for AEMChange Cloud Type from SAP_EM to SAP_AEM.
Hit Enter and copy all.Skip errors for duplicate Event Linkages
Delete all Default Values (not required for SAP AEM):
Delete Error Type Mapping (not required for SAP AEM):
You can keep the message type in case you delete the old Instance pointing to the SAP Event Mesh.Update message types if keeping the old SAP_EM instance::Create new Message Type in transaction WE81.Activate Change Pointer for the new message type in transaction BD50.
Add Event Linkages for the new message type:
Go to Header Attributes.Delete all Header Attributes for SAP EM.Add new Header Attributes for SAP AEM.
Go to Field Mapping and configure a dynamic topic.Each level becomes a segment in the dynamic topic.There are static segments (Default Values) and dynamic segments (Source structure and Source field).
Step 6: Add validation Instance for the SAP BTP.
Got to Connections and add New Entry.A Validation Instance will be necessary for the authentication against the BTP.Add RFC destination for Handshake (from Step 1).
Go to Default Values and specify:ACI_CLIENT_ID: Client ID from the Service Key.ACI_TOKEN_DESTINATION: RFC-Destination for the Token (from Step 1).AUTH_TYPE: OAUTH (Certificate also possible; refer to official documentation).
Add client secret from the Service KeyTransaction: SPROGo to: Integration with Other SAP Components -> SAP NetWeaver AddOn for Event enablement -> Set the cloud connection passwordOr go directly to transaction: /ASADEV/SCI_TPWSelect the Cloud Instance for validation: SAP_VALIDATIONEnter the client secret in the Cloud Shared Secret field and execute.
Step 7: Test the new connection to SAP Advanced Event Mesh.
After the steps from above we can now test our new connection to the SAP Advanced Event Mesh.
Change something in the Application, where your Event Add-on for ERP does have an Oubtound Object configured and check the monitor transaction /ASADEV/ACI_MONITOR.
Cloud response should be 200 OK.
On the left side of the Trace we can see the JSON and dynamic topic, that was used to send the message to the SAP Advances Event Mesh.
This was configured inside the Field Mapping of the Outbound Object.
Migration Completed
After these steps, your SAP system is successfully switched from SAP Event Mesh to SAP Advanced Event Mesh using ASAAEMEE.
No changes are required in event definitions.
Monitoring and validation ensure messages are delivered correctly.Find more configuration options for component ASAAEMEE inside the SAP Discovery Center mission “Data Exchange to Connect SAP ERP with SAP Advanced Event Mesh for Event-Driven Integration“.
IntroductionEvent-driven architectures are increasingly shaping modern SAP landscapes. Many customers started their journey using the NetWeaver add-on for event enablement (component ASANWEE) to publish business events from their SAP systems to SAP Event Mesh.While this setup works well for basic SAP BTP scenarios, growing enterprise requirements — such as hybrid integration, advanced routing, and high availability — often require a more powerful event broker.This is where the Event Add-On for ERP (ASAAEMEE) in combination with SAP Advanced Event Mesh becomes highly relevant.This article applies to:SAP ERP (ECC 6.0 and higher)SAP S/4HANA (on-premise, private cloud, all versions)and explains the technical migration steps from component ASANWEE to ASAAEMEE. Prerequisits:NetWeaver Add-On for Event Enablement is installed (component ASANWEE).Event Add-on for ERP is installed (component ASAAEMEE, installed on top of ASANWEE).SAP Advanced Event Mesh service instance is provisioned.Service Key from the BTP is available.Ensure that the erp_event_add_on entitlement is added to your subaccount in the SAP BTP cockpit.The SAP Integration Suite, Advanced Event Mesh instance must be of type standard plan, not default plan. For details on migrating to the standard service plan, refer to the SAP Advanced Event Mesh migration guide. Migration StepsStep 1: Create RFC-Destinations.To establish the connection to the SAP Advanced Event Mesh, we will create three RFC-Destinations in transaction SM59.1. Create RFC-Destination pointing to the REST endpoint of the Advanced Event Mesh (Available inside the AEM broker).Type: G (HTTP Connection to External Server).Target Host: AEM REST endpoint host.Basic Authentication: Add credentials, listed in the AEM broker for the REST endpoint.SSL: Active.Connection test should return in a 405 Method Not Allowed. 2. Create RFC-Destination for the Handshake (Available inside the SAP BTP Service Key).Type: GTarget Host: Handshake URL from the SAP BTP Service KeyPath Prefix: /handshakeSSL: Active.3. Create RFC-Destination for the Token (Available inside the SAP BTP Service Key).Type: GTarget Host: Token endpoint from Service KeyPath Prefix: /oauth/tokenSSL: Active. Step 2: Add Certificates to the Trust Store.To enable secure communication with SAP Advanced Event Mesh, the server certificate must be trusted in your SAP system.Open transaction STRUST.Select the SSL Client PSE that is used in the RFC destination created in SM59 (usually SSL Client (Anonymous) unless a specific PSE was assigned).Click Import Certificate.Upload the certificate file (.cer / .crt).Click Add to Certificate List and save. Step 3: Enable the Event Add-On for ERP.Inside your SAP Advanced Event Mesh, navigate to Event Add-On for ERP.After enabling the service, the component can be installed on your SAP system. Step 4: Activate BC-Set.Business Configuration Sets contain customizing and configuration-related table entries required for proper communication with SAP Advanced Event Mesh.Transaction: SCPR20Enter BC-Set name:/ASADEV/ACI_BCSET_FRAMEWORK_AEMChoose Activate. Step 5: Copy Instance for SAP Event Mesh to new Instance for SAP Advanced Event Mesh.Go to SPRO -> IMG -> Integration with Other SAP Components -> SAP NetWeaver AddOn for Event enablement -> Connection and Replication Object Customizing Or go directly to transaction /ASADEV/ACI_SETTINGS.Copy the existing SAP Event Mesh instance to create a new SAP Advanced Event Mesh instance:Replace RFC destinations with the ones created for AEMChange Cloud Type from SAP_EM to SAP_AEM.Hit Enter and copy all.Skip errors for duplicate Event LinkagesDelete all Default Values (not required for SAP AEM):Delete Error Type Mapping (not required for SAP AEM):You can keep the message type in case you delete the old Instance pointing to the SAP Event Mesh.Update message types if keeping the old SAP_EM instance::Create new Message Type in transaction WE81.Activate Change Pointer for the new message type in transaction BD50.Add Event Linkages for the new message type: Go to Header Attributes.Delete all Header Attributes for SAP EM.Add new Header Attributes for SAP AEM. Go to Field Mapping and configure a dynamic topic.Each level becomes a segment in the dynamic topic.There are static segments (Default Values) and dynamic segments (Source structure and Source field). Step 6: Add validation Instance for the SAP BTP.Got to Connections and add New Entry.A Validation Instance will be necessary for the authentication against the BTP.Add RFC destination for Handshake (from Step 1). Go to Default Values and specify:ACI_CLIENT_ID: Client ID from the Service Key.ACI_TOKEN_DESTINATION: RFC-Destination for the Token (from Step 1).AUTH_TYPE: OAUTH (Certificate also possible; refer to official documentation).Add client secret from the Service KeyTransaction: SPROGo to: Integration with Other SAP Components -> SAP NetWeaver AddOn for Event enablement -> Set the cloud connection passwordOr go directly to transaction: /ASADEV/SCI_TPWSelect the Cloud Instance for validation: SAP_VALIDATIONEnter the client secret in the Cloud Shared Secret field and execute. Step 7: Test the new connection to SAP Advanced Event Mesh.After the steps from above we can now test our new connection to the SAP Advanced Event Mesh.Change something in the Application, where your Event Add-on for ERP does have an Oubtound Object configured and check the monitor transaction /ASADEV/ACI_MONITOR.Cloud response should be 200 OK.On the left side of the Trace we can see the JSON and dynamic topic, that was used to send the message to the SAP Advances Event Mesh.This was configured inside the Field Mapping of the Outbound Object.Migration CompletedAfter these steps, your SAP system is successfully switched from SAP Event Mesh to SAP Advanced Event Mesh using ASAAEMEE.No changes are required in event definitions.Monitoring and validation ensure messages are delivered correctly.Find more configuration options for component ASAAEMEE inside the SAP Discovery Center mission “Data Exchange to Connect SAP ERP with SAP Advanced Event Mesh for Event-Driven Integration”. Read More Technology Blog Posts by Members articles
#SAP
#SAPTechnologyblog
