Setting Up SAP Event Mesh

A service key in SAP Event Mesh ensures secure and authenticated communication between an SAP system and SAP Ariba supplier quotation management. Create a service key in the Instances section for the default Event Mesh instance. Once the service key is created on the BTP account, download the file with the service key. It will be used in the next setup steps.

When SAP S/4HANA and SAP BTP communicate with each other, the exchange needs to be secured. Adding a certificate in SAP S/4HANA will ensure authentication and provide secure connection during data exchange.

In the service key file, find the section with the eaa/url and open it in a browser. Right-click the link, and check that the communication is secure and the certificate is valid. Then, on the Certificate Viewer, go to Details and export the certificate.

Next, upload the certificate to SAP S/4HANA.

A channel ensures real-time, event-driven communication between SAP BTP and SAP S/4HANA. Create a new channel by using the service key you just created. Provide a name and description. Once the channel is established, activate and test the connection.

Outbound binding supports the exchange of documents in event-based architecture. Enablement of outbound bindings is mandatory for real-time business process integration.

Outbound bindings are created for existing channels, and are based on topics.

Create outbound bindings with the following topics:

• sap/s4/beh/sourcingproject/v1/SourcingProject/*
• sap/s4/beh/sourcingprojectnegotiation/v1/SourcingProjectNegotiation/*
• sap/s4/beh/sourcingprojectquotation/v1/SourcingProjectQuotation/*
• sap/s4/beh/legaldocument/v1/LegalDocument/Created/*
• sap/s4/beh/legaltransaction/v1/LegalTransaction/Created/*

During the sourcing project, several documents and changes can be published to SAP Ariba supplier quotation management. At the same time, several different events can be created by buyers or suppliers.

To keep everything organized and avoid any confusion in the process, SAP Event Mesh queues are used. These queues help manage the flow by connecting events to specific topics, ensuring events are delivered reliably. Essentially, a queue functions as a storage space for these events, keeping everything streamlined and ensuring a smooth exchange of information

To create queues in SAP Event Mesh, two roles are needed: Enterprise Messaging Administrator and Enterprise Messaging Developer.

Create the following queues:

• LegalDocument_Created:

  <namespace>/ce/sap/s4/beh/sourcingprojectquotation/v1/SourcingProjectQuotation/Submitted/v1

• LegalTransaction_Created:

  <namespace>/ce/sap/s4/beh/legaltransaction/v1/LegalTransaction/Created/v1

• Negotiation_Canceled:

  <namespace>/ce/sap/s4/beh/sourcingprojectnegotiation/v1/SourcingProjectNegotiation/Canceled/v1

• Negotiation_Completed:

  <namespace>/ce/sap/s4/beh/sourcingprojectnegotiation/v1/SourcingProjectNegotiation/Completed/v1

• Negotiation_Ended:

  <namespace>/ce/sap/s4/beh/sourcingprojectnegotiation/v1/SourcingProjectNegotiation/NegotiationEnded/v1

• Negotiation_Published:

  <namespace>/ce/sap/s4/beh/sourcingprojectnegotiation/v1/SourcingProjectNegotiation/Published/v1

• Quotation_Changed:

  <namespace>/ce/sap/s4/beh/sourcingprojectquotation/v1/SourcingProjectQuotation/Changed/v1

• Quotation_Submitted:

  <namespace>/ce/sap/s4/beh/sourcingprojectquotation/v1/SourcingProjectQuotation/Submitted/v1

• SourcingProject_Changed:

  <namespace>/ce/sap/s4/beh/sourcingproject/v1/SourcingProject/Changed/v1

• SourcingProject_Published:

  <namespace>/ce/sap/s4/beh/sourcingproject/v1/SourcingProject/Published/v1

The namespace corresponds to the SAP Event Mesh namespace.

Communication management is the foundation for secure system integration. Communication management comprises four elements:

• Communication user
• Communication system
• Communication scenarios
• Communication arrangement

A Communication user enables communication between SAP Ariba supplier quotation management and SAP Event Mesh. The Communication user needs to authenticate themselves using the communication user ID and password.

You need a communication system for inbound communication. This communication system will ensure that events are sent to SAP Ariba supplier quotation management.

The communication arrangement defines which communication system and which communication user will call the needed API. You create communication arrangements based on predefined communication scenarios.

Webhooks are part of the even-driven system architecture. They enable real-time business operations by notifying the system about events. Webhooks are created in SAP Event Mesh, and they are created per queue.

Establish the following webhooks:

• LegalDocument_Created
• LegalTransaction_Created
• Negotiation_Canceled
• Negotiation_Completed
• Negotiation_Ended
• Negotiation_Published
• Quotation_Changed
• Quotation_Submitted
• SourcingProject_Changed
• SourcingProject_Published

The URL needed in the webhooks setup is taken from the Communication Arrangement.

In the webhooks, enable the exempt handshake and provide the HTTP_INBOUND user credentials.

The SourcingProject_Changed and SourcingProject_Published webhooks are routed to HTTP service /BIDS/HTTP_EM_SOURCING_PROJECT.

The other webhooks created will be routed to HTTP service /BIDS/HTTP_EM_QUOTATION.

• Establish a service key in SAP Event Mesh to secure communication and download the file to use in further setup steps.
• Enhance secure communication between SAP S/4HANA and SAP BTP by adding certificates in SAP S/4HANA.
• Create channels for real-time communication between SAP systems and add outbound bindings for event-based document exchange.
• Set up webhooks and queues in SAP Event Mesh for reliable event delivery, enabling real-time operations with specific topic connections.