Trigger event lost in Build Process Automation

[MioYasutake]

Hi community,

I have configured Event Mesh (in Integration Suite) and SAP Build Process Automation to start a process when a journal entiry is created in S/4HANA on-premise.

A webhook subscription has been created in Event Mesh, and the handshake was successful.

A process has been created with an event trigger, and deployed.

When a journal entry is created in S/4HANA, the number of t"Message Queued" increased to 1, and soon decreased to 0. This indicates that the message was sent to the webhook (Build Process Automation).

However, no process started in Build Process Automation. Now I am wondering where the message has gone.

Monitoroing > Event Aquisition > Business Events shows no data.

Could anyone tell me where such "lost" events can be monitored and investigated?

Best regards,

Mio Yasutake

[Mell]

Hello Mio Yasutake,

Did you found a solution for this? We are trying the exact same thing and it doesn't work for us either in the Event Mesh, Integration Suite while in the other hand in the Event Mesh, Default Plan (with the same set-up) is working. 

Also the SBPA API trigger for the events that SAP states in the documentation is working from the postman but we only face problems in the Integration Suite, Event Mesh

Thank you very much in advance

[Rwitte]

We are also running into this issue. Was somebody already able to resolve this issue? We are stuck with this at the moment as there is no indication what happens to the event in BPA and why it is not processed correctly.

[Rwitte]

Maybe @ajmaradiaga can help here?

[Mell]

Hello Rwitte,

We were able to resolve this issue. In our case Integration Suite Event Mesh was not sending, WebHook-Request-Origin mandatory header. We opened a ticket in SAP and they fixed the issue. 

After the issue is fixed the set up is working correctly if the webhook is configured as mentioned here: Create an Event to Start a Process | SAP Help Portal

[MioYasutake · Accepted solution]

As @Mell mentioned, the issue was resolved by the SAP side, by adding the WebHook-Request-Origin header to the requests for the webhook. To ensure failed messages are not lost, you can set the Quality of Service to 1 when creating a webhook subscription. With this setting, failed messages remain in the queue.

https://help.sap.com/docs/integration-suite/sap-integration-suite/create-webhook-subscription

If you want to try sending events to BPA from Postman, please set the following header parameters:

Content-Type: application/cloudevents+json

WebHook-Request-Origin: <The host part of messaging.uri in the event mesh's service key>  e.g., <subdomain>-<subaccountid>.eu10.a.eventmesh.integration.cloud.sap