Event message from driver to EM system

[former_member636423]

Hi,

We have a requirement whereby the drivers while delivering product to customer will update the delivery in a handheld device .The handheld device has a software loaded into it which transmits XML message to SAP EM system so that events like loading, unloading, POD information can be send vide interface .

Can the experts suggest how this integration with handheld device can be integrated with SAP EM.Also based on drivers movement the GPS map will track the driver movement which is there in the device and accordingly the delivery location details should be updated in the EM and TM.

[rafael_cano_perez]

Hi Indraneel

Yo have all the information you need for the mapping in this SAP document:

"Event Message Input in SAP EM 4.0: BAPI EventHandler. AddEventMessages02 and IDoc EVMSTA02"

I am not sure where to get a valid url to download it, but it shouldn't be too difficult to look for it in the SAP support site or elsewhere.

Regards.

[former_member636423]

Hi,

Thanks for the detailed feedback.

Since we are planning to use XML from the external device and call EM BAPI hence is there any link by which we can do a field mapping between the message and fields send by the external system to SAP EM. I want to send the info to PI guy so that he can do a field mapping with the various fields available in SAP EM

[rafael_cano_perez]

Hi Indraneel

There are too many options for the XML generated in the handheld device to reach an SAP EM system, that is hard to depict them all.

Normally SAP EM is not exposed directly in Internet, so some external server could receive this XML, via SOAP webService, REST POST, converted to OData ...

This gateway service ( SAP Cloud, own virtual host, SAP Gateway, ... ) should then either pass it to EM for custom XML reading or convert it first to an EM event reporting IDoc or direct EM BAPI call.

If EM receives directly the XML, then custom code has to identify to which event handler the message is sent to and the message payload. If it is already converted to an EM format ( IDoc or BAPI call ) then only target event handler identification, and valid event code, and possibly event reason code and parameters, is needed.

And this is the most important thing; regardless of the communication route from device to EM, the XML message has to have a valid tracking id type and code, as well as valid event code, reason code, etc.

If geo coordinates are also available in the original message, they can be used to locate the event in a map, and possibly update a TM resource location. There is plenty SAP documentation on this topic.

Hope this high level view helps.

Regards, Rafael

[former_member636423]

Hi,

A quick question-Assuming that message is send from the device as XML, then in that case is my assumption correct:

The XML send as a WSDL will be converted by PI into XML message and then thru RFC updater in the PI , the EM BAPI will be called and then the triggering of event handler and posting of EVM will occur.

If yes only thing we need to compare is the message/payload content send by the device is comparable with the PI service. If not then a custom proxy has to be created. Is my understanding correct.

[rafael_cano_perez]

Yes, somehow.

The WSDL should be provided by PI ( web fronted of PI ) to allow the reception of XML via a SOAP web service. It should be a custom web service build to match the XML of the device.

Then PI would map the web service payload ( the XML from the device ) into internal table parameters of the EM BAPI and do the actual call ( RFC ) to EM.

Regards, Rafael