cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Automatic sending of SalesOrder messages from the S/4 HANA Public Cloud to SAP Event Mesh

MichaelSeydler
Discoverer
0 Likes
841

Hello Community,

When a new SalesOrder message is created or updated in the S/4 HANA Public Cloud, I would like this message to be automatically triggered in the SAP Event Mesh and stored in the salesorder queue of the SAP Event Mash. I have already stored an “event mesh” system with the corresponding host and outbound communication (OAuth 2.0 via clientID and clientsecret from the event mesh) in the S/4 HANA Public Cloud under Communication Systems. I have created a sales order queue directly in the event mesh under the corresponding message client and stored the topic “sap/s4/beh/salesorder/created/v1”. What steps still need to be taken explicitly in the S/4 HANA Public Cloud so that the sales orders are automatically sent to the queue?

In general, I later retrieve the contents of the queue from the cloud integration via an AMQP adapter and then the other SalesOrder information using an OData call.

Thanks in advance and best regards

Michael Seydler

Accepted Solutions (0)

Answers (2)

Answers (2)

Chuma
Active Contributor
0 Likes

Hello @MichaelSeydler 

Thank you for the details. You’re nearly done. Here are the final steps in SAP S/4HANA Cloud, Public Edition, to ensure Sales Order events are delivered to your Event Mesh queue:

Configure or confirm SAP_COM_0092 – Business Event Handling and direct it to your existing Communication System (OAuth 2.0 client from your Event Mesh message client)

Enterprise Event Enablement (EEE)
In the EEE apps:

Create a channel (type: SAP Event Mesh) and bind it to your SAP_COM_0092 configuration.

Add outbound topic bindings for sales order events.,

  • sap/s4/beh/salesorder/v1/SalesOrder/Created/v1

Event Mesh subscription
On SAP Event Mesh, ensure your queue (e.g., salesOrderQueue) subscribes to the exact topics above (or a safe wildcard such as sap/s4/beh/salesorder/v1/SalesOrder/*/v1).

Test and integrate
Create or update a Sales Order to ensure messages are received in the queue. Use SAP Cloud Integration with the AMQP adapter to consume messages, then call OData to fetch the complete Sales Order payload as needed.

Below are some useful SAP Documentation

S/4HANA Cloud Business Event Handling (SAP_COM_0092) – scope & setup (Help Portal)

Enterprise Event Enablement in S/4HANA Cloud – channels & outbound topic bindings (Help Portal)

SAP Event Mesh – queues, subscriptions, and topic wildcards (Help Portal)

SAP Cloud Integration – AMQP adapter guide (Help Portal)

Best regards,
Chuma

 

DequanXu
Product and Topic Expert
Product and Topic Expert
0 Likes

Hello,

To ensure sales orders in SAP S/4HANA Public Cloud are automatically sent to the sales order queue Event Driven Integration with SAP S/4 HANA Cloud u… - SAP Community in SAP Event Mesh, you need to complete the following steps:

1. Configure the Enterprise Event Enablement

  • Navigate to the Enterprise Event Enablement application in your S/4HANA Cloud system.
  • Ensure your user has the necessary permissions, specifically the role SAP_BR_ADMINISTRATOR.

2. Activate the Outbound Event

3. Verify Communication Arrangement

  • Check that the communication arrangement for eventing is correctly set up using the scenario SAP_COM_0092, if applicable.
  • Ensure it lists the event mesh as a client for outbound topics.

4. Set Up Event Mesh Queue

  • Within the SAP Event Mesh, ensure the queue salesOrderChangedQueue subscribes to the event sap/s4/beh/salesorder/created/v1.
  • Make sure the queue is correctly configured to handle incoming sales order events.

5. Configure Webhook (Optional)

  • If using a webhook in SAP Event Mesh, ensure proper settings including OAuth2.0 client credentials for security.

6. Integration Suite Configuration

  • Set up the AMQP adapter in your SAP Cloud Integration to retrieve messages from the sales order queue.
  • Ensure that the configuration allows for handling the data content type and formatting (e.g., JSON to XML) for subsequent OData calls.

Best regards,

Dequan Xu