messaging within EM

[Former Member]

Hi,

Currently we have a scenario where based on events reporting like departure/arrival, messages goes out to customers about shipment information an d this is triggered  if BRF plus conditions are satisfied.

Now basically for the consultants we usually go to bobf and check if message is triggered successfully or check with PI in certain cases.

However for end user its important that they have info if message is triggered successfully since database access will not be given to them.

Is there any suggestion as how we can have this build or any tool you suggest  which we can build

[sukumar_perumalsamy]

Hi Indraneel,

1) You can use Dynpro enhancement in EM WebUI to look for  invalid event message reported in EM,  after selecting the invalid events provide the  options to change the values of event message and re-process it from WebUI.

2) In AIF custom business validation,  tracking id mapping , edit and re-process the event message is possible.

Going forward use ES for event message posting to EM and don't use the Idoc or RFC calls from PI for event posting.

thanks and regards

Sukumar

[former_member193027]

from technical architecture perspective do we require to install any additional component within EM system to have the AIF functionality going.

What is the transaction code to launch the AIF transaction.

[sukumar_perumalsamy]

you need to have below AIF Add on component in EM 9

AIF	701	0003	SAPK-70103INAIF
AIFX	701	0002	SAPK-70102INAIFX

[kevin_wilson2]

Sukamar,

You can't just say to avoid RFC and IDoc in favor of ES like that. If you are a PI guy then I can understand your preference but in the end the enterprise service calls the BAPI just as the IDoc does so the mechanism to post an event comes down to what skills are available in the company implementing EM (If they are limited in PI skills then map to IDoc), if the system sending the messages is an SAP system then use RFC, if the company uses IDocs as there method to pass data around then use IDocs... And there are many more considerations, especially around IDocs (Persistance of the data is much long that ES, error handling is much more robust, integration with workflow, can search via data elements whereas you cant in ES, ...)

Hope this helps.

Kevin

[sukumar_perumalsamy]

Kevin,

I believe most of the IDOC FM's are using RFC/BAPI to post the inbound message to SAP.

Successfully posted ES messages are auto archived by system , where as idoc you have to manually execute the archiving process.

ES suits well for the organisation receiving millions of events per hour/per day.

I agree with you idoc and RFC suitable only  if the sender is SAP and they use ALE instead EDI or integration tool.

Cheers,

Sukumar

[kevin_wilson2]

Indraneel,

Typically a user does not check the integrity of the technical solution. This is normal across SAP and also in business processes. You have to trust the system to take care of business and the support folks should ensure that no errors are found, the queues are unblocked, the EH isn't locked etc...

If a user want to check if a message was sent to a customer they should simply go to the EM Web UI and check that the event was posted (E.g. event "Sent Arrival Notice") If it's not there then they should assume it wasn't created.

Thanks

Kevin

[former_member193027]

Thx for the response but users also want to know if message has been send correction from SAP system and not just events reporting.Can we use AIF to have this functionality feasible.

[kevin_wilson2]

I still maintain that the user process should not include checking that the system is working... If the user wants to see that a message was sent to a customer then implement the send using an event. If they see the event "Customer Notified" then they know it has gone. The guaranteed method of delivery between SAP EM and the customer will ensure they get the message. If they want to see the content then use some ABAP to store the content against a business object and fire up the default method to view the content using the standard EM link feature.