Which kind of EBO alarm information can be extracted through SmartConnector?

[Theo]

We have a partner which has on a project the requirement to send selectively alarms to SAP.

The goal of this is to create purchase requisitions in SAP and then create PO to external contractor.

Process should is as follows:

1. Alarm pops up in EBO
2. Someone checks it, decides can't be fixed internally or with personnel available.
3. Send alarm and associated object information to SAP for automated purchase requisition creation.

Now my question is, can SmartConnector react to the "Assign" action from the alarm list and then trigger this send to SAP action?

[JeffBowman]

Hi Theo,

The typical way that Smart Connector interacts with Alarms in EBO is via EWS, and unfortunately, there is no concept of 'assigned' in EWS, so this information is never conveyed back to Smart Connector.

So without dissecting EBO's native protocols, i don't know if there will be an easy way to do this.

Best Regards,

-Jeff

[KarimHussain]

Hello, 

I'm thinking maybe you can do this without SmartConnector.

Set up an alarm triggered notification with SNMP or mail as distribution. Filter it as you would like, maybe only alarms that are acknowledged. Develop a software that recieves the alarm and parses the message body and then does what ever else operations as needed in SAP.

You can provide the prevous alarm state and current state to make sure that the program can make sure to only work on events that transition from alarm to acknowledged. Then you can also add the comment attribute to the report template to provide any metadata. Also a dummy group / account and provide that data too in the template so the software can make sure to only work on events assigned to a specific object.

I think that is how I would do it.

If you have External Log Storage option with PostgreSQL installed you could write a client to subscribe to changes in the event table as datasource instead.

So this would be an example scenario:

Alarm triggers > User adds comments > User assigns to user group SAPdummy > User acknowledge alarm > Alarm event gets distributed using a specific notification report template > Program picks up message > Program makes sure it is transitioned from alarm to acknowledged and assigned to SAPdummy > Program does stuff in SAP like creating a workd order