New type of activities introduced in SAP EM 9.2: Post Processing Activities
With EM 9.2 SP06 the new activity type “Post Processing Activity” gets introduced, which can be used to execute certain actions only once instead of multiple times when processing event messages.
One post processing activity can be assigned to each rule set and it will be executed exactly once after rule set processing is done. This allows to trigger follow-up actions in a mass enabled way instead of triggering the single action possibly multiple times during rule set processing. To make this work rule set activities which are executed during the rule set processing have to collect all data that is necessary for the post processing activity instead of triggering the actions itself. How this can be done in detail, you can check in this document: Post Processing Activity to boost performance of EM – TM integration
One new activity is already available in the standard (as well with SP06) to boost the performance of the EM – TM integration for scenarios in which event message processing is done in a mass-enabled way. The document mentioned above explains the details regarding this new activity TM_UPDATE_EXEC.
New customizing:
Post Processing Activities can be created via IMG activity “Define Activities for SAP Event Management”:
Alternatively a new activity can as well be created via IMG activity “Define Rule Sets”. Here the Post Processing Activity can also be assigned to one or more rule sets:
The SP06 of SAP EM 9.2 is planned to be released on 19th of July 2016. For those who can’t wait until then, the following notes can be implemented alternatively – but this will include quite some manual steps:
2300737 : Value ‘Post Processing Activity’ is missing in domain /SAPTRX/FUNC_TYPE
2254731 : Post processing activity after rule set processing
Enjoy the new feature and let us know, how you will leverage it!
Cheers, Daniel
Hello Daniel,
the post-processing activity template mentions this:
Can you shortly outline the reason behind this? Creating a new EH would not trigger the rule set and hence not the post-processing activity, so recursions should not happen. With /SAPTRX/BAPI_EH_ADD_EVENTMSG_02 I assume the cause is similar to the ADD_EVENT_MESSAGE warning.
Would the underlying concerns be void if we call those BAPIs indirectly via a separate queue since we would then be talking about a new LUW?
Best regards,
Philip
Hello Philip,
EH Post can also have a ruleset (EH Update Activities).
If you call it as a QRFC there should be no problem.
Best regards,
Steffen