Major new improvements to the SAP EM Overdue Monitor have been released by SAP

[kevin_wilson2]

SAP has released 2 new OSS notes October of last year that will bring certain relief to those SAP EM implementations that are running with large volumes and high numbers of expected events. I bring it up here again because I still see implementations where folks are not leveraging these new improvements!

For those of us that breathe SAP Event Management we have seen numerous implementations where the /SAPTRX/EE_MONITOR job steps on itself or simply runs forever… Help has arrived …

OPTION 1: Process all overdue events in one run

Report /SAPTRX/EE_MONITOR_ADVANCED has been released in OSS note 1915817 to replace the original /SAPTRX/EE_MONITOR. This report loops through all expected events that have not been reported and where the date occurs in the past. This is where the performance improvement is achieved. The selection screen (shown below) has an option to select the date based on the Expected Event Date or the Expected Message Date. The original report used the first option and selected on both the dates. By understanding which value your implementation is using (Message or Event) you can select the appropriate option to run the report.

If you select the Expected Event Date option then the EVT index is used on the select on /SAPTRX/EH_EXPEV (via view /SAPTRX/V_EXPE_A). For the Message Expected Date option the MSG index is used instead.

OPTION 2: Process “packs” of overdue events in several runs

Report /SAPTRX/EE_MONITOR_PACK has been modified in OSS note 1919850. This report allows you to process overdue events in packets. This allows you to reduce the backlog of overdue events by ensuring that the program runs to completion instead of clocking forever because there are too many overdue events to process…

The selection screen (shown below) has been extended to include the same options as mentioned above and also behaves in the same way when selecting data based on the specified indexes.

In summary, if you are using expected events in your implementation and are running the overdue monitor, you should go ahead and implement these 2 notes and then schedule the overdue monitor accordingly.