Custom Events in SAP Event Mesh. Step-by-Step (Part 2 – Trigger a Custom Event)

Prerequisite

• SAP NetWeaver add-on for event enablement is installed on your system.

Part 1: We will create a custom Event Linkage for a Material Change using transaction SWO1 and SWEC.

Part 2: Now we can make use of it in our SAP NetWeaver add-on for event enablement

Introduction to Part 2

After creating our custom event for a material change in part 1, we will make use of it with the SAP NetWeaver add-on. This way we can push a Material Change in real-time into the cloud.

Step 1: Customize outbound object

First, we will configure an Outbound Object.

SPRO –> IMG –> Integration with Other SAP Components –> SAP NetWeaver AddOn for Event Enablement –> Connection and Replication Object Customizing

Figure 1 Outbound Object

Step 2: Establish Business Object Event Linkage

After creating our Object Type in Part 1, we will configure the linkage to a Business Object Event.
Therefore, we will use transaction SWE2 and specify our custom Object Type ZBUS1001.
Receiver Type has to be created beforehand as seen in this blog post, using transaction WE81 and BD50.

Maintain the fields like seen in the figure below and click on safe.

Figure 2 Business Object Event Linkage

Step 3: Test the Event

After a material change the data will be sent by the SAP NetWeaver add-on to the SAP Event Mesh. In transaction /ASADEV/ACI_MONITOR or SLG1 we can see that the event was triggered correctly.

Figure 3 Business Object Event Linkage

Conclusion

In Part 2 we did following steps:

• Configure an Outbound Object in the SAP NetWeaver add-on for event enablement.
• Create linkage between BO Event and BO Subtype in SWE2.
• Finally trigger a material change and inspect it in the ACI-Monitor.

Please provide feedback or thoughts in the comment section.
There is a Q&A regarding the SAP Event Mesh.
You can also follow the tags and profiles for more upcoming articles.